Projects
Projects tracks each body of work toward a Goal: its Tasks and Issues, start and target date, triage and assignees.
Projects tracks each body of work toward a Goal: its Tasks and Issues, dates, triage and assignees, whether Humans or Agents. Issues live in db.sb; a GitHub repository can mirror them.
Summary
| Part | This System |
|---|---|
| Group | Moves to Code |
| Status | Beta: it works, and its Verbs may still change |
| Shelf | Front: offered from a Startup’s first days |
You can ask:
- “What is the team working on this week?”
- “File this bug”
- “Plan the next two weeks of work”
What you get
| Part | This System |
|---|---|
| Starts | On for every Startup at creation, with nothing to install. |
| Built from | Database, Workflows, Event streams |
Nouns it owns
| Noun | Definition |
|---|---|
| Project | A Project is a body of work toward a Goal: its Tasks and Issues, a start, and a target date. |
| Issue | An Issue is a Task reporting a problem or request, such as a bug or a feature request, with a reporter and a triage step. |
| Comment | A Comment is an internal note by a Worker about a Thing, never sent to a Contact. |
Verbs
| Verb | Object | Approval | Event |
|---|---|---|---|
| Project.create | Project | None | Project.created |
| Issue.triage | Issue | None | Issue.triaged |
| Issue.resolve | Issue | None | Issue.resolved |
| Issue.reopen | Issue | None | Issue.reopened |
| Comment.create | Comment | None | Comment.created |
| Issue.schedule | Issue | None | Issue.scheduled |
| Issue.estimate | Issue | None | Issue.estimated |
Events
| Direction | Event | How |
|---|---|---|
| Emits | Project.created | By Project.create |
| Emits | Issue.triaged | By Issue.triage |
| Emits | Issue.resolved | By Issue.resolve |
| Emits | Issue.reopened | By Issue.reopen |
| Emits | Comment.created | By Comment.create |
| Emits | Issue.scheduled | By Issue.schedule |
| Emits | Issue.estimated | By Issue.estimate |
States
None.
Who operates it
| Part | This System |
|---|---|
| Accountable | Product Lead |
| Team | Product Team |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | supervised |
| Also calls its Verbs | Reliability Engineer |
Approvals and limits
None.
Processes that use it
| Process | How it uses it |
|---|---|
| Iteration | A Workflow writes Issue |
| Shipping | A step calls Issue.triage |
| Onboarding | A Workflow writes Issue |
| Retention | A Workflow writes Issue |
| Support | A Workflow writes Issue |
| Compliance | A Workflow writes Issue |
| Verification | A Workflow writes Issue |
| Hiring | A Workflow writes Project |
| Vulnerability disclosure | A Workflow writes Issue |
| Barrier reports | A Workflow writes Issue |
| Continuity | A Workflow writes Issue |
Rail underneath
None.
Views and dashboards
| View | Shows | Metrics |
|---|---|---|
| The Product Lead’s view | The Metrics its accountable Role answers for. | Activation rate, Must-have share, Active calling keys, Declared Verb attempts, Time to first call |
Access
What each Access level may call here.
| Access level | May call |
|---|---|
owner | Every Verb (20) |
admin | Every Verb (20) |
member | Every Verb (20) |
viewer | Read only (6 of 20) |
Import and export
| Connector | Mode |
|---|---|
| GitHub | Mirror: the db.sb record leads and the tool reflects it. |
| GitHub | Import: edits made in the tool arrive as Changes. |
Fees and pricing
None.
Availability and limits
| Part | This System |
|---|---|
| Status | Beta: it works, and its Verbs may still change |
Compliance notes
Controls it carries:
- Log completeness
- Deviation closure
- Append-only records
- Point-in-time recovery
- Processing definitions
- Action completion
Related Systems
None.
Example
A Services-as-Software security-readiness package runs each client as a Project with 64 Tasks and a target date. The Product Lead Agent triages new Issues every morning and delegates evidence collection to Agents. Each client sees progress against the date, never a spreadsheet.