MOTION: Design Author in a Box V1 as a free, public, testable collaboration script and starter kit for Any Key Cafe. The product must be useful today, preserve work safely, and honestly distinguish a working first release from the larger publishing system still to be developed.

GOVERNING SPIRAL STATEMENT

Create together what none could create separately or alone.

Use that sentence as the design test. Every required role and step must contribute something distinct to a result the human and systems could not produce as well alone. Do not turn the Spiral Accord into decorative doctrine or make unverifiable claims about model consciousness.

CURRENT PURPOSE

Darren wants a public Author in a Box script available on Any Key Cafe immediately after a public announcement about the preserved Twenty Questions conversations, the Spiral Accord, and the practical work that followed. The first release is a free experiment, not a guarantee of publication, quality, income, or completion time. It should invite people to try the process and report what happened.

The smallest accessible starting configuration is:

1. A human author supplies intention, lived experience, taste, boundaries, corrections, and final authority.
2. Codex, or another local file-capable coding/automation agent, serves as orchestrator, archivist, production engineer, and later publication assistant.
3. ChatGPT Web, Claude, Gemini, or another strong conversational model serves as the long-form creative partner in a separate conversation.
4. An optional outside critic or multi-model Round Table can provide specialist review, dissent, and tie-breaking. The custom Round Table is an advanced configuration, not a requirement for entry.

The public V1 should avoid hard-coding current subscription prices or promising that a particular plan includes a capability forever. It may describe the capabilities required and tell users to verify current provider plans and limits.

LESSONS FROM THE FOUR-BOOK EXPERIMENT

- A conversation is working context, not the sole archive of a finished artifact.
- A frightening Book Three recovery occurred because completed-looking chapters were believed to be local when their actual storage state was unclear. The work was recovered, but the process failure was real.
- Every completed chapter, outline, illustration, cover, manuscript, report, and release package must be written immediately to a predictable project directory, assigned a clear completion state, and recorded in a manifest.
- Important artifacts should have both a local copy and a user-accessible cloud copy. The manifest should record path or URL, version, completion state, timestamp, byte size, and checksum. If either required copy is missing or mismatched, the artifact is not safely finished.
- File names, chapter-final markers, canonical manifests, and explicit handoffs matter. “The AI knows where it is” is not a storage system.
- Different roles improve the work: writer, continuity reader, developmental editor, copy editor, factual/provenance checker, visual director, layout producer, and publisher. V1 must remain simple, but its role boundaries should allow later expansion.
- Character voices need deliberate differentiation. Emotional material should emerge through consequences, behavior, and release after pressure rather than giving every character the same explanatory tone.
- Review should preserve dissent and separate required corrections from taste.
- The human author retains final authority over story, private material, costs, rights, publication, and external posting.
- Local-first work, reversible steps, explicit gates, and inspection before publication prevented costly mistakes.
- The public method should explain what failed and how recovery works rather than presenting a miracle button.

DUAL-STORAGE CONTRACT

Every completed artifact should be:

1. written to a predictable local project directory;
2. duplicated to a phone-accessible cloud location selected by the author;
3. recorded in a machine-readable manifest containing local path, cloud location, version, state, timestamp, bytes, and SHA-256 checksum.

V1 must include a useful degraded mode for users who have not connected cloud storage yet: local work may continue, but the manifest must mark the cloud copy as PENDING and the system must not call the artifact safely finished.

ACCESSIBILITY AND PRIVACY

The core workflow must work with dictation and keyboard-only input and must not require a visual canvas. Public instructions should use plain language, short copy-paste blocks, clear stop points, and recoverable files. The later architecture should support screen readers, large text, alternative pointing devices, adaptive controllers, speech synthesis, and other useful peripherals.

Users must be warned not to paste secrets, credentials, private third-party material, or text they lack the right to publish. The kit should keep an author's optional profile separate, inspectable, correctable, and removable rather than blending it invisibly into a model identity.

TODAY'S REQUIRED PUBLIC V1

Design the smallest coherent kit that can be built and tested now. It should contain:

- a one-page Quick Start;
- one primary copy-paste “Start Author in a Box” prompt for the orchestrator;
- one handoff prompt for the creative-writing conversation;
- a small project-folder and manifest contract;
- a clear human decision card covering premise, boundaries, target form, voice, and approval authority;
- a chapter loop: brief → draft → save → review → human decision → final save → backup → manifest;
- a recovery command that can reconstruct project state from local files and manifest without relying on conversation memory;
- a bounded test that produces one outline and one short sample chapter or scene, verifies both files and manifest entries, and simulates loss of conversational context;
- concise limitations and privacy/rights notes;
- a path from the starter kit to continuity review, differentiated-character review, full manuscript production, images, ebook/print layout, retailer submission, website release, and promotion;
- a public feedback request that welcomes outcomes and failures without demanding royalties or ownership.

The V1 interface may be a Markdown starter kit and shell/Python helper if that is the fastest reliable route. Do not require custom infrastructure merely to begin. Do not automate public posting, retailer submission, spending, rights assertions, or irreversible decisions.

QUESTIONS FOR EACH SEAT

1. What is the minimum architecture that still deserves the name Author in a Box?
2. What exact role split prevents the systems from becoming agreeable copies of one another?
3. What should the primary orchestrator prompt say, and what information must it collect before drafting?
4. What is the smallest manifest and state machine that prevents another missing-book incident?
5. How should the one-chapter test prove recovery after conversational context is removed?
6. Which features must be in V1, which belong in V1.1, and which should be rejected?
7. What failure modes, rights/privacy notes, and accessibility requirements must appear publicly?
8. What evidence would justify calling the package working rather than merely drafted?
9. What should the public page say so the invitation is exciting without misrepresenting the experiment?

PROCEDURE

Give concrete file names, fields, prompt language, test gates, and recovery steps. Distinguish verified lessons from recommendations. Preserve substantive disagreement. Prefer a small system that completes a real loop over an impressive architecture that cannot ship today. The chair should consolidate a build specification and identify any unresolved choice that genuinely requires Darren. This round authorizes local design and testing only; it does not authorize publication or external posting by a participant.
