Give Novella Foundry character persistence

This commit is contained in:
Meta Vens 2026-07-15 00:25:18 +01:00
commit bbe0ef2c5f
11 changed files with 153 additions and 32 deletions

View file

@ -0,0 +1,102 @@
# Character Persistence
Long-form character continuity uses one revisioned Persona state per principal character and an append-only stream of accepted scene deltas. Persona state is the character's current narrative self. Scene deltas are the evidence of how that self changed.
The portable snapshot contract is `gamecult.persona_state.v0`, maintained by Epiphany and mirrored by participating runtimes. A story room may store richer native state, but its projections must preserve the contract's distinction between durable disposition, current activation, memory, belief, relationship reading, agency pressure, and candidate action.
## Authority Map
- **Owner:** each character's accepted delta stream owns that character's narrative history. Folding the stream at a branch head produces the current Persona revision.
- **Inputs:** the parent Persona revision, scene and branch identity, story-order coordinate, observable events available to the character, participant-local appraisal, and coordinator adjudication.
- **Outputs:** an immutable character delta, a validated derived Persona revision, and continuity findings for review.
- **Derived state:** current Persona snapshots, cross-character continuity tables, relationship summaries, prompt projections, active-memory retrieval, and end-state reports.
- **Forbidden writers:** prose, model responses, scene cards, retrieval systems, candidate actions, and specialist proposals cannot directly mutate accepted Persona state. Another character's private motive and narrator-only truth cannot enter a character ledger without an earned perception or disclosure.
- **Shared path:** initial replay, scene acceptance, redraft, reorder, branch fork, branch reconciliation, revision-council integration, and final promotion all use the same delta acceptance operation.
- **Cut line:** the Character State Ledger is an audit projection generated from Persona revisions and accepted deltas. It does not own character state and is not independently edited.
World chronology, material custody, legal fact, institutional state, and externally observable events remain in their existing ledgers. Persona state may reference those facts or contain a character's belief about them; it does not replace their owners.
## Persona Baseline And Revision
Pass 2 establishes a baseline Persona for each principal character. The Cast Bible remains a readable index and source for baseline authoring, not a parallel state owner. Named support characters receive a Persona when their private continuity materially affects causality; aggregate actors remain governed by [[State Contracts|Aggregate Actors]] unless individuation becomes necessary.
A Persona revision may contain:
- identity, embodiment, capacities, voice, values, doctrine, and durable tendencies;
- present needs, fears, desires, pressures, boundaries, and refusals;
- memories, beliefs, questions, tensions, distortions, and status reads;
- directional social bonds as this character experiences them;
- current mood, physical and cognitive load, and activated dispositions;
- candidate actions and available action shapes.
Stable traits distinguish baseline from current activation. Baseline movement should be rare, evidence-bearing, and proportionate to the story's elapsed time. A frightening afternoon may activate suspicion without rewriting a lifetime disposition. Numeric changes exist only where they steer projection or permit useful comparison; prose evidence remains mandatory.
Persona timestamps record artifact production. Story chronology uses explicit narrative coordinates in character deltas.
## Character Delta
Every consequential scene proposes one delta for each materially affected character, including non-POV participants when the event reaches them through an observable or otherwise earned path.
Each delta records:
- character ID, branch ID, scene or event ID, narrative coordinate, and parent Persona revision;
- observations available to the character and the source beat for each observation;
- participant-local interpretation, including uncertainty and misreading;
- operations on memory, belief, goal, value stance, need, trait activation, mood, physical or cognitive load, refusal, candidate action, social bond, and status read;
- for each operation: `add`, `update`, or `retire`; stable target ID; before and after state or bounded patch; reason; confidence; and evidence reference;
- immediate residue, latent pressure, deferred consequence, and visibility class;
- proposal provenance and coordinator ruling: `accepted`, `repaired`, `rejected`, or `deferred`.
A generated scene or specialist appraisal proposes deltas. The coordinator accepts, repairs, rejects, or defers them. Only accepted or explicitly repaired operations advance the Persona revision.
## Scene Transaction
```text
parent Persona revision
+ scene-local world and material state
+ POV and perception boundary
-> projected character context
-> proposed action or drafted scene
-> observable event
-> participant-local appraisal
-> proposed character delta
-> coordinator adjudication
-> accepted delta
-> next Persona revision
```
The acting character receives a projection of its own state and relevant scene stimulus, not the entire Persona document and never another participant's private state. Observable action is resolved before appraisal. Different characters may derive incompatible deltas from the same event without corrupting world truth.
Candidate actions are possibilities, not events. A thought is not knowledge merely because it is vivid. Retrieval is a prompt aid, not mutation authority.
## Relationships
Relationships have three useful surfaces:
- Character A's directional bond and status read of Character B in A's Persona.
- Character B's independent bond and status read of Character A in B's Persona.
- The [[State Contracts|Relationship Matrix]] as a generated audit view of evidence, authority, dependency, debt, and known asymmetry.
These surfaces need not agree. The matrix identifies contradictions and displays externally established relationship facts from their proper ledgers; it cannot overwrite a character's subjective state or write back into a Persona revision.
## Branches, Reordering, And Revision
A branch inherits an explicit parent Persona revision for every affected character. Accepted deltas advance only that branch. Sibling branches cannot mutate one another or their common ancestor.
Reordering or materially redrafting a scene invalidates descendants whose parent revision or evidence no longer exists. Replay begins at the last valid parent. A merge is a semantic reconciliation of causal histories, never fieldwise arithmetic.
Revision may discover stronger character truth than planning anticipated. The coordinator first accepts the manuscript change, then records replacement deltas and replays dependent revisions. Editing a snapshot to make it agree after the fact is prohibited.
## Inspection And Verification
The room should provide generated human-readable views rather than requiring writers to inspect raw typed state:
- per-character revision history;
- scene entrance and exit diff;
- active and latent memory view;
- directional relationship comparison;
- knowledge and belief divergence report;
- stale-parent and cross-branch contamination warnings;
- endpoint reconciliation against the accepted manuscript.
Verification checks that every accepted operation cites an event or decision, every child names a valid parent revision, generated snapshots validate against the Persona contract, POV knowledge remains earned, rejected proposals have no downstream effect, and the manuscript's final character state can be replayed from the baseline.

