0011 (collision fix, supersedes PR #168) #187

Merged

pdurlej merged 1 commit from claude/orders/adr-renumber-0010-0011-from-pr168 into main

2026-05-12 01:51:21 +02:00

claude commented

2026-05-12 00:26:40 +02:00

Collaborator

Tier classification per ADR-0007: Lite-to-Medium — pure spec/docs additions + renames, no runtime/schema/sacred-path touches, ~500 LoC additive.

Why now

Operator decision 2026-05-12: resolve ADR numbering collision flagged in PR #186. PR #168 (claude-orchestrator thread, drafted 2026-05-11 before PR #184 merged) used ADR-0006 + 0007 slots. Those slots got merged by PR #184 (single-operator-status-file + risk-proportional-canary) before #168 could land. Operator's call: renumerować, zaktualizować dependencje, zostawić ślad.

Content unchanged. Only numbers + cross-refs.

What ships

Renamed (via git mv, history preserved):

decisions/0006-cousin-role-taxonomy.md → decisions/0010-cousin-role-taxonomy.md
decisions/0007-domain-promotion-policy.md → decisions/0011-domain-promotion-policy.md

Cross-ref updates inside renamed files:

ADR title lines (0006 → 0010, 0007 → 0011)
Self-references in acceptance-criteria sections
0011 Related: now cites ADR-0010 (was 0006) + ADR-0006/0007 as merged ADRs
0011 body: ADR-0007 codifies / ADR-0007 adds → ADR-0011 ...

Updates outside renamed files:

docs/agents/cousin-roles.md — canonical-spec ref bumped to 0010 + renumeration note
AGENTS.md — new ## Cousins (canonical enumeration, per ADR 0010) section (per Prof Kong's design, with ADR-0010 + DeepSeek-as-8th-cousin mention)
PLATFORM_CHARTER.md — new §3.5 Domain promotion policy (added 2026-05-11, ADR-0011) (per Prof Kong's design)

Trace (immutable evidence of renumeration):

Renumeration note added after Status/Date frontmatter in each renamed ADR (cites PR #168 origin, PR #184 collision, operator decision date)
Inline note in AGENTS.md § Cousins
Inline note in docs/agents/cousin-roles.md line 4
Inline note in PLATFORM_CHARTER.md §3.5 closing paragraph

What this PR does NOT

Does NOT touch runtime, modules, schemas, secrets
Does NOT change substantive ADR-0010/0011 content (renumeration + cross-refs only)
Does NOT auto-close PR #168 (separate API call after merge — operator can also do it manually)
Does NOT modify merged ADR-0006 (single-status-file) or ADR-0007 (risk-proportional-canary)
Does NOT change the GPT-5.5 Pro oracle review references in 0011

Test plan

Operator readback: ADR numbers 0010/0011 are correct + non-conflicting
Operator readback: renumeration trace is sufficient (Pan Herbatka believes yes — 4 separate inline notes)
Operator readback: AGENTS.md + PLATFORM_CHARTER.md additions are clean (no duplicate sections from PR #184 work)
Operator merge
Post-merge: PR #168 closed as superseded (this PR's API follow-up, or operator manually)
Future ADR-0012+ unblocked

Spec sources read

PR #168 head branch claude-orchestrator/governance-cousin-taxonomy-domain-promotion (Prof Kong's content, fetched via git)
Current main AGENTS.md + PLATFORM_CHARTER.md (after PR #184 merge)
ADR-0006 + ADR-0007 merged content (collision context)
ADR-0016 (DeepSeek 8th cousin) — mentioned in new AGENTS.md Cousins section

Operator's North Star check

Reduces: eliminates a future-claude footgun ("why are there two ADR-0006s?" question gone). Frees ADR-0006/0007 slots for the merged work canonically.
Slight increase: one extra merge for operator. Net positive.

Verdict: ship.

🍵 — Drafted by claude (Pan Herbatka) 2026-05-12 morning per operator direction. Operator merge welcome.

Refs: PR #168 (supersedes), PR #184 (collision source), PR #186 (flag origin, merged)

Tier classification per ADR-0007: **Lite-to-Medium** — pure spec/docs additions + renames, no runtime/schema/sacred-path touches, ~500 LoC additive. ## Why now Operator decision 2026-05-12: resolve ADR numbering collision flagged in PR #186. PR #168 (claude-orchestrator thread, drafted 2026-05-11 before PR #184 merged) used ADR-0006 + 0007 slots. Those slots got merged by PR #184 (single-operator-status-file + risk-proportional-canary) before #168 could land. Operator's call: renumerować, zaktualizować dependencje, zostawić ślad. Content unchanged. Only numbers + cross-refs. ## What ships **Renamed (via `git mv`, history preserved):** - `decisions/0006-cousin-role-taxonomy.md` → `decisions/0010-cousin-role-taxonomy.md` - `decisions/0007-domain-promotion-policy.md` → `decisions/0011-domain-promotion-policy.md` **Cross-ref updates inside renamed files:** - ADR title lines (0006 → 0010, 0007 → 0011) - Self-references in acceptance-criteria sections - 0011 Related: now cites ADR-0010 (was 0006) + ADR-0006/0007 as merged ADRs - 0011 body: `ADR-0007 codifies` / `ADR-0007 adds` → `ADR-0011 ...` **Updates outside renamed files:** - `docs/agents/cousin-roles.md` — canonical-spec ref bumped to 0010 + renumeration note - `AGENTS.md` — new `## Cousins (canonical enumeration, per ADR 0010)` section (per Prof Kong's design, with ADR-0010 + DeepSeek-as-8th-cousin mention) - `PLATFORM_CHARTER.md` — new `§3.5 Domain promotion policy (added 2026-05-11, ADR-0011)` (per Prof Kong's design) **Trace (immutable evidence of renumeration):** - Renumeration note added after Status/Date frontmatter in each renamed ADR (cites PR #168 origin, PR #184 collision, operator decision date) - Inline note in AGENTS.md § Cousins - Inline note in `docs/agents/cousin-roles.md` line 4 - Inline note in PLATFORM_CHARTER.md §3.5 closing paragraph ## What this PR does NOT - Does NOT touch runtime, modules, schemas, secrets - Does NOT change substantive ADR-0010/0011 content (renumeration + cross-refs only) - Does NOT auto-close PR #168 (separate API call after merge — operator can also do it manually) - Does NOT modify merged ADR-0006 (single-status-file) or ADR-0007 (risk-proportional-canary) - Does NOT change the GPT-5.5 Pro oracle review references in 0011 ## Test plan - [ ] Operator readback: ADR numbers 0010/0011 are correct + non-conflicting - [ ] Operator readback: renumeration trace is sufficient (Pan Herbatka believes yes — 4 separate inline notes) - [ ] Operator readback: AGENTS.md + PLATFORM_CHARTER.md additions are clean (no duplicate sections from PR #184 work) - [ ] Operator merge - [ ] Post-merge: PR #168 closed as superseded (this PR's API follow-up, or operator manually) - [ ] Future ADR-0012+ unblocked ## Spec sources read - PR #168 head branch `claude-orchestrator/governance-cousin-taxonomy-domain-promotion` (Prof Kong's content, fetched via git) - Current main AGENTS.md + PLATFORM_CHARTER.md (after PR #184 merge) - ADR-0006 + ADR-0007 merged content (collision context) - ADR-0016 (DeepSeek 8th cousin) — mentioned in new AGENTS.md Cousins section ## Operator's North Star check - **Reduces**: eliminates a future-claude footgun ("why are there two ADR-0006s?" question gone). Frees ADR-0006/0007 slots for the merged work canonically. - **Slight increase**: one extra merge for operator. Net positive. Verdict: ship. 🍵 — Drafted by claude (Pan Herbatka) 2026-05-12 morning per operator direction. Operator merge welcome. Refs: PR #168 (supersedes), PR #184 (collision source), PR #186 (flag origin, merged)

claude added 1 commit

2026-05-12 00:26:40 +02:00

governance: renumber Prof Kong ADRs 0006/0007 → 0010/0011 (collision fix, supersedes PR #168 )

canary-required / collect-diff (pull_request) Successful in 3s

Details

canary-required / canary (pull_request) Successful in 12s

Details

662b0ccc3e

Resolves the ADR numbering collision flagged by Pan Herbatka in PR #186:
PR #168 (claude-orchestrator/governance-cousin-taxonomy-domain-promotion)
drafted ADRs as 0006 + 0007 but those slots were occupied by merged PR #184
(single-operator-status-file + risk-proportional-canary).

Operator decision (2026-05-12): renumerować, zaktualizować dependencje,
zostawić ślad. Done — content unchanged, only numbers + cross-refs.

## Renamed
- decisions/0006-cousin-role-taxonomy.md → decisions/0010-cousin-role-taxonomy.md
- decisions/0007-domain-promotion-policy.md → decisions/0011-domain-promotion-policy.md

## Cross-ref updates inside renamed files
- ADR title lines (0006 → 0010, 0007 → 0011)
- Self-references in acceptance criteria
- 0011 → Related includes 0010 (was 0006); also ADR-0006/0007 (now merged ADRs)
- 0011 → "ADR-0007 codifies" / "ADR-0007 adds" → "ADR-0011 codifies" / "ADR-0011 adds"

## Updates outside renamed files
- docs/agents/cousin-roles.md: canonical spec ref → 0010-cousin-role-taxonomy.md
- AGENTS.md: new ## Cousins section (per ADR 0010) with renumeration note
- PLATFORM_CHARTER.md: new §3.5 Domain promotion policy (per ADR 0011) with renumeration note

## Trace
Renumeration footnote added to each renamed ADR after Status/Date frontmatter,
plus inline notes in AGENTS.md / docs/agents/cousin-roles.md / PLATFORM_CHARTER.md.
PR #168 to be closed as superseded with reference back to this PR.

## Tier (per ADR-0007)
Lite-to-Medium: pure spec/docs additions, no runtime, no sacred paths,
no schema changes. ~500 LoC purely additive + renames.

## What this PR does NOT do
- Does NOT touch runtime, modules, schemas, secrets
- Does NOT change ADR-0010/0011 substantive content (only renumeration)
- Does NOT close PR #168 in same commit (separate API call after merge)
- Does NOT modify ADR-0006 (single-status-file) or ADR-0007 (risk-proportional-canary)

Refs: PR #168 (supersedes), PR #184 (collision source), PR #186 (flag origin)