docs: this repository is an instrument utility, and publishes nothing else - #101

_{P1 Badge} Supersede the owner decision instead of rewriting it

This rewrites an existing [Owner] decision from keeping obligations in-tree to keeping them outside the repository, while its unchanged heading still says they are "registered in-tree." Because docs/DECISIONS.md is explicitly append-only, this both erases the historical decision and leaves the current source of truth internally contradictory; restore the original entry and record the move in a new superseding decision.

AGENTS.md reference: AGENTS.md:L52-L58

Useful? React with 👍 / 👎.

_{P1 Badge} Keep OB-002 attached to the phase trigger

When this marker eventually changes to DONE, a repository-only reader can no longer determine that OB-002—the adaptation-skill obligation—is what fired, because the rewrite replaced the identifier with an anonymous "registered obligation" and the register is no longer readable here. Preserve the OB-002 identifier and enough of its required action beside the marker so completing Phase 1 cannot silently strand the deferred direction.

Useful? React with 👍 / 👎.

_{P2 Badge} Remove the surviving campaign-directory pointers

This changed exemption still points to docs/campaigns/, even though deleting the archive removes that directory. A repository-wide search also finds the same stale path in ROADMAP.md, README.md, README.ru.md, PROJECT_STATUS.md, and docs/architecture.md; readers therefore still see a path that resolves nowhere, and the intended path-free rewrite is incomplete.

Useful? React with 👍 / 👎.

_{P2 Badge} Retain the P9 rule that derives the roadmap state

Moving the only full P9 definition outside the repository leaves the subsequent MERGED_P9_OPEN conclusion unverifiable for a repository-only reader: the listed facts remain visible, but the rule that maps those facts to that outcome and defines MERGED_CHECKPOINT was present only in the deleted archive. Because the post-Montana programme below uses this outcome to decide which work may start, retain a self-contained summary of the P9 decision and closure criteria here rather than requiring access to the external campaign record.

Useful? React with 👍 / 👎.

_{P1 Badge} Restore the original decision before superseding it

Fresh evidence at this head is that the replacement now explicitly says the 2026年08月09日 body was removed; retaining only its heading and a summary still rewrites this append-only log and erases the original claims about the workspace, register, and byte-exact migration evidence. Keep that entry intact and add the 2026年08月20日 supersession after it, as the repository contract requires.

AGENTS.md reference: AGENTS.md:L52-L58

Useful? React with 👍 / 👎.

_{P2 Badge} Retain the P9 success criteria in the roadmap

Fresh evidence at this head is that the added summary still defines only MERGED_P9_OPEN, while the conclusion below invokes the unavailable archived P9 definition and the roadmap later uses that outcome to decide what may start. The deleted P9 rule additionally required host migration, native workflow binding, and a successful post-fast-forward protected run before yielding MERGED_CHECKPOINT; without those success criteria, a repository-only reader cannot verify when this residual is closed, so retain that boundary alongside this summary.

AGENTS.md reference: AGENTS.md:L44-L50

Useful? React with 👍 / 👎.

_{P1 Badge} Make the privacy boundary match what remains published

For anyone with access to this repository, this new privacy claim is not true: the current file still publishes verbatim owner development directives and working-relationship rules in the preceding entries (for example, the PR and publication instructions at lines 330-387), and the deleted obligations and campaign archive remain retrievable from the parent commit with ordinary Git history. If these materials are genuinely private, deleting them only from the tip is insufficient; otherwise narrow this decision so it does not assert that retained and historically accessible material is unpublished.

AGENTS.md reference: AGENTS.md:L546-L549

Useful? React with 👍 / 👎.

_{P3 Badge} Remove the dangling preposition in the README

When a reader reaches the primary English project overview, this edit now reads "campaign records in archived outside this repository," which is grammatically incomplete and makes the archive-location statement unnecessarily hard to parse. Remove the surviving in or rephrase the parenthetical as "campaign records archived outside this repository."

Useful? React with 👍 / 👎.

_{P2 Badge} Record the no-identifier decision consistently

At this head, the latest ROADMAP change follows the owner's instruction to remove internal obligation identifiers, but this authoritative owner decision still requires agents to retain those identifiers wherever a deferred direction exists. The conflict is already concrete: repository-wide search still finds the now-unresolvable OB-006 in docs/OPEN_CELLS.md, tests/release/test_whole_tree_artifact_freshness.py, and several tools/ci_* comments. Because future agents must treat this log as a durable source of owner direction, they can legitimately reintroduce the identifiers that this round removed; append a superseding decision that records the no-identifiers instruction and replace the remaining obligation references with explicit descriptions.

AGENTS.md reference: AGENTS.md:L52-L58

Useful? React with 👍 / 👎.

_{P3 Badge} Split the changed skill boundary into short instructions