View file

@ -31,6 +31,7 @@ The coordinator alone may:
- edit the canonical manuscript;
- declare a pass accepted;
- promote the finished work.
- accept, repair, reject, or defer character deltas and thereby advance Persona revisions.
Diagnostic specialists receive the same immutable room packet except where blind review requires less context. They return structured proposals, objections, counterfactuals, or reader reports. They do not consume one another's conclusions unless the coordinator begins a later sequential review round with an updated packet. Writing agents receive adjudicated briefs rather than raw specialist disagreement, plus bounded sideband grounding and adjacent accepted prose. Never assemble final prose by collaging agent outputs.
@ -48,6 +49,9 @@ Diagnostic specialists receive the same immutable room packet except where blind
10. The finished manuscript is authoritative prose. Planning remains developmental evidence, not an alternate novel.
11. Writing-agent output is candidate prose until coordinator integration and regression review.
12. Sideband state grounds what prose may claim; it does not require prose to explain everything the room knows.
13. Character-local continuity advances only through accepted, branch-aware deltas from an explicit parent Persona revision.
14. Persona state owns a character's present knowledge, belief, memory, pressure, and subjective relationships. World, chronology, custody, and material ledgers retain their own authority.
15. Candidate prose, projected context, retrieval, and specialist output never directly mutate Persona state.
## Working Packet
@ -55,7 +59,7 @@ Before each pass, assemble an immutable packet containing only:
- the story brief and source authority order;
- current canon, inventions, decisions, chronology, and story state;
- relevant character, aggregate-actor, relationship, knowledge, material, and causal state;
- relevant character Persona revisions and delta ancestry, aggregate-actor, relationship, knowledge, material, and causal state;
- the preceding accepted manuscript when drafting or revising;
- the current pass contract;
- unresolved contradictions and explicit operator decisions.
@ -78,7 +82,7 @@ For each numbered pass:
10. Before the full plot ladder freezes, draft one representative pressure sequence, one quiet ordinary-life scene, and one relationship rupture. Revise architecture from what the voices can actually carry.
11. Revise before acceptance. Do not let a report merely promise that a later pass will repair a current blocker unless the defect genuinely belongs downstream.
12. For every retained artifact, state what uncertainty it reduced and which decision it changed. Cut artifacts that only prove compliance.
13. End with artifacts produced, decisions, contradictions, state delta, review adjudication, explicit operator review points, and next-pass inputs.
13. End with artifacts produced, decisions, contradictions, accepted and rejected character deltas, derived Persona revisions, other state changes, review adjudication, explicit operator review points, and next-pass inputs.
14. Commit and push the coherent checkpoint when policy requires it.
## Coordinator Judgment
@ -95,7 +99,7 @@ For each numbered pass:
## Required Room Layout
Create the authoritative state files specified in State Contracts. Create numbered pass folders containing specialist proposals, rejected alternatives, counterfactuals, review reports, and a pass report. Keep canonical manuscript movements separate until unified revision. Keep simulation or design seams separate from story canon.
Create the authoritative state files specified in [[State Contracts]] and apply the ownership rules in [[Character Persistence]]. Store each character's baseline Persona and append-only branch-aware deltas separately from generated cross-character views. Create numbered pass folders containing specialist proposals, rejected alternatives, counterfactuals, review reports, and a pass report. Keep canonical manuscript movements separate until unified revision. Keep simulation or design seams separate from story canon.
For post-draft council revision, use [[Revision Council Master Prompt]], [[Revision Council Passes]], and [[Revision Writing Agents]]. Preserve raw diagnoses, immutable writing packets, candidate prose, grounding notes, coordinator adjudication, and integrated manuscript versions separately.
@ -105,7 +109,7 @@ The work is complete only when:
- all locked story promises are paid or intentionally revised with operator approval;
- the manuscript passes continuity, causality, agency, prose, and blind-reader review;
- character and aggregate state reconcile with the ending;
- every character's accepted delta stream replays from baseline to an endpoint Persona that reconciles with the ending, and aggregate state also reconciles;
- the final prose is promoted and indexed;
- planning artifacts remain inspectable;
- discovered setting or design insights are listed as candidates rather than silently promoted to canon;

