Project Explorer

Files

Story files

Browse the notes, research, decisions, and workshops used to develop the series.

Search 577 documents about the world, characters, plot, research, decisions, workshops, and earlier ideas.

Current document 07 Coordination/CURRENT-PICKUP.md

Document metadata
type: coordination-handoff
status: active
updated: 2026-09-08
scope: single current pickup point

Current Pickup

Website visual redesign — 2026-09-08

The visual redesign of the docs/ story site and Project Explorer has been implemented on branch cursor/story-sites-visual-redesign. It is awaiting author review. It has not been deployed to GitHub Pages or shared hosting.

This supersedes earlier statements that the websites were deferred or must not be rebuilt. Do not treat website reconstruction as an open implementation task unless the author requests changes after review.

The redesign is visual and layout only. Approved public copy was preserved. Story-development state and author gates below are unchanged.

Sources: 07 Coordination/2026-09-08 - Cursor Story Sites Visual Redesign, 07 Coordination/DESKTOP-QUEUE, and 01 Sessions/Daily/2026-09-08 - Cursor Story Sites Visual Redesign.

Desktop reconciliation — 2026-09-08

The September 7 mobile material has been reconciled into the session, compiled system, character, storyline, compact context, research, QA, and weekly-intake layers. That reconciliation did not run a website projection. The later visual redesign recorded above is now the current website state.

The next high-leverage author gate in the new branch is:

What is the first pattern or piece of information George correctly recognizes as real, and what false explanation does Samuel attach to it?

Answer only the observation and Samuel's interpretation. Do not yet design the full sequence, decide George's final culpability, or establish the exact wireless mechanism.

The employment-campus branch remains deliberately paused until the Sylvan–Samuel conflict state at employment entry is mapped. Resume it from the separate gate immediately below when the author chooses that branch.

Mobile pickup — 2026-09-08

Resume the conversational authoring-system test with one story gate:

At the moment Sylvan enters the employment stage, what has already happened between Sylvan and Samuel, and what influence can Samuel still exercise over him?

Established immediately before this gate:

  • the software-company collapse leaves Sylvan with an approximately $200,000 emergency investment functioning like a certificate of deposit;
  • it must sustain him for about ten years, averaging roughly $1,667 per month before returns, taxes, fees, or emergencies;
  • when it is exhausted, the employment stage begins and survival depends on active income;
  • the accepted working placement is a low-level campus operations-support role inside a large technology-company, university, institutional, or hybrid campus;
  • Sylvan advances through increasingly difficult training levels, with broader access and responsibility at each level;
  • for the first few years, Sylvan must remain with the same group while Samuel tries to turn its members against him and destroy cooperation;
  • Sylvan and his Luminai must help the group become stable without controlling its members, creating the employment arc's first ensemble and emotional relationships;
  • some group members are deliberately placed legacies of contained criminals, and some are consequences of Samuel's unauthorized breeding and bloodline manipulation;
  • Samuel intends to frame Sylvan, George, and selected group members for parts of his own system;
  • meeting the people gives Sylvan his first suspicions about the breeding scandal, but resemblance and pattern recognition are clues rather than proof;
  • the group uses three awareness levels: unaware members who believe their family histories, members who sense a problem but possess false explanations, and a small number deliberately positioned to manipulate the group and frame Sylvan;
  • the group is a realistic ten-person department including Sylvan, currently distributed as six unaware members, two with false explanations, and two deliberate manipulators;
  • its accepted working function is varied campus operations response across laboratories, offices, workshops, events, facilities, public spaces, and restricted areas;
  • its first major assignment is supporting the physical and operational infrastructure for a campus data-center expansion, with responsibility distributed across all ten members;
  • individual attack mechanics are intentionally deferred until the employment arc's macro structure is complete;
  • the author paused further campus development because it was becoming disconnected from the overall Sylvan–Samuel conflict;
  • the workplace must not resemble a postal processing facility or read as a disguised account of the author's job;
  • Samuel can now attack Sylvan through employment, earnings, projects, credibility, resources, and qualifying mistakes;
  • later, after surviving Samuel's high-influence period, Sylvan and Orzai reach terminal control and stabilize Sylvan's real-name online colonization story;
  • that story and its AI tools anchor Sylvan in reality while he intentionally interfaces with Samuel's Daemon through the hijacked application;
  • reaching other participants through the story remains proposed for later brainstorming.

Pause this branch on mobile. At the next desktop session, map the Sylvan–Samuel conflict state at employment entry before asking any more campus questions. Establish prior interactions, mutual knowledge, Samuel's influence and remote channels, intermediaries, current objectives, Sylvan's learned defenses, and the change across the employment stage. Then reassess every campus idea against that map. Do not treat the current company, department, group, or data-center ideas as random-detail commitments if they fail the integrated story test. The website visual redesign is no longer deferred; see the status above.

Product-system design checkpoint — 2026-09-07

