Artifact conformance: one shared pass, bound in every workflow that writes artifacts

[m2ux]

Summary

The pass that measures a planning folder's artifacts against their guides existed as three near-identical copies, under work-package, workflow-design and workflow-authoring, and ran in those three workflows only. Thirteen workflows wrote artifacts with no conformance check at all, so whatever the writing register and the line budgets say, nothing detected drift. This work gives the pass one home under meta, parameterises the two maps it reads, and binds it in every workflow that has artifacts to check.

What changes

One home, no workflow's maps inside it. meta/techniques/verify-artifact-conforms.md takes the caller's canonical-home map and its planning-artifact-to-guide map as inputs, so the shared operation carries no workflow's policy of its own. artifact_dir defaults to the session planning folder, and a caller whose artifacts land elsewhere — prism and its report directory, codebase-wiki and its wiki path — binds that instead. The pass now checks the artifact writing register alongside the guide rules and the canonical-home map, and reports a filename that resolves to no guide as a finding against the folder.

Eleven more bind sites. prism, prism-audit, prism-evaluate, requirements-refinement, codebase-wiki, cicd-pipeline-security-audit, substrate-node-security-audit, midnight-system-review, work-packages and remediate-vuln each bind the pass at the boundary after their artifacts are written and before the gate or delivery that reads them. The three original callers retarget to the shared op and bind their own maps.

Two workflows do not bind it, for stated reasons

ponytail declares four artifacts and no directory to write them to — no planning folder variable, no output path, and no write step. A conformance step there would point at an unbound path, so the gap is recorded here rather than papered over with a binding that cannot run.

meta persists only the planning README, which verify-readme-conforms already checks against the universal template.

Scope of change

One new shared technique, three deleted copies, eleven activity bind sites, three contract citations retargeted, and the README and technique-index entries that named the deleted files.

Acceptance

• The conformance pass lives in one shared home and carries no workflow's canonical-home map or guide map.
• Every workflow that persists artifacts into a directory binds it — thirteen in total, up from three.
• The pass checks the writing register, the guide each filename maps to, and the caller's canonical-home map.
• All 22 guards pass. The shared operation's return contract is classified in the binding-fidelity triage under the existing shared-op-return-contract rationale, the same way every other meta library op is.

Landing order

The paired server PR carries the binding-fidelity triage entry and the two new guards, so it lands first; this branch is red against the current main guard set without it.

Non-goals

• Authoring the guides the pass will look for. Those land in the creation-guides item.
• Giving ponytail an artifact directory. That is its own change, and naming it here is the point.

Part of #403 (W5, corpus half). Stacked on #423.

[m2ux]

An audit pass against the workflow canon found and fixed a delivery break plus twelve findings, pushed as follow-up commits on this branch and its base.

The break. Four corpus files the new creation-guide guard depends on — the cicd resources README and the prism, prism-evaluate and work-package guide maps — were authored while developing the guard and never committed. The guards were passing against a working tree rather than against what was pushed. Merged as-is, check-artifact-guides would have failed on the merged corpus. They are now committed on the creation-guides branch.

High findings

• Seven prism map rows attributed an artifact's shape to a lens its producing pass does not dispatch: the reflect meta pass runs claim, not l12g; the verified initial and corrected passes both run l12, not knowledge-audit and oracle; the first adaptive stage runs deep-scan, not sdl-abstraction; and subsystem regions run whichever prism the assignment gives them. Each row now names the lens the pass actually dispatches, one row per artifact so a wrong lens is visible against the step that writes it. The two synthesis artifacts whose steps dispatch no lens are triaged as owing a guide rather than pointed at one that does not shape them.
• The guard resolved a guide from any resource whose body mentioned the filename, so 14 of 139 artifacts passed on a false match — a guide's own traces-to line certified evidence-log.md, and the close-out guide certified assumptions-log.md and token-usage.md. Resolution now reads only the span where a resource declares what it is the guide for. The honest count is 21 artifacts owing a guide, up from 16, and the corpus side answered the difference by naming the seven work-package guides that already existed.

Also fixed

• Three callers authored a guide map and did not pass it; all eleven maps are now bound.
• The shared operation's violations list enumerated one workflow's rule slugs while the rule beside it said the operation carries no workflow's policy.
• artifact_dir's default read a designator no contract declared; the meta root contract now declares planning_folder_path.
• The rule that replaced the deleted design-session copy said only what the Inputs said, and now carries the prohibition that copy existed for.
• A Protocol note restated a contract fact and hung off the wrong bullet.
• The wiki index and log and the midnight findings register gained budgets a conformance pass can measure.

Recorded, not fixed: the line-budget class stays inert wherever a guide declares no budget; ponytail still has no artifact directory to bind the pass against; and the walk-snapshot corpus stamp re-baselines after merge.

Guards: 22/22. Suite green apart from that stamp.

[m2ux]

Scope grew after review — every persisted artifact now has a guide.

This PR originally covered the ten artifacts whose shape was prescribed nowhere at all, leaving a further set whose shape sat inline in protocol prose to a classified triage. That triage is now closed: guides were authored for all of them, and scripts/artifact-guide-baseline.json is deleted.

Seventeen distinct artifacts gained a guide in total. Beyond the original ten:

Workflow	Artifacts
prism-audit	AUDIT-REPORT.md, DETAILED-FINDINGS.md, DESIGN-TRADE-OFFS.md
prism	RUN-MANIFEST.md, portfolio-synthesis.md, reflect-synthesis.md
midnight-system-review	change-surface.md, investigation-plan.md, evidence-log.md
ponytail	lean-brief.md, lean-change.md, audit-findings.md, debt-ledger.md
work-package	token-usage.md, provenance-log.md, the ADR record; change-block-index.md mapped to the guide that already owned its shape

The published reports needed no new design work — their consumer contracts were already written into the producing techniques' Rules, so the guides are a lift plus a cite. Where the shape genuinely belongs to something else, the map says so rather than inventing a guide: a per-lens prism artifact takes its shape from the lens the unit runs, and the map names the lens each pass actually dispatches.

Two further changes ride along:

• Line budgets everywhere. The conformance pass checks a budget only where a guide declares one, so the check was inert across most of the corpus. All 104 guides a map row cites now carry one, derived from the guide's own template — whole-file where the shape is fixed, per item where the artifact grows with its subject.
• ponytail gained an artifact directory. It declared four artifacts with nowhere to write them; it now declares artifact_dir and binds the conformance pass like every other workflow.