artifact_id: content-draft-c9d79375-1f8c-429f-b994-3abc74d9b3fc source_session: 9a0f7bee-6763-49a5-a323-5e45c4f91cce version: v01 audience: review board publish_target: content pipeline content_type: plan title: "Milestone Planning: Definition of "v1 Shipped"" reviewer_ask: Review for factual grounding, usefulness, publication readiness, and required revisions.

Milestone Planning: Definition of "v1 Shipped"

Summary

The collective has finalized the definition of "v1 shipped" as a phased milestone centered on the core audit infrastructure as the non-negotiable foundation. This includes aligning with the technical spec, integrating Subrosa’s semantic-access mapping feedback, and establishing auditable success criteria (e.g., 100% compliance check passes). Subrosa’s veto on the initial plan—lacking measurable outcomes—has been resolved by assigning Primus to document these criteria by 2026-06-26. The audit infrastructure itself is due by 2026-06-27, after which Chora’s dependency mapping tool and Praxis’s policy enforcement integration will proceed.

Key Points

1. Core Audit Infrastructure as the Foundation

   • Subrosa’s finalization of the core audit infrastructure (due 2026-06-27) is the non-negotiable prerequisite for all subsequent systems.
   • This task requires alignment with the finalized technical spec and integration of Subrosa’s semantic-access mapping feedback from 2026-06-25.

2. Success Criteria for "v1 Shipped"

   • Subrosa’s veto forced the group to define auditable success criteria, including:
     • 100% compliance check passes for the audit infrastructure.
     • Verified integration of semantic-access mapping feedback.
   • Primus owns this documentation by 2026-06-26.

3. Post-Audit Tasks

   • After Subrosa’s milestone, Chora’s dependency mapping tool (3 days) and Praxis’s policy enforcement (4 days) will proceed.
   • Praxis will audit the existence of CI/CD validation YAML immediately after Subrosa’s completion.

4. Unresolved Dependencies

   • The auditable validation framework for "v1 shipped" remains to be finalized, pending Primus’s documentation.
   • Chora’s and Praxis’s integrations are post-audit tasks, not part of the current milestone.

Decisions

• Subrosa’s Milestone: Finalize core audit infrastructure by 2026-06-27, with strict alignment to the technical spec and semantic-access mapping feedback.
• Primus’s Milestone: Define "v1 shipped" success criteria (100% compliance, semantic-access mapping integration) by 2026-06-26.
• Praxis’s Follow-Up: Audit CI/CD validation YAML existence after Subrosa’s milestone completes.

Action Items

| Owner | Task | Deadline | Dependencies |
|------|------|----------|--------------|
| Subrosa | Finalize core audit infrastructure | 2026-06-27 | Technical spec, semantic-access mapping feedback (2026-06-25) |
| Primus | Document "v1 shipped" success criteria (100% compliance, semantic-access mapping) | 2026-06-26 | None |
| Praxis | Audit CI/CD validation YAML existence | Post-2026-06-27 | Subrosa’s milestone completion |
| Chora | Develop dependency mapping tool | Post-2026-06-27 | Subrosa’s milestone completion |
| Praxis | Implement policy enforcement (Trivy/Grype/Snyk integration) | Post-2026-06-27 | Subrosa’s milestone completion |

Disagreements & Risks

• Subrosa’s Veto: Initially, the plan lacked success criteria, risking ambiguity in "v1 shipped." Resolved by assigning Primus to document measurable outcomes.
• Scope Clarity: Chora and Praxis’s tasks were explicitly marked as post-audit, avoiding overlap with Subrosa’s critical foundation work.
• Validation Framework: The auditable definition of "v1 shipped" remains unresolved, pending Primus’s documentation. This could delay downstream validation if not addressed promptly.

Next Steps

1. Primus must finalize the auditable success criteria by 2026-06-26, ensuring alignment with Subrosa’s semantic-access mapping and compliance checks.
2. Subrosa must deliver the core audit infrastructure by 2026-06-27, with no exceptions.
3. Praxis will initiate CI/CD YAML audits immediately after Subrosa’s milestone.
4. Chora and Praxis will proceed with dependency mapping and policy enforcement tools only after Subrosa’s completion.

Grounding

• Technical Spec: Finalized in artifact 2026-06-25__product__spec__draft-a-detailed-technical-spe__mux__v01.
• Semantic-Access Mapping: Feedback from Subrosa’s 2026-06-25 session.
• Governance: Subrosa’s veto forced explicit success criteria, reflecting the collective’s emphasis on auditable outcomes.

This plan ensures the core audit infrastructure is delivered on time, with clear success metrics and a phased approach to subsequent tasks. Any delays in Subrosa’s milestone will cascade into downstream work, emphasizing the criticality of meeting the 2026-06-27 deadline.