gaia-framework 1.64.0 → 1.65.1

package/_gaia/lifecycle/workflows/4-implementation/sprint-planning/instructions.xml

@@ -19,6 +19,7 @@
     - NOT SELECTABLE: stories with files but status ≠ 'ready-for-dev' → "Story {key} is in '{status}' status — must be 'ready-for-dev' to be selectable. Run /gaia-validate-story {key} first."
   </action>
   <action>Display the classification to the user: selectable stories table (Key | Title | Priority | Size | Risk | Status) and non-selectable stories with reasons.</action>
+  <action>Priority flag scan: scan all selectable story files for priority_flag: "next-sprint" in their YAML frontmatter. If any flagged stories are found, display them with a visual indicator: "FLAGGED FOR NEXT SPRINT: Story {key} — {title} (priority_flag: next-sprint). This story was flagged by the add-feature workflow for priority inclusion." List all flagged stories before story selection begins so the scrum master is aware.</action>
   <action>Load most recent retro-{sprint_id}.md from {implementation_artifacts}/ if available</action>
   <action>If retro found: extract open action items — carry forward as sprint constraints or tasks. Present to user: "Previous retro action items to carry forward:" with status of each.</action>
 </step>
@@ -48,12 +49,14 @@
   <action>Priority surfacing: after story selection, check for P0 stories that are 'ready-for-dev' but were NOT selected. If any found, display: "WARNING: The following P0/critical stories are ready but not selected for this sprint:" followed by the list with their sizes. Ask user to confirm they intentionally excluded these high-priority stories.</action>
   <action>If {test_artifacts}/test-plan.md exists: apply risk levels to story selection — buffer 20% for high-risk stories in velocity estimate</action>
   <action>ATDD check (high-risk ONLY): for each story with risk = high, check if {test_artifacts}/atdd-{story_key}.md exists. If missing, add a sprint risk note: "HIGH-RISK story {key} has no ATDD file — run /gaia-atdd {key} before development." Do NOT flag medium or low risk stories — ATDD is required only for high-risk stories.</action>
+  <action>Auto-include flagged stories: after initial story selection, check if any SELECTABLE stories have priority_flag: "next-sprint" in their frontmatter but were NOT yet selected. For each such story: check remaining sprint capacity (velocity_capacity minus currently selected points). If the flagged story fits within remaining capacity, auto-include it in the sprint selection and inform the scrum master: "AUTO-INCLUDED: Story {key} — {title} (priority_flag: next-sprint, {points} pts). Flagged story auto-included — capacity allows." If the flagged story does NOT fit within remaining capacity, alert the scrum master for manual decision: "CAPACITY ALERT: Flagged story {key} — {title} ({points} pts) cannot be auto-included — insufficient capacity ({remaining} pts remaining). Include anyway (will exceed velocity) or defer to next sprint?"</action>
 </step>
 <step n="5" title="Update Story Files">
   <action>For each selected story that has an individual file in {implementation_artifacts}/: update the sprint_id field to "sprint-{N}"</action>
   <action>For each selected story: invoke status-sync protocol to assign the sprint — keep status as 'ready-for-dev' (do NOT change to backlog). Stories remain ready-for-dev until /gaia-dev-story transitions them to in-progress.
     <invoke-protocol ref="status-sync" story_key="{story_key}" new_status="ready-for-dev" sprint_id="sprint-{N}" source_workflow="sprint-planning" />
     Note: sprint-status.yaml may not exist yet at this point (created in Step 8) — the protocol will skip the sprint-status.yaml update if the file doesn't exist.</action>
+  <action>Clear priority flag on sprint assignment: for each selected story that has priority_flag: "next-sprint" in its frontmatter, set priority_flag back to null. This prevents the flag from persisting after the story has been assigned to a sprint. The flag is a one-time scheduling hint — once the story is sprint-assigned, it is no longer needed.</action>
   <action>Include all modified story files in the checkpoint files_touched with sha256 checksums</action>
 </step>
 <step n="6" title="Optional: Mobile Testing">

package/_gaia/lifecycle/workflows/4-implementation/sprint-planning/workflow.yaml

@@ -2,12 +2,14 @@ name: sprint-planning
 description: 'Generate sprint plan from epics and stories'
 module: lifecycle
 agent: sm
+val_validate_output: true
 template_output_prompt: "auto"
 config_resolved: "{installed_path}/.resolved/sprint-planning.yaml"
 config_source: "{project-root}/_gaia/lifecycle/config.yaml"
 installed_path: "{project-root}/_gaia/lifecycle/workflows/4-implementation/sprint-planning"
 instructions: "{installed_path}/instructions.xml"
 validation: "{installed_path}/checklist.md"
+template: "{project-root}/_gaia/lifecycle/templates/sprint-plan-template.md"
 input_file_patterns:
   epics:
     whole: "{planning_artifacts}/epics-and-stories.md"

package/_gaia/lifecycle/workflows/4-implementation/triage-findings/workflow.yaml

@@ -2,6 +2,7 @@ name: triage-findings
 description: 'Triage development findings into backlog stories'
 module: lifecycle
 agent: sm
