[EPIC] E-00: DevOps AI Capture Layer

[carloshumbertoreyesortiz]

Epic E-00

The capability layer through which requirements enter the platform from any source where they natively arise: Teams meetings, Slack messages, Confluence pages, Jira tickets, VS Code Command Palette, and Terminal CLI. All six channels normalize to a single NormalizedIntake schema (same one used by E-09 Slack scaffold per US-039/US-040), so downstream agents are channel-agnostic. This is a clarification of how requirements enter the platform — not new scope. Per Praveen/Apoorv/Per feedback during the 2026-06-19 design review.

Phase: 0 · Stories: 8 · Points: 39
Impl guide: §00.5 (capture-layer.md)
Companion: IMPL-AGENTIC-SDLC-001 Rev 1.5 (docs/capture-layer.md), ARCH-AGENTIC-SDLC-001 Rev 1.6 §02.0

Acceptance criteria

• All six capture channels (Teams, Slack, Confluence, Jira, VS Code, CLI) produce NormalizedIntake records that pass schema validation.
• End-to-end smoke test: a requirement captured via each channel surfaces in Claude Code as a plan-mode session within 60 seconds.
• Trust boundary preserved: every NormalizedIntake record carries trust:'untrusted' and content is wrapped per US-023 before reaching the planner.
• Author attribution recorded for every capture (name + email from the source channel), feeds into provenance.
• Capture Layer is operable independently per channel — a team that doesn't use Teams skips US-053 without breaking the rest.

Stories in this epic

• US-052 — Define NormalizedIntake schema with all six source types (3 pts)
• US-053 — Teams app registration + meeting-transcript webhook (8 pts)
• US-054 — Slack intake handler — replaces US-038 from E-09 scope (5 pts)
• US-055 — Confluence watched-space subscription (5 pts)
• US-056 — Jira watched-project subscription (5 pts)
• US-057 — VS Code Command Palette extension — Send Selection to Agentic (5 pts)
• US-058 — Terminal CLI — agentic capture command (3 pts)
• US-059 — End-to-end Capture Layer smoke test through all six channels (5 pts)