Rolling out to a team

The whole value is that everyone reads the same canvas. These four habits are what keep that true once more than one person can edit it.

1. 01One canvas, not one per personMake a single canvas the team's source and invite editors to it. Two canvases with similar contents is the failure this product exists to prevent.
2. 02A token per repo, not per personIssue one token per repository and name it after the repo. When a repo is archived or a vendor leaves, revoking one token takes the access away without touching anything else.
3. 03Lock it once it is realA locked canvas turns every edit into a proposal with a before, an after and a reason. Owners approve; everyone else still reads.
4. 04Review the queue, not the pull requestsDesign decisions land in the approval queue instead of being argued in code review. The change is recorded once, and every agent picks it up on the next prompt.