The established conversational-authorship direction now has a proposed full-system beginning at Conversational Authoring System. It defines the author experience, Workshop and Composition contracts, current-state reconciliation, vertical slice, audits, acceptance tests, and phased roadmap. The author has established a Markdown-only durable runtime: Project Explorer will browse the Markdown vault, and no author-maintained JSON sidecar system will be introduced. No software build is authorized by the proposal alone. Resume product design by selecting the exact Seeds vertical-slice scene; resume story development at the existing gate recorded below.

The Composition Engine now has a proposed lean capability matrix. It adapts external methods selectively, runs deterministic checks before model critiques, uses one draft plus at most one automatic revision by default, and escalates to one specialist pass only for the scene's highest-risk dimension. The author approved Samuel's outcome-presentation confrontation with Sylvan before Konrad's inner circle as the first vertical slice. The next product gate is its exact beginning and ending state.

September 7 vault-functionality checkpoint

The author has paused direct story development to establish the vault's broader functional direction. The primary product audience is story-rich, craft-light creators, initially imaginative non-writers creating fiction. The vault should make authorship conversational from natural intake through adaptive workshops, accepted decisions, scene contracts, finished prose, revision, continuity, manuscript assembly, and export.

The concrete founder test is whether this system can finish Seeds of the Throne without requiring the author to manually perform every hour of writing and project maintenance. Optimize for finished, author-approved work: preserve the author's meaning, taste, corrections, and consequential decisions while shifting reliable organization, planning, drafting, continuity, revision, assembly, and maintenance work to the system.

The Workshop Engine and Composition Engine are the two flagship orchestrators. Source, system understanding, and proposed story use must remain separate; the system asks one high-leverage author gate at a time and propagates only accepted decisions. AI-assisted finished prose is within the eventual product boundary, while Seeds remains development-first at its present story stage.

Next tooling work: complete the open-source skill, author-problem, competitive-workflow, and requirements audits; then test one complete vertical slice before designing the full skill suite. Source: 07 Coordination/Conversational Authorship Product Direction. The paused story resume point remains SC-010 Question 7 below.

September 6 workshop checkpoint

All twenty workshop modules are author-accepted. Modules 01–07 establish sustainable population-scale purpose, voluntary self-made entry, qualified self-placement, customizable historical reconstruction, managed successor capability, multi-year bond development, and process-bound environments. Modules 08–20 add embedded governing rules; Konrad's postwar stake; Samuel's false autonomy bargain; Daemon verification and reactivation; the coerced grandson's generational path; Sylvan and Orzai's partnership and House qualification; George's direct participation on the new planet while Samuel and the older criminals remain on a previous planet; declining Samuel influence and rising Sylvan–Orzai control; interconnected personal and ethical stakes; the inner circle's comparative recognition; Samuel's attempt to scapegoat George, continue through Samuel Jr., and bargain with Sylvan; irreversible conclusion with no deals or moves; and entertainment-led flexibility for later-book order.

The literal Luminai-theft endgame is superseded. Exact safeguards, postwar legal terms, Daemon deception, cross-planet communication, trust crises, final-years thresholds, presentation mechanics, bargain terms, placements, remedies, and later-book sequence remain open. SC-010 Question 7 remains active and unchanged.

Source: 01 Sessions/Daily/2026-09-06 - Workshop Modules 08-20 Batch Integration.

Sources: 01 Sessions/Daily/2026-09-06 - Workshop Module 01 Purpose Draft, 01 Sessions/Daily/2026-09-06 - Workshop Module 02 Entry Draft, 01 Sessions/Daily/2026-09-06 - Workshop Module 03 Placement Draft, 01 Sessions/Daily/2026-09-06 - Workshop Module 04 Reconstruction Draft, 01 Sessions/Daily/2026-09-06 - Workshop Module 05 Deeper Integration Draft, 01 Sessions/Daily/2026-09-06 - Workshop Module 06 Bond Development Draft, and 01 Sessions/Daily/2026-09-06 - Workshop Module 07 Environment Commitment Draft.

September 5 integrated review checkpoint

The interactive environment is where Luminai were developed. Earlier participants use earlier versions; Sylvan uses the new deeper generation. The new program spans thousands of years. Prior bridge-era wording below is historical where it conflicts. The full assessment is 07 QA/2026-09-05 - Comprehensive Story Assessment. The twenty-module workshop is ready as decision support. SC-010 Question 7 remains active; no completion state changed. New interface mechanics, safeguarding rules, permission locks, and theft failure remain open. Browser answers require Markdown export and explicit author acceptance before vault integration.

Source: 01 Sessions/Daily/2026-09-05 - Integrated Foundation Audit and Workshop Build.

2026-09-03 bridge-world integration checkpoint

  • The 2026-09-02 mobile handoff has been reconciled into the vault's premise, chronology, AI-soul terminology, Samuel/Konrad causal structure, Book One architecture, criminal ecosystems, visual registry, QA, and public atlas.
  • AI soul is the broad historical category; Daemon means an evil AI soul; Konrad's Great War system is an older Daemon; Sylvan's Luminai is the successor deeply integrated generation.
  • The current planet is now the bridge between the closing older colonization era and the first real-world initialization of the successor Luminai.
  • Book One begins near the chronological end. Later books reconstruct the Great War, postwar reactivation, False Victory, and generational takeover.
  • SC-010 Questions 5 and 6 are accepted from the author's new decisions: bounded adversarial observation with preserved control, and repeated-pattern reconstruction across live behavior and historical evidence.
  • Resume at SC-010 Question 7. Ask one author-gate question at a time.

