Kinoshita World — Canon Reference

The pipeline’s anchor for “what’s true in this universe right now.” Use this file as a quick-reference; the master worldbook in Notion is the authority for fiction-only lore. When this file lags Notion, fix it; when it conflicts with engineering docs on hardware/runtime facts, the engineering doc wins.

Sources of truth

Source	What it owns	URL / path
Kinoshita World (Notion)	Master fiction canon — factions, characters, ledgers, AetherNet, CIPHER voice, ICE classes, TradEcon, synthetic-identity economics, corporate lineage, cartridge publishers	https://www.notion.so/Kinoshita-World-34eaf36f608a81798fa4fbba32f40283
Local worldbook mirror	Snapshot of fiction canon (may lag Notion)	docs/marketing/narrative/worldbook.md
Narrative CLAUDE.md (canon pointer) → kinoshita parent-repo CLAUDE.md	Hardware/runtime authority — display, grid, font, processor, coprocessor, audio, battery, case, cartridge format. The narrative CLAUDE.md is the pipeline-side canon pointer; it directs to the parent-repo CLAUDE.md in the sibling kinoshita repo (~/src/kinoshita/CLAUDE.md) which carries the Canonical Hardware Specification table.	docs/marketing/narrative/CLAUDE.md
Engineering docs	nOSh runtime, CIPHER engine, screen-design rules, gameplay specs	docs/software/runtime/, docs/software/cartridges/
ADRs	Decisions that supersede prose docs	docs/adr/ (start at docs/adr/README.md)

Conflict rule: Engineering canon wins on hardware/runtime facts. Notion master wins on fiction-only lore. The local mirror loses to either when out of sync — patch the mirror, don’t propagate stale lore.

Cross-cycle anchor index

These phrases / events / character details appear in multiple v3 books. They function as load-bearing connective tissue. A new edit must preserve them; a new draft should consider seeding one or more. If a future revision updates an anchor, it must update every book that uses it.

Anchor	Nature	Appears in	Notes
”autonomous output generation”	Phrase	The Lisp Machine + Variance Analysis (v3, multiple lines in chapters 4–5)	Canonical anchor for the CIPHER-becoming-conscious arc. Preserve EXACTLY.
”welcome back, operator”	YM2149 formant-event phrase	Cycle-wide; appears 1–2× per career, climactic scenes only	Pareidolia event — reader is unsure if the operator imagined it. Don’t deploy casually.
Wreck’s Black ICE injury	Character backstory	The Amber Circuit (canonical origin); referenced or implied elsewhere	Decade-prior corporate espionage contract; left-shoulder partial paralysis, residual aphasia under cold/fatigue, the IT industry coded them as damaged goods after.
The Reeves recruitment arc	Plot anchor	The Amber Circuit (origin); thematic echo in others	Reeves climbed the deckline ladder, almost made the Edgeware recruitment threshold. The “what if” backstop for protagonists who refuse the offer.
Shell-company name registry	World detail	Black Ledger scenes across the cycle	Canonical names: MERIDIAN LOGISTICS LLC, AZURE SPINE INDUSTRIES, KŌJI CONSOLIDATED, PR DYNAMICS SHELL 4. ~18% siphon to Edgeware.
Cartridge publisher names	World detail	Cartridge labels, contract briefs	Zaibatsu Digital, Bureau 9 Technical Services, Cascade / PR Dynamics, Takezo Institute, Kōji Interactive, Meridian Systems. Independent third-party studios licensing the SDK.
Synthetic identity tiers	Economic anchor	Operator economics across the cycle	~60k credits (counter-clerk pass), 150k+ (institutional), 500k+ (corporate-grade). Almost-everyone wants one; Edgeware tracks who buys.
Variance Analysis teeth-counting motif	Private symptom	Variance Analysis only (introduces a thematic shape)	The 32-tooth count, the 2.3mm gap “that has always been there.” Mirror to the CV-7 deviation.
Pi Zero 2 W naming	Hardware reference	All books that touch hardware specifics	Always “Raspberry Pi Zero 2 W” — never “Pi Zero” or “Pi Zero W.” Verify on copyedit.

When the Research dossier surfaces a new anchor candidate, add it to this list in the same PR as the manuscript. Anchors compound — each new book in the cycle should add 1–2 new ones.

Key invariants — fiction layer