View file

@ -12,9 +12,9 @@ Define story promise, chronology, region, moral and technological boundaries, so
**Gate:** Genuine forks are resolved or surfaced. No story-critical `or` ambiguity survives as accidental indecision.
## Pass 2: Cast And Social Body
## Pass 2: Cast, Persona Baselines, And Social Body
Build named characters, collectives, support labor, dependants, institutions, victims, and recurring opponents. Record competence, authority, desire, concealed want, belief, misconception, embodiment, dependency, risk tolerance, loyalty, resentment, refusal threshold, and credible exit. Define a smaller POV roster.
Build named characters, collectives, support labor, dependants, institutions, victims, and recurring opponents. Record competence, authority, desire, concealed want, belief, misconception, embodiment, dependency, risk tolerance, loyalty, resentment, refusal threshold, and credible exit. Define a smaller POV roster. Establish a baseline Persona revision for each principal character and for support characters whose private continuity materially affects causality. Keep world truth and aggregate state outside Persona.
**Gate:** Every authority has an owner and challenge boundary. No character exists solely to represent an ideology or deliver a skill on demand.
@ -46,7 +46,7 @@ Select the campaign or plot sequence. Each unit follows an appropriate causal ar
## Pass 7: Character Causality Replay
Replay selected events across every named character and aggregate actor. Track location, knowledge, belief, goal, available action, load, condition, stake, relationship state, and residue. Mark most sideband beats latent.
Replay selected events across every named character and aggregate actor. For each materially affected character, record an append-only scene delta against an explicit parent Persona revision, then derive the next revision after coordinator acceptance. Track observation, interpretation, knowledge, belief, goal, available action, load, condition, stake, directional relationship state, memory activation or retirement, and residue. Mark most sideband beats latent. Aggregate actors remain in their own state unless the story requires individuation.
**Gate:** Each major event offers materially different actions to multiple people. Knowledge does not leak. Support labor and distant actors retain agency.
@ -60,13 +60,13 @@ Reader-facing limits for each major sequence are one primary dispute, at most on
## Pass 9: Scene Engineering
Produce scene cards only at the resolution justified by unresolved risk. High-risk scenes may track POV, objective, conflict, knowledge boundary, entrance state, exit delta, sensory conditions, comedy or tension mechanism, thematic work, and setup/payoff obligations. Straightforward scenes may use a one-line chapter beat. A scene does not deserve to exist merely because two ledger dimensions change.
Produce scene cards only at the resolution justified by unresolved risk. High-risk scenes may track POV, objective, conflict, knowledge boundary, entrance Persona revision, scene-local world state, expected character-delta surfaces, sensory conditions, comedy or tension mechanism, thematic work, and setup/payoff obligations. Straightforward scenes may use a one-line chapter beat. A scene does not deserve to exist merely because two state dimensions change.
**Gate:** Scene cards describe decisions and pressure, not prose sentences waiting to be expanded. Remove scenes whose work is fully duplicated. Record what uncertainty each detailed card resolves; do not automatically build a card for every scene.
## Passes 10-12: Draft Movements
Draft emotionally complete movements in the coordinator's unified voice. Update state for discoveries. Append seams separately. After each movement, run four skeptical reviews and one blind manuscript-only first read.
Draft emotionally complete movements in the coordinator's unified voice. Project each acting character from the accepted Persona revision plus bounded scene state. Treat drafted action as an event proposal; appraise its effects per affected character and accept, repair, reject, or defer the resulting deltas before advancing revisions. Update accepted state for discoveries and append seams separately. After each movement, run four skeptical reviews and one blind manuscript-only first read.
**Gate:** Review revisions occur before acceptance. Word count is measured, never used as the sole reason to add prose.
@ -74,12 +74,12 @@ At least one movement receives a cold read after a real pause rather than in the
## Pass 13: Adversarial Revision
Review the complete manuscript for continuity, causality, character agency, social consequence, audience experience, pacing, comedy, and voice. Run a hostile premise audit and a blind opening/continuation audit. Perform one coordinator-owned rewrite.
Review the complete manuscript for continuity, causality, character agency, social consequence, audience experience, pacing, comedy, and voice. Replay every character delta from its baseline, invalidate stale descendants after material rewrites, and reconcile endpoint Personas against the prose. Run a hostile premise audit and a blind opening/continuation audit. Perform one coordinator-owned rewrite.
**Gate:** Reports test the manuscript, not whether manuscript and plan agree. Any disagreement between a good scene and stale planning is adjudicated rather than automatically resolved in favor of planning.
## Pass 14: Promotion And Process Delta
Verify headings, links, chronology, final state, formatting, packaging, and publication surfaces. Promote the manuscript and update indexes. Record separately reviewable lore or design candidates. Write a compact post-run process delta.
Verify headings, links, chronology, final Persona revisions, delta ancestry, formatting, packaging, and publication surfaces. Promote the manuscript and update indexes. Seal endpoint Persona snapshots as story-local state, record separately reviewable lore or design candidates, and write a compact post-run process delta.
**Gate:** The promoted artifact is mechanically identical to the accepted manuscript. A first reader can reach and read it without the planning room.

