Skip to content
sdlc

Initial Product Definition

Status: open/active · Version: 0.1.0-alpha

Goal

Section titled “Goal”

Settle what the SDLC product is, why it exists, and how it is shaped — the definition foundation everything else builds on — and do it on a TypeScript substrate. This is the fresh-start pass over the documentation and data model: the why (vision, the Drivers), the Product itself (PR-0001-sdlc), the Principles, the entity data model and its contract, the system architecture, and a single generated documentation index. It supersedes the framing of the prior construction-sequence milestones (now deferred), reorganizing their settled substance around product releases rather than build phases.

Success criteria

Section titled “Success criteria”
  • Why is authored — vision, the Drivers roster, and the Product entity PR-0001-sdlc are coherent and current.
  • Principles published — the P-entity roster exists, each carries a ^summary, and each is categorized via its principle/<category> tag.
  • Data model is authoritative — roster D-ORMG-data-model, identifier shape D-0002-entity-identifier-shape, definition contract S-0005-entity-definition-contract, and system architecture D-VSLI-distributed-work-runner-architecture are settled and internally consistent.
  • Documentation consolidated — a single generated front-door index; hand-maintained narrative docs retired or folded into entities; the index skill defined (generator deferred to its task).
  • TypeScript substrate is the recorded direction for tooling.

Deliverables

Section titled “Deliverables”

Out of scope

Section titled “Out of scope”
  • Building the orchestrated execution loop — M-QXR3-claude-orchestrated-task-execution-prototype.
  • Executing the TypeScript migration itself (this milestone records the direction, not the port).
  • The wider entity-model build-out (Goal / Requirement / AcceptanceCriterion / Constraint) beyond what definition needs.

Risks / open questions

Section titled “Risks / open questions”
  • The TypeScript migration is in flight; some substrate references will churn until it lands.
  • The data model is still settling (milestone-as-release versioning, Epic→parent_key, task kind); definition may need a second pass as those decisions execute.

← Back to Milestones