Skip to content

docs: add broker reasoning execution binding and bundle contract#53

Merged
mdheller merged 7 commits intomainfrom
docs/broker-reasoning-binding
Apr 29, 2026
Merged

docs: add broker reasoning execution binding and bundle contract#53
mdheller merged 7 commits intomainfrom
docs/broker-reasoning-binding

Conversation

@mdheller
Copy link
Copy Markdown
Member

@mdheller mdheller commented Apr 26, 2026

Summary

Adds the AgentPlane execution binding for the cross-cloud services broker reasoning loop and a concrete broker execution bundle contract.

Adds

  • docs/integration/broker-reasoning-execution-binding.md
  • schemas/broker-execution-bundle.schema.v0.1.json
  • examples/broker-execution-bundle.example.json
  • scripts/validate_broker_execution_bundle.py
  • GitHub Actions validation for the bundle contract and general JSON/Python hygiene

Scope

AgentPlane executes and emits evidence. It does not own broker doctrine or policy authority.

Comment thread .github/workflows/broker-execution-bundle.yml Fixed
Copy link
Copy Markdown
Member Author

Repair status: I added explicit permissions: contents: read to the new workflow and added a branch-local lint workflow/job context. The latest head currently has no workflow/status emission in the connector view, so merge is blocked until CI emits the required protected check contexts. Once checks appear green, retry squash merge.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds an AgentPlane “broker reasoning execution binding” document and introduces a concrete “broker execution bundle” contract (schema + example) with CI validation to keep the contract and example in sync.

Changes:

  • Add integration documentation describing AgentPlane’s execution/replay responsibilities for broker reasoning.
  • Introduce broker-execution-bundle JSON Schema v0.1 plus a worked example JSON file.
  • Add a Python validator script and GitHub Actions workflows to validate/compile/verify these assets in CI.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file
File Description
docs/integration/broker-reasoning-execution-binding.md New integration guide describing AgentPlane’s role and expected inputs/outputs.
schemas/broker-execution-bundle.schema.v0.1.json New JSON Schema defining the broker execution bundle contract.
examples/broker-execution-bundle.example.json Example payload intended to validate against the new schema.
scripts/validate_broker_execution_bundle.py Schema/example validator used by CI workflow.
.github/workflows/broker-execution-bundle.yml CI workflow to run the schema/example validator on relevant changes.
.github/workflows/lint.yml New lint workflow for JSON validity + Python compilation (currently misconfigured).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

example = load_json(EXAMPLE)
Draft202012Validator.check_schema(schema)
validator = Draft202012Validator(schema)
errors = sorted(validator.iter_errors(example), key=lambda error: list(error.path))

- name: Compile Python scripts
run: |
python3 -m py_compile scripts/validate_meshrush_candidate.py
Comment on lines +1 to +9
name: broker-execution-bundle

on:
pull_request:
paths:
- "schemas/broker-execution-bundle.schema.v0.1.json"
- "examples/broker-execution-bundle.example.json"
- "scripts/validate_broker_execution_bundle.py"
- ".github/workflows/broker-execution-bundle.yml"
Comment on lines +1 to +4
# Broker Reasoning Execution Binding

## Purpose

Comment on lines +1 to +4
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "BrokerExecutionBundle v0.1",
"type": "object",
- provider adapter conformance tests
- exit-plan simulations
- continuity tests
- cost-meter validation jobs
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a “broker execution bundle” contract (schema + example + validator + CI workflow) and documents AgentPlane’s role as the governed execution/replay plane for broker reasoning.

Changes:

  • Introduces BrokerExecutionBundle JSON Schema v0.1 plus a matching example and a validation script.
  • Adds a dedicated GitHub Actions workflow to validate the example against the schema.
  • Adds a new integration guide documenting the broker reasoning execution binding (AgentPlane responsibilities, inputs, outputs).

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file
File Description
scripts/validate_broker_execution_bundle.py Validates the example bundle JSON against the new JSON Schema.
schemas/broker-execution-bundle.schema.v0.1.json Defines the v0.1 BrokerExecutionBundle schema.
examples/broker-execution-bundle.example.json Provides a sample bundle intended to validate against the schema.
docs/integration/broker-reasoning-execution-binding.md Documents AgentPlane’s responsibilities and evidence outputs for broker-related execution.
.github/workflows/lint.yml Adds a new lint workflow (currently contains a failing py_compile target).
.github/workflows/broker-execution-bundle.yml Adds CI validation for the broker execution bundle schema + example.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +5 to +8
AgentPlane is the governed execution and replay plane for the cross-cloud services broker model.