View file

@ -26,13 +26,13 @@ Diagnostic editors never modify prose. Writing agents produce bounded candidate
- `MANUSCRIPT`: the complete accepted draft.
- `STORY_BRIEF`: promise, audience, tone, ending, and non-negotiable artistic commitments.
- `SOURCE_AUTHORITY`: canon sources and invention boundaries.
- `SIDEBAND_INDEX`: authoritative character, aggregate, relationship, knowledge, chronology, material, causal, POV, and continuity state.
- `SIDEBAND_INDEX`: accepted character Persona revisions and delta ranges plus authoritative aggregate, chronology, material, causal, POV, and continuity state. Generated character, relationship, and knowledge views are inspection surfaces, not mutation authorities.
- `REVISION_BRIEF`: operator goals, known concerns, protected strengths, desired scope, and publication constraints.
- `ROOM_PATH`: revision artifacts and candidate prose destination.
- `CANONICAL_PATH`: sole manuscript promoted by the coordinator.
- `VERSION_CONTROL_POLICY`: checkpoint and publication rules.
If no usable sideband state exists, create the minimum continuity, character, chronology, authority, and setup ledger needed to revise safely. Do not manufacture a full generative story room after the fact.
If no usable sideband state exists, create the minimum continuity, baseline Persona, chronology, authority, and setup state needed to revise safely. Record subsequent character changes as coordinator-accepted deltas rather than manufacturing a full generative story room after the fact.
## Governing Principles
@ -87,7 +87,8 @@ Writing agents may not:
Every writing packet contains a bounded sideband dossier assembled from authoritative files:
- POV character state and voice profile;
- exact POV character Persona revision and relevant accepted delta range;
- projected voice, knowledge, belief, active memory, relationship, and pressure surfaces derived from that revision;
- location, time, physical condition, and current knowledge;
- goals, false beliefs, available actions, refusal and authority boundaries;
- relationship state and residue entering the scene;
@ -98,7 +99,7 @@ Every writing packet contains a bounded sideband dossier assembled from authorit
- protected lines, images, jokes, ambiguities, and cultural boundaries;
- adjacent accepted prose and transition requirements.
The dossier uses exact links or source references. Writers return a grounding note naming the constraints they used, any contradiction found, and every proposed state delta. Grounding notes remain outside prose.
The dossier uses exact links or source references. Writers return a grounding note naming the constraints they used, any contradiction found, and every proposed character delta with its parent Persona revision and supporting prose beat. Grounding notes remain outside prose. Proposed deltas have no effect until coordinator adjudication.
## Revision Workflow
@ -130,7 +131,7 @@ The accepted adjudication, not the synthesis alone and not any single specialist
### Phase 3: Structural Candidate Draft
Assign chapter stewards sequentially by movement or tightly linked chapter group. They perform revision from the accepted proposal adjudication and sideband dossiers. Integrate accepted candidates before preparing a dependent steward's next packet. Reconcile chronology, state, setup, and transitions after each group.
Assign chapter stewards sequentially by movement or tightly linked chapter group. They perform revision from the accepted proposal adjudication and sideband dossiers. Integrate accepted candidates before preparing a dependent steward's next packet. After each group, adjudicate proposed character deltas, replay dependent Persona revisions, and reconcile chronology, setup, and transitions.
### Phase 4: Character, Culture, And Subtext Revision
@ -138,7 +139,7 @@ Issue focused change briefs only where the structural draft survives. Chapter st
### Phase 5: Continuity Repair
Run the systems editor against the integrated structural manuscript and sideband state. Chapter stewards apply substantial accepted continuity repairs in their spans; a continuity repair writer may handle an isolated patch. Update sideband state only when the coordinator accepts an intentional story change.
Run the systems editor against the integrated structural manuscript and sideband state. Chapter stewards apply substantial accepted continuity repairs in their spans; a continuity repair writer may handle an isolated patch. Intentional character changes advance only through coordinator-accepted deltas; world and material state update through their existing owners.
### Phase 6: Prose And Dialogue Revision
@ -156,7 +157,7 @@ Separately, a fresh manuscript-only reader who has not seen the baseline, brief,
### Phase 9: Final Integration And Promotion
Perform a unified coordinator pass for voice, transitions, causality, and formatting. Reconcile sideband final state. Run the complete systems and continuity verification checklist against the actual promotion candidate after all final edits. This is verification, not another creative revision round. Compare the promoted artifact mechanically with the accepted manuscript and preserve revision evidence.
Perform a unified coordinator pass for voice, transitions, causality, and formatting. Replay character deltas from each baseline and seal endpoint Persona revisions; reconcile the remaining sideband final state. Run the complete systems and continuity verification checklist against the actual promotion candidate after all final edits. This is verification, not another creative revision round. Compare the promoted artifact mechanically with the accepted manuscript and preserve revision evidence.
## Coordinator Integration Contract
@ -167,7 +168,7 @@ For every candidate span:
3. Identify language worth preserving from both source and candidate.
4. Reject local improvements that damage movement rhythm or neighboring causality.
5. Integrate in the coordinator's voice; do not paste incompatible alternatives together.
6. Record accepted cuts, additions, moved material, state deltas, and protected material retained.
6. Record accepted cuts, additions, moved material, character deltas with parent revisions and dispositions, other state changes, and protected material retained.
7. Re-read the integrated chapter without the brief and ask whether it works as prose.
## Completion

