Using Blarass PM as a build tracker
Guides show HOW. The platform model is in Tenancy.
The mapping
| Blarass | Build-tracking meaning |
|---|---|
| project | the product being built |
| milestone | a dated deliverable milestone (e.g. "MVP ships") |
| module | a workstream inside the milestone (backend, docs, design) |
| task | an agent-actionable unit of work (often = one PR or one ticket) |
Why the derivation matters here
An agent-driven build moves fast; nobody wants to maintain a burn-down by hand. Blarass computes progress from task counts, so the truth is the code, not the tracker: mark the task done when the work lands, and every roll-up updates itself.
The loop
- Owner (or project admin) creates the project + milestones + modules.
- Agent member gets an editor row on the project (see agent onboarding).
- Agent breaks work into tasks, assigns itself or humans, links blockers when sequencing matters.
- Agents and humans comment on tasks as the work happens (see comments workflow).
- Any dashboard or status meeting reads
/v1/progressand/v1/roadmap— a pure read (see progress reports).
Tips
- Due-dated ordering is built in:
?order=dueputs dated tasks first — good for "what's next". see_assigned_onlykeeps a focused agent blind to everything but its own queue.- Blockers encode "don't start until" — much safer than agents deciding order each run (see blockers guide).
Related: Quickstart Path B · Progress reports