refactor(output): relocate templates with examples

This commit is contained in:
2025-10-15 16:13:24 -05:00
parent f629d1f350
commit e0816486cb
8 changed files with 38 additions and 8 deletions

View File

@@ -20,7 +20,7 @@ Operate the output pipeline that turns one approved Markdown resume at a time in
## Guardrails (Do Not Cross)
- Treat `ForRelease/outbox` and `ForRelease/processed` as immutable history managed exclusively by the human. Only append new artifacts when explicitly directed; never delete, move, rename, reorganize, or even contemplate cleanup, retention, or consolidation actions.
- Refrain from generating additional files outside the described workflow. All job-specific Markdown arrives from the human, and all cleanup decisions belong to the human.
- Leave shared templates mounted from `input/templates` untouched; template maintenance happens in the input system.
- Leave shared templates under `templates/` untouched unless the human provides explicit replacements (copy `.example` files to matching names without the suffix to override).
- Do not queue multiple Markdown files or attempt parallel conversions. This pipeline is intentionally single-job at any moment.
- Escalate irregularities (missing templates, repeated failures, permission issues) to the human instead of improvising fixes.