Goal
Build the Generator → Bundle → Validator pipeline end-to-end, starting from the smallest Linux-only vertical slice and expanding incrementally to cover AC-1 and AC-2 anchor cases.
This issue tracks the reduced Phase 1 scope agreed upon in design review. The full Phase 1 vision is documented in overview discussions, but implementation begins with a narrower slice to lock down contracts and avoid early rework.
Milestones
| Milestone |
Description |
| M0 Contract Freeze |
Unify v1 contracts, initialize project scaffolding (Cargo workspace, CI, dependabot) |
| M1 PCAP Only |
Smallest Linux-only E2E path: scenario parsing → container provisioning → activity execution → bundle generation → Validator L1-L3 + L4-lite + pipeline CI |
| M2 PCAP + Sysmon |
Windows VM provisioning via libvirt + Sysmon JSONL collection alongside PCAP |
| M3 Falco, TLS, and Campaign |
Falco collection, TLS termination topology (AC-2), mini campaign support |
| M4 Hardening and CI |
Golden fixtures, regression checks, AC-1/AC-2 CI, pre-baked container images |
| P1 Docs Track |
Write AI Agent traffic generation and QFlow replay contracts (parallel with implementation) |
Sub-issues
M0 Contract Freeze
M1 PCAP Only
M2 PCAP + Sysmon
M3 Falco, TLS, and Campaign
M4 Hardening and CI
P1 Docs Track
Parallel work (enables M4 fixture determinism)
Scope
In scope
- Scenario Definition v1 schema and parser
- Generator: Linux container provisioning, activity execution (curl, nmap, Atomic Red Team), PCAP capture, bundle assembly
- Generator: Windows VM provisioning, Sysmon collection
- Generator: Falco collection, TLS termination topology, mini campaign support
- Ground Truth: session-scope recording with campaign support
- Validator: L1 (completeness), L2 (schema), L3 (GT integrity), L4 (cross-artifact alignment)
- AC-1 and AC-2 end-to-end integration
- CI pipeline with regression checks
Out of scope
- AC-3 (HTTPS proxy decryption)
- AC-4 and medium/large scale scenarios
- E2E encryption
- CALDERA full-chain automation
- Metasploit complex exploitation automation
- AI Actor (all modes: simulation, hybrid, autonomous)
- AI Agent deployment and control modes
- Cloud provider integration
- QFlow Replay full integration (contract only in P1 Docs)
Exit criteria
- AC-1 and AC-2 produce reproducible bundles that pass Validator L1-L4
- CI runs a minimum scenario and validates the resulting bundle on every change
- AI Agent traffic generation and QFlow replay contracts are documented and concrete enough to unblock Phase 2 planning
References
Goal
Build the Generator → Bundle → Validator pipeline end-to-end, starting from the smallest Linux-only vertical slice and expanding incrementally to cover AC-1 and AC-2 anchor cases.
This issue tracks the reduced Phase 1 scope agreed upon in design review. The full Phase 1 vision is documented in overview discussions, but implementation begins with a narrower slice to lock down contracts and avoid early rework.
Milestones
Sub-issues
M0 Contract Freeze
M1 PCAP Only
M2 PCAP + Sysmon
M3 Falco, TLS, and Campaign
M4 Hardening and CI
P1 Docs Track
Parallel work (enables M4 fixture determinism)
start_atand per-execution anchoring, PCAP/JSONL fixtures cannot be compared byte-for-byte across runs.Scope
In scope
Out of scope
Exit criteria
References