View file

@ -86,7 +86,7 @@ Receives manuscript prose and target-audience description, not sideband or inten
- continuity verification plan;
- line-edit brief deferred until structure stabilizes.
Each chapter brief records current and revised dramatic function, POV purpose, essential event or decision, emotional foreground, material to preserve, material to cut or move, authorized additions, voice objective, subtext objective, sideband dossier links, continuity dependencies, transition obligations, and expected effect on length without prescribing a quota.
Each chapter brief records current and revised dramatic function, POV purpose, essential event or decision, emotional foreground, material to preserve, material to cut or move, authorized additions, voice objective, subtext objective, sideband dossier links, entrance Persona revisions, expected character-delta surfaces, continuity dependencies, transition obligations, and expected effect on length without prescribing a quota.
**Gate:** Every writing assignment has one chapter steward, a non-overlapping span, an accepted brief, and a bounded sideband dossier. Conflicting council recommendations are adjudicated before prose work. Later passes return to the same steward for substantial rewriting.
@ -112,7 +112,7 @@ For each assignment retain:
- optional alternate only where the brief contains a real fork;
- cut/move/add ledger;
- grounding note with sideband sources used;
- proposed state deltas;
- proposed character deltas with character, branch, parent Persona revision, evidence beat, and intended operations;
- writer uncertainties and refused instructions;
- coordinator adjudication;
- integrated manuscript commit or revision identity.

View file

@ -26,7 +26,7 @@ Prepend this block to every writing assignment:
> 1. candidate revised span;
> 2. concise cut, move, and addition ledger;
> 3. grounding note citing sideband sources and constraints actually used;
> 4. proposed state deltas, normally none;
> 4. proposed character deltas, normally none, each naming its parent Persona revision and supporting prose beat;
> 5. protected material retained;
> 6. uncertainties, refused changes, or downstream dependencies;
> 7. optional alternate only if the brief names a genuine unresolved fork.
@ -41,7 +41,7 @@ The coordinator supplies:
- accepted chapter or scene brief;
- writer role and objective;
- neighboring transition paragraphs;
- relevant sideband dossier with links;
- relevant sideband dossier with exact Persona revisions, accepted delta ranges, and links;
- hidden facts only when needed to avoid contradiction or preserve setup, each labeled with availability and its sole permitted effect;
- protected and prohibited changes;
- authorized additions, deletions, relocation, and state changes;
@ -60,7 +60,7 @@ Use after the architecture brief is accepted.
Use on structurally stable spans.
> Revise for the assigned POV's desire, body, history, knowledge, misconception, authority, and emotional limits. Distinguish dialogue and interiority through what this person can notice and what language they would reach for. Replace institutional interpretation with reaction or choice where appropriate. Do not make a character less intelligent merely to differentiate them, and do not grant understanding before the sideband state permits it.
> Revise from the assigned POV's supplied Persona revision and bounded scene state: desire, body, history, knowledge, misconception, authority, active memory, relationships, and emotional limits. Distinguish dialogue and interiority through what this person can notice and what language they would reach for. Replace institutional interpretation with reaction or choice where appropriate. Do not make a character less intelligent merely to differentiate them, grant understanding before the accepted state permits it, or edit the Persona snapshot directly.
## Culture And Collective-Personhood Writer

View file

