Proposal archive

Adopted and retired design proposals, kept out of the frontier.

Nothing here describes a live design question. Everything still current was extracted before the move; what remains is the irreproducible remainder — dated current-state anchors and the corpus measurements a design rested on.

What this is for

Three jobs, all deliberate: re-extraction (something current was left behind and must be promoted into the frontier), decision audit (reconstructing how a choice was reached in more detail than its ADR compresses), and re-opening (a foreclosed design becomes live again — which means writing a new proposal in the frontier, not editing one here).

Archived files are frozen. Correct them only for link integrity when something they point at moves.

This README is the door: nothing else outside the archive links to files in it, so reaching one means coming through the Contents list below. If a job here turns up something still current, promote it into the frontier rather than linking to it.

What must hold of an archived proposal, and why: ../README.md. How a proposal gets here: retire an artifact. Decision record: ADR 056.

Contents

  • External articles collection — adopted by ADR 057, 2026-07-26. Editorial/expository profile, ProperDocs publication channel, excluded draft subtree, dated-body lifecycle, and searchable source lineage; the first-article test configuration is the texture behind the shipped procedure.
  • Harness-orchestrated review sweeps — adopted by ADR 035, 2026-07-01. Parent-owned, harness-neutral orchestration over deterministic job endpoints; the earlier Claude-only experiment and the instruction-versus-vendor-script choice are the texture behind the shipped procedure.
  • Source genre is one open-vocabulary field on the snapshot — adopted by ADR 045, 2026-07-12. Genre unification across snapshots and ingest-reports; the open-vocabulary mechanism choice (a vocabulary file versus per-constraint severity) and the per-genre lens-home question are the texture behind that decision.
  • Assertion force separate from lifecycle status — retired by ADR 044, 2026-07-11. The proposal to split the fused status field into a structural lifecycle enum plus contract-declared assertion force, including its later axis-decomposition self-critique; ADR 044 deleted the field instead.

Complete file listing (generated at build time)