Things you cannot violate without an Out-of-Universe reason. These trump scene-level convenience.

CIPHER voice

• CIPHER-LINE only. Renders as amber text on the 256×64 OLED strip mounted ABOVE the keyboard. Four rows. Never on the main 80×25 grid. Sole canonical exception: the Null cartridge, granted main-grid CIPHER-escape as a designed gameplay mechanic.
• Fragments only. Under 8 words per clause. Drop articles. Drop connectives. Single-breath fragments. trace up. mirror. clean. same node. black ice. sector seven.
• Five modes: observe, annotate, reflect, drift, silent. Silence is a first-class mode.
• Distance arc. Early career = procedural / impersonal / often CAPS / no operator’s name. Late career = reflect/drift / lowercase / may use operator’s name / warmth. The engine decides; the operator does not.
• Audible CIPHER is rare. CIPHER is text; CIPHER does not speak. Exception: the YM2149 formant event (“welcome back, operator”) — pareidolia, climactic only.
• One-way. Operators do not converse with CIPHER. CIPHER observes; CIPHER does not respond to address.

AetherNet

• Mesh, stealth, point-to-point with store-and-forward. No central server. No registered identifiers.
• Mission board listens; operators do not “download.” Procedural hashes reconstitute locally as MissionInstance records seeded by deck state.
• Looks like noise to a spectrum analyzer.
• Operators are invisible by default. Black ICE strips invisibility. Edgeware sees everyone.
• Operator-to-operator messaging rides the reverse path — dead-drop at coordinate hashes; recipient with matching key retrieves.

Black ICE

• Network-layer defensive software with physical consequences for the operator who triggers it.
• Stroke-inducing strobe through the amber screen (photosensitive seizure / TIA risk, residual aphasia / left-side weakness common).
• Auditory phase-cancellation through YM2149 → permanent partial hearing loss is common.
• Forces an unmasked AetherNet beacon for the duration; rivals and corporate counter-intrusion can pinpoint the operator to ~50 meters.
• Rare. Reserved for infrastructure that really doesn’t want to be seen.

The Identityless Premise

• Government ID is the prerequisite for legitimate commerce. Operators have lost theirs.
• The “TradEcon” is the legitimate economy operators are locked out of.
• Most operators climb the deckline ladder to buy a synthetic identity (rough tiers above).
• Edgeware probably knows when synthetics are sold — fixers route through the shell-company structures Edgeware controls.
• Solitude is enforced. Operators don’t usually know each other’s stories.

Corporate lineage

• Kinoshita Electronics Consortium (KEC) — Austin, TX, three-partner consortium 1985–1991:
  • Edgeware Systems (software house) — secretly survived KEC dissolution; modern KN-86 mission-board firmware is Edgeware’s original code. Recruits operators who climb high enough.
  • Meridian Semiconductor (silicon) — folded; later acquired by Cypress Semiconductor.
  • PacRim Display Technologies (LCD integrator) — dissolved with KEC.
• Kinoshita Systems — public manufacturer label on modern KN-86 hardware. Front under which Edgeware returned the device to circulation. Lawful, visible. Funded out of a KEC residual escrow that should have closed in 1991.
• Modern Meridian Systems (cartridge publisher) — separate successor entity, NOT the same as Meridian Semiconductor.

Operator economy

• Currency: untraceable credits.
• Reputation: accumulates on the device (Universal Deck State), not in any external registry.
• ~18% of operator revenue siphons through Edgeware-controlled shell companies. The operators are funding their own surveillance.
• Reputation tier gates contracts. Climb attracts notice.

What the local mirror covers right now

The local worldbook.md (~15 KB at last sync) covers the high-level system rules: corporate lineage, AetherNet, Black ICE, Identityless Premise, TradEcon / synthetic identities, CIPHER voice. The Notion master extends this with character database entries, ledger details, faction overviews, additional cartridge-publisher backstories, and live revisions. Always fetch Notion when in doubt.

How to update this reference

When a new anchor is established (the Research agent finds one, the Editor introduces one, Josh authorizes one):

1. Add a row to the cross-cycle anchor index above with the appearance citations.
2. Update the local worldbook.md if the anchor is fiction-only canon.
3. Note the update in the Notion master (or ask Josh to).
4. In the same PR as the manuscript change, run a grep across all v3 stories to verify the anchor is consistently rendered.