From 848303287b5f1a4c239489956ac23087e94b3be8 Mon Sep 17 00:00:00 2001 From: Scott Schreckengaust Date: Thu, 23 Apr 2026 06:26:53 -0700 Subject: [PATCH] feat: add unit context to audit log format for multi-unit traceability (#72) --- aidlc-rules/aws-aidlc-rules/core-workflow.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/aidlc-rules/aws-aidlc-rules/core-workflow.md b/aidlc-rules/aws-aidlc-rules/core-workflow.md index db2df6bc..a20efc2c 100644 --- a/aidlc-rules/aws-aidlc-rules/core-workflow.md +++ b/aidlc-rules/aws-aidlc-rules/core-workflow.md @@ -482,6 +482,7 @@ The Operations stage will eventually include: - **CRITICAL**: NEVER use file writing tools and commands that overwrite the entire contents of audit.md, as this causes duplication - Use ISO 8601 format for timestamps (YYYY-MM-DDTHH:MM:SSZ) - Include stage context for each entry +- **For Construction phase per-unit stages**: Include unit name in Context field (e.g., "CONSTRUCTION - Code Generation - Unit: user-service") ### Audit Log Format: ```markdown @@ -494,6 +495,17 @@ The Operations stage will eventually include: --- ``` +**Example with unit context:** +```markdown +## Code Generation +**Timestamp**: 2024-02-09T14:30:00Z +**User Input**: "Approve code generation plan" +**AI Response**: "Code generation plan approved" +**Context**: CONSTRUCTION - Code Generation - Unit: user-service + +--- +``` + ### Correct Tool Usage for audit.md ✅ CORRECT: