Shared work. The view that makes it clear.
Use a small typed schema and one set of records across checklist, list, table, board, timeline, calendar, Gantt and summary views. Keep execution readable without treating a status as acceptance.
Launch candidate · independent qualification pending
Launch candidate · independent qualification pending. CP-039/040 will assess release claims and real human acceptance.
Switch the perspective, keep the records.
Saved native views map your fields to the presentation. A board needs a compatible status mapping; scheduling views need mapped dates. Missing mappings produce diagnostics instead of invented dates or status.
Edit through native controls, use keyboard alternatives for moves, and reconcile a stale version before saving. Shared and personal views support different reading jobs over the same authoritative dataset.
Choose authority deliberately.
Portable JSON/YAML preserves stable record identities and versioned schemas. Import preview lets you review cloning or reconciliation before changing records. Git authority migration switches only after exact source confirmation.
GitHub writeback requires current provider write authority and an approved source binding. Azure supports authorized reads and imports with explicit unsupported-write diagnostics. A local file or Project association is never an access grant.
Customize presentation within a narrow capability boundary.
Use declarative native Tracker embeds in documents, or the framework-neutral Tracker SDK for a custom renderer. The broker checks current authority for each operation; the bundle receives no app credentials.
Hosted or external renderers require the isolated content gateway and explicit capabilities. Static assets are served without customer server builds. Native fallback remains available when configuration or authority is unavailable.
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.