Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,8 @@ jobs:
run: python tools/mirrors_index_check.py
- name: Certificate source bindings still match the tree, and the index names them
run: python tools/pinned_sources_check.py
- name: An asserted operator directive cites its source (presence of sourcing, not truth)
run: python tools/operator_directive_check.py
- name: Drive source map is queryable
run: python tools/drive_index.py stats
- name: Scoped Drive coverage and exact packed-byte reconstruction
Expand Down
14 changes: 9 additions & 5 deletions docs/RESEARCH_MAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -677,11 +677,15 @@ below is quoted from those bytes.
promotion." The Board's OPERATOR PACKAGE DECISION of 2026-07-24 is the one
operator sentence in the corpus about a Git repository: "REPOSITORY ROUTING:
private Git repository creation and exact-history push are approved when
platform access becomes available." (Dylan subsequently authorized public
visibility on 2026-09-20; unauthenticated access was verified that day.
Public visitors have no write access. This later visibility decision does
not change the quoted historical routing, Drive sharing, or scientific
gates — see `governance/GIT_ADAPTATION.md`.)
platform access becomes available." (This repository is public, checked
2026-09-26; the visibility decision is the owner's, and the only sourced record
in this tree about it is the 2026-09-18 execution handoff
`drive/deltas/2026-09-18/DG-EXEC-20260918-49291487/DRIVE_GITHUB_EXECUTION_HANDOFF.md`,
which records the owner asking to restrict who works in the repository, not
to hide it — see `governance/GIT_ADAPTATION.md`, which withdraws an unsourced
directive that this passage previously asserted in the opposite direction. The
quoted historical routing, Drive sharing and scientific gates are unchanged by
visibility either way.)
* `14_COORDINATION_AUTOMATION_SPINE` (170) — the live registers
(`04.1_LIVE_REGISTERS`: the GP-REG-032-v1.2 workbook, its leaf card, the
deletion log), the automation lineage (GP-AUTO-034: **R0.4 current
Expand Down
42 changes: 38 additions & 4 deletions governance/GIT_ADAPTATION.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,10 +45,44 @@ paragraph called the Board's sentence the only one; the restatements are
GP/CL-line records of the same decision.) It approves a *private* repository as the formalization,
source-control, reproducibility and CI-handoff system of record and, in the
same decision, "NOT APPROVED: blanket terminalization or mathematical promotion
of any included claim." 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. Private draft work may
continue; this does not authorize public publication or mathematical promotion.
of any included claim." This repository is **public** — checked on 2026-09-26 two ways: the
GitHub API reports `private=false`, and the account's repository listing reports
`visibility=public`. The one *sourced* record in this tree about that visibility
is `drive/deltas/2026-09-18/DG-EXEC-20260918-49291487/DRIVE_GITHUB_EXECUTION_HANDOFF.md`:
"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 file, line 17, cited path `drive/deltas/2026-09-18/DG-EXEC-20260918-49291487/DRIVE_GITHUB_EXECUTION_HANDOFF.md`).
Whether to keep it so remains the owner's to decide. Private draft work may
continue; nothing in this paragraph authorizes public publication or mathematical
promotion.

**Withdrawn on 2026-09-26, and recorded rather than deleted.** Until that date
this paragraph and `docs/RESEARCH_MAP.md` each asserted an operator directive
about repository visibility, with no source anywhere in this tree, and the two
contradicted each other. Quoted verbatim so the withdrawal is checkable — as
transcription, not as assertion; **no operator directive is asserted here:**

```text
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, they are dated the same day, and neither cites a Drive
id, an artifact id, or any record in `registers/` or `drive/`. The status half of
the first is also false: the repository is public. And the first is not merely
unsourced but **contradicted by a sourced record already in the tree** — the
2026-09-18 execution handoff cited above says to preserve public visibility and
restrict who works in the repository, not to hide it. Which, if either, reflects an
actual decision is the operator's to say and nobody else's — this note asserts
only that neither was sourced and that both could not hold.
`tools/operator_directive_check.py`, added in the same commit, refuses either
shape from now on.

| Drive construct (protocol) | Repository equivalent | Notes on guarantees |
|---|---|---|
Expand Down
2 changes: 1 addition & 1 deletion governance/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ about which protocol governs.
**Scope note on OP-PROT-012.** The Drive object this reading copy comes from
(`1hBQR7Pa10DpVeOxTCLv1qIozLT-bU_hgZKo6ksODCuo`) carries the title *"HISTORICAL
OP-PROT-012 — APPROVAL ROUTING SUPERSEDED BY R17"* (retitled 2026-09-17). The
register says what R17 retired: `autonomy_control` AUTONOMOUS_DECISION_BUDGET =
register `registers/json/autonomy_control.json` says what R17 retired: AUTONOMOUS_DECISION_BUDGET =
"RETIRED — R17 evidence predicates" ("Current owner-authorized operations have
no 50-decision counter gate"), and CONTROL_PLANE_VERSION = "R17 supersedes R16
operational entry/budget/provider locks. Scientific predicates and exact frozen
Expand Down
Loading
Loading