Prepare proposal
What an agent can hand a human or dedicated signer for review. Prepare does not commit.
Section guide: Records. Sequence: Write path. Authority: Access model.
Illustrative only. Not a published data model. The durable contract is the authority sequence (simulate → prepare → external sign → submit_signed), not these field names.
What this illustrates
| Idea | Buyer meaning |
|---|---|
| Proposal identity | Which change is under review |
| Base revision | Which shared-record revision the proposal starts from |
| Intended effect | What would change if signed and submitted |
| External signature required | Humans (or a dedicated signer) keep write finality |
commit: false | Nothing lands until a signed submit |
Example (synthetic)
{
"proposal_kind": "legate_prepare",
"proposal_id": "prep_example_1001",
"scope_id": "scope_example_001",
"base_revision": "rev_example_42",
"created_at": "2026-08-06T18:05:00Z",
"actor": {
"type": "agent",
"credential_ref": "cred_example_short_lived"
},
"intended_effect": {
"summary": "Example update to shared operational fields"
},
"commit": false,
"requires": {
"external_signature": true,
"write_consent": true,
"pack": "legate.write"
}
}
Do not paste production prepare payloads into public tickets.