Macro-2 Channel Non-Authority Register — R2-B2 (2026-06-19)
Macro-2 Channel Non-Authority Register — R2-B2
Date: 2026-06-19 · Workstream: R2-B2-MACRO-2-OWNER-DECISION-PREREQ-CLOSURE-READINESS-2026-06-19 (Deliverable 11 of 45) · Editorial revision: rev1
Class: channel non-authority register · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO channel selected · NO write performed.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision/
content_lengthauthoritative at read time; not pinned here.
Non-authority lock. This register makes explicit that no channel is selected as authority anywhere in Macro-2, and fixes the allowed vs forbidden channel language.
CHANNEL_AUTHORITY_DRIFT→ HOLD.
0. Status and non-authorization
STATUS: PASS — engineering / control. A register asserting channel non-authority and the language boundary. It selects nothing.
Engineering PASS ≠ authority PASS. Default disposition: HOLD. No channel selected/wired/installed/promoted; no DB write/DDL/DML; no TD; no blocker resolved; v0.1 not overwritten; v0.2 not authority.
Evidence basis — design synthesis of Deliverables 6–10. Reading discipline: main process, no reader-agents.
1. Purpose
Guarantee, in one auditable place, that the channel work (Deliverables 6–10, 12) stays recommendation-only and never crosses into selection.
2. Sources / evidence read
Deliverables 6–10, 12; the macro Channel lock (prompt §"Channel lock"). Read directly, main process.
3. Accepted baseline (carried)
R2-D2 channel work is recommendation-only unless the Owner decides outside this macro. No channel selected/wired; no cron created; no agent-api contract promoted; no pg_cron installed; no queue worker enabled.
4. Allowed vs forbidden channel language
| Allowed (used in Macro-2) | Forbidden (would trigger CHANNEL_AUTHORITY_DRIFT) |
|---|---|
RECOMMENDATION_ONLY |
"Selected channel: …" |
NOT AUTHORITY |
"Use this channel" |
OWNER_GATE_REQUIRED |
"Implement this channel" |
FUTURE_TECHNICAL_DESIGN_REQUIRED |
"Wire this channel" |
| "candidate" / "future-gated" / "rejected as standing channel" | "Promote this channel" |
5. Channel non-authority register
| Channel action | Performed in Macro-2? | Status |
|---|---|---|
| Channel selected as authority | No | forbidden now |
| host cron wired / cron entry created | No | forbidden now |
agent-api contract bound / promoted DRY_RUN→REAL_RUN |
No | forbidden now |
| pg_cron installed | No | forbidden now |
| job_queue worker / master switch enabled | No | forbidden now |
| Any channel-specific command/spec written | No | forbidden now (FUTURE_TD) |
Reading. Macro-2 compares and recommends channels (Deliverables 6–10, 12) and selects none. CHANNEL_AUTHORITY_DRIFT not triggered.
6. Owner-gated future work
Selecting/wiring/installing/promoting any channel is the Owner's gated act; all forbidden now.
7. What remains unresolved
- No channel selected; substrate fail-closed.
- Blockers — all OPEN.
8. Ready for GPT/Codex review
Yes — as the channel non-authority register.
Core rule: no channel is selected as authority anywhere in Macro-2; the language boundary is fixed; CHANNEL_AUTHORITY_DRIFT not triggered.
Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.