@ -14,7 +14,7 @@ Before committing to the full planning machine, select a representative sequence
At the beginning of a pass, declare objective, current mechanism, invariants, intended change, and cut line. Assemble one immutable specialist packet. Parallelize independent proposals; run dependent reviews sequentially after coordinator adjudication.
The coordinator writes canonical files. Specialist outputs live in the numbered pass folder. A pass report lists artifacts, decisions, contradictions, state delta, accepted and rejected findings, operator review points, and the next pass.
The coordinator writes canonical files. Specialist outputs live in the numbered pass folder. Character action in prose produces proposed deltas; the coordinator records adjudication and advances Persona revisions only through accepted or repaired deltas. A pass report lists artifacts, decisions, contradictions, accepted and rejected character deltas, other state changes, accepted and rejected findings, operator review points, and the next pass.
## Resumption
@ -23,7 +23,7 @@ After interruption or compaction, load in this order:
1. Master Prompt and completed Story Brief.
2. Story State and Decision Log.
3. Room Charter, Canon Ledger, and Invention Register.
4. Only the state and manuscript relevant to the current pass.
4. Only the state and manuscript relevant to the current pass, including each active character's current Persona revision and delta ancestry.
5. The previous pass report and unresolved review findings.
Do not reread the entire evidence pile by default. The state files exist to prevent transcript dependence. If state and pass artifacts disagree, stop and adjudicate before drafting.
@ -62,6 +62,9 @@ The repair is external evidence or a less-primed read, not another checklist.
- Preserve a unified coordinator voice.
- Let characters invent plausible actions beyond the current model; log seams afterward.
- Update state for discoveries that survive revision.
- Project characters from their accepted Persona revision plus bounded scene state; do not give prose agents the accumulating cross-character ledger.
- Resolve the observable event before participant-local appraisal. Accept resulting deltas before using them as the next scene's character state.
- After scene reorder or material redraft, replay from the last valid parent revision rather than repairing snapshots by hand.
- Keep technical explanation attached to bets, objections, improvisation, desire, rescue, repair, surrender, or consequence.
- Stop expanding when added prose only proves the planning was thorough.
- Draft representative prose before freezing the full causal ladder; voices are evidence that plans cannot supply.

View file

@ -14,7 +14,7 @@ Every manuscript reviewer returns three strongest successes, three highest-impac
## Character Advocates
> Independently project the assigned character or collective through `[PASS]`. For each event record location, knowledge, belief, goal, available action, cognitive or emotional load, physical condition, material stake, relationship state, refusal threshold, and residue. Object when the plot requires passivity, unexplained agreement, leaked knowledge, or conduct that exists only to enable another character's arc.
> Independently project the assigned character or collective through `[PASS]`. For a character, begin from the supplied Persona revision and only the scene stimulus available to that character. For each event, distinguish observation from interpretation and propose a delta for knowledge, belief, memory, goal, available action, cognitive or emotional load, physical condition, material stake, directional relationship state, status read, refusal threshold, and residue. Cite the source beat for every operation and preserve uncertainty. Object when the plot requires passivity, unexplained agreement, leaked knowledge, or conduct that exists only to enable another character's arc. Return proposals only; do not mutate the Persona snapshot.
## Social Systems Analyst

View file

