telemetry/log-work

To log auditable work events, you generate a dated U.Work Markdown record capturing who performed the action, when, and with which inputs and outputs. This creates structured traceability for QA, governance, and post-hoc analysis.

A U.Work record is a timestamped Markdown file documenting the execution of a specific method by a designated performer. You need it when you require auditable traceability of real-time actions across bounded contexts.

You create a structured work log by binding required inputs—method, role_assignment, context, and action—plus optional agent metadata and outputs. The skill writes a timestamped Markdown file under your context's telemetry work directory.

Yes, this logging approach applies to manual tasks, pipeline runs, and any bounded context activity. It captures time windows, evaluated state changes, resources used, and outcomes to support accountability and KPI calculations.

Markdown files for structured telemetry logging are basic artifacts written to a local runtime directory. They do not require external dependencies but are limited to file-based storage without built-in database indexing or query capabilities.

No, the work log skill requires no external dependencies or components. It generates timestamped Markdown files directly within your runtime contexts and optionally emits telemetry if configured.