governance/check-roc-compliance

To audit session activity against a Rule of Constraints policy, provide the context, session ID, and RoC file path. The skill validates inputs, loads the RoC file, and generates a deterministic Markdown report highlighting policy violations and recommended outcomes.

A Rule of Constraints compliance report evaluates bounded context sessions against defined policy requirements. It identifies non-compliant actions and surfaces policy gaps, producing a timestamped Markdown file to support governance audits and session traceability.

To generate a compliance report for a specific session, invoke the audit with the required context, session ID, and RoC file path. The system writes a timestamped Markdown report under the runtime contexts directory for that bounded context.

Yes, you can log RoC compliance audits for observability. When telemetry is available, the skill emits a U.Work record alongside the Markdown report to support audit traceability and governance tracking.

Checking RoC compliance requires three inputs: the bounded context, the session ID, and the RoC file path. The skill validates these parameters before loading the policy and producing the compliance report.

No, you do not need telemetry enabled to run a policy-driven audit. Telemetry is optional; the skill produces the compliance report regardless, but only emits a U.Work log entry when telemetry is available.