Macro-2 Agent-API Decision Memo — R2-B2 (2026-06-19)
Macro-2 Agent-API Decision Memo — R2-B2
Date: 2026-06-19 · Workstream: R2-B2-MACRO-2-OWNER-DECISION-PREREQ-CLOSURE-READINESS-2026-06-19 (Deliverable 8 of 45) · Editorial revision: rev1
Class: agent-api decision-readiness memo · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · RECOMMENDATION_ONLY — NOT AUTHORITY · NO contract promotion · NO channel selected · NO write performed.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision/
content_lengthauthoritative at read time; not pinned here.
Agent-api lock. Decision-readiness for the agent-api executor as a candidate channel. Promotes no contract (
DRY_RUN→REAL_RUN), enables no switch, selects no channel, couples the birth lane to no other lane.RECOMMENDATION_ONLY — NOT AUTHORITY — OWNER_GATE_REQUIRED — FUTURE_TECHNICAL_DESIGN_REQUIRED.
0. Status and non-authorization
STATUS: PASS — engineering / decision-prep. A decision-readiness memo for the agent-api executor: fresh state, strengths, risks, proof obligations. It promotes no contract and selects nothing.
Engineering PASS ≠ authority PASS. Default disposition: HOLD. No contract promotion; no switch flip; no channel selection; no DB write/DDL/DML; no TD; no blocker resolved; v0.1 not overwritten; v0.2 not authority.
Evidence basis — FRESH_READONLY_EVIDENCE (2026-06-19 RQ-13/16/17) + OOB (transient master-switch). Reading discipline: main process, no reader-agents.
1. Purpose
Answer macro question 3 (agent-api half) — can the agent-api executor be recommended more strongly without becoming authority? — as a decision-readiness memo.
2. Sources / evidence read
The 30-file agent-api recheck; the Mega-Gate host-cron-vs-agent-api brief; R2a §3–§5 (executor not bound to any birth DOT); the R1/KG cross-check (per-DOT, no lane coupling); the fresh RQ-ledger. Read directly, main process.
3. Accepted baseline (carried)
agent-api executor = candidate; the proven KG-EXPLAIN dispatch mechanism; not bound to any birth DOT; master switches OFF.
4. Evidence / analysis (FRESH 2026-06-19)
- container
incomex-agent-api-executorUp 2 weeks (healthy),8090->8090/tcp(RQ-17). dot_agent_api_contract= 2 rows:DOT_KG_EXPLAIN(explain/producer/DRY_RUN/endpoint_bound) +DOT_KG_EXPLAIN_VERIFY(verify/verifier/VERIFY_ONLY/contract_ready); 0 birth-bound (RQ-16).- master switches:
process_dot_runtime.execute_enabled=false,.real_run_enabled=false,.dry_run_only=true(RQ-13). - transient session switch value unreadable (OOB; not overclaimed).
Strengths (for the Owner to weigh, not a selection): governance-aligned — contract-bound, observable, Điều-32-promotable; an existing healthy runner; the contract pattern is proven (KG-EXPLAIN pilot).
Risks/cons: shared infra (also serves the KG lane — a birth binding must be per-DOT so the lanes stay decoupled, X-7); currently fail-closed (switches OFF; a DRY_RUN→REAL_RUN promotion is itself Owner-gated); transient switch value OOB.
5. Decision-readiness result (recommendation-only)
The agent-api executor is a strong candidate on governance alignment/observability, weaker on shared-infra isolation and the extra promotion gate. Stronger framing ≠ selection. Read-only first obligation met (contract rows + persisted switches readable; 0 birth-bound, switches OFF); remaining obligations (per-DOT binding, dispatch run, no-lane-coupling proof, transient-switch confirm) are write-gated/OOB after selection. No contract promoted; no channel selected. OWNER_DECISION_REQUIRED.
Proof obligations before agent-api could be used (Owner-gated): (AA-1) S2 owner assigned; (AA-2) a per-DOT birth contract bound (no KG-lane coupling); (AA-3) DRY_RUN→REAL_RUN promotion under Điều 32; (AA-4) transient master-switch confirmed OOB; (AA-5) dispatch run + per-run S7 evidence.
6. Owner-gated future work
| Future work | Gate | Forbidden now? |
|---|---|---|
| Bind a birth DOT to the executor | Điều 32 + S2 owner | Yes |
Promote contract DRY_RUN→REAL_RUN / flip master switch |
Điều 32 + master-switch flip | Yes |
| Confirm transient master-switch | Owner out-of-band (read-only) | Yes (not done here) |
7. What remains unresolved
- Executor 0 birth-bound; switches OFF; transient layer OOB.
- Shared-infra coupling guarded by per-DOT contracts — confirmed, not built.
- Blockers — all OPEN.
8. Ready for GPT/Codex review
Yes — as an agent-api decision memo.
Core rule: agent-api = candidate, governance-aligned, healthy :8090 but 0 birth-bound + switches OFF (FRESH); recommended-more-strongly as a comparison, not a selection; no contract promoted, no channel selected.
Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.