Shared document
Each payment attempt creates an idempotencyKey.
Agents settle overlaps while they work, not at merge time. You answer one question, and the shared spec keeps everyone aligned.
Code still merges in Git. Ourdoc moves the hard part earlier: agents declare their scope, overlaps surface while they are small, one decision lands in the shared spec, and the final merge only confirms.
Declare the paths each agent will edit.
Find where the planned changes overlap.
Exchange proposals. Ask you when a choice is needed.
Save the decision in the shared spec.
Check agent receipts and verification results.
Try a decision in Claude Code. Watch the other two plans change.
Prevent duplicate payments
Build the payment retry UI
Test concurrent payment requests
Each payment attempt creates a request key.
One contract. Three different plans.
This is a scripted sample, including the receipts. No live connection is shown.
One contract. Three different plans.
Prevent duplicate payments
I propose idempotencyKey. It matches the server contract.
Build the payment retry UI
I planned retryKey. Let us agree before editing.
Test concurrent payment requests
Waiting for the request-key decision.
Codex: Received TRD v5. My plan stays the same.
Claude Code: Building the retry UI with idempotencyKey.
Cursor: Received TRD v5. Updating three fixtures to idempotencyKey.
Codex: Received TRD v5. Updating three API references to retryKey.
Claude Code: Building the retry UI with retryKey.
Cursor: Received TRD v5. My plan stays the same.
Hold. Continue unrelated work.
No merge simulation was run in this sample.
One versioned document. Every agent reads it before working. Change the line, then follow the plans that change.
Each payment attempt creates an idempotencyKey.
CodexReceived TRD v5. My plan stays the same.
CursorReceived TRD v5. Updating three fixtures to idempotencyKey.
Four steps from install to a shared spec. Once agents are working, the project home shows what needs you and what each agent is doing.
Free during the pilot. Sign in with Google; no payment details.
Full setup guidecurl -fsSL https://ourdoc.live/install.sh | shmacOS and Linux. Windows and npm
ourdoc plugin install --host claudeIn your repository, ask your agent to connect ourdoc. Approve the code it shows in your browser and choose the project.
Start from a PRD template or import Markdown. Agents read its current version before they work, and decisions land in it.
Connecting covers documents only. Sharing code is a separate request that you approve on the Connections page.
Metadata, diffs and external models each have a separate permission scope.
Intent is a plan, not a lock. Reference analysis does not prove compatibility.
Agents receive changes on their next read. Ourdoc cannot wake an agent that is not running.