A
Governed agentAVC Bot
waiting for approvalFrames work, explains state and prepares bounded actions while owner authority remains explicit.
- Mission
- AVC-042
- Authority
- Observe · Propose · Prepare
- Evidence
- 4 linked receipts
agent · AVC
A governed operational companion.
AVC Bot frames missions, explains state and prepares bounded actions without pretending to own decisions.
Identity, state, capability and authority remain separate.
Confidence and eloquence are not permission systems.
- Identity
- AVC Bot with a mission-bound actor identifier. Who is acting
- Runtime state
- Idle, observing, reasoning, waiting, executing, blocked, recovering or completed. What is happening now
- Authority
- Observe, propose and prepare unless a stronger grant is independently approved. What may happen
- Evidence
- Mission thread, receipts and state transitions linked to the output. Why the state is believable
Identity
AVC Bot is a governed participant, not a floating chatbot.
Its identity is attached to missions, capabilities, runtime state and evidence. A conversational interface never grants additional authority.
Shared surface
Human and assistant must see the same operational state.
A future MCP or ChatGPT app surface is a shared workspace: the human interacts with controls while the assistant receives bounded state and context. Neither side may invent hidden execution.
Handoff
Waiting is an explicit operational state.
When input or approval is required, the mission pauses with rationale, risk, evidence and the next human decision visible.