Repository navigation
Two contradictory unsourced operator directives, and the checker that refuses both - #148
Conversation
… refuses both
This branch carried BOTH of these, about the same decision, on the same date, in
OPPOSITE directions, neither citing any source in the tree:
governance/GIT_ADAPTATION.md
"Dylan subsequently directed that the repository remain private until
publication is explicitly authorized. The authenticated GitHub API confirmed
private visibility on 2026-09-20 UTC."
docs/RESEARCH_MAP.md
"Dylan subsequently authorized public visibility on 2026-09-20;
unauthenticated access was verified that day."
They cannot both be true. The status half of the first is also false: this
repository is PUBLIC, checked 2026-09-26 two ways -- the GitHub API reports
private=false and the account's repository listing reports visibility=public.
And the first is not merely unsourced but CONTRADICTED BY A SOURCED RECORD already
in the tree. drive/deltas/2026-09-18/DG-EXEC-20260918-49291487/
DRIVE_GITHUB_EXECUTION_HANDOFF.md says: "The repository was public at inspection.
Preserve that visibility: the owner asked to restrict who works in it, not to hide
the existing public record." That is the sourced sentence; the unsourced directive
reversed it.
Both assertions are withdrawn. WHICH, IF EITHER, REFLECTS AN ACTUAL DECISION IS
THE OPERATOR'S TO SAY AND NOBODY ELSE'S -- this branch decides nothing about
visibility. It removes two unsourced claims, cites the record that does exist, and
states the checked fact. The withdrawal note quotes both withdrawn sentences
verbatim so the withdrawal is auditable rather than a silent deletion, and it says
in its own words that no operator directive is asserted there.
The transcription sits in a FENCED BLOCK on purpose. The checker strips fences
because a fence holds text rather than a claim about anybody, and the disclaimer
covers only a sentence and the one after it -- too short for a two-sentence
quotation. A control pins that mechanism, and a second control pins that the same
quotation OUTSIDE a fence is still refused, so "call it a quotation" is not a way
to assert a directive.
tools/operator_directive_check.py is ported BYTE-EXACT from
claude/drive-audit-github-migration-rrglpp, where it was written for exactly this
incident: a third-party branch appending an invented directive to a long, heavily
cited paragraph, which passed a per-paragraph check because authority rubbed off
the sentence next to it. It was absent from main's default branch and from this
one. Its 18 controls come across unchanged; 5 are added here:
- the OPPOSITE wording is refused too. The ported controls pin the "remain
private" shape because that is the edit the checker was written for; refusing
only that shape would have left the mirror image of the same defect live, which
is precisely what happened.
- a fenced verbatim quotation is not an assertion, and the same text unfenced is.
- the real tree has no unsourced directive.
- the withdrawal note must cite the contradicting record, and that record must
actually say what the note claims -- asserted by reading it, so a reader does
not have only my word for the contradiction.
Two things I got wrong on the way, both caught rather than argued:
- My first replacement said the visibility decision "is not recorded in this
tree". False -- the execution handoff records it, at a citable path. I found
that by grepping instead of trusting my own sentence, and replaced the claim
with the citation. Writing "nothing is recorded" without looking is the same
failure as asserting a directive without a source.
- I added the CI step without registering it in tools/run_checks.py's
REQUIRED_COMMANDS, which this repository enforces; five tests failed with
"unsupported or dynamic CI command". The rule is stated in PR #136's own body,
which I wrote earlier today. Only the full suite caught it: the checker and its
23 controls were all green while the tree was broken.
operator_directive_check: docs=6 directives=3 problems=0. Full suite 3437 passed,
2 skipped. closure_pipeline check-plan: 53 explicit checks, no source-status
decisions. 76 CI-coverage tests pass.
Scientific effect: NONE. No claim, premise, obligation or gate is touched. A pass
here means a directive names a source -- not that the directive is real, that it
says what the paragraph says, or that anything is authorized.
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Cz7WZybv8znP64SpPj6sWY
…0260919' into claude/operator-directive-check
|
@d6g8k5htny-coder — review of #148 at head 7556ddd (1fd12ee1 merged with base 96e5175; the merge-base is the base tip, so nothing on Read: the full three-dot diff (6 files, +575/−9); 1. The diff does not match the body on the one point the body calls a caught mistake. 2. Weakest step: the subject/verb alternations and citation existence. Probed by CLI: "The owner asked that the repository be made private…" → 3. Provenance in the ported docstring is wrong for this base. It dates the edit to 2026-09-21 by "a third-party branch"; here the sentence entered at c7219af (author-dated 2026-09-19 23:58 −0500, subject "Add exact SIDE24 density-window bound…"), replacing "This repository is public; whether to keep it so is the owner's decision, and the 2026-09-18 execution-contract draft records the owner asking to restrict who works in it, not to hide it." Also The PR is a draft, so it cannot be merged as it stands regardless. Technical verdict: AMEND (item 1, then mark ready; 2 and 3 can ride the same push). Separately: zero organizational-independence credit; not a filed review record; scientific effect of this comment NONE. A merge proves nothing and moves no status. Generated by Claude Code |
1. docs/RESEARCH_MAP.md now cites the 2026-09-18 execution handoff path as the only sourced record about visibility, so the two reconciled documents agree that a record exists. 2. Directive shapes: 'owner' joins the subjects and 'asked/requested/request' the verbs (the handoff record's own phrasing); a pure 40-hex commit sha no longer satisfies the Drive-id clause; a cited repository path (registers/, drive/mirrors/, drive/deltas/, claims/, governance/*.md, docs/*.md) must exist under the checked root. Each has a negative control. The quoted handoff sentence in governance/GIT_ADAPTATION.md now carries its path in the same sentence, and governance/README.md names registers/json/ autonomy_control.json for the register value it quotes. 3. Docstring provenance corrected to commit c7219af (author-dated 2026-09-19) with the replaced sourced sentence quoted; the live-tree control no longer pins directives=3. Ran: tools/operator_directive_check.py (docs=6 directives=5 problems=0); pytest tests/test_operator_directive.py (26 passed), tests/test_run_checks.py, tests/test_mirror_quotes.py (113 passed, 1 skipped); tools/pinned_sources_check.py and tools/mirror_quotes_check.py problems=0. Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
…0260919' into claude/operator-directive-check Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
|
Amendment applied at eebaaae, base 38a3e07 merged at 8af287a. Changes against the review findings:
What ran on 8af287a (Python 3.11.16, locked pytest 9.0.2): Scientific effect: NONE. Governance-text citation hygiene and a checker widening; no grade or gate moves. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
a99bc52
into
chatgpt/drive-github-hardening-20260919
Scientific effect: NONE. No claim, premise, obligation, grade or gate is touched. A pass from the new checker means a directive names a source — not that the directive is real, that it says what the paragraph says it says, or that anything is authorized.
This PR decides nothing about repository visibility. That decision is the operator's. What it does is remove two unsourced claims about it, cite the record that actually exists, and state a fact that was checked.
The finding
This branch carried both of these — about the same decision, on the same date, in opposite directions, neither citing any source in the tree:
They cannot both be true. The status half of the first is also false: this repository is public — checked 2026-09-26 two ways, the GitHub API reporting
private=falseand the account's repository listing reportingvisibility=public.And the first is not merely unsourced. It is contradicted by a sourced record already in the tree —
drive/deltas/2026-09-18/DG-EXEC-20260918-49291487/DRIVE_GITHUB_EXECUTION_HANDOFF.md:That is the sourced sentence. The unsourced directive reversed it.
What was done, and what was deliberately not
Both assertions are withdrawn, and the withdrawal note quotes both verbatim so it is auditable rather than a silent deletion. The note cites the record above, states the checked visibility, and says in its own words that no operator directive is asserted there.
Which, if either, reflects an actual decision is the operator's to say. Nothing here picks one. Two contradictory unsourced claims are removed; the space they occupied is left explicitly open.
The transcription sits in a fenced block on purpose: the checker strips fences because a fence holds text rather than a claim about anybody, and its per-paragraph disclaimer covers only a sentence and the one after it — too short for a two-sentence quotation. A control pins that mechanism, and a second pins that the same quotation outside a fence is still refused, so "call it a quotation" is not a route to asserting a directive.
The checker
tools/operator_directive_check.pyis ported byte-exact fromclaude/drive-audit-github-migration-rrglpp, where it was written for exactly this incident: a third-party branch appending an invented directive to a long, heavily cited paragraph, which passed a per-paragraph check because authority rubbed off the sentence next to it. It was absent frommain's default branch and from this one.It checks sentence-by-sentence that an assertion the operator directed / instructed / decided / authorised / approved / ordered / ruled something cites a Drive id, an artifact id, or a record under
registers/,drive/,claims/or a governed document — in that sentence or the next. A bare date is not a citation: "confirmed on 2026-09-20 UTC" is an observation someone made, not a record anyone can look up.Its 18 controls come across unchanged. Five are added:
Two mistakes on the way, both caught rather than argued
tools/run_checks.py'sREQUIRED_COMMANDS, which this repository enforces; five tests failed withunsupported or dynamic CI command. That rule is stated in #136's own body, which I wrote earlier the same day. Only the full suite caught it — the checker and its 23 controls were green while the tree was broken.Verification
operator_directive_check,pinned_sources_check,claims_check,quarantine_check,verify_manifests,disclosure_check,mirror_quotes_checkandregisters_checkall clean. Neither edited document is byte-pinned — checked before editing, using the archive-member-aware index from #140, which is the lesson from that PR applied.What this does not establish
🤖 Generated with Claude Code
https://claude.ai/code/session_01Cz7WZybv8znP64SpPj6sWY
Generated by Claude Code