Skip to content

docs: record the 2026-11-13/14 goal-review rulings - #62

Merged
djbclark merged 11 commits into
masterfrom
docs/goal-review-rulings-20261114
Nov 15, 2026
Merged

djbclark merged 11 commits into
masterfrom
docs/goal-review-rulings-20261114

Conversation

@djbclark

@djbclark djbclark commented Nov 14, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Writes every operator ruling of the 2026-11-14 goal-review walk (rulings file lines 4-56) into the repo's normative docs, each where a reader of that section would look, quoting the chosen option exactly and citing "operator ruling, 2026-11-14" plus the item id. Docs only: no code, no builds.

  • AGENTS.md: standing rule 3 now carries B10 (spike lane O1, tiered review O2, docs freeze O4; O6 not chosen); the B11 round 2 "Keep Mac, SKIPs" text, PR 52 gate 2 (WarpBuild), the PR 52 follow-up issues, the ShizukuTendCF dev-mode/dev-build rule and the AGPL-3.0-only review TUI.
  • docs/architecture/architecture-DEFINITIVE-v3.md (the map): D47-D50 added as ruled rows; D6, D8, D16, D45, D46 and R5 amended; section 0 maxim; new section 9.12 (safety score); Android, macOS and build-order sections.
  • change-process.md (Nix on the release path, build-time only; the person's-own-fork sentence), upstream-register.md and upstream-overlay.md (B11 and round 2).
  • docs/review-2026-11-13/: each ruled proposal section gets a "Ruled" paragraph and its proposed text rewritten (for example M-§8-01 for "make that both", M-§9-03 caps table, G-§7-01 floor, X-safety-06 with the arXiv citation); the goal definition gets the B13 edits; 14 §B has a ruling index.
  • Also repairs the 21 dangling references bin/xref_lint.py found in the review docs (it now reports 0 findings).

Ruled but not yet implemented says so in the text (for example B-5b "1. Replace": "ruled; implementation pending in a follow-up PR", overlay phase B).

arXiv 2404.13076 was fetched before it was cited (Panickssery, Bowman, Feng, "LLM Evaluators Recognize and Favor Their Own Generations", 15 Apr 2024, https://arxiv.org/abs/2404.13076) and is cited only for self-preference bias.

Judgment calls to confirm

  1. AGENTS.md rule 3: the ruling does not define "light review". I kept the cross-model independence rule for it and kept one frontier review for non-doc, non-device code (compiler, CI, tooling).
  2. 00-goal-definition G4: applied B13 wording 3 ("score from 0 to 100", mechanical ceiling), keeping the highlighting clause. Revert that one sentence if ruling line 25 is read as "no G4 edit".
  3. Map build order: the old "Step N" names are kept (other docs use them); a new Stage 0-16 table carries the ruled order.
  4. Schema-touching rulings (each needs two frontier reviews before it is built): B2 standing modes (new approval-record shape), C-policy-01 schema_version 6 and contract_version const 2, B3 sub 1 profile field on entries (rides the agent-id bump), B8 sub 1 score values fixed in the schema. This PR only records them.

Coverage table (rulings file line -> where it now lives)

Line Ruling Lives in
4 B1 map §9.11, D50; 00-goal-definition "Later rulings" 1; 10 X-trust-01; 14 §B
5 B2 map §9.1, D50; 03 M-§10-01; 02 G-§7-02; 10 X-trust-01/06; 14 §B
6 C-policy-01 version 6 map §9.6; 05 C-policy-01, C-schema-06; 14 §B
7 Beeper 14 §B "Rulings outside B1 to B13" (recorded here only)
8 B3 map §12; 03 M-§12-03; 07 §5; 05 C-android-01/04; 14 §B
9 B4 D47-D50 map §13, D47-D50 rows; 03 M-§15-01..04; 02 G-§18-02; 14 §B
10 Linux order map §12, D48; 03 M-§12-07; 02 G-§18-02
11 canary map §12, D48; 03 M-§12-07
12 Nix release path, build-time only change-process §2; map R5, D6; 03 M-§2-04; 08 X-nix-12/13
13 monitor role state 2 map §8, §13; 03 M-§13-01; 02 G-§18-02
14 D16 deferred map D16 row; 03 M-§13-01; 02 G-§10-01
15 B5 map §12 "Engine pin"; 03 M-§12-02/03; 11 §7
16 B6 map §12 macOS; 03 M-§12-01; 05 C-deploy-01
17 B7 map §5; 03 M-§2-13, M-§15-03; 08 X-nix-02/05; 05 Idea 1
18 B8 map §9.12; 00-goal-definition G4; 03 M-§9-02; 09 Q3, X-safety-01
19 contract_version const 2 map §9.6; 05 C-policy-01; 14 §B
20 PR 52 gate 2 AGENTS.md "Verifying policy and the CFEngine build"; map §13 stage 2; 03 M-§12-02
21 B9 00-goal-definition "Later rulings" 3; map §12; 14 §B
22 B10 AGENTS.md standing rule 3; 13 X-pm-07; 14 §B
23 B11 upstream-register "Operator rulings of 2026-11-14"; 14 §B
24 B13 item 1 00-goal-definition "Later rulings" 1; map §9.11; 14 §B
25 B13 items 2/3/6/7 00-goal-definition G4 and "Later rulings"; map §9.12; 13 X-pm-03
26 B13 item 4 00-goal-definition G8 lead sentence; map §13; 13 X-pm-05
27 B13 item 5 00-goal-definition G8 item 3; map §13; 13 X-pm-04
28 Smaller 1 dev mode AGENTS.md "Android work"; 05 C-android-03; 03 M-§2-10
29 Smaller 2 maxim map §0 item 1; 03 M-§0-02
30 Smaller 1 rider AGENTS.md "Android work" item 3; 05 C-android-03
31 Smaller 3 D47 vs D8 map D47, D8, §0; 03 M-§15-01; 02 G-§17-01
32 Smaller 4 own fork change-process §2 rule 5; 12 X-forks-05
33 Smaller 5 D46 map D46, §5; 02 G-§4-01; 03 M-§13-01 Step 0
34 Smaller 6 (superseded) 03 M-§8-01 (recorded as superseded by line 35); 14 §B
35 Smaller 6 "make that both" map §8, §12 item 7, D45, D18; 03 M-§8-01, M-§12-05 item 7
36 Smaller 7 delegation upstream-register "Operator rulings of 2026-11-14" item 6
37 Smaller 7 outcome same, item 6 (not sent; worker 7d55e815 preparing)
38 B12 AGENTS.md "Licensing"; map §6; 09 X-safety-11; 14 §B
39 B3 sub 1 profile field map §12, §9.6; 07 X-android-05; 03 M-§12-04, M-§12-05 item 4
40 B3 sub 2 validator map D45 (1)-(2), §12; 03 M-§12-06; 07 X-android-13
41 B3 sub 3 never a DPC slot map R4, §12; 07 X-android-09; 03 M-§12-03/04
42 B3 sub 4 review surface map §13 (replaces Step 9 row); 09 X-safety-08; 07 X-android-14
43 B6 sub 1 VM on bigmac map §12; 03 M-§12-01; 05 C-deploy-01, C-macos-01
44 B6 sub 2 dry-run only map §12, §8; 03 M-§12-01 (Q18)
45 VM image minimised map §12 "Image size"; 03 M-§12-01 (queued as build work)
46 B6 sub 3 root in VM map §12; 03 M-§12-01
47 B8 sub 1 table 03 M-§9-03 (full values); map §9.12; 09 Q3
48 B8 sub 2 floor 02 G-§7-01; map §9.12; 09 Idea 11
49 B8 sub 3 build order map §9.12, §13; 02 G-§18-02; 09 Idea 12; 13 A(i)-9
50 B8 sub 4 09 X-safety-06; map §9.12, §11; 14 §B
51 PR 52 follow-ups AGENTS.md "Verifying policy and the CFEngine build"; 14 §B
52 issues filed same (#53, #54, #55, tracker #56)
53 B11 r2 item 1 Replace upstream-register ruling section item 2; upstream-overlay §7 (implementation pending)
54 B11 r2 item 2 Keep Mac, SKIPs AGENTS.md "Verifying policy and the CFEngine build"; upstream-register item 3
55 B11 r2 item 3 order upstream-register item 4
56 B11 r2 item 4 .gitmodules upstream-register item 5

Zero unmapped lines (4-56); none "not applicable".

Fix round 1 (head 9b3da02)

Corrections from the three reviews of the first head; no new decisions, and every "open" item below is left for the operator.

  • Schema facts: the base is already v6 with contract_version const 2 (PR 52). C-policy-01 is recorded as implemented there; the profile/agent-id and standing-modes changes take "the next unused schema version (v7 or later)", grouping not ruled. The Stage 0 "one bump" allocation is gone. schema/*.json untouched.
  • Stale status: PR 52 (2c78680), policy: cross-check the loaded CMDB against host_specific.json; refuse to actuate on any difference (Q10) #42 (acec5b5) and Pin the fork at the fail-closed CMDB loader (R13) #41 (daa4530) are merged; the original gate/queue text is kept and marked historical. The WarpBuild spike run (https://github.com/frdminc/tendcf/actions/runs/43602684071) completed with conclusion success.
  • Spike lane: O1's rails restored word for word from X-pm-07; "a spike workflow runs with permissions: contents: read and no secrets" is added and marked as a lead/reviewer hardening, not part of the ruling.
  • Light tier: read conservatively: it changes review depth, never routing, quota, reservation or admission rules; AGENTS.md rules and normative trust/consent/privilege/review text are not "light docs"; a mixed PR takes its highest tier; policy run by root cf-execd counts as root code.
  • Linux: the freeze wording is removed; "later in the order, not paused" stands.
  • Also: option-number notes on B3, B7, B8; the rulings file is committed beside 14 as docs/review-2026-11-13/rulings-record-2026-11-14.md and local paths are stripped from public docs; X-safety-06's task and model scope restored; stale arXiv to-do removed; step-to-stage mapping sentence; standing approval marked as a reading of line 5 (only the nonce is dropped); dev build's distinct applicationId and signing key noted as a recommended follow-up, not ruled.

Fix round 2 (head 9edc7da)

Rebased onto master 401e0f6 (PR 61 merged 2026-11-15: pin 4443504); no conflicts. Records the four operator rulings given on the review questions, quoted exactly, and appends them as lines 57-60 of docs/review-2026-11-13/rulings-record-2026-11-14.md:

  1. Q1, root-enforcement timing: "2. Exception for the VM": an explicit, ruled exception like pastebin's; the VM may enforce early, canary only, operator-authored data (stage table stage 1 and D45 timing).

  2. Q2, light review: "2. Cheaper reviewer allowed": any model outside the author's family not on the weaker-tier ban list may do a light review; if it is a frontier model the frontier checks still apply (AGENTS.md rule 3). The conservative limits from round 1 stay and are labelled as lead/reviewer readings.

  3. Q3, Android log/index: "1. Agent keeps log role": "only" is about decisions; the thin Kotlin agent still writes the device JSONL and index as a support role; the map and D18 stand.

  4. Q4, schema grouping: "1. Decide at design review": docs say "the next unused version (v7 or later)", grouping not ruled; the schema design review (two frontier reviews) decides.

  5. Q5, G4 goal sentence: "1. Yes, keep it": the current 00-goal-definition.md G4 sentence (wording 3 plus the highlighting clause) is the ruled wording.

  6. Q6, reviewer-proposed map text: "1. Keep both": map section 0 item 3 (M-§0-01) and the section 8 log-archive paragraph (M-§8-01) stay, in scope of recording rulings.

  7. Q7, "AI reviewer subtracts up to 30": "1. Defer to design review": stays open; the schema design review decides.

Open items awaiting operator ruling (2026-11-14)

Still open (listed in 14-synthesis-and-rulings.md): only Q7, whether the 30-point maximum is per AI reviewer or the total for all AI reviewers; the schema design review decides.

Fix round 3 (head cb84942)

Round-2 reviews: Astra (gpt-6-astra, high) changes-requested; Fable (claude-fable-5-2, high) changes-requested; adversary findings 1 medium, 4 low. This round fixes each once; no new decisions.

  • L64 (new operator ruling, "PR 62 round-2 review"): appended verbatim to rulings-record-2026-11-14.md (now 64 lines) and recorded in 14. AGENTS.md rule 3 now states the ruled O2 tiers and Q2 in their own cited sentences; the lead notes (light-docs limits, spike permissions: contents: read and no secrets, one frontier review for compiler/CI/tooling) are labelled "in force as lead practice until djbclark rules otherwise"; the not-light list is widened per L64; Opus and Sonnet are stated as one family.
  • Q7: every place now says "open: deferred to the schema design review (operator ruling, 2026-11-14, PR 62 review Q7)" and does not choose per reviewer or total.
  • Q3: the Android log notes in the map (sections 8 and stages 6-7) no longer say "open".
  • Standing-approval reading: one wording in every place, labelled a reading, not part of the ruling; the schema design review confirms.
  • Q1: the exception is worded narrowly everywhere ("canary only, operator-authored data").
  • Also: plugin-layout.md annotated with the Smaller 5 (L33) deferral of out-of-tree discovery; rulings index and "Lives in" pointers completed; PR 61 timestamp aligned; B8 option-number note.
  • Follow-up, not done here (adversary 5): a ruleset for the spike workflow.

Fix round 4 (head de1b8a0)

Round-3 reviews: Fable (claude-fable-5-2, high) approve with 7 low/nit findings; Gemini 4 Argon (high) approve with 2 nit findings (Astra's codex pool is below the tendcf floor until 2026-11-18, so it did not review this round); adversary findings 1 low and 3 info. This round fixes each once; prose only, no new decisions, and the rulings record is unchanged.

  • Standing-approval reading (adversary C1, Fable A5): one strong-form wording in all six places (AGENTS.md "Android work" item 5, review docs 02, 03 and 10 (two places), and the map's section 9.1), labelled "a reading of the ruling (L5, B2), not part of it"; the wording is a lead decision from the round-3 review. A standing approval drops only the per-change nonce; every standing mode is owner-enrolled and refusable, and none is a default; dropping any other check needs an operator ruling.
  • AGENTS.md rule 3 (adversary C2, C4, Fable A6): the "not part of the ruling, still in force" sentence is scoped to the three L64 notes and the labelled readings, all of which only tighten; a reading that loosens a rule needs an operator ruling. Limit (a)'s widening is tagged as L64 wording; only its file list is the lead's examples.
  • 14-synthesis-and-rulings.md (Fable A1, A3, A4, adversary C3, Argon 1, 2): "Ruled:" keeps only L64's own open list and the files follow as the lead's current examples; the Q7 text quotes 09 as it stands ("up to 30, only for findings citing a key path") with the aggregation still open; the section 9.12 pointer and the "Where" list agree; Smaller 5 "Lives in" adds the map D46, plugin-layout.md and change-process.md.
  • plugin-layout.md (Fable A2, A7): drops "and a later ruling revives it" (L33 sets two conditions only); says PRs Pin the fork at the fail-closed CMDB loader (R13) #41 and policy: cross-check the loaded CMDB against host_specific.json; refuse to actuate on any difference (Q10) #42 are merged.

Fix round 5 (head d96d13a)

Round-4 reviews: Fable (claude-fable-5-2, high) approve with 1 low and 2 nit findings; adversary no findings above info (3 info); the Argon r4 review is folded into this round. This round fixes each once; prose only, no new decisions, and the rulings record is unchanged.

  • Standing-approval reading (Fable A1): the same body in all six places, still labelled "a reading of the ruling (L5, B2), not part of it". A standing approval drops only the per-change nonce (DC-2's device nonce); it keeps B1's other content checks and the rest of DC-2 (per-target validity, single use or high-water mark, persisted rejects); its ceremony class is still checked against the validator's derived requirement (section 9.8); it names its signer and algorithm only if X-trust-06 is adopted (proposed, not ruled).
  • Map DC-2 sentence (adversary info 1): now says the DC-2 question is settled "within the reading below".
  • 14-synthesis-and-rulings.md (Fable A2, adversary info 2): the change-process.md pointers are "section 3 property 1, section 6 gate 2"; a schema design review agenda note lists the ceremony-class, persisted-rejects and X-trust-06 points as open.
  • AGENTS.md rule 3 (Fable A3): says the two readings are in force as lead practice, on the lead's authority, and that L64 covers only the three notes.

Fix round 6 (head 7392291)

Round-5 reviews: Fable (claude-fable-5-2, high) changes-requested (1 medium, 1 nit); Gemini 4 Argon (high) approve with 1 nit; adversary 2 low and 2 info. This round fixes each once; prose only, no new rulings, and the rulings record is unchanged.

  • Standing-approval reading (adversary L1): all six copies add an interim default, in the stricter direction and still labelled a reading: until the operator rules, a standing approval covers ordinary changes only; whether one may cover privileged or baseline changes is for the schema design review to propose and the operator to rule. Everything else in the reading is unchanged.
  • Schema design review agenda (Fable A1, A2, adversary L2 and info 3, Argon nit): the note in 14-synthesis-and-rulings.md is rewritten (still a lead note, not a ruling). The review proposes to the operator: privileged or baseline coverage, how persisted rejects apply, how the single-use counter applies to a record that authorises more than one change, which signers a standing approval may name outside developer mode, and X-trust-06. The ceremony-class check, persisted rejects and the counter stay; dropping a check needs an operator ruling.

Round-6 reviews (final, head 7392291): Fable (claude-fable-5-2, high) approve with 2 nits; Gemini 4 Argon (high) approve with no findings; adversary security review: no findings above info (1 info). All round-5 findings are resolved. Follow-ups after merge (not blocking): the interim "ordinary only" default should also name the hold window (Fable nit 1, adversary info); the reading's label could drop "round-3" (Fable nit 2). Astra's codex pool is below the tendcf floor until 2026-11-18, so it did not review rounds 3-6.

🤖 Generated with Claude Code


Note

High Risk
This PR redefines review gates in AGENTS.md and trust/consent/platform enforcement text across the architecture map and change-process docs, which directly governs how privileged work is reviewed and merged even though no runtime code changes.

Overview
This PR writes the 2026-11-14 goal-review walk into normative docs—mostly prose, no code or schema changes—so decisions live where implementers and reviewers already look, with operator ruling, 2026-11-14 citations and exact chosen options.

AGENTS.md standing rule 3 is reworked for B10: a spike lane (unmerged spike/*, safety rails, GitHub contents: read), tiered cross-model review (light for docs/spike notes, one frontier for device code, two for root/trust/key/handshake and design rulings), and a docs freeze until spikes run for state-1 work. It also records WarpBuild macOS check 8, PR 52 follow-up issues, ShizukuTendCF dev-mode/dev-build rules, AGPL-3.0-only review TUI licensing, and Mac SKIP vs Linux require fork loader policy test gating.

architecture-DEFINITIVE-v3.md absorbs D47–D50 (adoption aim, platform order, Nix-first authoring, peer handshake/content checks), adds §9.12 safety score, standing approval modes, Android/macOS state-1 shape, fleet log archive indexes, a Stage 0–16 build order table, and widespread amendments to D6/D8/D14–D18/D45–D46. change-process.md, plugin-layout.md (defer out-of-tree plugins), and upstream overlay/register docs pick up B11/B-5b and fork-pin narrative.

The docs/review-2026-11-13/ tree gains or extends goal-definition, fork-management, and ruling cross-references; several items stay ruled but implementation pending (e.g. overlay B-5b replace, schema v7+ grouping).

Reviewed by Cursor Bugbot for commit 7392291. Bugbot is set up for automated code reviews on this repo. Configure here.

@cursor

cursor Bot commented Nov 14, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 30d181bd-5630-4cb9-8632-e8f9f4c48f53)

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-14T22:56:08.270257Z 5fd6ec3 PR opened
🔒 Security Review ✅ Completed 2026-11-14T22:57:09.586380Z 5fd6ec3 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5fd6ec39b4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread AGENTS.md
Comment on lines 149 to +152
- Design rulings (a `schema_version` bump, the privilege or enforcement
scope on a host, a deploy plan, the unit-writer or consent-diff design)
get two independent frontier reviews, astra and Fable. Argon stands in
scope on a host, a deploy plan, the unit-writer or consent-diff design),
and root, trust-root, key and handshake code (O2, above), get two
independent frontier reviews, astra and Fable. Argon stands in

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Apply O2's narrowed definition of a design ruling

For deploy-plan, unit-writer, or consent-diff documentation changes that do not change a schema or trust, this retains the old two-frontier-review requirement even though the adopted O2 explicitly narrows “design ruling” to schema bumps and trust changes (docs/review-2026-11-13/13-premortem-and-ideas.md:192-196). Consequently, these changes still require both frontier pools and can remain blocked on quota, rather than receiving the lighter review the ruling selected. Narrow this definition to match O2 while retaining the separate two-review requirement for root, trust-root, key, and handshake code.

AGENTS.md reference: AGENTS.md:L68-L69

Useful? React with 👍 / 👎.

@cursor

cursor Bot commented Nov 14, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 77481b4a-36c1-46d4-8d4d-9212f3eb1824)

djbclark and others added 6 commits November 14, 2026 19:13
…em format

New files only; no original document is changed.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Thirteen response and research documents (01-13) measured against the
goal agreed 2026-11-13, the six independent check files that tried to
refute them, and a synthesis listing the rulings needed, confirmed
defects and a merge map. No original document is changed.

Reviewers and checkers are all Claude Opus; this is not the cross-model
frontier review, and nothing was built or executed.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A later pass re-fetched 35 source groups the first review could not
read: 15 confirmed, 18 weakened, 1 refuted (the paper's Promise Theory
purpose claim), 1 still unfetched. Corrections R1-R21 are applied to
the response documents and the synthesis; two items are added to the
sources check (P-§3.1-s28, P-§3.2-s29). No original document is changed.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Writes every operator ruling of the 2026-11-14 goal-review walk (B1-B13,
riders, sub-rulings, smaller rulings, PR 52 items, B11 round 2) into the
normative docs: AGENTS.md rule 3 (spike lane, tiered review, docs freeze),
the map and decision register (D47-D50 new; D6, D8, D16, D45, D46 amended),
change-process and the upstream register, and the review proposals they
settle. Also repairs the 21 dangling references xref_lint found in the
review docs. Ruled items not yet built say so.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Corrects the rulings record against the three reviews of PR 62:
schema facts (v6 and contract_version const 2 are implemented by PR 52;
later changes take the next unused version, grouping not ruled), stale
merge/pending statuses (PR 52, #42, #41 merged; WarpBuild run
succeeded), the spike lane's rails restored word for word with the
workflow-permission hardening marked as hardening, the light review tier
read conservatively (no waiver of routing or admission rules), the Linux
design-work freeze removed (later in the order, not paused), option-number
notes, and open items marked 'open: awaiting operator ruling' (Android
log/index ownership, root enforcement timing, reviewer eligibility,
schema grouping) with a new open-items list in 14. The rulings file is
now committed beside 14 as rulings-record-2026-11-14.md and local paths
are stripped from public docs. No new decisions.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Records the four operator rulings given on the PR 62 review questions
(root-enforcement timing: exception for the VM; light review: cheaper
reviewer allowed; Android log/index: agent keeps log role; schema
grouping: decide at design review), replacing the round-1 open notes,
appends them to the in-repo rulings record (lines 57-60), and marks the
PR 61 pin move merged (401e0f6). Fable B2, B4 and B5 stay open.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@djbclark
djbclark force-pushed the docs/goal-review-rulings-20261114 branch from 9b3da02 to ae841bc Compare November 15, 2026 00:16
@cursor

cursor Bot commented Nov 15, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 7fa8fd29-a472-43df-b431-f020eb98bced)

Q5 "1. Yes, keep it" (the G4 sentence in the goal text is the ruled
wording), Q6 "1. Keep both" (map section 0 item 3 and the section 8
log-archive paragraph stay), Q7 "1. Defer to design review" (the AI
reviewer's up-to-30 stays open). Appended as lines 61-63 of the rulings
record; 14's open-items list now holds Q7 only.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@cursor

cursor Bot commented Nov 15, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 2a475e1e-783f-4432-b39d-29dae9d3022d)

… L64)

Records the operator ruling on the round-2 review (L64) and corrects the
round-2 review findings: AGENTS.md rule 3 restated (ruled O2 tiers and Q2
in their own cited sentences, the lead notes labelled lead practice, the
not-light list widened, Opus and Sonnet one family), Q7 marked as
deferred to the schema design review everywhere without choosing per
reviewer or total, the Android log notes after Q3 closed in the map, one
wording for the standing-approval reading, the Q1 exception worded
narrowly, plugin-layout.md annotated with the L33 deferral, the rulings
index and Lives-in pointers completed, PR 61 timestamp aligned. No new
decisions.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@cursor

cursor Bot commented Nov 15, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: bfa8cd75-bf56-44df-9570-49b8544bd515)

Use one strong-form wording for the standing-approval reading in six
places, labelled a reading of the ruling (L5, B2); scope the AGENTS.md
rule 3 lead-practice sentence to readings that only tighten; keep only
L64's own text under Ruled in 14; align the Q7 wording; drop the
'later ruling revives it' phrase in plugin-layout; add the D46 and
plugin-layout 'Lives in' pointers for Smaller 5. No change to the
rulings record.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@cursor

cursor Bot commented Nov 15, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 5f52d5d3-ba84-4427-9040-6c85165a7328)

Reword the standing-approval reading in all six places: it keeps B1's
other content checks and the rest of DC-2, its ceremony class is still
checked, and signer and algorithm depend on X-trust-06 being adopted.
Say the two readings are lead practice on the lead's authority, point
the map's DC-2 sentence at the reading, correct the change-process
pointers, and list the open points as a schema design review agenda
item. No change to the rulings record.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@cursor

cursor Bot commented Nov 15, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: e5c8c284-58d8-437f-9a54-fb5627f15bbc)

Add an interim default to the standing-approval reading in all six
places: until the operator rules, a standing approval covers ordinary
changes only. Rewrite the schema design review agenda note in 14 so it
lists the questions the review proposes to the operator and the checks
that stay. No change to the rulings record.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@cursor

cursor Bot commented Nov 15, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 9b89fd31-2791-45a4-8463-e2b3f329d393)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant