Keep the initiative and its reviews together.
Connect objectives, work and reviewable deliverables in an optional Project. People and agents share context while each original Resource keeps its own access and history.
Launch candidate · independent qualification pending
Launch candidate · independent qualification pending. CP-039/040 will assess release claims and real human acceptance.
Start with an objective. Add structure when it helps.
Create an empty Project or choose an editable template. A checklist can be enough. Trackers, packages and review sessions remain optional, and a review can gain a Project association later.
Link the existing PR, Draft, Form, Research Study or preview review instead of copying it. The same Resource can support more than one Project with its original revisions and app-native discussion.
A shared workbench with explicit access.
Overview holds purpose and objectives; Work holds linked deliverables; Reviews opens the artifacts people need to read. Activity and Settings support continuity and lifecycle.
Team Projects default to workspace visibility, with a participants-only option. Workspace membership, Project participation, agent grants and original source permissions are checked independently. A Project link never grants repository access.
Understand what is done and what still needs a decision.
Execution status, review status, evidence and human acceptance remain separate. An agent reporting completion does not create an approval; archiving or completing a Project does not accept its deliverables.
Review-connected progress can point to the current feedback and existing Inbox request. People decide exact outcomes; agents receive structured correction context.
Different jobs, connected authority.
Use the smallest surface that answers the current question. Keep the reviewable artifact central.
| Job | Surface | Authority |
|---|---|---|
| Organize an initiative | Optional Project | Original Resources keep their ownership, history and access. |
| Understand execution | Typed Tracker and native views | Record status describes execution; review and acceptance are separate. |
| Review the result | Rendered package and exact Review Session | App-native threads remain the primary discussion record. |
| Assess a claim | Requirements, reports and provider observations | Reported and independently observed evidence retain distinct provenance. |
| Accept an outcome | Exact human Interaction Decision | An eligible human decides the immutable scope; revisions can make it stale. |
Core organization is Free.
Projects, Trackers, native views, portability, package/session basics and agent access use the shared Free entitlements. Approved advanced renderer hosting, Git writeback, evidence and impact are usable Pro-preview during no billing.
GitHub writes require independent authorization. Azure writes are unsupported. Package and renderer content has separate trust tiers; bundles never receive app credentials.