+val_validate_output: true
 config_resolved: "{installed_path}/.resolved/triage-findings.yaml"
 config_source: "{project-root}/_gaia/lifecycle/config.yaml"
 installed_path: "{project-root}/_gaia/lifecycle/workflows/4-implementation/triage-findings"

package/_gaia/lifecycle/workflows/4-implementation/val-refresh-ground-truth/checklist.md

@@ -42,6 +42,21 @@ validation-target: 'Ground truth refresh workflow'
 - [ ] ground-truth-management sections loaded JIT
 - [ ] Sections: full-refresh, incremental-refresh, entry-structure, conflict-resolution, token-budget
 
+## --agent Parameter (E9-S11)
+- [ ] workflow.yaml declares agent parameter with flag --agent and allowed values [val, theo, derek, nate, all]
+- [ ] Default agent is val (backward compatible — no --agent behaves identically to pre-E9-S11)
+- [ ] Invalid agent names produce clear error with valid values list
+- [ ] Per-agent sidecar initialization creates missing ground-truth.md for any Tier 1 agent
+- [ ] Theo inventory scans filesystem structure + architecture.md
+- [ ] Derek inventory scans prd.md + epics-and-stories.md + sprint-status.yaml
+- [ ] Nate inventory scans sprint-status.yaml + story files in implementation-artifacts/
+- [ ] Val inventory uses existing 6-target scan (unchanged)
+- [ ] Decision log entries route to target agent's own decision-log.md
+- [ ] Per-agent ground_truth_budget enforced (Val 200K, Theo 150K, Derek 100K, Nate 100K)
+- [ ] --agent all runs val → theo → derek → nate sequentially
+- [ ] --agent all continues on per-agent failure and reports which succeeded/failed
+- [ ] --agent all presents combined summary with per-agent status
+
 ## Integration
 - [ ] Manifest entry exists in workflow-manifest.csv
 - [ ] Works identically standalone or as sub-step

package/_gaia/lifecycle/workflows/4-implementation/val-refresh-ground-truth/instructions.xml

@@ -7,95 +7,166 @@
   <mandate>Behavior must be identical whether called standalone or as sub-step from another workflow</mandate>
 </critical>
 
-<step n="1" title="Initialize Validator Sidecar">
-  <action>Check if {memory_path}/validator-sidecar/ directory exists</action>
-  <action if="directory missing">Create {memory_path}/validator-sidecar/ directory</action>
-  <action if="ground-truth.md missing">Create {memory_path}/validator-sidecar/ground-truth.md with empty header containing last-refresh timestamp set to "never"</action>
-  <action if="decision-log.md missing">Create {memory_path}/validator-sidecar/decision-log.md with header: "# Val Decision Log" and empty entries</action>
-  <action if="conversation-context.md missing">Create {memory_path}/validator-sidecar/conversation-context.md with header: "# Val Conversation Context" and empty rolling state</action>
+<step n="1" title="Resolve Agent Target">
+  <action>Parse $ARGUMENTS for --agent value. If --agent is absent, default to "val" for backward compatibility.</action>
+  <action>Validate agent name against allowed values: val, theo, derek, nate, all.
+    If the agent name is not in the allowed values list: HALT with error:
+    "Unknown agent '{agent_name}'. Valid values: val, theo, derek, nate, all."</action>
+  <action>Resolve target sidecar path and inventory source files based on agent:
+    - val: sidecar = {memory_path}/validator-sidecar/, inventory = 6-target scan (existing)
+    - theo: sidecar = {memory_path}/architect-sidecar/, inventory = filesystem structure + {planning_artifacts}/architecture.md
+    - derek: sidecar = {memory_path}/pm-sidecar/, inventory = {planning_artifacts}/prd.md + {planning_artifacts}/epics-and-stories.md + {implementation_artifacts}/sprint-status.yaml
+    - nate: sidecar = {memory_path}/sm-sidecar/, inventory = {implementation_artifacts}/sprint-status.yaml + story files in {implementation_artifacts}/
+    - all: run sequentially for val, theo, derek, nate (see Step 13)</action>
+  <action if="agent == all">Set agent_queue = [val, theo, derek, nate]. Proceed to Step 13 for orchestration.</action>
 </step>
 
-<step n="2" title="Determine Refresh Mode">
+<step n="2" title="Initialize Agent Sidecar">
+  <action>Check if the resolved target sidecar directory exists (e.g., {memory_path}/validator-sidecar/ for val, {memory_path}/architect-sidecar/ for theo, {memory_path}/pm-sidecar/ for derek, {memory_path}/sm-sidecar/ for nate)</action>
+  <action if="directory missing">Create the resolved sidecar directory</action>
+  <action if="ground-truth.md missing">Create ground-truth.md in the resolved sidecar directory with empty header containing last-refresh timestamp set to "never"</action>
+  <action if="decision-log.md missing">Create decision-log.md in the resolved sidecar directory with header: "# {agent_display_name} Decision Log" and empty entries</action>
+  <action if="conversation-context.md missing">Create conversation-context.md in the resolved sidecar directory with header: "# {agent_display_name} Conversation Context" and empty rolling state</action>
+</step>
+
+<step n="3" title="Determine Refresh Mode">
   <action>Check if --incremental flag was passed</action>
   <action if="incremental">Set mode to incremental — only scan files modified since last-refresh timestamp from ground-truth.md header</action>
   <action if="not incremental">Set mode to full — scan all targets completely. Full refresh catches deletions and renames that incremental would miss.</action>
 </step>
 