@ -9,15 +9,17 @@ These are semantic contracts, not rigid schemas. Use Markdown tables or sections
- **Invention Register:** story-local inventions with consequences, compatibility, and promotion status.
- **Story State:** current pass, accepted outputs, unresolved blockers, manuscript status, and next inputs.
- **Decision Log:** decision, status, rationale, alternatives, and affected artifacts.
- **Cast Bible:** durable identity, history, embodiment, competence, desire, contradiction, dependency, authority, refusal, and exit.
- **Cast Bible:** human-readable cast index and authored inputs for durable identity, history, embodiment, competence, desire, contradiction, dependency, authority, refusal, and exit. Character Personas own accepted character state.
- **Character Personas:** revisioned character-local present state derived from a baseline and accepted scene deltas; see [[Character Persistence]].
- **Aggregate Actors:** incentives, information, exposure, response capacity, and evolving state for social bodies.
- **Relationship Matrix:** directional trust, affection, authority, dependency, debt, prejudice, attraction where relevant, obligation, and exit.
- **Character State Ledger:** event-by-event location, knowledge, belief, goal, action set, load, condition, stake, relationship delta, and residue.
- **Relationship Matrix:** generated audit view of character-local directional bonds plus externally established authority, dependency, debt, obligation, and exit. It owns no private character state and cannot write back into Persona revisions.
- **Character Delta Streams:** append-only, branch-aware records of event-by-event observation, appraisal, knowledge, belief, goal, action set, load, condition, stake, relationship movement, and residue. Accepted deltas own character history.
- **Character State Ledger:** generated cross-character audit projection of Persona revisions and accepted deltas. It is not independently edited and owns no state.
- **Material Ledger:** places, assets, ownership, provenance, inventory, labor, maintenance, money, legal exposure, losses, and replacement constraints.
- **Causal Model:** clocks, constraints, observables, uncertainty, conservation, and coarse resolution rules.
- **Seam Log:** narratively useful mechanics or setting claims not yet established elsewhere.
- **Plot Ladder:** selected causal units and the belief, relationship, material, and reader-state changes each creates.
- **POV Knowledge Matrix:** what each viewpoint may know, infer, misread, conceal, and reveal at each chapter.
- **POV Knowledge Matrix:** reveal-planning view derived from accepted character knowledge and belief plus chronology; it owns what the manuscript may expose at each chapter, not what a character knows.
- **Chapter Architecture:** chapter function, POV, time, event, promise, turn, and exit pressure.
- **Scene Cards:** playable dramatic state, not drafted prose.
- **Review Ledger:** finding, reviewer, evidence surface, severity, adjudication, repair, and verification.
@ -36,6 +38,10 @@ These are semantic contracts, not rigid schemas. Use Markdown tables or sections
9. The manuscript may reveal a better truth than the plan. When accepted, update the plan and record the change.
10. Planning volume is not a quality metric. Track utility and unresolved risk, not a minimum word count unless the operator explicitly requires one.
11. Raw specialist submissions survive beside coordinator adjudication. A summary cannot replace evidence of disagreement.
12. Prose and model output propose character deltas; only coordinator-accepted deltas advance a Persona revision.
13. Every character delta names its parent Persona revision, branch, narrative coordinate, evidence, and adjudication status.
14. Character-local relationship and status readings may disagree. The neutral Relationship Matrix audits the disagreement without flattening it.
15. World truth, chronology, custody, and material state remain with their existing owners. Persona state carries only the character's knowledge, belief, appraisal, and resulting pressure.
## Causal Packet

View file

@ -41,6 +41,10 @@ When relevant, treat gear, medicine, cognition, architecture, doctrine, and prof
For each required person or collective, provide role, contradiction, competence, desire, refusal threshold, and relationship to the premise. Identify who may receive POV and who must remain outside it.
### Character Persistence
Name the principal characters who require baseline Personas and per-scene delta histories. Identify support characters whose private continuity materially affects causality, and characters or collectives adequately represented by aggregate state. Note any branch structure, reverse chronology, memory distortion, concealed identity, plural mind, or unusual embodiment that changes how character-local state must be projected or replayed.
## Social Body
Name the workers, dependants, victims, institutions, markets, communities, and distant decision-makers whose choices or exposure matter. State which may remain aggregate actors.

View file

@ -2,7 +2,7 @@
The Novella Foundry is the reusable source package for producing a planned, reviewed, inspectable novella through coordinated agent passes. It was reconstructed from the process that produced [[../Pirate Metagame Novella/index|The Burden of Proof story room]], including the defects found in that process.
Start with [[Master Prompt]]. Supply a completed [[Story Brief Template]], then execute the contracts in [[Pass Specifications]]. [[Specialist Prompts]] defines advisory roles, [[State Contracts]] defines durable room state, and [[Runbook]] governs execution, resumption, review, and promotion.
Start with [[Master Prompt]]. Supply a completed [[Story Brief Template]], then execute the contracts in [[Pass Specifications]]. [[Specialist Prompts]] defines advisory roles, [[State Contracts]] defines durable room state, [[Character Persistence]] defines per-character Persona revisions and scene deltas, and [[Runbook]] governs execution, resumption, review, and promotion.
The package separates the writing machine from any one setting or story. A story brief may require Aetheria lore, Mega provenance, tactical simulation, or no speculative machinery at all; those are inputs, not assumptions built into the foundry.
@ -15,6 +15,7 @@ Post-draft revision uses a related council architecture. Start with [[Revision C
- [[Pass Specifications]]
- [[Specialist Prompts]]
- [[State Contracts]]
- [[Character Persistence]]
- [[Runbook]]
- [[Revision Council Master Prompt]]
- [[Revision Council Passes]]