Stage 2Let the bot draft — don't do the typing yourself
Every bot runs a Tier-1 Read/Analyze flow by default. Nothing goes out. The output is a draft, a plan, a diagnosis — reviewable before anything commits.
What the draft includes by default: cited sources (cited_sources JSON array · verifiable URIs), the model profile used, the recursion depth observed, a trace ID you can look up in the Audit Trail.
Stage 3Approve the Tier-2 move — the one that matters
Anything that mutates the outside world — sending a message, signing a doc, triggering a payment, posting a tweet — is a Tier-2 Write/Transact move. That one pauses at a Telegram inline button. Your tap is the gate.
Draft
The bot shows you the exact payload: recipient, body, amount, timing. Nothing is sent yet.
Prompt
A Telegram Approve or Reject button pair appears under the message. Each approval is a signed, single-use HMAC token bound to your user + the action + the body hash.
Approve
You tap. The policy proxy verifies the token is unexpired and not replayed, then forwards the call upstream. Logged as TIER2_HUMAN_APPROVED in evokaf_telemetry_stream.
Reject
The agent discards the draft; the event logs as HUMAN_REJECTED. No retry without a fresh draft.
No tap
Nothing happens — ever. The token expires. fail-closed
Kill switch: at any time, in any bot, type /freeze. That agent's is_frozen flips to 1 and every request returns BLOCKED_KILL_SWITCH until you unfreeze. Global freeze is a single row flip in clow_global_state.
Stage 4Compound — the flywheel that pays you back
Each session feeds a trajectory store the next session reads from. The same bot gets sharper at your work — not everyone's.
Weekly
ARM dashboard
Acquire · Retain · Monetize. One screen: new, D7-active, D30-active, MRR. Open /analytics.
Monthly
Audit Pass Certificate
Each promoted SKILL.md genome ships a signed certificate (ASR, held-out hash, chain head, QDefence scan).
Quarterly
EvoSkillOpt promotion
Mutations earn promotion only through the externally graded Q-Gate: 13 tests × 5 repeats, held-out suite rotated monthly.
Always-on
Agent BOM
Public /agent-bom.json — Ed25519 signed. Verify offline. The manifest is the proof of what you're running.
Your compounding move: once a month, review the ARM dashboard. Pick one bot whose D7 retention is below 25%. Run /launch on the use case that bot is strongest at, and share one deliverable publicly. That's the whole loop.