feat(agents): add RAG specialist role in sprint 2

[AccessiT3ch]

Context

Sprint 1 focuses on implementation and baseline validation. If patterns stabilize, Sprint 2 should encode them into a dedicated specialist role.

Scope

Define and add a RAG Specialist agent in Sprint 2 with tight domain boundaries.

Acceptance Criteria

• Agent charter covers retrieval/indexing/evaluation workflows only
• Handoff contracts defined with Orchestrator, MCP Architect, and Docs roles
• Tool scope is minimal and justified (no broad terminal powers by default)
• Includes anti-patterns: over-coupling to one editor/client, hidden model assumptions
• Pilot run in one sprint phase with documented effectiveness vs baseline

Notes

MCP specialist support should be pulled in as needed via existing MCP Architect role.

• Evidence artifact: docs/plans/2026-03-19-rag-sprint-planning-g1-pilot-vs-baseline.md (commit db2174d)

Controlling planning artifacts

• RG4 re-entry: docs/plans/2026-03-19-rag-sprint-planning-rg4-reentry-update.md

• Sprint 1 execution sequencing: docs/plans/2026-03-19-rag-sprint-1-execution-sequencing.md

• Sprint 1 kickoff packet: docs/plans/2026-03-19-rag-sprint-1-phase4-kickoff-packet.md

[AccessiT3ch]

Sprint 2 kickoff (carry-forward from Sprint 1): Phase 1 research outcomes integrated; Phase 2 retrieval substrate contracts stabilized; Phase 3 BEIR-lite + instrumentation + CI guardrails delivered. Commit evidence: 8dd71b9, b3a245c, 965b445, 666c19a. Sprint 2 starter checklist (RAG specialist): [ ] lock issue #8 acceptance criteria, [ ] expand retrieval evaluation set and regression thresholds, [ ] validate instrumentation for recall/latency/token-cost, [ ] run CI guardrails and record baseline deltas, [ ] post weekly progress updates with commit links.

[AccessiT3ch]

Sprint 2 progress update:

Completed:

• Phase 2 role-contract work is complete and review-approved.
• Added new RAG Specialist role contract and fleet catalog entry.
• Marked issue checkboxes complete for AC1-AC4.

Implementation references:

• PR: feat(rag): execute Sprint 2 phases 1-4 with gated delivery #14
• Commits: aa313ff, 9d791a3

Current gate status:

• feat(agents): add RAG specialist role in sprint 2 #8 remains intentionally open pending AC5 (pilot run effectiveness evidence vs baseline).

Next:

• Produce pilot-results artifact (baseline vs pilot metrics + decision memo) and link it for closure readiness.

[AccessiT3ch]

Sprint planning update (Phase 4): Review Gate 4 is APPROVED with HOLD posture.

Decisions now locked:

• Keep HOLD and close blockers before release.
• Close feat(agents): add RAG specialist role in sprint 2 #8 with one documented pilot-vs-baseline effectiveness comparison.
• Require 3 consecutive compliant boundary-safety windows before release.
• Phase 5 will package a HOLD-state closure plan.

Current blocker path:

• G1: close feat(agents): add RAG specialist role in sprint 2 #8 pilot-effectiveness evidence.
• G2: consolidate integrated evidence packet.
• G3: repeat boundary-safety evidence in pilot context.
• G4: satisfy explicit release checklist.

Next: execute blocker closure items and rerun release decision gate after evidence updates.

[AccessiT3ch]

G1 completed: pilot-vs-baseline comparison artifact added and final acceptance checkbox updated. Effectiveness documented as partially effective with repeatability caveat tracked in HOLD closure path (G2-G4).