From source material to a reviewable change

Suppose a new interface specification says that the webshop now sends orders to ERP. Start by asking the client to show the current link and any existing change requests. Work in a small scope and keep each proposed fact tied to the material that supports it.

Read and draft

1. Confirm the workspace and permissions with get_identity.
2. Locate the existing records and links. Use pull_workspace for a typed snapshot when available. Check coverage, excluded types and pagination before using it as your basis.
3. Ask for a proposed diff and source references before any submission. If the documents disagree or the recipient is unclear, keep it as a question for the owner.

Validate and submit deliberately

Ask the client to use validate_changes on the same items it plans to submit. Fix errors, review warnings and check the IDs of any records resolved by name. Validation checks the draft and creates no model changes. It is a separate check from wider landscape quality. Check Verify, missing relationships and supporting evidence for the latter.

Use an explicit change request when the edits should be grouped and reviewed together. A human's MCP call can write directly when the workspace mode and permissions allow it, so confirm the submission route before calling propose_changes. Agents submit proposals. Ask the client to return the result or request ID and identify whether it wrote a record, added a request item or created a proposal.

Review and confirm the result

Open the change request on Governance > Change requests (/changes) in Atlas, inspect the items and check their sources. An MCP review_url opens that request at /changes/<id>; old /settings/mcp/proposals/<id> bookmarks redirect to the same request. Where your role allows it, you can reject one item, edit its JSON payload before applying it, or accept the low-risk items while leaving structural items open for review. For a dated change, return after implementation and compare the resulting fact sheet to the intended change. If the workspace revision changed, read again and reconcile your draft before submitting.

For the distinction between validating a draft, reviewing its evidence and checking workspace quality, see Validate changes and inspect quality.