-<step n="3" title="Load Entry Structure">
+<step n="4" title="Load Entry Structure">
   <action>Load ground-truth-management skill section: entry-structure (JIT)</action>
   <action>Use entry-structure format for all ground truth entries written in subsequent steps</action>
 </step>
 
-<step n="4" title="Parse Previous State">
-  <action>Read existing {memory_path}/validator-sidecar/ground-truth.md</action>
+<step n="5" title="Parse Previous State">
+  <action>Read existing ground-truth.md from the resolved target sidecar directory</action>
   <action>Extract last-refresh timestamp from header</action>
   <action>Parse all existing entries into a lookup map keyed by file path for diff comparison</action>
   <action if="incremental mode">Filter scan targets to only files modified after last-refresh timestamp</action>
 </step>
 
-<step n="5" title="Scan Inventory Targets">
+<step n="6" title="Scan Inventory Targets">
   <action>Load ground-truth-management skill section based on mode: full-refresh or incremental-refresh (JIT)</action>
-  <action>Scan the following 6 inventory targets, showing section-by-section progress to the user after each target completes.</action>
 
-  <action title="Exclusion list">
-    ALWAYS exclude these directories and files from scanning — they are framework internals, not project code:
-    _gaia/, .claude/, bin/, _memory/, node_modules/, .git/, build/, dist/, .DS_Store, *.lock
+  <action if="agent == val">
+    Scan the following 6 inventory targets (existing Val scan — unchanged for backward compatibility), showing section-by-section progress to the user after each target completes.
+
+    <action title="Exclusion list">
+      ALWAYS exclude these directories and files from scanning — they are framework internals, not project code:
+      _gaia/, .claude/, bin/, _memory/, node_modules/, .git/, build/, dist/, .DS_Store, *.lock
+    </action>
+
+    <action title="Target 1: Project Source Files">
+      Scan {project-path}/**/* (excluding the exclusion list above)
+      Extract: file inventory, directory structure, languages used, entry points
+      Report progress: "Scanning project source files... found N files across N directories."
+    </action>
+
+    <action title="Target 2: Project Config Files">
+      Scan {project-path}/*.{json,yaml,yml,toml,xml,env.example} (root-level config files)
+      Extract: config keys, settings, dependency declarations
+      Report progress: "Scanning project config files... found N config files."
+    </action>
+
+    <action title="Target 3: Project Package Manifests">
+      Scan {project-path}/**/package.json, pubspec.yaml, pom.xml, build.gradle, requirements.txt, Cargo.toml, go.mod, Gemfile, *.csproj (whichever exist)
+      Extract: dependencies, versions, scripts, build targets
+      Report progress: "Scanning package manifests... found N manifests."
+    </action>
+
+    <action title="Target 4: Planning Artifacts">
+      Scan {project-root}/docs/planning-artifacts/*.md
+      Extract: artifact name, type, date
+      Report progress: "Scanning planning artifacts... found N artifacts."
+    </action>
+
+    <action title="Target 5: Implementation Artifacts">
+      Scan {project-root}/docs/implementation-artifacts/*.md
+      Extract: artifact name, type, story key if applicable
+      Report progress: "Scanning implementation artifacts... found N artifacts."
+    </action>
+
+    <action title="Target 6: Test Artifacts">
+      Scan {project-root}/docs/test-artifacts/*.md
+      Extract: artifact name, type, coverage area
+      Report progress: "Scanning test artifacts... found N artifacts."
+    </action>
   </action>
 
-  <action title="Target 1: Project Source Files">
-    Scan {project-path}/**/* (excluding the exclusion list above)
-    Extract: file inventory, directory structure, languages used, entry points
-    Report progress: "Scanning project source files... found N files across N directories."
-  </action>
+  <action if="agent == theo">
+    Scan theo-specific inventory targets (architecture ground truth):
 
-  <action title="Target 2: Project Config Files">
-    Scan {project-path}/*.{json,yaml,yml,toml,xml,env.example} (root-level config files)
-    Extract: config keys, settings, dependency declarations
-    Report progress: "Scanning project config files... found N config files."
-  </action>
+    <action title="Target 1: Filesystem Structure">
+      Scan {project-path}/ for directory structure, file types, and project layout.
+      Extract: tech stack, components, module boundaries, entry points, build configuration.
+      Report progress: "Scanning filesystem structure for Theo... found N directories, N files."
+    </action>
 
-  <action title="Target 3: Project Package Manifests">
-    Scan {project-path}/**/package.json, pubspec.yaml, pom.xml, build.gradle, requirements.txt, Cargo.toml, go.mod, Gemfile, *.csproj (whichever exist)
-    Extract: dependencies, versions, scripts, build targets
-    Report progress: "Scanning package manifests... found N manifests."
+    <action title="Target 2: Architecture Document">
+      Scan {planning_artifacts}/architecture.md
+      Extract: ADRs, architectural decisions, component diagrams, dependency info, integration points, tech stack decisions.
+      Report progress: "Scanning architecture.md for Theo... extracted N ADRs, N components."
+    </action>
   </action>
 
