cos-runtime-development

To add an intent kind to the CoS runtime, you extend the ADK scaffold within existing node pipeline boundaries like intent analysis and context assembly, then update validation tests and documentation for the new intent behavior.

You wire MCP tools to the CoS runtime by connecting evidence queries and session routes to existing Meridian integration contracts, ensuring the pipeline preserves advisory-only behavior without mutating evidence source-of-truth state.

The CoS runtime node pipeline converts operator intents into traceable outcomes through sequential stages: intent analysis, context assembly, evidence aggregation, recommendation synthesis, decision preparation, and trace emission.

Yes, you can wrap the CoS runtime in an HTTP host to expose workstation API routes, connecting decision and session endpoints while satisfying ADK pipeline boundary constraints and maintaining advisory-only state behavior.

The CoS runtime enforces advisory-only behavior for evidence and state, meaning you cannot mutate ledger source-of-truth data, and all edits must remain confined to existing node boundaries to satisfy ADK pipeline constraints.

Yes, when API surfaces or configuration keys change, you must update CoS runtime documentation and add or modify node-level tests to keep behavior discoverable and prevent configuration drift.