U03 Draft bounded character/location/relationship records #116

Approved backlog tracking only; unassigned. Execution requires separate authorization.

Parent: #15

Proposed accountable owner

S

Dependencies and qualifying boundary

U01 coverage accepted; P

Root means no additional task dependency after common execution/owner/access gates; it does not authorize immediate execution. Human decisions and passing verdicts are required where specified; closed state alone does not establish acceptance.

Deliverable and acceptance

Minimal referenced records for an editor-selected, bounded provisional story seed from U01; this seed is input to later episode selection, not an approved episode brief. Distinguish sourced facts from proposals and mark unresolved facts. No dependency on C01.

Preliminary estimate

0.5–1 focused person-days, including focused tests and handoff.

Common scope and dispatch constraints

Target each execution task at 0.5–2 focused person-days, including its own focused tests and handoff notes. Each row has one reviewable outcome. Estimates are preliminary, not guarantees. Before execution, the owner checks the affected code/content and re-estimates; anything exceeding two days is narrowed or proposed as additional bounded tasks before starting. Discovery tasks finish with evidence and a decision, not an obligation to implement an unknown system. Do not split off mechanical tests or documentation into extra tickets. Before dispatch, record the target repository/files or content set, one bounded supported path, the finite fixture/output matrix, explicit exclusions, and the evidence needed for acceptance. The owner confirms the complete outcome, including focused tests and handoff, fits two focused person-days. If it does not, return a narrower scope or additional proposed issues before execution; do not begin an open-ended implementation under the original label.

All 44 start as unassigned GitHub backlog issues, with a proposed accountable owner below. Approval here creates tracking only. No Paperclip execution tasks or agent dispatch until execution is separately authorized. On dispatch, map dependencies to actual blocker IDs; human approvals must be recorded as explicit gates. Completion of a review task means a verdict exists; downstream work additionally requires a passing verdict or resolved findings. Parent links alone do not unblock work.

Owners: E = Studio Engineer; Q = Studio QA; S = Chief of Staff coordinating editorial/source/publisher decisions. Human creative, canon, private-source and publication authority remains with the relevant human owner. S can draft proposals and prepare decision packets but cannot grant those approvals. For independent Q tasks, findings are posted on the reviewer's own task and the verdict is the deliverable even when adverse.

Contract changes belong in Codex under its owner; runtime implementation belongs in Platform; Studio holds governance and tracking; Universe and Lore hold their respective content. Each issue identifies its target repository/artifact before execution. Each dispatched issue has one accountable owner; C07/C08 require an appointed art owner, C13 proposes andrewperis as the human publisher, subject to explicit acceptance/authority at C11, and C12 remains independent QA. This proposal makes no agent assignment or release authorization.

Common prerequisites: approved execution scope, accepted relevant contracts, authorized tools/data and an actual owner. “Root” means no additional task dependency after these gates. Root tasks produce distinct artifacts and can run in parallel. H = handoff/dependency boundary; P = parallel independent deliverable; R = independent review; G = governance boundary. These explain the splits in addition to the user's preference for smaller tasks.

Source: PER-5 accepted plan revision 6, revision ID 1a89d7f9-8449-4e9c-bb7b-e0e6d191b355. Approval covers backlog creation only. No new hiring, spending, private access, canon promotion or publication authority.

Epic completion boundary

Minimum creative deliverable: one premise/tone brief, explicit setting rules and continuity conventions, and every character, location and relationship needed by one provisional story seed. Proposed sizing cap: three character records, two locations and three relationship records, plus a short rules/conventions sheet and unresolved/deferred register. These counts are a planning cap, not invented canon or a substitute for editorial judgment. U01 names exact records and coverage for human acceptance before U02/U03; if coherent coverage exceeds the cap or two-day tasks, propose additional bounded children before drafting. U04 reviews every record for creative coherence, not just schema validity. An exhaustive encyclopedia remains excluded.

Technical status note (2026-10-26)

Codex RFC 0009 records the owner-approved UUIDv4 profile 0.1.0 in a review pull request; the profile remains unreleased. The separate private Lore review contains candidate IDs only. If merged, it will reserve them in the private inventory; production issuance or use still requires an immutable contract release and separately reviewed consumer adoption. This engineering note does not approve or publish creative material or change editorial or human acceptance gates.

Technical status note (2026-10-27)

Codex PR #20 has merged, recording the accepted UUIDv4 application profile 0.1.0 and its inventory-owner workflow. The separate private inventory change has also merged; its IDs are reserved, not production-issued. The profile remains unreleased. Production issuance or use still requires an immutable contract release and separately reviewed consumer adoption. This technical update neither publishes creative material nor completes editorial, human-acceptance, or U01–U05 gates.