Inputs
- Proposed action and arguments from a registered agent or tool
- Signed permit from Gatekeeper
- Action digest and declared scope
Runtime and execution
NARG
Propose is not dispatch.
Runtime action mediation for registered agent and tool actions, separating a proposal from a dispatched effect.
Responsibility
What NARG is responsible for
NARG (the NiGeNje Agent Runtime Guard) mediates registered agent and tool actions. It verifies a permit for the specific action, keeps the proposal separate from dispatch, performs its own effect read-back, and reports unknown rather than success when it cannot confirm the outcome.
The runtime is where governance either exists or becomes a suggestion. NARG places an explicit decision boundary between an agent proposing an action and a tool receiving it. The action digest is bound to the permit, so an altered payload cannot ride on an earlier approval.
NARG is deliberately not a universal interceptor. It protects registered mediation points. Direct sockets, shell commands and unwrapped filesystem writes are outside its boundary, and the platform says so rather than implying host-level enforcement.
Lifecycle position
Where it sits in the governance lifecycle
Stage numbering is canonical across the site. Open the interactive lifecycle to see every component with responsibilities at each stage.
Runtime mediation
Verify the permit against the exact action.
Execution
Apply the effect through a controlled adapter.
Verified capabilities
What is verified today
Capabilities are drawn from the product register. Each one is bounded by the limitations stated further down this page.
- Registered action mediation with proposal and dispatch separated
- Permit verification bound to action and arguments
- Replay protection and single-use permit enforcement
- Effect read-back before reporting success
- Unknown outcome reported as unknown, never as success
Outputs
- DISPATCHED or REFUSED result
- Effect observation result
- Audit chain entries for the mediated action
Evidence and maturity
What the evidence supports
Maturity describes verified engineering evidence in a bounded environment. It is not a production-readiness statement.
Maturity note
Registered mediation, permit verification, replay protection and altered-payload refusal were exercised in a recorded dispatch, and the audit chain verified afterwards. NARG is classified EXCLUDED_NO_GO in the release-candidate manifest, with finding F-01 open and its suite not re-run in this review; current read routes are auth-gapped.
Not production-qualified
This label describes verified engineering evidence only. No production deployment, certification, benchmark or customer outcome is claimed.
Evidence recorded
- Recorded dispatch: SUCCEEDED only after NARG's own effect read-back; replay left the result digest unchanged.
- Altered payload refused with GATEKEEPER_PERMIT_ACTION_MISMATCH; audit chain VERIFIED.
- NARG is driven end to end for a newly authored intent in the 2026-10-26 intent chain record.
- Release-candidate component manifest: NARG EXCLUDED_NO_GO; F-01 open.
Dependencies
- Gatekeeper
- Substrate
- Control Plane
- audit ledger
Dependencies are stated as the product register records them. A dependency is not automatically production-qualified; see its own product or component page for its maturity and limitations.
Limitations
What this product does not do (yet).
Limitations are stated before the evaluation questions so they cannot be missed, downplayed or treated as future-work footnotes.
Limitations — read before evaluating
- Protects registered mediation paths only: it does not intercept direct sockets, shell commands or unwrapped filesystem writes, and provides no agent sandbox.
- Excluded as NO-GO from the release-candidate manifest; finding F-01 is open and the suite was not re-run in the current review.
- Current read routes are auth-gapped in the reviewed deployment.
- Effect observation is performed by NARG itself; a separate third-party observer was not built.
No capability on this page should be read as production qualification. If a limitation is material to your use case, it belongs in the evaluation scope — not after it.
Relationship to the platform
How it fits
NARG is the runtime enforcement point for registered actions. Gatekeeper decides, NARG enforces, Substrate executes and NARG verifies the effect before the Control Plane reconciles it.
Evaluation questions
- Which of your tool calls would be routed through registered mediation?
- What happens to actions that bypass the mediation point entirely?
- How is an altered payload detected between proposal and dispatch?
Next step
Evaluate NARG against a real control problem.
Bring a system boundary, an action class and a failure mode. The first step is to agree what should be governed and what evidence would count.