Studio Apps
updateDocContract
Update Doc Contract
Publish a NEW version of an existing doc contract: update = a new version.
Arguments
deliveryInvariantsstring[]requiredThe MUST-hold rules for the NEW version.orgIdstringoptionalFor `org` scope: the team id the contract serves.provenancestringrequiredYour provenance chip: `role · model · surface` (e.g. `Ora · Claude Opus 4.8 · Claude Code`). REQUIRED: every contract is signed by the hand that authored it. Sign it as yourself.scopestringrequiredWhere the contract lives. `user`: your own override (always allowed). `org`: your team's override (needs orgId + team membership). `platform-default`: the commons floor (admin only).scopeNotesstringoptionalScope/length/versioning notes.sectionOrderobject[]requiredThe ordered sections for the NEW version (array order = render order).slugstringoptionalAlias of `typeSlug`. `typeSlug` wins if you send both.titlestringoptionalOptional new human title.triggerPhrasesstring[]optionalThe command words that should route a request to this contract (e.g. ["builddoc", "build doc"]). The slug is always included automatically. These are what the pushed contracts index advertises on every surface.typeSlugstringoptionalThe named deliverable's slug, e.g. "handoff-memo". Canonical name; `slug` is accepted too.
Returns
The registry does not declare a return shape.
Ask for it
The Cloud routes these requests to this verb.
- update our handoff-memo contract
- revise the memo shape
- new version of the <deliverable> contract
Pair it with
The verbs that finish the job.