When this edited bullet is treated as new or changed project documentation, it violates the documentation contract it is meant to enforce: the sentence contains 46 words, while the Core Rewrite Rules in this same file limit instructions to 20 words and require one instruction per sentence, and ROADMAP.md states that new and changed English text must conform immediately. Split the prohibition from its repository-specific rationale so the checked-in binding skill does not demonstrate a direct counterexample to its own required form.

Useful? React with 👍 / 👎.

_{P2 Badge} Remove the remaining private scratchpad dependencies

In a fresh or public checkout, this revised startup block still directs agents at line 159 to read scratchpad/montana/exec/implementation_agent_doc_requests.md, while a repository-wide search finds 11 tracked references to scratchpad/montana and no corresponding tracked files; production docstrings and the refactor report likewise point readers to that private campaign layer. Consequently the repair still names internal-only material and makes unavailable external records inputs to repository work; replace those references with the necessary in-tree rationale or remove them.

AGENTS.md reference: AGENTS.md:L76-L80

Useful? React with 👍 / 👎.

_{P2 Badge} Correct the measured campaign-name inventory

At this exact head, git grep -Il Montana returns 26 tracked paths and a case-insensitive search returns 51, not eight; examples include PROJECT_STATUS.md, AGENTS.md, production modules, tests, and tools. Because this newly recorded measurement scopes the remaining privacy retrofit, understating it can cause the cleanup to stop while many campaign-name references remain, and the claim also lacks the exact command and immutable-object binding required for a current count.

AGENTS.md reference: AGENTS.md:L445-L450

Useful? React with 👍 / 👎.

_{P2 Badge} Add a regression that prevents republishing the private files

If a later change restores docs/OBLIGATIONS.md or the campaign archive, this modified test remains green because it checks only whether referenced paths exist; once either private file is restored, its references resolve, and no other repository guard rejects the publication. The change describes the prior publication as a confirmed, machine-testable privacy mistake, so add a negative-control regression that rejects those private paths or equivalent tracked register/archive material rather than relying on deletion at this one head.

AGENTS.md reference: AGENTS.md:L358-L365

Useful? React with 👍 / 👎.

_{P2 Badge} Keep the binding documentation scope in the repository

For a repository-only documentation change, this rewrite makes the governing scope unavailable: the deleted OB-012 row was the only place specifying that client-facing and agent-layer English were governed while Russian text, verbatim evidence, archives, and changelog history were exempt. The remaining roadmap still says new text conforms "per the obligation" and later points readers to "its disposition list," but neither source is now readable here, so an agent cannot determine what must be rewritten or protected from rewriting. Retain that public scope and its dispositions in an authoritative in-tree document without the private register identifier.

AGENTS.md reference: AGENTS.md:L44-L58

Useful? React with 👍 / 👎.

_{P1 Badge} Stop granting coverage without the preserved review report

This run still sets whole_file=True, so when a current file matches the recorded commit, the loop adds it to whole_file["fable"] even though the evidence field now confirms that no report is available for verification. Running this ledger can therefore grant whole-file coverage to the 26 assistant/reporting paths from an unavailable transcript; remove the run from coverage, as was done for WORKTREE_REVIEW_RUNS, or validate a persisted hash-bound report before applying it.

AGENTS.md reference: AGENTS.md:L163-L165

Useful? React with 👍 / 👎.

_{P2 Badge} Reject renamed copies of the private documents

Fresh evidence at this head is that the new publication guard checks only the two former exact path names. If the obligation register or campaign archive is restored as, for example, docs/directions.md, and it contains no old scratchpad reference, _private_publication_violations() returns no violation, so the regression stays green despite republishing the same private material. Add a negative control and a content/root-level invariant that survives renaming rather than treating the deleted filenames as the privacy boundary.

AGENTS.md reference: AGENTS.md:L361-L365

Useful? React with 👍 / 👎.

_{P2 Badge} Restrict the verbatim exemption to immutable records

Applying this substitution to every tracked Markdown file creates an unrestricted opt-out from the dead-path guard: a newly added or edited document can wrap a misspelled backtick path in the generic verbatim fences, and the entire block disappears before validation. Nothing checks that the block is an immutable historical record rather than current instructions, so the gate can remain green while actionable documentation points to a missing file; constrain the exemption to the intended append-only source/section and add a negative control for fenced current prose.

AGENTS.md reference: AGENTS.md:L361-L365

Useful? React with 👍 / 👎.

_{P2 Badge} Keep audit ledgers in the evidence review lane

Moving the generated ledger to .audit-run changes its classification without updating _review_lane: because the path ends in .md and .audit-run/ is not recognized, both this output and the dual-review ledger are now assigned to R09 (canonical product/operator documentation) instead of the former R10 historical/generated-evidence lane. The generators explicitly inventory these output paths, so their review maps now misstate non-authoritative audit evidence as canonical documentation; classify .audit-run/ as evidence before the generic Markdown rule.

AGENTS.md reference: AGENTS.md:L76-L80

Useful? React with 👍 / 👎.