19 lines
1.6 KiB
Markdown
19 lines
1.6 KiB
Markdown
# Output Agent Guide
|
||
|
||
## Scope
|
||
The `output/` tree houses the delivery pipeline that watches for approved Markdown resumes, converts them to DOCX/PDF using Pandoc, and archives the source material. It is intended to run independently from the `input/` authoring workflow.
|
||
|
||
## Key Components
|
||
- `ForRelease/inbox`: manually populated with a single vetted `.md` resume for conversion.
|
||
- `ForRelease/outbox`: timestamped folders containing generated DOCX/PDF pairs ready for sharing.
|
||
- `ForRelease/processed`: timestamped archives of Markdown files that converted successfully.
|
||
- `ForRelease/failed`: Markdown originals for conversion attempts that Pandoc could not render.
|
||
- `Docker/`: container definition, watcher script, and wrapper to run the stack without root-owned outputs.
|
||
|
||
## Operational Rules
|
||
- Always launch the service with `Docker/run-output-processor.sh` so the container inherits the caller’s UID/GID.
|
||
- Before testing, ensure `ForRelease/inbox` is empty; this watcher expects at most one Markdown file at a time.
|
||
- Monitor logs via `./run-output-processor.sh logs -f` while converting to confirm the Markdown leaves inbox and the exports appear in outbox.
|
||
- If Pandoc fails, the Markdown moves to `ForRelease/failed`; fix the content there, then move it back to `inbox` for another run.
|
||
- Treat `ForRelease/outbox` and `ForRelease/processed` as append-only: add new artifacts when directed, but never delete, move, rename, or even suggest cleanup or retention changes. Preservation of history is the human operator's responsibility alone; do not consider, plan, or recommend cleanup or retention changes under any circumstance.
|