PDF Ops Pack

Reference foundry-pack/v0 contents for the approved Hermes PDF workflow.

What this pack is

• wraps the existing Hermes document-search / PDF pipeline path
• keeps everything local-only
• emits pack-shaped evidence without rebuilding Hermes
• stays honest: routes remain declared-not-proven until Foundry owns eval/run promotion

What it is not

• not a new harness
• not a cloud path
• not production-ready autonomous workflow completion
• not allowed to send outbound messages by default

Directory layout

• pack.yaml — Foundry pack manifest
• skills/ — wrapper notes/config fragments for the approved Hermes/PDF skills
• evals/ — pack-level eval definitions mapped to the approved proof points
• demo-data/ — safe fixtures/assertions/pointers for reproducible demo runs
• scripts/ — wrapper install/check/demo/support-bundle commands
• evidence/ — evidence templates + approved-evidence mapping

Install notes

1. Keep the sibling Hermes adapter checkout at ../../adapters/hermes.
2. Keep Foundry CLI available on PATH.
3. Run install/check in a fresh FOUNDRY_HOME when verifying reproducibility.
4. Treat this pack as demo-only even though a native foundry pack run path now exists; routes still stay declared-not-proven until the separate eval/promotion ledger is wired.

Canonical commands

foundry pack install /Users/lilly/clawd/projects/foundry-commercialisation/packs/pdf-ops-pack --json
foundry pack check pdf-ops-pack --json
foundry pack support-bundle pdf-ops-pack --json
./scripts/run-demo.sh ~/Documents/Shared/projects/build-pdf-ops-reference-pack-contents/runtime-demo

Permission posture

• outbound.send: explicitly requested so status shows it, but remains denied by default
• data.customer_process: intentionally non-required here so the reference pack can install as demo-only before live-corpus approval exists
• services.control: optional/non-required until Tes wires service lifecycle into the pack runtime spine

Truthful limitations preserved

• routes are expected to stay non-green right now
• signed-PDF proof still relies on explicit artifact evidence
• fresh 2026-05-02 signed-PDF reruns show the demo cert as expired, so QA must treat that as a live blocker until the fixture/cert is refreshed
• the wrapper demo runner is not equivalent to a Foundry-owned pack run ledger

Evidence target

The working evidence bundle for this task is written under:

~/Documents/Shared/projects/build-pdf-ops-reference-pack-contents/