docs: add public repo front door and missing execution contracts#14
docs: add public repo front door and missing execution contracts#14
Conversation
Signed-off-by: mdheller <21163552+mdheller@users.noreply.github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: be7306bb1d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "capturedAt", | ||
| "valid", | ||
| "checks" |
There was a problem hiding this comment.
Align required ValidationArtifact fields with emitter output
The new schema requires capturedAt, valid, and checks, but scripts/validate_bundle.py currently writes validatedAt and result and does not emit a checks array (see the report object in that script). This means the validation artifact produced by the existing workflow cannot satisfy the published contract, so any schema-based validation step will fail for every run.
Useful? React with 👍 / 👎.
|
Re-checked against current Confirmed
So this PR remains the correct rebased scope:
Two useful follow-ons still remain after merge:
External positioning remains strongest as workflow orchestration / execution control, not agent gatewaying, based on the current public surface. |
Summary
This PR captures the still-missing public-surface delta on top of the current
mainbranch.It does not try to replay the older hardening pack. Instead it preserves the newer work already on
main:examples/receipts/docs/runtime-governance/control-matrix-integration.mdWhat this adds
README.mdso the repo no longer presents as a file tree plus About textdocs/replay-boundary.mdto make the currentReplayArtifactcontract explicitschemas/validation-artifact.schema.v0.1.jsonschemas/placement-decision.schema.v0.1.jsonWhy
Publicly,
agentplaneis currently strongest as workflow orchestration / execution control:mainBut two concepts already present in scripts/docs were not yet first-class public schema files on
main:ValidationArtifactPlacementDecisionAnd the repo still lacked a root reader path plus a concise replay-boundary note.
Deliberately not included
This PR does not yet resolve the naming seam between
PlacementDecisionandplacement-receipt.json.That should be a follow-up cleanup once we decide whether one becomes canonical and the other derived.
Files changed
README.mddocs/replay-boundary.mdschemas/validation-artifact.schema.v0.1.jsonschemas/placement-decision.schema.v0.1.json