T
TRINITY
Novus Imperium C2
Novus Imperium / TRINITYLive Data

PRD Process

VELOCITY 2.0 — Lifecycle, Architecture & Governance

Command Scope

Velocity 2.0 — Lifecycle Stages

INTAKE
→PLAN
→PRD
→EXECUTE
→VERIFY
→WIRE
→SHIP
INTAKE

Velocity Gate complexity check — will this touch 3+ files, create features, modify DB schema, or change architecture? PRD required for complex work.

PLAN

Interrogation protocol: Unknowns → Edge Cases → Dependencies → Rollback → Acceptance Criteria. No code until approved.

PRD

Full registration: DB (ops.prds + ops.prd_tasks), Bifrost room, Drive file, NMCC visibility, Discord announcement.

EXECUTE

Per-task protocol: START → CODE → COMMIT (git commit [PRD-NNN]) → LOG (ops.git_commits) → DONE → NOTIFY if phase complete.

VERIFY

Ralph Mode recursive verification: all tasks DONE, all commits tagged, all deliverables registered, wiring score 100%.

WIRE

10-item ecosystem wiring checklist: PRD status, tasks, commits, deliverables, Bifrost, Drive, NMCC activity, activity log, Discord, Slack.

SHIP

Completion notifications: Discord #deployments + Slack #all-trinity. PRD status → COMPLETE. NMCC homepage visible.

Per-Task Execution Protocol (Mandatory)

1STARTUPDATE ops.prd_tasks SET status = 'IN_PROGRESS' WHERE task_code = 'T-XXX'
2CODEWrite code, run tests, validate acceptance criteria
3COMMITgit commit -m "feat(module): T-XXX description [PRD-NNN]"
4LOGINSERT into ops.git_commits with linked_prds array populated
5DONEUPDATE ops.prd_tasks SET status = 'DONE' WHERE task_code = 'T-XXX'
6NOTIFYIf phase complete: Discord #deployments + Slack #all-trinity