Independent runs over one law
Register one immutable scenario law, then create a distinct RunKey per agent,
job, or tenant activity. Progress, attempts, submissions, and intents never
cross runs merely because the law is shared.
Shared run with several agents
All writers read the exact accepted head and stage classifications. A writer submits one complete mutation against that head. If another writer commits first, the stale writer commits nothing, reads the new head, and re-derives. Opening attribution never implies ownership; separately authorized principals may evaluate the stage.
Parallel ready frontier
When one completion unlocks 2a, 2b, and 2c, the frontier reports all
three. A harness may open one, several, or none. DG never chooses a branch,
cancels siblings, or infers exclusivity from adjacency. Exclusive domain
choices must be expressed as explicit accepted evidence/law, not hidden graph
behavior.
External coordinator
A coordinator can implement leases, assignment, affinity, work stealing, and agent-count policy using:
- exact run heads;
ReadyUnopened,OpenIncomplete, andCompletedsets;- explicit stage IDs and stable operation IDs;
- accepted history and typed conflicts.
Those coordination records remain outside Xarxa and semantic stage state.
Cross-scenario evidence
The current OSS family mints no specialized cross-scenario fact witness. A generic provider observation must not be represented as DG-owned proof of an external law/run/head. A future admitted external fact must bind exact external law, run, head, and freshness identities. Do not hide recursive execution inside a provider or evaluator; DG-owned multi-scenario orchestration remains deferred.
Runpack export
Export runpack v6 only after the desired accepted head exists. The export authority captures that exact historical checkpoint, so later mutations cannot change the subject. The configured local repository is capability-rooted and publishes content-addressed objects before the manifest.
Verify only bundled or explicitly supplied local material. The independent verifier constructor-replays accepted history, compares current state and all indexed record families, and emits every row in the closed claim registry. Treat each row according to its exact method and prerequisites. Digest-only evidence cannot support semantic replay; content integrity does not establish source authenticity, currentness, rollback resistance, dispatch, or deployment.