Tool Governance
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Discovery of a tool does not authorize its effectful use; policy and confirmation requirements remain attached to the call.
The governed execution contract separates publication, discovery, proposal, policy evaluation, confirmation and dispatch. Publication or tool discovery is not authorization. A state-changing operation must not run until the relevant context, policy, evidence and confirmation conditions are met; confirmation must not dispatch it twice.
Engineering rules
- Evaluate authorization using the same execution context as the final dispatch.
- Keep a pending confirmation bound to one request and its typed arguments.
- Revalidate mutable conditions before confirming an effectful action.
- Record both rejection and execution outcomes for auditing and session continuation.
Chapter outline (original LaTeX headings)
- Authority Model
- Protocol-Neutral Execution Context
- Governed Action Metadata
- PendingConfirmation Semantics
- Reject
- Confirm
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/governed-agent-execution-contract.tex.