workflow/respond-to-approval

To record an approval decision for auditability, you log the decision, responder, notes, and timestamps into a structured markdown file under runtime/contexts/<context>/approvals/. The skill also emits a U.Work record for telemetry when available.

Yes, you can log approval responses across multiple sessions by applying the skill within bounded contexts. It organizes records under runtime/contexts/<context>/approvals/ to maintain governance and traceability for each specific session.

When logging an approval response, you need to provide the context, session_id, approval_id, decision, and the responder identity. The skill validates these inputs and ensures safe path segments before writing the markdown record.

Yes, the skill automatically emits a U.Work record for approval decisions when telemetry or log-work capabilities are available. This maintains a continuous activity trace alongside the stored markdown audit file.

The best way to maintain audit trails for workflow approvals is to consistently capture decisions, responder identities, and timestamps in structured files. This skill standardizes that process, ensuring compliance and traceability across bounded contexts.