Skip to content

feat(spec): reconcile execution-control contracts with current runtime surfaces#104

Closed
mdheller wants to merge 9 commits into
mainfrom
spec-contract-pack-v0-3-20260507
Closed

feat(spec): reconcile execution-control contracts with current runtime surfaces#104
mdheller wants to merge 9 commits into
mainfrom
spec-contract-pack-v0-3-20260507

Conversation

@mdheller
Copy link
Copy Markdown
Contributor

@mdheller mdheller commented May 7, 2026

Summary

Fresh replacement for the stale/closed execution-control tranche. This branch is based on current main after the recent agent-harness, runtime-observability, OpsHistory, reasoning, Agent Machine, local runtime, browser, and shell receipt tranches.

What changed

Adds a reuse-first reconciliation note:

  • docs/execution-control-reconciliation-v0.3.md

Adds six net-new top-level schemas that remain non-overlapping after upstream movement:

  • schemas/ExecutionFork.json
  • schemas/RoutingContract.json
  • schemas/ToolExposurePolicy.json
  • schemas/QuotaPolicy.json
  • schemas/RunnerGroup.json
  • schemas/ProtocolWorkbench.json

Explicitly deferred from the prior tranche

The prior branch proposed additional objects that now overlap with upstream work and are intentionally deferred here:

  • CapabilityPolicy — defer to existing Policy, PolicyDecision, CapabilityToken, and CapabilityLedger until a genuine missing shape is proven.
  • ArtifactDescriptor — defer until reconciled with AgentHarness download artifact receipts, RuntimeInstall receipts, OpsHistory, and Memory Mesh artifact pointer conventions.
  • ValidationProgram — profile WorkflowSpec.
  • AgentSkillBundle — profile SkillManifest.
  • GovernedRun — profile RunRecord and AgentHarnessExecutionReceipts.
  • CairnEvidenceManifest — profile TruthSurface, DeltaSurface, and existing provenance/receipt contracts.

Why

Current sourceos-spec/main moved substantially since the earlier branch. This PR avoids duplicate schema classes and preserves the missing control-plane vocabulary:

  • lightweight execution forks
  • routing contracts
  • tool exposure policy
  • quota policy
  • runner bundles
  • protocol workbenches

Validation / upstream check

Before opening this PR:

  • Verified the prior PR #20 is closed and unmerged.
  • Verified the old branch was hundreds of commits behind current main.
  • Searched for exact schema names in current sourceos-spec; no direct matches were found.
  • Sampled recent upstream families to avoid overlap with agent harness receipts, runtime observability, OpsHistory, reasoning contracts, Agent Machine/model carry projections, and local runtime contracts.
  • Compared this branch against main: ahead by 7, behind by 0.

Deliberate scope limits

  • No ADR.
  • No examples yet; examples should follow after schema review.
  • No OpenAPI/AsyncAPI changes yet.
  • No derived profile work in downstream repos yet.

Follow-on work

  1. Add examples for the six accepted net-new schemas.
  2. Add focused validators after the schemas stabilize.
  3. Add catalog and changelog entries.
  4. Add derived profile mappings in SocioProphet/socioprophet-agent-standards.
  5. Wire consumers in agentplane, policy-fabric, TriTRPC, workstation-contracts, and openclaw.

mdheller added a commit that referenced this pull request May 23, 2026
Replays the execution-control contract tranche from #104 onto current main.

Captured:
- execution-control reconciliation note
- ExecutionFork
- RoutingContract
- ToolExposurePolicy
- QuotaPolicy
- RunnerGroup
- ProtocolWorkbench
- matching examples
- focused validator and workflow

Validation on 4e7cfc8:
- Execution Control Contracts: success
- validate-ops-history: success

Supersedes #104.
Copy link
Copy Markdown
Contributor Author

Capture update: superseded by #111.

#111 replayed this execution-control tranche onto current main and merged as d5af546333b4d05435055101cd4d349c7f501671.

Captured:

  • docs/execution-control-reconciliation-v0.3.md
  • schemas/ExecutionFork.json
  • schemas/RoutingContract.json
  • schemas/ToolExposurePolicy.json
  • schemas/QuotaPolicy.json
  • schemas/RunnerGroup.json
  • schemas/ProtocolWorkbench.json
  • matching examples for all six schemas
  • tools/validate_execution_control_examples.py
  • focused Execution Control Contracts workflow

Validation observed on #111 head 4e7cfc8f79d57872f42a4347281d7a476e9901b7:

  • Execution Control Contracts: success
  • validate-ops-history: success

Content status: fully captured. This draft can be closed as superseded.

@mdheller mdheller closed this May 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant