RFC-0015 · Reference catalog
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
Generated reference catalog. This page renders structured Lean data for RFC-0015: defined terms, diagnostics, dependencies, and invariants. It does not establish proof coverage or runtime conformance. The authored narrative lives in
RFC-0015.This page is generated from the
lean/Gnomon/Spec/module for RFC-0015. Edit that source and regenerate this catalog.
Title: Agent Runtime Binding
Status: draft
Owners: AI, Runtime
Diagnostic range: M01500-M01599
Proof citations in source: 16 / 16. Standalone proof verification is pending.
Definitions
(none defined)
Diagnostics
| Code | Severity | Description |
|---|---|---|
M01500 | Error | Agent write attempt targets field or entity outside declared permissions; invocation rolled back |
M01501 | Error | Health check probe returned non-2xx or timed out; dispatch aborted |
M01502 | Error | draft agent referenced by a binding in a bundle with ciState: ready |
M01503 | Error | Binding model: references a model whose roles does not include runtime-agent |
M01504 | Error | No binding resolved for agent in the active environment; action cannot dispatch |
M01505 | Error | All retry attempts exhausted for a transient dispatch failure |
M01506 | Error | Model response failed structural validation against agent’s declared output types |
M01510 | Error | binding declaration missing required property (agent:, environment:, or model:) |
M01511 | Error | Multiple bindings resolve to the same agent for the same environment tag (ambiguous binding) |
M01512 | Error | model: reference in binding cannot be resolved to a known model declaration |
M01513 | Warning | No healthCheck declared; endpoint liveness is not probed before dispatch |
M01514 | Warning | No retryPolicy declared; transient dispatch failures will not be retried |
M01515 | Warning | timeout: exceeds 120s; review whether a shorter timeout is appropriate |
M01516 | Error | Binding references a model declaration whose digest has changed since last activation; re-activation required |
M01517 | Warning | Binding environment: URI references an endpoint not on the platform allowlist of approved inference endpoints |
M01540 | Error | Dispatch rejected — circuit breaker is open; endpoint exceeded failure threshold |
M01541 | Warning | Action-level agentTimeout exceeds binding-level timeout: — action timeout has no effect; binding timeout is the ceiling |
Invariants
- A binding is invalid if its agent reference cannot be resolved to a known agent declaration in the bundle. (enforced by: compile-time)
- A binding’s model reference must resolve to a model whose roles include runtime-agent. (enforced by: compile-time)
- A draft agent must not be activatable in a bundle with ciState ready. (enforced by: compile-time)
- All writes within a single agent invocation are transactional; any permission or validation failure rolls back all of them. (enforced by: runtime)
- An agent must not invoke another agent directly; multi-agent workflows must pass data through the object graph via separate actions. (enforced by: runtime)
- Every agent invocation must produce an audit log entry committed in the same transaction as the object graph write. (enforced by: runtime + DB-transaction)
- Every write an agent attempts during execution must be covered by the agent’s declared permissions block; out-of-scope writes are rejected at the runtime boundary. (enforced by: runtime)
- For any agent and envTag pair, exactly one binding may be active in a given install plan. (enforced by: compile-time)
- The constructed prompt must not include data from gnomon instances outside the agent’s read scope, defaulting to deny when scope is indeterminate. (enforced by: runtime)
- The runtime must not write any portion of an agent’s output if any portion fails validation or permission checks. (enforced by: runtime)
Normative Statements
Statements are structured source data. Proof citations, where present, have not passed a standalone Gnomon proof gate.
Declaration Constraints
- MUST — A binding MUST specify an environment: URI and a model: reference.
- MAY — An agent MAY have zero or more bindings.
- MUST_NOT — An agent bound in an install plan with ciState: ready MUST NOT carry the draft modifier.
- MUST_NOT — Bindings MUST NOT be declared inside entity, flow, or policy blocks; they are top-level declarations. (proof citation:
rfc0015_b8_grounded; verification pending) - MUST — Every binding declaration MUST reference exactly one agent declaration via its agent: property. (proof citation:
rfc0015_b25_grounded; verification pending) - MUST — Every write the agent attempts MUST be covered by the agent’s declared permissions block; out-of-scope writes roll back the entire invocation atomically. (proof citation:
rfc0015_b5_grounded; verification pending) - MUST_NOT — Runtime MUST NOT dispatch to a binding whose health check has not returned a successful response.
- MUST — The model referenced in a binding MUST resolve to a model declaration that includes runtime-agent in its roles. (proof citation:
rfc0015_b32_grounded; verification pending)
Execution Protocol
- MUST — Before each write the runtime MUST verify target is within permissions, no escalation of asserted to inferred occurs, and no terminal/high-authority state is targeted. (proof citation:
rfc0015_b37_grounded; verification pending) - MUST — If a binding declares healthCheck, runtime MUST issue an HTTP GET to the resolved endpoint before proceeding.
- MUST_NOT — Prompt construction MUST NOT include data outside the agent’s declared permissions scope. (proof citation:
rfc0015_b0_grounded; verification pending) - MUST_NOT — Runtime MUST NOT retry dispatch to an unhealthy endpoint.
- MUST — Runtime MUST execute the dispatch steps in order; any failed step halts the sequence.
- MUST — Runtime MUST validate the model’s response against the output types declared in the agent’s outputs block. (proof citation:
rfc0015_b27_grounded; verification pending)
Goals
- MUST_NOT — Agents carrying the draft epistemic modifier MUST NOT be activatable in bundles with ciState: ready.
- MUST — Binding failure MUST produce a structured diagnostic and MUST NOT crash the runtime. (proof citation:
rfc0015_b16_grounded; verification pending) - MUST — Runtime MUST enforce that all agent writes fall within the agent’s declared permissions before any write reaches the object graph. (proof citation:
rfc0015_b34_grounded; verification pending)
Health Checking
- MUST — Health probe is an HTTP GET; status 200-299 is healthy, anything else or timeout is unhealthy; probe timeout fixed at 5 seconds.
Invariants
- MUST — All writes within a single agent invocation are transactional; a failure rolls back all of them.
- MUST — Every agent invocation MUST produce an audit log entry committed in the same transaction as the object graph write.
- MUST — For any (agent, envTag) pair, exactly one binding may be active in a given install plan.
- MUST_NOT — Runtime MUST NOT write any portion of an agent’s output if any portion fails validation or permission checks. (proof citation:
rfc0015_b21_grounded; verification pending)
Model Role Validation
- MUST — Compiler MUST verify the referenced model includes runtime-agent in its roles list at compile time. (proof citation:
rfc0015_b29_grounded; verification pending)
Permission Enforcement
- MUST_NOT — Agents MUST NOT escalate their own permissions via registry writes, rule injection, or producing values used to authorize further writes. (proof citation:
rfc0015_b42_grounded; verification pending) - MUST — Permission violation MUST cause atomic rollback of the entire agent invocation and MUST be recorded in the audit log.
- MUST — Runtime MUST treat the permissions list as a closed set; any write to a target not on the list MUST be rejected before reaching the object graph. (proof citation:
rfc0015_b3_grounded; verification pending)
Security
- MUST_NOT — Agents MUST NOT acquire write access beyond their permissions block through prompt injection, indirect rule-triggered writes, or binding reconfiguration. (proof citation:
rfc0015_b10_grounded; verification pending) - MUST_NOT — An agent MUST NOT invoke another agent directly; multi-agent workflows MUST pass data through the object graph via separate actions.
- MUST — Audit log entry for each agent invocation MUST be written in the same database transaction as the object graph write.
- MUST_NOT — Constructed prompt MUST NOT include data from gnomon instances outside the agent’s read scope; default to deny if scope is undeterminable. (proof citation:
rfc0015_b12_grounded; verification pending) - MUST — environment: URI MUST be validated at compile time against a platform allowlist of approved inference endpoints.
The binding Declaration
- MUST — binding-body must include agent:, environment:, and model:; absence produces M01510. (proof citation:
rfc0015_b19_grounded; verification pending)
draft Agents and Bundle Readiness
- MUST_NOT — An agent with the draft modifier MUST NOT be bound in a bundle with ciState: ready.
Linked References
(no cross-RFC dependencies)