1
Idea
  • Document the idea in brain with:
  • Problem statement: what is breaking or missing
  • Expected outcome: what success looks like
  • Rough size estimate: hours + any tool/service cost
  • No executor assigned yet — idea must be validated before scoping
idea logged in brain with problem statement and expected outcome
2
Scoped (SLA: 168h from Idea)
  • Akash reviews idea and decides: proceed or kill
  • If proceeding, define:
  • Requirements: what exactly will be built
  • Acceptance criteria: specific, testable conditions for "done"
  • Dependencies and blockers: what must exist before build can start
  • Owner: assign executor by name
all five fields above are logged and executor is assigned
3
In Progress
  • Executor builds to spec against acceptance criteria
  • Post update in #akash-notes when 50% complete — include: what's done, what's left, any blockers
  • If blocked → move to Blocked stage (Stage 8), do not hold silently in In Progress
  • Akash available for clarification on spec — executor pings directly in Slack
build complete and executor self-verifies against all acceptance criteria
Branch
QA fails:
Return to In Progress immediately. Attach specific failure notes per criterion to brain project. Executor must address all failures — no partial re-QA until all are fixed.
4
Review / QA (SLA: 48h)
  • Akash (or designated QA reviewer) tests each acceptance criterion explicitly
  • Log pass/fail per criterion in brain project record
  • If any criterion fails → return to In Progress with specific failure notes (see Offshoots)
  • No partial passes — all criteria must pass before Deployed
all acceptance criteria pass QA
5
Deployed
  • Deploy to production environment
  • Announce in #akash-notes: project name + what it does + link (if applicable)
  • Update any affected SOPs to reference new system
  • Log deploy date in brain project record
system is live in production and announced
6
Documented (SLA: 168h post-deploy)
  • Write SOP or reference doc — use standard 9-section format where applicable
  • Link doc in `brain.resource_docs` with relevant tags
  • If a scheduled task was deployed: confirm heartbeat coverage is active
doc exists and is linked in brain
7
Archived (terminal)
  • Move project to Archived in brain
documented and no further action needed — WIN terminal
8
Blocked
  • Document blocker in brain project record: what it is, who can unblock it, estimated resolution date
  • Notify Akash immediately via Slack
  • Return to prior stage when blocker is resolved
  • Check in on blocker every 48h if unresolved
blocker resolved — return to prior stage
Branch
Blocked:
Log blocker in brain, notify Akash, check in every 48h. Do not let blocked projects sit silent — they surface in weekly review.
Hands off to - **Deployed system** → relevant SOP updated to reference new tool or automation (same session as deploy). - **Documented project** → linked in `brain.resource_docs` with tags matching system category. - **Scheduled tasks deployed** → confirm row exists in `brain.background_tasks` heartbeat coverage.