Skip to content

Define execution provenance v1 (#69) #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
andrewperis merged 3 commits into from
Sep 11, 2026
Merged

Define execution provenance v1 (#69) #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
901543a
Define execution provenance v1
andrewperis Sep 11, 2026
6b6f192
Add provenance conformance fixtures and assessment
andrewperis Sep 11, 2026
416f049
Enforce provenance policy and execution invariants
andrewperis Sep 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,14 @@ compatible, or editorial.

## Unreleased

- Hardened the unreleased Execution Provenance candidate after PR #9 review:
enforce identity policy, portable domains, status/finish relationships,
structured processing identity and timestamp formats; add 64 conformance cases.

- Added Execution Provenance v1.0.0 (new candidate contract): metadata-only
records, canonical identity, classification-aware redaction, observer failure
isolation, RFC 0005, and synthetic conformance fixtures for issue #69.

- Added the Structured Output v1.0.0 candidate (new contract): RFC 0004,
validated result/failure schema, raw/normalized identity, exact schema
verification, retention and provider-constraint provenance, explicit failure
Expand Down
23 changes: 23 additions & 0 deletions CONSTITUTION_CONFORMANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,28 @@
# Constitution conformance record

## Issue #69 assessment — 2026-09-11

PR #9 review follow-up: all five schema findings addressed with 64 passing
schema conformance cases. Policy suppression, numeric domains, outcome pairing,
processing identity and date-time format assertion are enforced. Platform's
pinned consumer validator is refreshed in its coordinated existing PR #12.

This assessment extends and supersedes the prior issue #68 scope below for the
current candidate. Constitution v1.0.0 at
`a9cc8a503aa30e17820edc62ac95f7cbe10e0564` remains the authority.
Accountable owner: @andrewperis; status: Conforming candidate pending owner merge.
Base revision: `7fe034e508fdda2c70eb111c0517e1fe115e818b`.

Scope: Execution Provenance v1 candidate schema, RFC 0005, specification, redaction policy and synthetic fixtures.
Evidence: Coordinated Platform suite: 74 passing tests, including public/non-public context projection, identity tampering, structured outcomes and observer failure isolation.
No new constitutional exceptions. Public fixtures are synthetic. Body content,
authorization and diagnostic strings are omitted; non-public content identities
are suppressed. Sinks cannot change the provider result or trigger retries.
Caller-owned opaque identifiers, production sink retention/access controls and
immutable contract publication (#72) remain outside this candidate.
The schema defines a new independent candidate contract; existing contracts are unchanged.
Next review: before release or any security-boundary/dependency change.

## Constitutional alignment

- Constitution: [Definitely Secure Studio Constitution v1.0.0](https://github.com/DefinitelySecureStudio/studio/tree/constitution/v1.0.0)
Expand Down
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@

Stable specifications and contracts for Definitely Secure Studio systems.

The [Execution Provenance v1 candidate](specs/execution-provenance/README.md)
defines metadata-only execution evidence and observer policy.

> [!NOTE]
> This repository defines contracts. It does not implement production software
> and it does not own creative canon or private lore.
Expand Down
17 changes: 17 additions & 0 deletions fixtures/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,22 @@
# Conformance fixtures

Execution Provenance v1: `valid/execution-provenance-v1.json` is the synthetic
Platform observer example. `invalid/execution-provenance-v1.json` adds a
forbidden body field; closed-schema validation must reject it (its digest also
no longer matches). Digest tampering is separately tested by Platform.

`execution-provenance-v1-cases.json` contains schema-only overlays on the valid
fixture: `set` uses dotted record paths and `remove` names record fields. These
are not standalone envelopes; digest recomputation is deliberately excluded to
isolate schema rejection. The runner checks policy, parameter boundaries, every
status/finish pair, processing ids and RFC 3339 formats (including invalid dates).
With Platform's locked Ajv 8.20.0 and ajv-formats 3.0.1 installed in a sibling
checkout, run from Codex:

```sh
NODE_PATH=../platform/node_modules node --test tests/execution-provenance.test.cjs
```

Synthetic examples that demonstrate contract conformance belong here.

- [`valid/`](valid/) contains inputs that must pass validation.
Expand Down
Loading