Current Pack Audit

Audit basis

This redesign was grounded against the original Fossil-focused pack, not against prior summaries. The key source inputs were:

• rfc-workflow-setup/00-controller.md
• rfc-workflow-setup/01-source-authority.md
• rfc-workflow-setup/02-deliverables.md
• rfc-workflow-setup/04-validation-gates.md
• rfc-workflow-setup/05-context-engineering.md
• rfc-workflow-setup/runbooks/04-review-and-correct.md
• rfc-workflow-setup/runbooks/06-package-for-review.md
• prompt/PROMPT-FOSSIL-RFC.md at the ranges called out for suite charter, corpus rules, metadata, per-document briefs, references, and anomaly seeds
• prompt/RFC-KRAMDOWN-HOWTO.md for reusable render mechanics versus host-specific install steps
• the old harness adapter surfaces under rfc-workflow-setup/workflows/, rfc-workflow-setup/codex/, rfc-workflow-setup/claude-plugin/, and rfc-workflow-setup/omp/

What changed

The old pack mixed three concerns in one tree:

1. reusable workflow control logic
2. Fossil-specific source and document content
3. harness-specific entrypoints and runner assets

The redesign makes those seams explicit. Reusable mechanics now live in the neutral repo root (workflow.contract.yaml, core/, briefs/, toolchains/, templates/). Fossil-specific authoring material moves under projects/fossil/. Harness adapters are removed from source control in favor of a contract plus translator prompt.

Neutralized into reusable workflow assets

Old source basis	New reusable home	Why it was neutralized
00-controller.md stage checklist and stop conditions; 04-validation-gates.md gate model; runbooks 04-review-and-correct.md and 06-package-for-review.md	workflow.contract.yaml, core/controller.md, core/validation-gates.md	The sequencing, backpressure, correction loop, and packaging gates describe workflow mechanics, not Fossil behavior.
01-source-authority.md authority hierarchy and claim classes	core/source-authority.md, templates/CLAIM-LEDGER.md	Claim admission, evidence ranking, and conflict handling are reusable across any RFC corpus.
02-deliverables.md public/evidence split plus packet checklist	core/deliverables.md, templates/FINAL-PACKET-MANIFEST.md, templates/VALIDATION-REPORT.md	Public-versus-evidence separation is a workflow invariant and should not be buried inside a project pack.
05-context-engineering.md wiki/graph/run-artifact model	core/context-engineering.md, generic reviewer and author briefs under briefs/	The retrieval-and-proof pattern is source-agnostic even though the old file names a Fossil wiki layer.
Existing evidence templates in rfc-workflow-setup/templates/ plus the review/package runbooks	templates/CLAIM-LEDGER.md, templates/CAPABILITY-MATRIX.md, templates/EXAMPLES-LEDGER.md, templates/ESCALATION.md, templates/VALIDATION-REPORT.md, templates/FINAL-PACKET-MANIFEST.md	These artifacts are workflow proof tools, not Fossil-specific outputs.
RFC-KRAMDOWN-HOWTO.md sections on Markdown structure, XML/text build flow, reference caching, and warning interpretation	toolchains/kramdown-rfc-mechanics.md	The render pipeline is reusable, but only at the mechanics level. It belongs in toolchain guidance, not in a Fossil pack.

Moved into projects/fossil/

Fossil source basis	New Fossil pack home	Why it stays project-specific
PROMPT-FOSSIL-RFC.md:1-56	projects/fossil/suite-brief.md	The governing purpose and three-document scope are specific to Fossil artifact, delta, and sync drafts.
PROMPT-FOSSIL-RFC.md:58-200	projects/fossil/corpus-brief.md	The authority split between src/, observed repository bytes, and informative wiki docs is tied to the Fossil source tree and repository corpus.
PROMPT-FOSSIL-RFC.md:217-225,232-249,329-352	projects/fossil/draft-metadata.md	Document titles, intended status, abstract constraints, and reference set are specific to the Fossil draft family.
PROMPT-FOSSIL-RFC.md:230-530	projects/fossil/briefs/artifact.md, projects/fossil/briefs/delta.md, projects/fossil/briefs/sync.md	Card vocabularies, section requirements, protocol loops, and artifact rules are implementation-specific authoring inputs.
PROMPT-FOSSIL-RFC.md:221-229,256-289,358-517	projects/fossil/references.md	Fossil terminology, normative references, informative references, and protocol vocabulary belong with the Fossil pack.
PROMPT-FOSSIL-RFC.md:531-567	projects/fossil/examples/anomaly-seeds.md	The anomaly audit seeds describe Fossil parser edge cases and repository artifacts, not reusable workflow behavior.

What was removed from the reusable repo

Removed class	Grounding in the old pack	Why it was removed	Replacement
Harness-specific adapters and runner assets	rfc-workflow-setup/workflows/README.md, rfc-workflow-setup/codex/AGENTS.fragment.md, rfc-workflow-setup/codex/start-prompt.md, rfc-workflow-setup/claude-plugin/plugin.json, rfc-workflow-setup/omp/	The old pack already treated these as thin per-runner wrappers around the same staged workflow. Keeping them in the reusable repo would make one harness look canonical and would force parallel maintenance of multiple entry surfaces.	AGENTS.md plus prompts/translate-workflow-for-harness.md, generated at runtime from workflow.contract.yaml and the selected project pack.
Checked-in run outputs and reviewer residue	rfc-workflow-setup/runs/, including frozen drafts, reviewer notes, validation summaries, and .refcache/ under runs	Run artifacts prove one execution, but they are not reusable workflow assets. Keeping them in the reusable repo obscures the clean split between setup material and per-run evidence.	Future runs create their own work area outside the reusable setup files.
Environment-specific install commands	RFC-KRAMDOWN-HOWTO.md:18-37 (apt-get, gem install, pip install, Ubuntu notes)	These instructions are host-specific operational details, not stable workflow mechanics. They would age quickly and falsely imply a blessed execution environment.	Keep only toolchain mechanics in toolchains/; derive environment setup per runner or local platform.
Persistent reference caches as source assets	RFC-KRAMDOWN-HOWTO.md:138-160 describes KRAMDOWN_REFCACHE as a local build cache	Caches are execution byproducts. Checking them into the reusable repo would mix machine-local state with durable workflow inputs.	Recreate caches per environment when needed.

Why the harness-specific files are gone

The old pack showed that the workflow itself was already independent of the runner:

• the Codex fragment and start prompt both told the runner to read the same controller and runbooks
• the workflows README explicitly described the OMP JSON as a descriptor and the Claude workflow JS as another encoding of the same staged gates
• the Claude plugin manifest was only a local command adapter, not unique workflow logic

That is the signal to remove harness assets from the reusable repo. The reusable repository should define the workflow once, in neutral assets, and let the active harness translate that contract into native commands at runtime.

Maintainer guidance

When adding a new project pack:

1. keep reusable mechanics in core/, briefs/, toolchains/, and templates/
2. put source corpus rules, document scope, references, metadata, and anomaly seeds under projects/<name>/
3. do not reintroduce runner-specific directories like omp/, codex/, claude-plugin/, or checked-in workflow scripts
4. treat run outputs, caches, and reviewer packets as execution artifacts, not reusable repo content

That split keeps the repo legible: one workflow, many project packs, zero canonical harness.