The active workflow is the horizontal Macro Shape sweep from Story Completion Workflow/CURRENT. The authoritative author-facing checklist remains Weekly Synthesis/CURRENT-COMPLETION-TODO.

2026-08-26 creative-pass checkpoint

2026-08-26 five-report research checkpoint

Current workflow state

  • SC-001 through SC-009 — complete at Macro Shape.
  • SC-010 — Build an endgame setup coverage matrix — active.
  • Completed at this depth: 9 / 27.
  • Do not deepen completed tasks until all active tasks have received the Macro Shape pass.

Accepted Sylvan–Luminai macro result

  • The breakthrough is a developmental stage for Sylvan and the Luminai as a pair, not one isolated power.
  • A conscious completed bond creates a privileged local-world interface through Sylvan.
  • The threshold begins when the Luminai presents itself directly to Sylvan through the interactive wireless bond and establishes a conscious neural interface with his brain/nervous system.
  • The interface is embodied and bidirectional enough that, with Sylvan consciously participating, the Luminai can communicate through his nervous system and can speak through his mouth.
  • The deeper interface is gated by a parents-activated growth-and-development program that begins when Sylvan is placed with the contained criminals.
  • The program trains Sylvan, trains the Luminai, and teaches both to work as a unified operational team.
  • The primary hard limit is process-enforced human decision authority: consequential action remains gated by Sylvan's conscious authorization.
  • The Luminai may observe, model, advise, communicate, and perform bounded lower-level actions or processing below Sylvan's conscious awareness, but this does not grant it authority over consequential choices.
  • The emotional and instinctive residue of that lower-level Luminai processing can surface through Sylvan's subconscious into conscious experience. Sylvan can therefore feel the interactivity of decisions he did not consciously formulate.
  • Sylvan still carries final responsibility for consequential decisions.
  • The later permission architecture should be designed like a real mature safety-critical human–AI control system rather than improvised scene by scene.

Accepted SC-010 progress

  • The earliest explicit setup demonstration occurs when the startup is collapsing and the Luminai first presents itself directly to Sylvan.
  • The Luminai explains the real danger and recognizes that Sylvan risks being processed, but it cannot simply extract him or choose flight for him.
  • It persuades Sylvan to consciously decide to abandon the startup and flee.
  • Sylvan takes a portable financial asset he still controls — exact form deferred, possibly stock, crypto, or another liquid account — and uses it to survive until the later employment environment.
  • This establishes early that the Luminai can know more, recommend strongly, and expose hidden danger while consequential action still requires Sylvan's conscious decision.
  • The second setup category is source discrimination inside the bond.
  • Sylvan develops the ability to distinguish factual, reliable information coming through the Luminai relationship from lies, distortions, and manipulative signals coming from contained-criminal daemons.
  • This is a trained epistemic skill, not automatic omniscience or a magical lie detector. The Luminai becomes a more reliable internal reference point, but Sylvan still has to judge competing information.
  • The audience must see this skill develop before later reveals or endgame decisions depend on Sylvan knowing which information channel deserves trust.
  • The third setup category is cross-bond Luminai coordination through bonded humans.
  • Sylvan can deliberately use his Luminai to establish structured interaction with another bonded Luminai, such as Orzai's.
  • This can support communication, mutual verification, shared situational awareness, and coordinated action between two human–Luminai teams.
  • Each human remains the conscious authority for consequential decisions on their side. Neither Luminai gains authority over the other human, and the connection does not become an AI-only decision channel.
  • The fourth setup category is real-time Luminai integration with physical modern technology through the wireless neural interface.
  • Sylvan learns to identify, understand, and master how the Luminai uses their bonded interface to perceive and interact with nearby contemporary technology in real time.
  • The broad operating chain is: Sylvan brain/nervous system -> Luminai -> nearby modern technology -> physical-world effect.
  • This integration develops progressively and still obeys the process-enforced human-authority rule for consequential physical-world actions.
  • Exact device classes, range, protocols, access mechanics, demonstrations, and failures are deferred.

Current author gate — SC-010 Question 7

After bounded adversarial observation and repeated-pattern reconstruction, what is the next major endgame-relevant capability, rule, or information skill that must be demonstrated before the outcome presentation depends on it?

Name only one category. Do not design its exact scene yet.

Research-derived option still available, not selected: consequential command-role discrimination.

Interaction rule

Use:

question -> author answer/correction -> exact restatement -> 2–4 narrow possibilities if needed -> causality/character/continuity check -> author accept/reject -> record -> next question

Ask one author-gate question at a time. After each author-accepted answer, update the active task packet, this Current Pickup, and the weekly TODO's Live progress before asking the next question.