diff --git a/docs/comic-manifest-approvals.md b/docs/comic-manifest-approvals.md index 38031f9..651d29e 100644 --- a/docs/comic-manifest-approvals.md +++ b/docs/comic-manifest-approvals.md @@ -1,10 +1,12 @@ # Comic Manifest revision diffs and approval boundary (#95) -The unreleased `./comic-manifest` module adds `diffComicRevision` and -`createComicApprovalBoundary`. Both operate on explicit bounded raw JSON. They -do not read revision history, persist decisions, publish a release or promote -canon. Trust is injected by host code for each evaluation; no production trust -provider is installed here. +The immutable Platform Comic Manifest v1.0.0 GitHub release includes the +`./comic-manifest` module, with `diffComicRevision` and +`createComicApprovalBoundary`. The npm package remains private and was not +published to npm. Both functions operate on explicit bounded raw JSON. They do +not read revision history, persist decisions, publish a release or promote canon. +Trust is injected by host code for each evaluation; no production trust provider +is installed here. ## Current approval evaluation diff --git a/docs/comic-manifest-cli.md b/docs/comic-manifest-cli.md index 5b148bf..1d16c63 100644 --- a/docs/comic-manifest-cli.md +++ b/docs/comic-manifest-cli.md @@ -1,11 +1,13 @@ # Comic Manifest authoring CLI and offline reference flow (#97) -The unreleased `studio-comic` CLI is a local authoring and review aid over the -existing Comic Manifest APIs. It performs no network access, reference retrieval, -provider invocation, credential discovery, scheduling, retry, publication, or -canon write. The CLI does not load adapter modules. Production trust integrations -must call the library APIs from a separately reviewed host that installs current -approval, disclosure, attestation, and byte readers. +The `studio-comic` CLI is included in the immutable Platform Comic Manifest +v1.0.0 GitHub release. It is a local authoring and review aid over the existing +Comic Manifest APIs and performs no network access, reference retrieval, provider +invocation, credential discovery, scheduling, retry, publication, or canon write. +The CLI does not load adapter modules. The npm package remains private and was not +published to npm. Production trust integrations must call the library APIs from a +separately reviewed host that installs current approval, disclosure, attestation, +and byte readers. The implementation is additive to the package bin map. In a source checkout: @@ -14,8 +16,9 @@ npm ci node src/comic-manifest/cli.js --help ``` -The `studio-comic` executable is available when this private package is linked or -installed into a local workspace. No registry publication is part of this task. +The `studio-comic` executable can be used when this private package is linked or +installed into a local workspace; its package archive is also a GitHub release +asset. The package was not published to npm. ## Commands diff --git a/docs/comic-manifest-episodes.md b/docs/comic-manifest-episodes.md index fd82fca..8e15176 100644 --- a/docs/comic-manifest-episodes.md +++ b/docs/comic-manifest-episodes.md @@ -1,10 +1,12 @@ # Comic Manifest episode structure and revision relationships (#91) -The unreleased `./comic-manifest` module now adds four pure functions on top of -[#90's raw-input validator](comic-manifest-validation.md). They consume explicit -bounded JSON strings/Buffer/Uint8Array, return fixed value-free diagnostics on -failure, and perform no storage, retrieval, generation, rendering or publication. -The owner-merged Codex schema and released SDK/Builder bytes are unchanged. +The immutable Platform Comic Manifest v1.0.0 GitHub release includes the +`./comic-manifest` module and its four pure episode/revision functions, built on +[#90's raw-input validator](comic-manifest-validation.md). The npm package remains +private and was not published to npm. These functions consume explicit bounded +JSON strings/Buffer/Uint8Array, return fixed value-free diagnostics on failure, +and perform no storage, retrieval, generation, rendering or publication. The +owner-merged Codex schema and released SDK/Builder bytes are unchanged. ```js import { diff --git a/docs/comic-manifest-references.md b/docs/comic-manifest-references.md index 7823b63..7b7a838 100644 --- a/docs/comic-manifest-references.md +++ b/docs/comic-manifest-references.md @@ -1,6 +1,6 @@ # Comic Manifest immutable reference verification (#92) -The unreleased `./comic-manifest` module adds `planComicReferences`, +The immutable Platform Comic Manifest v1.0.0 GitHub release includes the `./comic-manifest` module with `planComicReferences`, `createComicReferenceResolver` and `COMIC_REFERENCE_LIMITS`. They implement the Codex v1 reference semantics, now pinned to the owner-reviewed [specification at merge 8044643](https://github.com/DefinitelySecureStudio/codex/blob/8044643bf888067f5a6e0d212f843d72e8787f2b/specs/manifests/comic-manifest-v1.md), @@ -224,10 +224,13 @@ are involved. Existing offline Builder conformance remains part of regression ch Constitution v1.0.0, tag `constitution/v1.0.0`, commit `a9cc8a503aa30e17820edc62ac95f7cbe10e0564`; Studio ADR 0018 at -`7b5065cef76bea9580609caba356b0d8fe7cc17c`. Owner @andrewperis reviews the exact -change. Universal, repository/production-system and automated-workflow profiles -apply to these controlled effects. The module remains unreleased, with production -adoption gated by #99. Existing normative schemas and foundation releases are -unchanged. Rollback removes the new resolver/planner exports and installed adapters; -it never rewrites historical artifacts or restores revoked permission. Reassess on +`7b5065cef76bea9580609caba356b0d8fe7cc17c`. Owner @andrewperis must review the +exact change; this guide records no Studio architecture acceptance. Universal, +repository/production-system and automated-workflow profiles +apply to these controlled effects. The implementation is included in the immutable +GitHub release, but the npm package remains private and unpublished to npm. +Production trust onboarding remains separately scoped; this release does not +provide production authorization. Existing normative schemas and foundation +releases are unchanged. Rollback removes consumer integration; it never rewrites +historical artifacts or restores revoked permission. Reassess on source, trust, classification, policy-clock, containment or downstream-use changes. diff --git a/docs/comic-manifest-release.md b/docs/comic-manifest-release.md index dc335e8..a4c0105 100644 --- a/docs/comic-manifest-release.md +++ b/docs/comic-manifest-release.md @@ -93,10 +93,13 @@ That acceptance applies only to the pinned golden packet. The separate owner A4 decision approved the exact Codex commit, tag and asset tuples for Codex publication; it did not approve Platform publication and is not represented as a human technical review of the released artifacts. -The task-specific Epic #6 A3 AI-review exception covered code-merge review only -and did not authorize the A4 release decision. No separate human review of final -release artifacts is claimed. The owner separately approved Platform publication for the exact built artifact -tuples now listed in the publication verification record. +The owner's October 6 AI-review/merge instruction was not registered as a formal +Constitutional exception. It does not establish human technical review of final +release artifacts or authorize A4 publication. No separate human review of the +final artifacts is claimed. The owner separately approved Platform publication +for the exact built artifact tuples listed in the publication verification +record. This Platform release guide makes no claim about Studio architecture +acceptance. ## Compatibility, deprecation, and support diff --git a/docs/comic-manifest-renditions.md b/docs/comic-manifest-renditions.md index 7a2d242..3ce3c71 100644 --- a/docs/comic-manifest-renditions.md +++ b/docs/comic-manifest-renditions.md @@ -1,7 +1,8 @@ # Comic Manifest rendition and publication outputs (#94) -The unreleased `./comic-manifest` validator adopts the exact schema and synthetic -fixtures from Codex merge `8044643bf888067f5a6e0d212f843d72e8787f2b`. It enforces +The immutable Platform Comic Manifest v1.0.0 GitHub release includes the +`./comic-manifest` validator, which adopts the exact schema and synthetic fixtures +from Codex merge `8044643bf888067f5a6e0d212f843d72e8787f2b`. It enforces the owner-approved rendition profile catalog, declared output limits and production/result/release metadata relationships. It does not retrieve, render, decode or distribute media, grant publication permission, decide rights, or promote diff --git a/docs/comic-manifest-validation.md b/docs/comic-manifest-validation.md index 73f80b8..018fd37 100644 --- a/docs/comic-manifest-validation.md +++ b/docs/comic-manifest-validation.md @@ -1,10 +1,14 @@ # Comic Manifest parsing and local validation (Studio #90) -The **unreleased** `@definitely-secure-studio/platform/comic-manifest` entry point -parses and validates explicit raw JSON against the published Codex Comic Manifest -1.0.0 schema. The Platform package remains private and unreleased. The module has no -default source reader, network fetcher, execution engine, production trust provider -or publisher. The explicit host-injected approval boundary is +The Platform Comic Manifest v1.0.0 implementation is included in the immutable +[GitHub release](https://github.com/DefinitelySecureStudio/platform/releases/tag/comic-manifest/v1.0.0). +The `@definitely-secure-studio/platform` npm package remains private and was not +published to npm. This `comic-manifest` entry point parses and validates explicit +raw JSON against the published Codex Comic Manifest 1.0.0 schema. The module has +no default source reader, network fetcher, execution engine, production trust +provider or publisher. The current tag and asset status is recorded in the +[publication proof](../release/comic-manifest-v1.0.0-publication-proof.json). +The explicit host-injected approval boundary is described in [#95](comic-manifest-approvals.md). It does not mutate the released Prompt SDK or Context Builder. @@ -152,11 +156,12 @@ exactly; that lock's source commit remains unchanged for the owner-reviewed scenario, negative cases and approval-time matrix. The published runtime pin and the historical test fixtures therefore have separate provenance records. -The Platform implementation remains an unreleased candidate. This PR updates only -the runtime pin, generated validator provenance and release-adoption evidence; it -does not change fixture, golden, catalog or oracle bytes or publish the Platform -package. The readiness check covers the upstream Codex adoption gate only; it does -not claim Platform publication, final artifact approval or release readiness. +At the time of the adoption PR, the Platform implementation was a candidate. That +PR updated only the runtime pin, generated validator provenance and release-adoption +evidence; it did not change fixture, golden, catalog or oracle bytes or publish the +package to npm. The readiness check covers only the upstream Codex adoption gate; +it is not current Platform publication status or final artifact approval. Platform +v1.0.0 was later published immutably; see the [publication proof](../release/comic-manifest-v1.0.0-publication-proof.json). ```sh npm ci @@ -169,9 +174,12 @@ The generator verifies schema size/digest and the installed/locked Ajv 8.20.0 an ajv-formats 3.0.1 versions before writing standalone validators. It takes explicit local bytes and never fetches. The committed generated file reproduces from the freshly downloaded published schema; the existing fixture file is byte-identical -to that asset and remains unchanged. This adoption updates only the unpublished -Platform runtime pin, validator provenance and release evidence. Released Prompt SDK -v1, Context Package v1 and Context Builder v1 bytes and locks remain unchanged. +to that asset and remains unchanged. The adoption updated only the Platform runtime +pin, validator provenance and release evidence. The committed API inventory keeps +`publication_status: candidate-unpublished` as a build-time candidate record; it is +neither current GitHub release status nor npm status and is intentionally unchanged. +Current release state is in the publication proof. Released Prompt SDK v1, Context +Package v1 and Context Builder v1 bytes and locks remain unchanged. Future normative profile changes return to Codex for review before an explicit Platform pin update and regeneration. @@ -193,6 +201,7 @@ repository/production-system and automated-workflow implementation profiles appl to this bounded module. Tests support parsing, privacy and effect-boundary review; owner review of the exact PR remains required. No creative/canon decision, real private-source access, production trust onboarding or release conformance is -claimed. Rollback removes the unreleased entry point and its development consumer; -it does not alter historical contracts or revive permission. Reassess on contract, +claimed. Rollback removes the development consumer and its integration; it does +not alter historical contracts, retract or replace the immutable GitHub release, or +revive permission. Reassess on contract, resource-limit, diagnostic, effect or authority-boundary changes. diff --git a/release/README.md b/release/README.md index 4f72698..f8af337 100644 --- a/release/README.md +++ b/release/README.md @@ -1,22 +1,38 @@ # Reviewed release inputs -## Comic Manifest v1 preparation (#99) - -The additive component candidate is `comic-manifest/v1.0.0` in package -`1.2.0`. Its independent Codex contract lock is -`comic-manifest-contract-lock.json`; it must not be appended to the historical -five-contract Prompt SDK lock or the separately verified Context Builder lock. -Run `node scripts/check-comic-manifest-release.mjs` to verify the exact published -Codex lock, immutable tag target, fresh-download tuple and regenerated runtime pin. -This is only the upstream contract-adoption gate. Platform remains private and -unpublished; a successful check does not approve or publish the Platform package. -After merge, the builder produces an approval-candidate set from the exact merge -commit/tree; it never creates tags, releases, uploads, changes publication status, -or grants approval. Its status fields describe the state when the files were built. - -`comic-manifest-verification.md` records the exact evidence required for a -post-merge candidate. The API inventory is `comic-manifest-api-v1.json`. Build -into a new external directory from the exact merge commit and tree: +## Comic Manifest v1 publication status and build provenance (#99) + +The Platform Comic Manifest v1.0.0 component was published immutably at the +[release tag `comic-manifest/v1.0.0`](https://github.com/DefinitelySecureStudio/platform/releases/tag/comic-manifest/v1.0.0), +from source commit `f0672d90a47473da6a27614cad07abc175546d67` and tree +`b876a434e5f557d88d254cd1e75a8121f23c4ba3`. The exact release state and all +eight public asset hashes, sizes and MIME observations are in the +[publication proof](comic-manifest-v1.0.0-publication-proof.json). The additive +package is version `1.2.0`, remains private, and was not published to npm. + +The independent Codex contract lock is `comic-manifest-contract-lock.json`; +do not append it to the historical five-contract Prompt SDK lock or the +separately verified Context Builder lock. Run +`node scripts/check-comic-manifest-release.mjs` to verify the published Codex +lock, immutable tag target, fresh-download tuple and regenerated runtime pin. +This is only the upstream contract-adoption gate. A passing result is not current +Platform publication status, Platform package approval, or npm publication. + +The committed API inventory `comic-manifest-api-v1.json` retains +`publication_status: candidate-unpublished`. This is build-time candidate +metadata and is intentionally preserved; it is not the current GitHub release +status or npm publication status. The candidate artifact and its provenance are +not rewritten after owner approval or publication. Use the publication proof +above for current release state. The dated +[verification record](comic-manifest-verification.md) remains a historical +pre-publication snapshot. + +### Candidate build and approval procedure + +For v1, the builder produced an approval-candidate set from the exact merged +commit/tree. It never creates tags, releases or uploads, and its provenance fields +describe the state when those files were built. To prepare a future version, build +into a new external directory from its exact reviewed merge commit and tree: ```sh node scripts/build-comic-manifest-release.mjs /absolute/new/output \ @@ -24,16 +40,16 @@ node scripts/build-comic-manifest-release.mjs /absolute/new/output \ ``` `node scripts/create-comic-manifest-approval-packet.mjs /absolute/new/output` -prints a detached packet with no owner decision. After an external authenticated -owner decision, record it in that packet and run +prints a detached packet with no owner decision. After the owner reviews the exact +source and eight file tuples, record that decision in the detached packet and run `node scripts/verify-comic-manifest-approval.mjs /absolute/new/output /path/to/owner-approval.json`. -The verifier's `approval_record_matches: true` result means the record matches -the exact eight files; `owner_identity_authenticated: false` and -`external_owner_authentication_required: true` make clear that it does not -authenticate the owner or authorize publication. Upload the approved files -unchanged without rebuilding. -See the [API/release guide](../docs/comic-manifest-release.md) for the full -workflow, artifact media-type handling, and Codex-before-Platform order. +The verifier's `approval_record_matches: true` means the record matches all eight +files; `owner_identity_authenticated: false` and +`external_owner_authentication_required: true` mean it does not authenticate the +owner or authorize publication. Publish only those approved files, unchanged and +without rebuilding. +See the [API/release guide](../docs/comic-manifest-release.md) for detailed +versioning, provenance, review and media-type guidance. ## Context Builder v1 preparation (#86) diff --git a/release/comic-manifest-verification.md b/release/comic-manifest-verification.md index dc65ba2..1d2c9d9 100644 --- a/release/comic-manifest-verification.md +++ b/release/comic-manifest-verification.md @@ -1,6 +1,8 @@ # Comic Manifest v1 verification record — Studio #99 -## Current state — 2026-10-09 +> **Historical snapshot: 2026-10-09, before Platform publication.** This record preserves the state and open gates at that checkpoint. For current Platform publication evidence, see the [immutable v1.0.0 release record](../docs/comic-manifest-platform-release-v1.0.0.md). + +## State as of 2026-10-09 (before Platform publication) Codex Comic Manifest 1.0.0 is published as an immutable GitHub release. The Platform #42 preparation PR is merged; this branch prepares the separate Platform @@ -22,8 +24,9 @@ has occurred. - Repository immutable-release policy was read as `enabled: true`; no security setting was changed. - Owner A4 approval covered this exact Codex commit, tag and three asset tuples. - It is distinct from and not inferred from the A3 AI-review exception or the - Issue 98 golden acceptance. + It is distinct from the October 6 AI-review/merge instruction, which was not + registered as a formal Constitutional exception. The Issue 98 golden acceptance + is separate as well. | Asset | Declared media type | Bytes | SHA-256 | GitHub asset metadata | Public download | |---|---|---:|---|---|---| @@ -38,7 +41,7 @@ counterpart byte-for-byte and by SHA-256. The table keeps contract-declared content type, GitHub asset metadata content type, and public HTTP download content type separate; no MIME value was copied between those layers. -### Platform adoption scope +### Platform adoption scope at the 2026-10-09 checkpoint The current Platform main base is `9476aeb27246230d982bd8cfde7cfc0d82939de7` (tree `683e2dd392c93f1e55502edeb8aeed54c46ba3a3`), containing merged preparation @@ -92,7 +95,7 @@ would create a different set and require a new approval. `2026-10-07T19:15:38Z`, applies only to its proposed golden/catalog/oracle bytes. It is neither a submitted GitHub review nor A4 release approval. -## Remaining gates +## Remaining gates at the 2026-10-09 checkpoint The parent independently reviews and merges this adoption PR after its exact-head CI passes. Then build and inspect the Platform source/package, lock and artifact