Specification · audit export
awaiting approval
Product
The record, the roles, the approvals and the evidence
Four parts of one delivery control plane. A canonical Work Item every view reads from, delivery authority that comes from project membership, human approval of exact revisions, and evidence that states where it came from. The first two are available; the last two are in development.
01 · Work Item · available
One Work Item, every view
Epics, stories, tasks, bugs, service requests, change requests and subtasks are one record. The backlog, list, board, My Work, saved views, search and counts all read it through the same query, so status and counts cannot disagree between views.
- Stable project-local references and immutable event history
- Hierarchy rules, blockers, labels, estimates and watchers
- Archival keeps the record instead of deleting it
WEB-30 · Epic · Reporting
WEB-41 · Story · Export invoices as CSV
WEB-44 · Bug · Fix date filter blocked
WEB-45 · Task · Update report help text
02 · Membership · available
Delivery authority comes from the project
Team roles govern the workspace and billing. Delivery authority comes from project membership: product owner, developer, tester, QA, client owner and client collaborator. An active project always has one accountable product owner, and clients join through an invitation with explicitly granted permissions.
team your Team
team role member
project Client portal rebuild
project role developer
accountable one product owner
client external member · invited
03 · Approvals · in development
Agents propose, people approve
For Git-backed tickets the workflow is fixed: brainstorming, a specification a person approves, a plan a person approves, execution, evidence review, then acceptance and closure by a person. An approval binds to the exact revision and content hash, so changed content needs a new approval.
04 · Evidence · in development
Evidence that says where it came from
Test runs and code references are recorded with a provenance level. A caller may submit evidence but never assign itself a stronger level. Passing tests and an Agent's completion report never close a ticket: a person accepts the exact code state and evidence.
self_attested submitted by an Agent client
repository_verified confirmed by a repository read
ci_verified confirmed by CI
human_verified ruled on by a person
Plan your next project from one record
Teams, projects and Work Items are available now. Talk to us if you want to follow the Agent workflow while it is in development.