Propose staged GitHub estate architecture

[seathatflowsinourveins]

Scope

Propose the W7 public architecture record for the GitHub estate: reusable foundation, generic private roles, staged native GitHub landing/release features, alternatives and measurable revisit conditions. The record remains proposed until the user's later acceptance.

• Base commit: fead5d8f8042f01ffc1a785f3b8ad6c410ccb506 (descends from required f3ebf469b).
• Lane: lane:foundation; the other lane's acknowledgement remains required before landing.
• Owned paths: docs/decisions/2026-10-05-github-estate-consolidation.md, plus its evidence-registry entry in the final commit.
• Draft gate: command-center Claude read of the exact head, one repair round and landing acknowledgement. A8-R5's passing owner-native field test is a separate A9 completion gate; its executable is requested and remains pending. The command center asks for user acceptance later.
• This is a separate task PR; Document NativeStack2604 evidence and distinguish old-bar readiness #715 remains unchanged on its Final architecture round 2 (wave 5): owners on the repository-quality rule, and NativeStack2604 plan rows for hcom, Chrome DevTools MCP, DSPy, SkillSpector, Inspect Scout and MCP conformance #713/final-E2E hold. Organization-gated campaign items remain pending.

SOTA sources

• adr/madr@4.0.0:template/adr-template.md: metadata, alternatives, outcome and confirmation; campaign additions are identified.
• GitHub merge queues and merge_group: organization availability and required merge-group CI qualification.
• GitHub concurrency, original github/docs@ddc34e6c:data/reusables/actions/actions-group-concurrency.md:15: default pending replacement versus queue: max, capacity and ordering limits.
• actions/dependency-review-action@a1d282b:README.md:57 and action.yml:25: upstream v5.0.0 runtime and explicit refs for non-PR events; no action is added by this PR.
• GitHub generated notes, immutable releases, gh release verify: reuse supported release features.
• native-agent-stack@fead5d8f:docs/lanes.md, .github/main-ruleset.json and scripts/host_receipts.py:register_file: existing boundary, interim snapshot and native registry maintenance.

Evidence-class table

Claim	Evidence class	Command / receipt
GitHub/MADR behavior and pinned interim policy	source_review	Original official documentation and pinned source read on 2026-10-05; no deployed queue/action acceptance
Metadata/hash/publication integrity	local_integration	python3 scripts/validate.py; actual final result recorded below
Generic private roles in public document	local_integration	Required negative git grep plus broader private-name check both returned1 with no output
Completeness of the proposed source/decision coverage	source_review	Bounded GPT critic; kept separate from the pending Claude-family read
A8-R5 field test	Pending	Owner's source/command requested; no substitute validator or passing verdict asserted
Architecture/user acceptance and host readiness	Pending/separate	Record remains proposed; new readiness requires final verified E2E

Local commands run

rtk git merge-base --is-ancestor f3ebf469b origin/main
0
rtk python3 -c 'from pathlib import Path; from scripts import host_receipts; host_receipts.register_file(Path("."), "docs/decisions/2026-10-05-github-estate-consolidation.md")'
0
rtk python3 scripts/validate.py
0 — final integrity/scope validation after documentary corrections:69 components,4 profiles,202 receipts,10105 hashed files; no live provider/GPU execution
rtk git diff --cached --check
0

The required campaign private-name expression and a broader private-name expression each returned1 with no output. Exact expressions are retained in the private coordination status so this public description also keeps private repository identities generic.

Decision record

docs/decisions/2026-10-05-github-estate-consolidation.md: proposed topology, three alternatives, landing/release phases, cleanup execution limits, review date and named sensors. Private inventory is maintained separately using the same proposed acceptance boundary.

Host evidence

No host receipt or platform-status change. No upstream/native runtime acceptance is claimed.

Checklist

• No workflows, action pins, credentials, hosting or billing settings changed.
• No user instructions quoted verbatim in committed text; private repository identities are generic in the public record.
• Peer worktrees and Document NativeStack2604 evidence and distinguish old-bar readiness #715 were preserved.
• Registry is the final commit; the command center refreshes it from main before landing.
• PR stays draft; no merge or user-acceptance claim.