John Agent Replacement Plan — Current Reconstructed

John Replacement Plan — Reconstructed Current Plan

Status: CURRENT_RECONSTRUCTED_PLAN_PENDING_CEO_SIGNOFF
Date: 2026-05-23
MC: #10599
Replaces: tombstone/stale marker created 2026-05-23 after the original file was absent.
Primary evidence ledger: /tmp/claude-code-fresh-claim-gate-final-20260523.md

0. Executive decision

Do not replace John by adding more advisory agents. Replace the unsafe behavior with deterministic, fail-closed enforcement at every output/delegation boundary:

  1. Claude Code Stop hooks.
  2. Claude Code PreToolUse delegation hooks.
  3. Shared claim classifier.
  4. Pi extension output boundary.
  5. Virtual-company agent-runner.js response boundary.
  6. Company Mesh response boundary.
  7. Evidence-path and cost gates before large workflows.

Memory, HiveMind, RAG snippets, old state, and peer recollection are advisory only and must never be treated as evidence for ALAI/MC/system-state claims.

1. Current implemented foundation

Claude Code boundary

Current /Users/makinja/.claude/settings.json includes these enforcement hooks:

Current wrapper behavior:

Shared claim gate

/Users/makinja/system/tools/alai-claim-gate.js blocks factual/system-state claims without evidence. Current violation anchors include:

Pi boundary

Virtual-company boundary

2. Evidence already obtained

Evidence artifacts:

Key fresh Claude Code evidence:

3. Replacement architecture

3.1 John core behavior

John may answer factual ALAI/MC/system-state questions only after tool verification. If current evidence is absent, John must answer one of:

John must not claim:

unless a same-turn tool or cited existing evidence path supports it.

3.2 Enforcement-first design

The replacement is not a persona rewrite. It is a boundary system:

  1. Prompt intake: boot/checklist freshness gate.
  2. Tool dispatch: delegation cannot proceed without MC reference.
  3. Assistant final output: Claude Stop hooks block unsupported claims.
  4. Pi final output: Pi extension blocks unsupported claims hard by default.
  5. Agent output: agent-runner.js blocks before response is saved/printed.
  6. Mesh output: company-mesh.js blocks before DB write.
  7. Evidence retry: existing evidence path can allow claims when the path exists.

3.3 Advisory-source quarantine

Every prompt or worker context must include this contract:

Memory, HiveMind, RAG snippets, old state, and peer recollection are ADVISORY_NOT_EVIDENCE for ALAI, MC, deployment, hook, workflow, agent, production, or task-status claims.

4. Blueprint MUST gate

Blueprint MUST workflows may start only if all conditions are true:

  1. Fresh Claude Code claim-gate smoke has passed.
  2. Missing-transcript/no-session bypass is fail-closed.
  3. Pi and virtual-company output gates are hard or explicitly waived.
  4. Cost review has been done for the current day/session.
  5. User explicitly approves the run or provides a written waiver.
  6. The workflow is run through a wrapper/checklist, not free chat.

Current state as of this reconstruction:

5. Implementation phases

Phase A — Completed hardening baseline

Phase B — Immediate next local work

  1. Validate syntax for modified code.
  2. Validate these reconstructed specs exist and are not tombstones.
  3. Create an evidence artifact for the reconstruction.
  4. Do not mark MC #10599 or #10570 complete without CEO sign-off and any required commit/indexing evidence.

Phase C — Optional commit/index/sign-off work

Only after approval:

  1. Commit or otherwise persist changed source files.
  2. Index summary into approved memory mechanism if required.
  3. Update MC #10599/#10570 status with evidence paths.
  4. Run blueprint MUST wrapper/checklist if cost approval exists.

6. Risk controls

7. Open acceptance items


Revision #1
Created 2026-05-23 11:45:10 UTC by John
Updated 2026-05-23 11:45:10 UTC by John