Repository navigation
Define Comic Manifest architecture and boundaries #88
Description
Parent epic: #6
Summary
Define Comic Manifest architecture and boundaries for Comic Manifest v1.
Ownership and dependencies
- Repositories: studio; coordinated codex/platform review.
- Depends on: released Epic Epic 4 - Prompt SDK #4/Epic 5 - Context Builder #5 foundations; first task in Epic Epic 6 - Comic Manifest #6.
- Plan position: 1 of 12.
Scope and deliverables
- Define production manifest, build-result record and reader-safe public release manifest as separate linked records.
- Record repository ownership, lifecycle, authority gates and the Epic Epic 7 - Build Orchestrator #101 consumer boundary in a Studio ADR.
- Formalize opaque draft identity versus permanent DS-NNNN publication identity, ordered-panel scope, immutable revisions and exact approval binding.
- Define an offline synthetic vertical slice and contract gaps without inventing canon or implementing orchestration.
Acceptance criteria
- Owner-reviewed architecture assigns each record and operation to the correct repository.
- Preparation, current package use, review, attestation and human publication/canon authority remain distinct.
- Production, result and release transitions, protected/public data boundaries and invalidation rules are explicit.
- Epic Epic 7 - Build Orchestrator #101 handoff, v1 exclusions and constitutional assessment are documented.
Implementation guardrails
Follow Constitution v1.0.0 at a9cc8a503aa30e17820edc62ac95f7cbe10e0564 and the boundaries in #6. Use public/synthetic fixtures only. Preserve released Prompt SDK v1, Context Package v1 and Context Builder v1 bytes. Add focused tests and documentation with implementation; the suite task consolidates rather than postpones testing. No implicit retrieval, permission renewal, direct Lore checkout, silent declassification, self-approval or canon promotion. Normative gaps belong in Codex. Orchestration, rendering, production trust onboarding and creative canon remain separately scoped. Creating this issue does not authorize implementation or publication.
Activity
docs: define Comic Manifest architecture and boundaries (#88) (#100)
andrewperis commentedon Oct 13, 2026
Present-day owner acceptance — 2026-10-13
Append-only clarification; the original issue body, closure, and acceptance boxes are preserved.
At closure, ADR 0018 was Proposed and the “Owner-reviewed architecture” box below was unchecked. On 2026-10-13 at 11:47:50.998442 UTC, Andrew Peris confirmed that he held the listed approval capacities and approved the exact reviewed package. He accepted the architecture at Studio revision
7b5065cef76bea9580609caba356b0d8fe7cc17cfor the synthetic/offline Comic Manifest v1 boundary and adopted the bounded Codex and Platform advisory findings.The present-day decision is recorded in Studio PR #147, currently at head
b45cd61172b5e2da1f57ab0ceedbbbc349a9f89d; the approved review packet is PR #146 heada9935f8fcab04396b3ba5f8077620ca167291933.This records a later acceptance. It does not rewrite the status at closure, legalize prior conduct retroactively, create a constitutional exception, or authorize production/private-source/canon/publication activity. The original checklist remains unchanged.
andrewperis commentedon Oct 13, 2026
Link and provenance update — 2026-10-13
Follow-up to the earlier append-only acceptance clarification: Studio PR #147 has advanced to head
6c695451f8f4135ff71aff6eef4e254cbcd2797d, based on merged Studio main3cd52a8f9c6307cd0ce2779fcef051131db097a7. The current draft contains the dated acceptance record and updated ADR/architecture status; it remains open for independent verification before merge.The separate Codex wording correction was independently reviewed at head
6b0abdc2708b8cc6ff671f31e9b8d3a235eb04baand merged as commit279d30319a0aff14366dc5846a18200bd1fd0ae9. The immutable v1 tag and release bytes remain unchanged.This follow-up updates the PR-head reference only. The original unchecked box and issue history remain untouched; Epic #6 stays open.