Skip to content

Draft: add core agent-plane schema scaffolds - #1

Merged
mdheller merged 16 commits into
mainfrom
feat/agent-plane-core-schemas-v0
Apr 5, 2026
Merged

Draft: add core agent-plane schema scaffolds#1
mdheller merged 16 commits into
mainfrom
feat/agent-plane-core-schemas-v0

Conversation

@mdheller

Copy link
Copy Markdown
Contributor

What this lands

This draft PR adds the first six core agent-plane schema scaffolds:

  • ExecutionDecision.json
  • AgentSession.json
  • ExecutionSurface.json
  • SkillManifest.json
  • MemoryEntry.json
  • SessionReceipt.json

Why now

The current public sourceos-spec surface is strong on metadata / governance / batch-run objects, but it does not yet name the core runtime law needed by the agent plane. These scaffolds are the smallest clean-room patch that starts to close that gap without overloading existing data-plane objects such as CapabilityToken, PolicyDecision, WorkloadSpec, or RunRecord.

Non-goals in this PR

This draft does not yet:

  • patch openapi.yaml
  • patch asyncapi.yaml
  • add tool/session/promotion/reversal artifacts
  • add the second-wave leak-derived objects (SessionReview, ExperimentFlag, RolloutPolicy, TelemetryEvent, FrustrationSignal, ReleaseReceipt)

Follow-up queue

  1. Wire the new schema family into OpenAPI / AsyncAPI.
  2. Patch SociOS-Linux/agentos-starter interfaces (MemoryAPI, Orchestrator, Executor).
  3. Extend SocioProphet/agentplane bundle / artifact schemas.
  4. Add validator/admission wiring in SociOS-Linux/imagelab.
  5. Normalize SourceOS-Linux/openclaw runtime surfaces against these contracts.

Clean-room posture

This work is based on public repo surfaces and public reporting about Claude Code’s leak-era lessons. It does not copy proprietary Anthropic implementation details.

@mdheller
mdheller marked this pull request as ready for review April 5, 2026 19:33
@mdheller
mdheller merged commit fb72d6f into mainApr 5, 2026
mdheller added a commit that referenced this pull request Aug 2, 2026
Copilot #2: InferenceReceipt off-device gate under-enforced — escalationChain
was not in the 'then' required list (minItems never fired if omitted) and
escalatedFrom could still be null. Now both are required+non-null for any
off-device (sovereign_cluster/external_permitted) receipt. Negative tests
added: missing/empty escalationChain and null escalatedFrom now all reject.
Copilot #1: unify field name — EscalationDecision.grantRef -> capabilityLeaseRef
to match InferenceReceipt for the same urn:srcos:lease: concept (schema +
example + ADR + CHANGELOG).
Sign up for freeto 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

@mdheller