It does not own broker doctrine or policy authorship. It validates, places, runs, and replays broker-related execution bundles and emits evidence artifacts.

@@ -0,0 +1,49 @@
# Broker Reasoning Execution Binding
Comment on lines +7 to +21
"bundle_id": { "type": "string", "minLength": 1 },
"purpose": { "type": "string", "minLength": 1 },
"provider_binding_id": { "type": "string", "minLength": 1 },
"policy_decision_id": { "type": "string", "minLength": 1 },
"execution_type": { "type": "string", "enum": ["validation", "smoke", "continuity", "exit", "cost_meter", "evidence_completeness"] },
"placement_constraints": { "type": "array", "items": { "type": "string" } },
"expected_artifacts": {
"type": "array",
"items": { "type": "string", "enum": ["ValidationArtifact", "PlacementDecision", "RunArtifact", "ReplayArtifact"] },
"minItems": 1
},
"evidence_refs": { "type": "array", "items": { "type": "string" } },
"max_run_seconds": { "type": "integer", "minimum": 1 }
},
"required": ["bundle_id", "purpose", "provider_binding_id", "policy_decision_id", "execution_type", "expected_artifacts", "max_run_seconds"]
Comment on lines +2 to +20
"bundle_id": "bundle-provider-binding-smoke-001",
"purpose": "Smoke-test approved ProviderBinding before production use.",
"provider_binding_id": "binding-standard-app-env-public-cloud-001",
"policy_decision_id": "decision-standard-app-env-001",
"execution_type": "smoke",
"placement_constraints": [
"linux-executor",
"network-restricted"
],
"expected_artifacts": [
"ValidationArtifact",
"PlacementDecision",
"RunArtifact",
"ReplayArtifact"
],
"evidence_refs": [
"evidence.standard-environment.v1"
],
"max_run_seconds": 600
Comment on lines +1 to +4
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "BrokerExecutionBundle v0.1",
"type": "object",

- name: Compile Python scripts
run: |
python3 -m py_compile scripts/validate_meshrush_candidate.py
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR introduces a first cut of a “broker execution bundle” contract (schema + example), adds CI validation for it, and documents the intended AgentPlane execution/replay binding for the broker reasoning loop.

Changes:

  • Add BrokerExecutionBundle JSON Schema v0.1 plus a corresponding example bundle JSON.
  • Add a Python script + GitHub Action workflow to validate the example against the schema using jsonschema.
  • Add a new integration doc describing AgentPlane’s responsibilities/inputs/outputs for broker-related execution and evidence.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
scripts/validate_broker_execution_bundle.py Validates the example bundle JSON against the new schema in CI.
schemas/broker-execution-bundle.schema.v0.1.json Defines the v0.1 JSON Schema contract for broker execution bundles.
examples/broker-execution-bundle.example.json Provides a concrete example expected to validate against the schema.
docs/integration/broker-reasoning-execution-binding.md Documents the AgentPlane execution binding and artifact expectations.
.github/workflows/lint.yml Adds a lint workflow (currently has a broken Python compile target).
.github/workflows/broker-execution-bundle.yml Adds focused CI to validate the schema+example via the new script.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +5 to +7
AgentPlane is the governed execution and replay plane for the cross-cloud services broker model.

It does not own broker doctrine or policy authorship. It validates, places, runs, and replays broker-related execution bundles and emits evidence artifacts.
Comment on lines +1 to +3
# Broker Reasoning Execution Binding

## Purpose
Comment on lines +19 to +21
- cost-meter validation jobs
- policy-decision replay jobs
- evidence completeness checks

- name: Compile Python scripts
run: |
python3 -m py_compile scripts/validate_meshrush_candidate.py
@mdheller mdheller changed the title docs: add broker reasoning execution binding docs: add broker reasoning execution binding and bundle contract Apr 29, 2026
@mdheller mdheller force-pushed the docs/broker-reasoning-binding branch from a92f690 to 3794ab9 Compare April 29, 2026 17:33
@mdheller mdheller merged commit 1665f86 into main Apr 29, 2026
12 checks passed
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.

3 participants