governance/start-agent-session

To create a deterministic agent session record, you supply a bounded context, session_id, and title. The process writes a markdown file to runtime/contexts/<context>/sessions/, sets status to active, and adds a started_at timestamp for governance tracking.

A bounded context isolates agent activity within a specific domain boundary for governance and audit tracking. You need it when establishing deterministic session anchors to ensure safe path segments, prevent file collisions, and maintain accurate telemetry records.

Yes, you can optionally log agent session telemetry by emitting a U.Work log entry via telemetry/log-work when the module is available, capturing initiation details and agent metadata alongside the session record creation.

You anchor governance decisions and handoffs by supplying an optional capability reference and a decisions list when starting the session. This links the session record to specific governance rules and documented handoff points.

No external dependencies are required to start an agent session. The core functionality validates inputs, ensures safe path segments, and creates directories as needed. Telemetry logging is optional and only activates if the telemetry/log-work module is present.

Limitations include strict input validation for safe path segments to prevent collisions or overwrites, meaning malformed context or session_id values will be rejected. Additionally, automatic U.Work telemetry logging only functions if the telemetry/log-work module is available.