Module intent_realization 

The intent_realization module: which work realises which intent, and why an intent stands where it stands.

Two read-only capabilities over crate::intent_realization. intent_realization.work joins this checkout’s ledger tasks (with every episode, provider and handover), the shared layer’s closed session records and the peer board to the intents, each link carrying its provenance, and reports each intent’s unmet criteria and drift. intent_realization.explain answers one intent: the sentences its stage rests on, the plan’s coverage of its criteria and the work realising it. Nothing is stored: a session ending or a provider changing moves no intent, because no intent state was ever held by either (ADR 0075).

use majordomus_cli::capability::builtin::intent_realization;
let m = intent_realization::module();
let ids: Vec<&str> = m.capabilities.iter().map(|e| e.capability.id.as_str()).collect();
assert_eq!(ids, ["intent_realization.work", "intent_realization.explain"]);

Structs

IntentExplainInput

Which intent to explain, by the id that is also its file name.

IntentRealizationInput

Which intent to answer the realization of; every intent when absent.

Functions

module

The module the registry composes: two read-only capabilities over one join, each declared once here and projected to the command line, HTTP, MCP and OpenAPI from that declaration.