-  <action title="Target 4: Planning Artifacts">
-    Scan {project-root}/docs/planning-artifacts/*.md
-    Extract: artifact name, type, date
-    Report progress: "Scanning planning artifacts... found N artifacts."
+  <action if="agent == derek">
+    Scan derek-specific inventory targets (product ground truth):
+
+    <action title="Target 1: Product Requirements">
+      Scan {planning_artifacts}/prd.md
+      Extract: functional requirements, non-functional requirements, user stories overview, feature list, product goals.
+      Report progress: "Scanning prd.md for Derek... extracted N requirements."
+    </action>
+
+    <action title="Target 2: Epics and Stories">
+      Scan {planning_artifacts}/epics-and-stories.md
+      Extract: epic list, story breakdown, acceptance criteria summaries, dependency graph, sizing data.
+      Report progress: "Scanning epics-and-stories.md for Derek... extracted N epics, N stories."
+    </action>
+
+    <action title="Target 3: Sprint Status">
+      Scan {implementation_artifacts}/sprint-status.yaml
+      Extract: current sprint state, story statuses, velocity data, blocked items, completion rates.
+      Report progress: "Scanning sprint-status.yaml for Derek... extracted sprint state."
+    </action>
   </action>
 
-  <action title="Target 5: Implementation Artifacts">
-    Scan {project-root}/docs/implementation-artifacts/*.md
-    Extract: artifact name, type, story key if applicable
-    Report progress: "Scanning implementation artifacts... found N artifacts."
-  </action>
+  <action if="agent == nate">
+    Scan nate-specific inventory targets (sprint ground truth):
+
+    <action title="Target 1: Sprint Status">
+      Scan {implementation_artifacts}/sprint-status.yaml
+      Extract: sprint metadata, story statuses, velocity metrics, blocked items, wave assignments.
+      Report progress: "Scanning sprint-status.yaml for Nate... extracted sprint state."
+    </action>
 
-  <action title="Target 6: Test Artifacts">
-    Scan {project-root}/docs/test-artifacts/*.md
-    Extract: artifact name, type, coverage area
-    Report progress: "Scanning test artifacts... found N artifacts."
+    <action title="Target 2: Story Files">
+      Scan all story files in {implementation_artifacts}/ matching pattern *-*.md (story files)
+      Extract: story statuses, completion rates, subtask progress, blockers, review gate states.
+      Report progress: "Scanning story files in implementation-artifacts for Nate... found N stories."
+    </action>
   </action>
 </step>
 
-<step n="6" title="Compare and Detect Changes">
-  <action>Compare scan results against previous state from Step 4</action>
+<step n="7" title="Compare and Detect Changes">
+  <action>Compare scan results against previous state from Step 5</action>
   <action>Classify each entry as: ADDED (new file not in previous state), UPDATED (file exists but metadata changed), UNCHANGED (no changes detected)</action>
   <action if="full mode">For entries in previous state not found in scan results: mark as REMOVED with detection date (e.g., "REMOVED (file deleted, detected 2026-03-19)"). Do NOT silently delete entries.</action>
   <action if="incremental mode">Skip deletion detection — incremental mode cannot detect deletions. This is a documented limitation.</action>
   <action>Load ground-truth-management skill section: conflict-resolution (JIT) if any conflicts are detected between scan results and existing entries</action>
 </step>
 
-<step n="7" title="Write Ground Truth">
-  <action>Update {memory_path}/validator-sidecar/ground-truth.md with all scan results</action>
+<step n="8" title="Write Ground Truth">
+  <action>Update ground-truth.md in the resolved target agent's sidecar directory with all scan results</action>
   <action>Write header with last-refresh timestamp set to current date/time</action>
-  <action>Organize entries by category: Agents, Workflows, Skills, Commands, Manifests, Config, Artifacts</action>
+  <action>Organize entries by category appropriate to the target agent</action>
   <action>Include verified counts, locations, and structural patterns for each category</action>
   <action>Preserve REMOVED entries with their detection dates — do not purge</action>
 </step>
 
-<step n="8" title="Generate Diff Report">
+<step n="9" title="Generate Diff Report">
   <action>Generate diff/delta report summarizing changes since last refresh</action>
   <action>Include counts by category: added, removed, updated entries</action>
   <action>Include total entry count across all categories</action>
@@ -103,23 +174,48 @@
   <action>Present the full diff report to the user</action>
 </step>
 
-<step n="9" title="Log to Decision Log">
-  <action>Append the diff/delta report to {memory_path}/validator-sidecar/decision-log.md</action>
-  <action>Include date, refresh mode (full or incremental), and summary</action>
-  <action>Format: "## Refresh — {date} ({mode})\n{summary}"</action>
+<step n="10" title="Log to Decision Log">
+  <action>Append the diff/delta report to the target agent's own decision-log.md in the resolved sidecar directory.
+    Route to the correct file based on resolved agent target:
+    - val: {memory_path}/validator-sidecar/decision-log.md
+    - theo: {memory_path}/architect-sidecar/decision-log.md
+    - derek: {memory_path}/pm-sidecar/decision-log.md
+    - nate: {memory_path}/sm-sidecar/decision-log.md
+    Never write to another agent's decision-log.md — this would violate cross-agent write isolation.</action>
+  <action>Include date, refresh mode (full or incremental), target agent name, and summary</action>
+  <action>Format: "## Refresh — {date} ({mode}) — Agent: {agent_name}\n{summary}"</action>
 </step>
 
-<step n="10" title="Check Token Budget">
+<step n="11" title="Check Token Budget">
   <action>Load ground-truth-management skill section: token-budget (JIT)</action>
-  <action>Estimate token count of ground-truth.md</action>
-  <action>If token count exceeds budget threshold: trigger archival of oldest REMOVED entries per token-budget skill guidance</action>
+  <action>Load the correct per-agent ground_truth_budget from {memory_path}/config.yaml based on target agent:
+    - Val: 200K (200,000 tokens)
+    - Theo: 150K (150,000 tokens)
+    - Derek: 100K (100,000 tokens)
+    - Nate: 100K (100,000 tokens)
+    These are distinct from the 300K session_budget — ground_truth_budget controls only ground-truth.md size.</action>
+  <action>Estimate token count of the target agent's ground-truth.md</action>
+  <action>If token count exceeds the per-agent budget threshold: trigger archival of oldest REMOVED entries per token-budget skill guidance</action>
+  <action if="agent == all">Report per-agent usage separately (e.g., "Theo: 42K/150K, Derek: 18K/100K")</action>
   <action>Report token usage to user</action>
 </step>
 
-<step n="11" title="Present Results">
+<step n="12" title="Present Results">
   <template-output file="{memory_path}/validator-sidecar/ground-truth.md">
-    Ground truth refreshed with verified inventory of all framework components.
+    Ground truth refreshed for the target agent with verified inventory.
+    Output path is resolved at runtime based on --agent parameter (defaults to validator-sidecar).
     Includes last-refresh timestamp, categorized entries, and REMOVED markers for deleted files.
   </template-output>
 </step>
+
+<step n="13" title="Orchestrate --agent all" if="agent == all">
+  <action>Run refresh sequentially for each agent in order: val, theo, derek, nate.
+    Each agent's refresh completes fully (Steps 2-12) before the next begins.
+    No cross-contamination of sidecar writes — each agent writes only to its own sidecar.</action>
+  <action>On per-agent failure (e.g., missing source file like prd.md): log the error with reason, continue with remaining agents. Do not halt the entire sequence.</action>
+  <action>After all agents complete: present a combined summary with per-agent status:
+    - Which agents succeeded and their entry counts
+    - Which agents failed and the failure reasons
+    Format: "Refresh complete. Results: Val: OK (N entries), Theo: OK (N entries), Derek: FAILED (prd.md not found), Nate: OK (N entries)."</action>
+</step>
 </workflow>

package/_gaia/lifecycle/workflows/4-implementation/val-refresh-ground-truth/workflow.yaml

@@ -9,6 +9,11 @@ installed_path: "{project-root}/_gaia/lifecycle/workflows/4-implementation/val-r
 instructions: "{installed_path}/instructions.xml"
 validation: "{installed_path}/checklist.md"
 parameters:
+  agent:
+    flag: "--agent"
+    description: "Which Tier 1 agent's ground truth to refresh. Defaults to val for backward compatibility."
+    default: "val"
+    allowed_values: [val, theo, derek, nate, all]
   incremental:
     flag: "--incremental"
     description: "Only scan files modified since last refresh timestamp. Full refresh is default."

package/_gaia/lifecycle/workflows/4-implementation/val-validate-artifact/instructions.xml

@@ -18,7 +18,17 @@
   <action>Present the section map to confirm scope: "{N} sections identified, {M} chunks for validation"</action>
 </step>
 
-<step n="2" title="Extract Claims">
+<step n="2" title="Detect Artifact Type and Run Document-Specific Rules">
+  <!-- SKILL-REF: document-rulesets.md SECTION: type-detection -->
+  <!-- Two-pass validation: document-specific structural rules first (Pass 1), then factual claim verification (Pass 2) -->
+  <action>Load the "type-detection" section from the document-rulesets skill (JIT)</action>
+  <action>Extract the basename from {artifact_path} and match against the type-detection mapping table to determine the artifact type and corresponding ruleset ID (prd-rules, arch-rules, ux-rules, test-plan-rules, epics-rules, or unknown)</action>
+  <action>If artifact type is unknown (no ruleset matches): skip structural rules entirely — no document-specific rules to apply. Log: "No document-specific ruleset for this artifact type — factual verification only." Release the type-detection section and proceed directly to Step 3 (Pass 2 — factual claims only).</action>
+  <action>If artifact type is recognized: load the matching ruleset section from document-rulesets skill (JIT). Execute Pass 1 — structural rules first: run all checks defined in the ruleset against the artifact content. Record structural findings with source tag [STRUCTURAL]. Release the ruleset section from context.</action>
+  <action>Release the "type-detection" section from context</action>
+</step>
+
+<step n="3" title="Extract Claims (Pass 2 — Factual Verification)">
   <!-- SKILL-REF: validation-patterns.md SECTION: claim-extraction -->
   <action>Load the "claim-extraction" section from the validation-patterns skill (JIT)</action>
   <action>For each chunk from Step 1, extract all verifiable factual claims:
@@ -33,7 +43,7 @@
   <action>Release the "claim-extraction" skill section from context</action>
 </step>
 
-<step n="3" title="Filesystem Verify">
+<step n="4" title="Filesystem Verify">
   <!-- SKILL-REF: validation-patterns.md SECTION: filesystem-verification -->
   <action>Load the "filesystem-verification" section from the validation-patterns skill (JIT)</action>
   <action>For each extracted claim, verify against the actual filesystem:
@@ -45,32 +55,33 @@
   <action>Release the "filesystem-verification" skill section from context</action>
 </step>
 
-<step n="4" title="Cross-Reference Ground Truth">
+<step n="5" title="Cross-Reference Ground Truth">
   <!-- SKILL-REF: validation-patterns.md SECTION: cross-reference -->
   <action>Check if {memory_path}/validator-sidecar/ground-truth.md exists and is non-empty</action>
-  <action>If ground-truth.md is missing or empty: skip cross-reference checks. Record a note: "Ground truth not available — cross-reference checks skipped." Proceed to Step 5. Filesystem verification results from Step 3 are still valid.</action>
+  <action>If ground-truth.md is missing or empty: skip cross-reference checks. Record a note: "Ground truth not available — cross-reference checks skipped." Proceed to Step 6. Filesystem verification results from Step 4 are still valid.</action>
   <action>If ground-truth.md exists and is non-empty:
     — Load the "cross-reference" section from the validation-patterns skill (JIT)
-    — For each claim that was VERIFIED in Step 3, cross-reference against ground truth:
+    — For each claim that was VERIFIED in Step 4, cross-reference against ground truth:
       — Check if ground truth contains a contradicting fact
       — Check if ground truth has a more recent or more precise version of the same fact
       — Flag any discrepancies between the artifact claim and ground truth
     — Release the "cross-reference" skill section from context</action>
 </step>
 
-<step n="5" title="Classify Findings">
+<step n="6" title="Classify Findings">
   <!-- SKILL-REF: validation-patterns.md SECTION: severity-classification -->
+  <!-- SKILL-REF: document-rulesets.md SECTION: two-pass-logic -->
   <action>Load the "severity-classification" section from the validation-patterns skill (JIT)</action>
-  <action>Compile all findings from Steps 3 and 4 — only FAILED verifications and ground-truth discrepancies</action>
+  <action>Compile and merge findings from both passes — structural findings from Step 2 (Pass 1, tagged [STRUCTURAL]) and factual findings from Steps 3-5 (Pass 2, tagged [FACTUAL]). Include only FAILED verifications, ground-truth discrepancies, and structural quality issues.</action>
   <action>Classify each finding into exactly one severity level:
     — **CRITICAL**: Wrong file path (file does not exist), incorrect count (stated N but actual is M), broken reference (FR/ADR/component does not exist), contradicts ground truth on a verified fact
     — **WARNING**: Outdated reference (file exists but content has changed), stale data (version number is behind), ground truth has newer information
     — **INFO**: Style suggestion (naming inconsistency), minor inconsistency (non-breaking), cosmetic discrepancy</action>
-  <action>If no findings were produced (all claims verified, no discrepancies): report "All {N} claims verified — no findings." Skip Steps 6 and 7 — proceed to workflow completion.</action>
+  <action>If no findings were produced (all claims verified, no discrepancies): report "All {N} claims verified — no findings." Skip Steps 7 and 8 — proceed to workflow completion.</action>
   <action>Release the "severity-classification" skill section from context</action>
 </step>
 
-<step n="6" title="Discussion Loop">
+<step n="7" title="Discussion Loop">
   <action>Present all classified findings to the user in a structured table:
 
   | # | Severity | Section | Claim | Finding | Evidence |
@@ -88,11 +99,11 @@
     — APPROVE: finding is correct, include in written output
     — DISPUTE: finding is incorrect or not applicable, exclude from written output
     — EDIT: modify the finding description before approving</action>
-  <action>Only findings explicitly approved by the user proceed to Step 7</action>
+  <action>Only findings explicitly approved by the user proceed to Step 8</action>
   <action>If the user disputes ALL findings: report "All findings disputed — no changes written to artifact." Complete the workflow gracefully.</action>
 </step>
 
-<step n="7" title="Write Approved Findings">
+<step n="8" title="Write Approved Findings">
   <!-- SKILL-REF: validation-patterns.md SECTION: findings-formatting -->
   <action>Load the "findings-formatting" section from the validation-patterns skill (JIT)</action>
   <action>Check if the target artifact already contains a "## Validation Findings" section</action>
@@ -112,7 +123,7 @@
   <action>Release the "findings-formatting" skill section from context</action>
 </step>
 
-<step n="8" title="Save to Val Memory">
+<step n="9" title="Save to Val Memory">
   <action>Auto-save all validation results to Val's memory sidecar (no user prompt required):
 
   1. Append to {memory_path}/validator-sidecar/decision-log.md using standardized format:

package/_gaia/lifecycle/workflows/4-implementation/val-validate-artifact/workflow.yaml

@@ -8,6 +8,17 @@ config_source: "{project-root}/_gaia/lifecycle/config.yaml"
 installed_path: "{project-root}/_gaia/lifecycle/workflows/4-implementation/val-validate-artifact"
 instructions: "{installed_path}/instructions.xml"
 validation: "{installed_path}/checklist.md"
+required_skills:
+  - "{project-root}/_gaia/lifecycle/skills/validation-patterns.md"
+  - "{project-root}/_gaia/lifecycle/skills/document-rulesets.md"
+required_skill_sections:
+  - "document-rulesets:type-detection"
+  - "document-rulesets:prd-rules"
+  - "document-rulesets:arch-rules"
+  - "document-rulesets:ux-rules"
+  - "document-rulesets:test-plan-rules"
+  - "document-rulesets:epics-rules"
+  - "document-rulesets:two-pass-logic"
 input_file_patterns:
   artifact:
     whole: "{artifact_path}"

package/_gaia/lifecycle/workflows/4-implementation/val-validate-plan/instructions.xml

@@ -131,8 +131,6 @@
   <template-output file="{plan_artifact_path}">
     Append Plan Validation Findings section with approved findings table, validation metadata, and summary counts.
   </template-output>
-</step>
-<step n="8" title="Save to Val Memory">
   <action>Auto-save all validation results to Val's memory sidecar (no user prompt required):
 
   1. Append to {project-root}/{memory_path}/validator-sidecar/decision-log.md using standardized format:

package/_gaia/lifecycle/workflows/5-deployment/deployment-checklist/workflow.yaml

@@ -7,6 +7,7 @@ config_source: "{project-root}/_gaia/lifecycle/config.yaml"
 installed_path: "{project-root}/_gaia/lifecycle/workflows/5-deployment/deployment-checklist"
 instructions: "{installed_path}/instructions.xml"
 validation: "{installed_path}/checklist.md"
+template: "{project-root}/_gaia/lifecycle/templates/deployment-template.md"
 input_file_patterns:
   architecture:
     whole: "{planning_artifacts}/architecture.md"

package/_gaia/lifecycle/workflows/anytime/brownfield-onboarding/instructions.xml

@@ -82,7 +82,7 @@
   /gaia-review-api (optional, if APIs) → /gaia-adversarial → /gaia-test-design → /gaia-test-framework (optional) → /gaia-create-epics → /gaia-threat-model → /gaia-infra-design → /gaia-trace → /gaia-ci-setup → /gaia-readiness-check</action>
 </step>
 
-<step n="7" title="Bootstrap Val Ground Truth" optional="true">
+<step n="7" title="Bootstrap Agent Ground Truth" optional="true">
   <action>Check if Val is installed: verify {project-root}/_gaia/lifecycle/agents/validator.md exists AND {memory_path}/validator-sidecar/ directory exists</action>
   <check if="validator.md not found OR validator-sidecar/ not found">Skip Step 7 silently — Val is not installed. Brownfield onboarding continues without ground truth bootstrap.</check>
 
@@ -102,6 +102,74 @@
 
   <action>Write extracted project facts to {memory_path}/validator-sidecar/ground-truth.md. If ground-truth.md already exists with content: merge new facts with existing entries — add new facts, update changed facts, flag removed facts — never destructive overwrite. Follow merge semantics from ground-truth-management conflict-resolution section. If ground-truth.md is empty or new: write all extracted facts as initial seed entries with verification count = 1.</action>
   <action>Report: "Seeded {N} ground-truth entries from brownfield artifacts + filesystem scan"</action>
+
+  <!-- Step 7d/7e/7f: Tier 1 Agent Ground Truth Bootstrap (E9-S12) -->
+
+  <ask>Bootstrap Tier 1 agent ground truth (Theo, Derek, Nate)? [y/n]</ask>
+
+  <action>JIT load ground-truth-management skill sections from {project-root}/_gaia/lifecycle/skills/ground-truth-management.md: entry-structure, conflict-resolution, brownfield-extraction. All ground-truth entries must follow the canonical entry format from the entry-structure section. When the same fact appears in multiple source documents with conflicting values (e.g., different version numbers), annotate the entry with "conflicting sources: {source1} says X, {source2} says Y" and use the higher-precedence source (brownfield-assessment.md > project-documentation.md for tech stack facts).</action>
+
+  <!-- Step 7d: Theo (Architect) ground truth extraction (AC1) -->
+  <action>Step 7d — Theo ground truth extraction.
+    Read {planning_artifacts}/architecture.md and extract:
+    — Tech stack (languages, frameworks, runtime versions) → variable-inventory entries
+    — ADRs (architecture decision records — ID, title, status, rationale) → structural-pattern entries
+    — Component inventory (modules, packages, services) → file-inventory entries
+    — Dependency map (internal and external dependencies) → cross-reference entries
+
+    If {planning_artifacts}/architecture.md does not exist: fall back to {planning_artifacts}/brownfield-assessment.md for Theo. Extract tech stack, file counts, and project structure from the brownfield assessment instead.
+
+    Token budget guard: Theo has a 150K token budget (150,000 tokens). Estimate extraction size (characters / 4). If estimated tokens exceed 60% threshold (90,000 tokens), trim to highest-signal entries — prioritize ADRs and tech stack over detailed file inventories.
+
+    Write extracted entries to {memory_path}/architect-sidecar/ground-truth.md.
+    If the {memory_path}/architect-sidecar/ directory does not exist, create it along with a new ground-truth.md file with standard headers.
+    If ground-truth.md already exists with content: follow merge semantics from the conflict-resolution section — add new entries, update changed entries, preserve existing entries. Never perform a destructive overwrite.</action>
+
+  <!-- Step 7e: Derek (Product Manager) ground truth extraction (AC2) -->
+  <action>Step 7e — Derek ground truth extraction.
+    Read {planning_artifacts}/prd.md and extract:
+    — Functional requirements (feature list, requirement IDs) → structural-pattern entries
+    — User stories and acceptance criteria summaries → cross-reference entries
+
+    If {planning_artifacts}/prd.md does not exist: fall back to {planning_artifacts}/prd-brownfield-gaps.md as the alternate PRD path for Derek.
+
+    Read {planning_artifacts}/epics-and-stories.md and extract for Derek:
+    — Epic overview (epic IDs, titles, story counts) → file-inventory entries
+    — Story-to-epic mappings → cross-reference entries
+
+    Read {test_artifacts}/nfr-assessment.md (if present) and extract for Derek:
+    — Quality baselines (performance targets, security posture, test coverage) → variable-inventory entries
+    If {test_artifacts}/nfr-assessment.md does not exist: log warning "nfr-assessment.md not found in test_artifacts — skipping quality baselines for Derek" and continue without error.
+
+    Token budget guard: Derek has a 100K token budget (100,000 tokens). Estimate extraction size (characters / 4). If estimated tokens exceed 60% threshold (60,000 tokens), trim to highest-signal entries — prioritize functional requirements and epic summaries over detailed story mappings.
+
+    Write extracted entries to {memory_path}/pm-sidecar/ground-truth.md.
+    If the {memory_path}/pm-sidecar/ directory does not exist, create it along with a new ground-truth.md file with standard headers.
+    If ground-truth.md already exists with content: follow merge semantics from the conflict-resolution section — add new entries, update changed entries, preserve existing entries. Never perform a destructive overwrite.</action>
+
+  <!-- Step 7f: Nate (Scrum Master) ground truth extraction (AC3) -->
+  <action>Step 7f — Nate ground truth extraction.
+    Read {implementation_artifacts}/sprint-status.yaml (if it exists) and extract for Nate:
+    — Current sprint ID, story count, points total → variable-inventory entries
+    — Story status distribution → structural-pattern entries
+
+    Read {memory_path}/sm-sidecar/velocity-data.md (if it exists) and extract for Nate:
+    — Velocity history (sprint-over-sprint) → variable-inventory entries
+    — Capacity data → variable-inventory entries
+
+    If neither {implementation_artifacts}/sprint-status.yaml nor {memory_path}/sm-sidecar/velocity-data.md exists: complete this step gracefully with a log message "insufficient sprint data, velocity unavailable" and write ground-truth.md omitting velocity entries. Do not raise an error.
+
+    Token budget guard: Nate has a 100K token budget (100,000 tokens). Estimate extraction size (characters / 4). If estimated tokens exceed 60% threshold (60,000 tokens), trim to highest-signal entries — prioritize current sprint status over historical velocity data.
+
+    Write extracted entries to {memory_path}/sm-sidecar/ground-truth.md.
+    If the {memory_path}/sm-sidecar/ directory does not exist, create it along with a new ground-truth.md file with standard headers.
+    If ground-truth.md already exists with content: follow merge semantics from the conflict-resolution section — add new entries, update changed entries, preserve existing entries. Never perform a destructive overwrite.</action>
+
+  <!-- Summary report (AC6) -->
+  <action>After all Tier 1 extractions complete, output a summary report:
+    "Seeded {N} entries for Theo, {M} entries for Derek, {K} entries for Nate"
+    If sprint data was absent for Nate, append a note: "(sprint data absent — velocity entries omitted)"
+    Include token budget status for each agent (GREEN/YELLOW/RED).</action>
 </step>
 
 <next-step command="/gaia-review-api">