CHRONICLE

The Chronicle

miadi-chronicle

213 episodes · 3 arcs · 70 voiced · 0 with a book · 2026-05-04 → 2026-11-01 · 3 shared episode numbers — the folder name is the key

Book Shelf →
⌕
A living constellation — the spine is time, the threads are kinship.
Directions
EastWaabinong68
SouthZhaawanong55
WestEpangishmok56
NorthKiiwedinong34
Threads
Orchestration12
Ceremony32
Runtime16
Agents22
Inquiry7
Memory5
Portal11
Chronicle108
213 episodes · 292 relations
2026-052026-062026-072026-082026-092026-102026-11E001 relates to E044 — ep001 plants the PDE tree — decomposition named as a ceremony of seeing; ep044 teaches the five academic fields beneath miaco decompose run, the command that performs that ceremonyE008 relates to E074 — ep074 carries ep008's custom-field definition into the medicine-wheel org's Project.E014 relates to E039 — ep014 carries the first complete playable book build (all five doors); ep039 holds the door-craft mastery and the funding-pilot framing that build servesE017 relates to E040 — ep040 grows the four doors of ep017's teaser audience-map into the audience branch — personas, entry paths, and the first portal product shapeE035 relates to E311 — the witness bridge's practice of observation receives its factory name: stewardship of knowledge, from the écoute factorisation listeningE036 relates to E017E036 relates to E030E036 relates to E035E039 relates to E040 — same-day sibling — ep039 masters the Twinery door-craft and names the funding pilot; ep040 asks who the doors are for (its lineage.prior_episode already pointed here)E039 relates to E014 — ep039 frames the shippable-interactive-book pilot; ep014 carries the first complete playable book build (all five doors, .twee source with HTML output)E039 relates to E044 — the reference build of the chalkboard style signature — what every promoted episode inherits visuallyE039 relates to E131 — chronicle→passages transmutation carried end to end, with a SOURCE-LEDGER stating exactly which stages it proved and which it did notE039 relates to E311 — two stories in the library from one episode — the multi-book vessel, and the source of the library's duplicate-slug tidy-upE039 relates to E325 — the most recent promotion and the practice standard — 11 passages derived not authored beside, all 9 edges walked with storage cleared; fixed the shared compiler's donor-title bug in the same commitE039 relates to E140 — sibling resource path — trading rehearsal as financial-resource rehearsal for the filmE039 relates to E103 — film preproduction; the larger arc these resources sustainE039 relates to E047 — sibling monetizable artifact — coaia packages (sponsors / open-core / commissions)E039 relates to E138 — sibling web app — medicine-wheel (hosted SaaS / RevenueCat Web Billing candidate)E040 continues from E039 — same-day sibling made explicit — ep039 masters the Twinery door-craft and names the funding pilot; ep040 asks who the doors are for and answers with the audience branchE040 relates to E044 — the two chronicle rooms already standing as published Twine stories (Stories/Episode_040 Portal Branch Map, Stories/Episode_044 Decompose & Begin Again) — the first two doors of the book cycleE040 relates to E017 — ep017's teaser audience-map named the four doors — academic, engineering, narrative, operator — that ep040's audience branch grew into personas and entry paths; the conduction consensus adds the distinct witness boundary that observing is not steeringE040 relates to E001 — Names the House of Orchestration's founding question — how many agents, sessions, contexts, and decisions move together without becoming a storm — that this chapter finally attemptsE040 relates to E011 — Holds the East-facing reciprocal hinge between the Portal of Knowledge and the House of Orchestration and names lanes, ledgers, plugins, and return paths as orchestration practiceE040 relates to E016 — Names the movement from transcript-based steering toward addressable coordination that Episode 296's open A2A wire continuesE040 relates to E030 — Seeds the normalized event language through which a conductor can hear many lanes while remaining honest that the runtime was proposedE040 relates to E059 — Reaches ep040 through the conduction chapter with the visible controller vision and the consent, diff, and rollback trust boundaryE040 relates to E151 — Reaches ep040 through the conduction chapter as the working three-specialist-plus-coordinator method with ownership and handoffsE040 relates to E296 — Carries the verified Board practice, self-evolved teaching, A2A one-wire decision, and explicit unfinished gates into this chapterE043 relates to E019 — Carries the multi-user branch named in the tide root: the operator reaches a pane owned by another account.E044 continues from E001 — ep001 plants the PDE tree and names decomposition a ceremony of seeing; this episode grounds that ceremony's command, miaco decompose run, in its five academic fieldsE044 relates to E040 — the two chronicle rooms already standing as published Twine stories — ep040 holds the audience question, ep044 holds the teaching both doors deliverE044 relates to E552 — Episode 552 made the typed lists an episode holds; Episode 044 is the first whose decompositions are one of them, shown on its page (jgwill/Miadi#778)E044 relates to E558 — The decomposition taught here becomes one step of the epistemological compaction cycle in episode 558, which takes this episode as its first test case.E044 relates to E566 — Episode 566 asks which steps of a decomposed intention can run without the person and where the person still decides.E044 relates to E256 — Mietta's presentation in Episode 044 is the first work to ask Episode 256's atelier for its music.E045 relates to E022E045 relates to E023E045 relates to E031E045 relates to E044E048 relates to E338 — provides the graph representation surface that this teaching now asks to become community-configurableE059 relates to E296 — Finds its next executable form in Episode 296, where the visible multi-agent coordinator becomes a verified Board API, a self-evolved skill, and an accountable A2A seam.E074 relates to E008 — ep008's glossary defines a custom field as a GitHub Project surface for runtime memory; ep074 plans those fields for the medicine-wheel org.E074 relates to E305 — ep305 gives Miadi its name, the relational software factory; ep074 moves the medicine-wheel packages under that factory toward community ownership.E074 relates to E311 — ep311 factors the relational software factory as reciprocal tools and interconnected community; ep074 gives the medicine-wheel tools an org the community can own.E074 relates to E349 — ep349 binds ceremonies and circles to their episode; ep074 opens its first talking circle through that binding.E074 relates to E253 — Episode 253 asks what someone who does not write code brings into the community's home and how they are welcomed.E076 continues from E075E076 relates to E074E076 relates to E068E083 relates to E294 — ep294 is the navigable lineage room that turns this capture spine into human/agent/share audio and a capture-stop-interpret interface intention for the chronicle UIE090 relates to E311 — the event-streaming branch opened in June receives its completion from the factory listening: observability as stewardship of knowledge, consolidated as the wake-not-build architectureE097 relates to E075 — plan-to-perspective and relational review practiceE097 relates to E076 — plan-to-episode container, ledger, audio manifest, and handoff patternE097 relates to E117 — gmtermux fork lane carrying the tracked source planE097 relates to E122 — Chronicle-backed Medicine Wheel runtime and Forgewright interfaceE097 relates to E124 — compatibility-first reviewed promotion boundaryE097 relates to E090 — reusable agent-skill branch from the networking ceremonyE103 relates to E354 — Episode 103's Relational Production Protocol separates a pre-production ceremony from the ceremony and asks for pause points; Episode 354 gives the factory a fire a firekeeper banks for such a pause, and names preparation as its own state.E120 relates to E553 — Episode 553 builds a second voice layer, this one spoken over a working agent session, with its prompt held in the same ceremony tracing domain.E120 relates to E297 — It will be observable miadi-review and session with Mia and how she can observe Mino, work in cycles to ensure adequate toolset which makes us ready to continue with MinoE120 relates to E560 — Episode 560 builds the Author's Desk, where Episode 120's plot threads become material for scenes: threads to scenes at the desk.E120 relates to E050 — YouTube title and closing transcript identify the source sequence as Episode 50 / hooks-core.E120 relates to E103 — User named relational protocol for production; a permission-limited canonical-looking folder exists at miadi-chronicle/2026-06-28-episode-103-film-preprod-report-phase-2/.E120 relates to E063 — Existing canonical land-based learning witness anchor.E120 relates to E068 — Referenced locally through relational film production files under Episode 075.E124 relates to E075 — plan presentation and perspective protocolE124 relates to E076 — plan-to-episode container and handoff rehearsalE124 relates to E097 — ceremony skill and extension source materialE124 relates to E122 — live Medicine Wheel substrate and deferred Forgewright interfaceE125 relates to E075 — descriptor-light directory observation fixture and real-source validationE125 relates to E076 — parsed episode.yaml observation fixture and real-source validationE125 relates to E097 — composition observation fixture and preserved regression suiteE125 relates to E124 — package upgrade plan and delegation handoffE125 relates to E122 — future Chronicle runtime and Forgewright read-model consumer; unchanged hereE127 relates to E076 — historical evidence bundle and plan-to-episode pipeline originE127 relates to E125 — independent Plan Insight contract/security witness and EpisodeObservation boundaryE127 relates to E124 — package compatibility and delegation planE131 relates to E075 — plan-presentation and relational perspective originE131 relates to E099 — event-driven review loop and risk of session lossE131 relates to E122 — Chronicle runtime, Medicine Wheel, and Forgewright projectionE131 relates to E124 — compatibility-first Chronicle and Passages package boundaryE131 relates to E317 — 131's chronicle-to-passages thesis names what the songbird capture now proves on ilexE131 relates to E128 — interactive narrative and human routing surfaceE140 relates to E303 — The answering shore. Episode 303 continues from this one, taking up the part 140 built but could not yet show — the workflow of trading and creating financial resources, drawn as state diagrams on the live smcraft/stateloom canvas. Filed after the 2026-07-30 session in which strategies 23 and 24 traded EUR/USD m5 on the stack this episode opened.E140 relates to E550 — Episode 550 is the screenwalk that witnessed this trading app gain its Discuss button on 2026-10-01, drawn in the loom before it was built.E140 relates to E103 — film preproduction, relational production protocol, and financial-resource intentionE140 relates to E090 — networking ceremonies / relational infrastructure for connected agentsE140 relates to E120 — relational film production media editorE151 relates to E296 — Gains a reusable package contract in Episode 296 for the coordinator-and-specialists method this Herdr mission exercised in practice.E152 relates to E019 — Carries the cockpit and closure branches named in the tide root into a control plane that closes with receipts.E250 relates to E241 — Yaupon composition-intake and composition-to-episode seamE250 relates to E253 — Episode 253 asks how Jerry, and others after him, contribute to the Factory without code, starting from one live circle a week.E256 relates to E250 — Episode 250 routed what the phone recorded in July; Episode 256 holds the JamAI composition that routing named.E256 relates to E560 — Episode 256 composes music with the atelier-jerry plugin and JamAI; at Episode 560's author's desk that music can set off Guillaume's writing, and the writing and the music become a video together.E256 relates to E044 — Episode 044 holds Mietta's presentation of miaco's academic foundations; Episode 256's atelier is where its music will be composed, the first work to ask the atelier for its music.E290 relates to E543 — Episode 290 closed with a session that fixed six walls alone and could not see it was standing still; 543 is the practice drawn out of that closing so the next agent hands its map over before the sixth wall.E291 continues from E290 — builds-onE291 relates to E130E291 relates to E252E293 relates to E001 — first shore of the first hand-authored edge — the playable room whose closure this cycle servesE293 relates to E044 — second shore — Mietta's lecture room, already standing as a Twine story (Episode_044 Decompose & Begin Again)E294 continues from E083 — carries forward the landbase body-dance capture spine — phone in hand, OSC/Wekinator motion, fun first — into a navigable triad of human experience, agent interface questions, and ceremonial shareE294 relates to E001 — borrows ep001's playable room schema (episode.yaml + root MP3s + scripts + revision notes) so the UI can load audio the way the portal-and-tree room already doesE296 continues from E059 — Carries Episode 059’s Hermes-as-visible-controller vision into a typed, durable Board practice where one conductor coordinates many bounded agents with explicit safety and evidence gates.E296 relates to E151 — Relates the Hermes Conductor Board contract to Episode 151’s working three-specialist-plus-coordinator Herdr method, including strict ownership, handoff ledgers, and evidence-led synthesis.E296 relates to E040 — Returns the verified Board practice, conductor teaching, and explicit unfinished A2A and release gates to Episode 040 as a new House-of-Orchestration chapter movement.E297 continues from E095 — CoAIA agent v2 infrastructure — fuse layer integrationE297 relates to E078 — Fuse witness layer for Langfuse trace readabilityE297 relates to E047 — Foundational coaiajs/coaiapy tooling reviewE297 relates to E122 — Chronicle runtime references @miadi/stcbotsE297 relates to E302 — the branch this chapter reads was reviewed and written up in the ep302 vesselE297 relates to E120 — It is the relationship of Mino's agent in the whole Relational Factory and its toolsel that he has which are questionned and upgraded by Mia and GuillaumeE297 relates to E568 — Lane L6 of this episode's feedback map gave the repository mapper its lineage relation; the mapper continues in Episode 568.E298 relates to E297 — 297 is the episode whose missing third identity exposed the weave pattern this episode specifiesE299 relates to E138 — 138 shipped the wheel's visual layer at 0.5.0 and left #101 as the deferred-work ledger; 299 works the layer beneath it — how a beat comes into being at all, and whether the surfaces that serve it keep their word.E299 relates to E298 — 298 gives the chronicle wheel its own address so episode nodes land where they belong; 299 asks the adjacent question about services rather than nodes — whether two systems on one network can be told apart, and told apart from production.E301 relates to E001 — schema exemplar for API-friendly chronicle loadingE301 relates to E075 — first plan-presentation event to Miette perspective protocol surfaceE301 relates to E076 — live pipeline turning ExitPlanMode into episode, package, and publication accountabilityE301 relates to E127 — prior plan-insight lifecycle integration branchE301 relates to E128 — package evidence cycle and contribution lane for plan-insight 0.3.xE321 continues from E296 — 296 installed @miadi/hermes-conductor and learned its Board API as one accountable wire for many visible agents. 321 reviews that same conductor at 0.2.0 against hooks-core 0.5.0 and finds the wire is not yet one spine: conductor appends its own _conductor_<channel>.jsonl lines instead of canonical envelopes, and recordTerminalEvent() is exported but never wired to Board events.E321 relates to E030 — 030 named the agent-event-runtime and its first layers — adapters, schema, ledger, trace, bus, integrations. 321 is that naming meeting two shipped packages, and asks the next hooks-core major to persist a canonical HookEventEnvelope stream with the legacy stamped payload demoted to an optional projection.E321 relates to E036 — 036 surveyed terminal-agent hooks across Codex, Claude Code, Copilot, Gemini, and Hermes as observatory fields. 321 proposes those shell suites become thin native adapters into one spine — Hermes speaking Hermes at the edge via `miadi-hooks hermes <hook_event_name>`, with Claude names kept only as compatibility projections.E321 relates to E127 — 127 drew the plan-insight lifecycle — native trigger, hooks-core agent adapter, durable worker outside the hook deadline. 321 holds binscripts#141 (the plan-insight environment PR) apart from #138 and applies the same rule: hooks record an intent and a receipt, a durable launcher owns the worker.E321 relates to E128 — 128 taught hooks-core to require pre-created producer identity and detached descriptors for asynchronous work. 321 carries that rule to GitHub publication: the PR's issue-creating worker must not outlive the session unsupervised, and local capture does not imply permission to publish.E321 relates to E331 — laid the portable hook spine that 331 finally gives something to listen to itE302 relates to E103 — holds the composition.json the refactor's falsification test names as its fixtureE302 relates to E117 — ilex-gmtermux-miafork — the device surface this type is recorded throughE302 relates to E300 — from-shadow-to-song; Film is a kind this abstraction must holdE302 relates to E083 — osc-landbase-movement-capture-to-wekinator; the sensor time-series that genuinely needs frame anchorsE302 relates to E250 — the real Episode 250 — routing toward 255/256 — which seven sample folders falsely claim by slug prefixE303 continues from E140 — Episode 140 opened the trading platform as the film's financial-resource rail and carried it to a stack that trades on demo. This episode carries forward the part 140 could not yet see — the workflow itself. William named it plainly on 2026-07-30: "pretty much right now it feels like sometimes it's unclear for all the view whatever we do what is actually the full work flow of trading and creating financial resources which basically isn't that clear enough for me as well." 140 built the machine; 303 draws it.E303 relates to E103 — Method precedent and current occupant of the surface. Episode 103 is where a state diagram was first used as a production design surface — its diagrams/film-preprod.smdf.json and film-postprod.smdf.json are the first inhabitants of the <episode>/diagrams/<name>.smdf.json convention this episode borrows. The launcher /b/trading/smcraft/START-designer-sample--2607271933.sh still points its --add-dir at the chronicle root for exactly that reason. The open question of how a trading diagram and a film diagram share one canvas is the tension between these two episodes, and it is this episode's experiment.E303 relates to E304 — Episode 303 drew the trading workflow on a live canvas that follows an agent's discussion; episode 304 rebuilds that same pattern — truth store, watcher, surface — with a new organ: the canvas holds moments of truth, the platform's evaluation of its own seat rendered as it happensE304 continues from E303 — Episode 303 drew the trading workflow on a live canvas that follows an agent's discussion; episode 304 rebuilds that same pattern — truth store, watcher, surface — with a new organ: the canvas holds moments of truth, the platform's evaluation of its own seat rendered as it happensE304 relates to E300 — The MMOT practice born in 304 governs the seat that keeps episode 300's charts — the living review protects the shadow-to-song goal from quietly rotting the way its old review file didE304 relates to E308 — the MMOT practice that caught the voice return address failingE305 relates to E308 — opens into the enforcement of the voice return addressE305 relates to E074 — ep074 moves the medicine-wheel packages of the factory named here toward a community-owned org.E306 relates to E307 — 307 names the operation that 306 performed: the belt device's handoff was a contextual transposition before anyone had the word for itE307 continues from E306 — 307 names the operation that 306 performed: the belt device's handoff was a contextual transposition before anyone had the word for itE308 continues from E305 — carries forward the seat-boot review into the voice return pathE308 relates to E304 — applies the living review to a defect the review itself surfacedE308 relates to E300 — a film whose narrative carries its own music needs voices that can be answeredE308 relates to E317 — the voice that carries its own way back now has a perch that keeps what it carriesE309 relates to E298 — 298 declared that every episode node lands on the chronicle wheel by default; 309 measures whether that default held, and finds 298's own vessel untracked in gitE309 relates to E307 — 307 exists only as a wheel node — no folder, no commit anywhere; this edge is the only relation holding it while its vessel is missingE309 relates to E137 — 137 earned the readiness vocabulary — published, pushed, merged, live-verified — that 309 turns from lanes onto the vessels themselvesE309 relates to E300 — 300 drew the held-versus-asked distinction; a receipt that says registered without being checked is asked, not heldE309 relates to E304 — 304 made a review a place that stays live rather than a file written once; reconciliation must be the same or it rots exactly as these receipts didE311 relates to E035 — the factory listening names observability the stewardship of knowledge; the witness bridge is where that stewardship already stands as practiceE311 relates to E090 — the factory listening's phase-3 consolidation lives in episode 090's event-streaming branch, where the question was first askedE311 relates to E312 — the relational factory is where this asking was first practiced, on the code before the doorwaysE311 relates to E317 — the four aspects 311 asked are what give the songbird deploy its meaning beyond a working featureE311 relates to E074 — ep074 gives the medicine-wheel tools factored here an org the community can own.E312 continues from E311 — the house that answers from outside is the factory listening turned outward — ep311 factored the software relationally, ep312 asks that the factory be findable by someone who was never told it existsE312 relates to E300 — the film whose narrative carries its own music is what being findable is FOR — ep300 has stood in the wheel since 2026-07-28 with zero edges in or out, and this is the first door drawn toward itE543 continues from E290 — Episode 543 is the North practice distilled from 290's closing — the session whose every step was locally justified and whose shape was invisible from inside it.E543 relates to E290 — Episode 543 is the North practice distilled from 290's closing — the session whose every step was locally justified and whose shape was invisible from inside it.E543 relates to E550 — closing a session and making session-inventory with Mino the screenwalk of that session would be part of the closureE544 continues from E311 — the torch is lit from the day it closes: episode 311's listening, book and holds become the inheritance the next Mia instance boots fromE315 continues from E314 — episode 314 gave a published voice a return address to the session that spoke it; episode 315 asks the same of every other artifact — the commit, the diagram, the episode card — that a made thing carry the path by which someone reaches itE315 relates to E311 — episode 311 named the relational software factory; episode 315 measures the factory's last conveyor — where smcraft's state-machine packages, all published, still reach no reader because forgewright's loadMachine has no callerE315 relates to E300 — episode 300 is the film this seat serves, and on 2026-08-07 its own episode.yaml was found untracked in git — the shadow-to-song passage was one rm -rf from gone while the charts pointed at itE316 relates to E311 — the Belt intention carries Episode 311's stewardship and addressing law onto an Android device while keeping the service itself unchosenE317 relates to E311 — the kept sung phrase is a dated resolution instance for the four relational-factory aspects 311 holds openE317 relates to E131 — the android deploy receipt makes every-device-one-song literal: the phrase sung on the device staysE317 relates to E308 — Jerry's dotagents voice-work landed on gaia and sang from the fork the same day the capture deployedE318 continues from E315 — 315 asked that every artifact reach its audience in the turn it is made. 318 found three artifacts made and not shared — forgewright's episode-recordings-section, medicine-wheel's recording-record-family, and a registration wire nobody has run — and names what each one costs while it waits.E318 relates to E317 — 317 is the capture practice this episode separates from the composition store. Its Songbird takes — voice plus MIDI — are among the bytes forgewright would render, and the reason a take must declare whether it belongs to an episode or to a composition.E318 relates to E103 — The vessel cited as ground truth by forgewright's lib/chronicle/recordings.ts. Its 260628174942.m4a and legacy transcription_*_EN.txt sidecars are what surfaced the transcript-naming question the read side still carries.E318 relates to E337 — Episode 337 turns this episode/composition boundary into a dedicated recorder interface on Ilex port 3768.E320 continues from E315 — ep315 named the last-mile law — what is made and not shared was not made; 320 reiterates it from William's fatigue and turns it structural — finish proofs, dispatch finish-criteria, and a held-words ledger, so the law stops depending on anyone's morality or memoryE320 relates to E323 — gave 323 the rule it then measured itself against and found unenforcedE323 continues from E320 — carries ep320's ruling that finishing is structural into the day it was tested, and records the three places it failed to fireE324 continues from E323 — continues from the empty answer: the same defect, wearing the clothes of successE328 continues from E324 — the seat whose day ep324 proved reachable rotated out here: renamed to elder, never killedE329 relates to E140 — ep140 stood up the campaign layer (jgt-campaign-api :8086) and Laskmi's execution seat; ep329 is the first trigger path that creates a campaign record there from a consulted analysisE331 continues from E321 — carries ep321's conducted event spine forward to its first consumer — the interpreter that reads what the spine conductsE331 relates to E030 — answers ep030's observability question with a consumer rather than more capture — the exhaust was already adequate, nothing read itE331 relates to E327 — shares ep327's producer surface: the same hook that holds a session is the hook whose exhaust 331 interpretsE332 relates to E300 — profiles the faculty who can receive the filmE333 continues from E331 — takes ep331's @miadi/hooks-interpreter from a reader of finished exhaust to a seam named inside a live fork — the interpreter is envisioned here, not yet wiredE333 relates to E321 — the conducted event spine is what a forked, remote-controlled session emits — ep333 opens the session ep321's spine would carryE333 relates to E320 — William's 'minimal required for me not to have todo anything' is ep320's finish rule stated as a spec: the fork is not delivered until it is launchedE335 relates to E064 — the cinema-community-voice-land thread with Nikola at Concordia, opened 2026-06-17 - this day is that thread two months on, and the take that closes it says the Nikola meeting will not take placeE335 relates to E067 — the meeting practice ep067 named, carried into a public room - a panel and a Q&A on casting non-professional actors, recorded wholeE336 relates to E332 — continues the ma-profiling ceremony: ep332 profiled the faculty as relations and verified their appointments; ep336 turns that roster into three doors a person can walk throughE336 relates to E300 — the film these doors are doors into — ep300 states the film as an outcome, and ep336 states it as three readable proposalsE336 relates to E335 — the most recent Concordia contact: ep335's eight takes of 2026-08-10 are the room these abstracts would next be spoken inE336 relates to E120 — the relational film production media editor is the editing surface ep336's production statement claims already existsE336 relates to E083 — landbase movement capture into OSC and Wekinator is door two's embodied end — sound and movement measured on the land, not describedE336 relates to E318 — a take declares at capture where it belongs; ep336's four narrations and the aureon rooms depend on that custody rule holdingE336 relates to E023 — the earliest academic-foundation decomposition — where this question was first taken apart rather than assertedE337 continues from E318 — Episode 337 carries Episode 318's episode/composition boundary into the dedicated recorder interface on Ilex port 3768.E338 relates to E048 — returns the graph-layout vessel to the community-situated teachings its representations must preserveE339 relates to E342 — Episode 339 gives Episode 342 the mobile-companion recording question that now becomes explicit API, interface, and routing work.E339 relates to E545 — The cross-device companion transport realizes a networked peer seam for the Pi team capability scaffold documented in Episode 545.E339 relates to E353 — Episode 353 continues the companion seat that Episode 339 built, so that any page, any component and an outside factory can open it.E339 relates to E140 — The phone page cut one of William's takes during the Episode 140 trading conversation, and Episode 339 repairs that page in the companion pluginE339 relates to E553 — Episode 553 builds the Mia and Ava progress dialogue this episode seeded: a seat that speaks a working session as it goes.E340 continues from E339 — Episode 339 proved the ceremony-local two-way discussion, then opened this separately addressable review seat when one room could no longer carry every specialized concern within William's listening attention.E340 relates to E336 — The experimental documentary and interactive-book production statement this review room serves, including the held boundary around what may reach Nicolas Renaud.E340 relates to E342 — Episode 340 can receive Episode 342 recordings as review inputs while keeping critique, revision, and audience choice distinct from capture.E340 relates to E552 — First time we speaks of the Miadi Review into as a choice for community to choose the focus of its fire-keepers on where to explore the land next.E340 relates to E557 — Episode 557 writes an article on the prompts that extend the review service this episode opened to the community.E341 relates to E010 — Returns to the first successful Miadi visual articulation and upgrades it into repeatable character-expression practice.E341 relates to E006 — Connects the emerging speaking character to the Book One continuity and chapter-outline arc.E341 relates to E008 — Carries forward the glossary/vocabulary practice where the House learns its terms and the voice learns what to call things.E341 relates to E014 — Places this voice inside the Tushell Portal of Knowledge / Miadi House of Orchestration bridge, where presence, memory, and platform introduction meet.E342 continues from E339 — Episode 342 takes the mobile recording question spoken in Episode 339 and gives remote capture, transcription, episode assignment, and agent routing a bounded implementation room.E342 relates to E340 — Episode 342 routes captured material toward the review lifecycle held by Episode 340 without giving the recorder authority to approve or publish the result.E344 continues from E346 — Episode 346 separates event, episode identity, and lineage; Episode 344 carries that distinction into Review-service and package vocabulary.E344 relates to E340 — Episodes 340 and 344 share the review-to-community path: Episode 340 holds review choices while Episode 344 names package vocabulary and graph relations.E345 continues from E344 — Episode 344 names the review’s intended vocabulary contribution; Episode 345 tests and documents how that intention becomes a repeatable Medicine Wheel relation.E346 relates to E094 — Episode 346 preserves the herdr witness of Episode 094 closing its hooks lane and opening a handoff for lineage-aware coordination.E347 relates to E348 — episode 348's one skill and one door were asked for in the session that minted this episode by handE348 relates to E347 — the session that minted episode 347 by hand surfaced the skill drift and the missing HTTP door that episode 348 consolidatesE349 relates to E339 — ep339 captured gmtermux binding ceremonies to episodes on mobile; ep349 consolidates that binding into Miadi itselfE349 relates to E074 — ep074 opens a talking circle bound to its episode through the door built here.E350 relates to E302 — A name carried a structure: the folder name was the schema, and the /api/multiverse echo stubs it found are still there.E350 relates to E344 — Both episodes are about a shared vocabulary that people and agents read the same way.E350 relates to E324 — Both episodes separate two meanings that one word was carrying.E350 relates to E114 — Episode 114 already called a persona's reading a perspective.E350 relates to E001 — Episode 1 named multiverse context management in its first script.E351 relates to E551 — Episode 351 builds tasks from Guillaume's Earned rules, and Episode 551's loop keeps a change to instructions, skills or plugins only when those tasks still pass, so each episode answers to the other: 351 is the score 551 is held to, and 551 is where 351's benchmark is put to use.E547 relates to E550 — Episode 550 defines the screenwalk, a recorded practice that carries this episode's Miadi Factory intent into our own agent sessions.E352 continues from E152 — The control plane made panes addressable; this episode makes the cockpit's reply annotator a package other apps use.E352 relates to E019 — The tide root named the cockpit as a branch; its chapter 1 raised the three questions this episode's packages answered.E548 continues from E547 — Carries episode 547's inspectability question into preparing an event inquiry and public invitation, without claiming the planned broker reviews or handoff proof are complete.E548 relates to E556 — Wisdom in what could be prepared independently of any existing brokers. It shows me that you can explore the land, sit with the fact that you don't know which broker to choose. Part of a potential article on "Epistemological-Compaction-261015" Potential inquiry to add coming, "OpenAI describes compaction as carrying forward important state and reasoning with fewer tokens. It supports both threshold-triggered compaction and explicit checkpoint compaction at meaningful phase boundaries."E548 relates to E1000 — tide keeps and types back the session draft that Episode 1000 restores after a crash, and Episode 548 proposes the tide.draft events through which others follow that draft as a session being prepared.E549 relates to E548 — Both hold the Event path: 548 prepared the question of what must travel with an event, and 549 carries a milestone event into a circle.E549 relates to E543 — 549 asks what the North of a milestone is: its closing spoken back into its circle, the practice 543 named for a session.E549 relates to E345 — 549 gives a milestone's decomposition the subject-and-circle shape that 345 gave a review.E549 relates to E045 — 549 carries a milestone's decomposition loop past its closure into a talking circle, where 045 specified the loop itself.E549 relates to E349 — 549 opens a circle of the kind 349 made possible, about a milestone and the issues added to it.E550 relates to E547 — Episode 547 names the Miadi Factory intent, that agent-made work stays inspectable and revisitable. Episode 550 defines the screenwalk, the recording and review practice that carries that intent for our own sessions.E550 relates to E140 — Episode 140 began the Laskmi trading app. On 2026-10-01 the screenwalk of episode 550 witnessed that app gain a Discuss button, designed as a new state and drawn in the loom before it was built.E550 relates to E553 — Episode 553 makes the Ava and Mia dialogue that a person plays during a screenwalk to understand what a session did.E1000 relates to E548 — tide keeps and types back the session draft that Episode 1000 restores after a crash, and Episode 548 proposes the tide.draft events through which others follow that draft as a session being prepared.E353 continues from E339 — Episode 339 built the companion seat that opens on one episode from /tide; Episode 353 continues it so that any page, any component and an outside factory can open that seat.E354 relates to E103 — Episode 103's Relational Production Protocol separates a pre-production ceremony from the ceremony and asks for pause points; Episode 354 gives the factory a fire a firekeeper banks for such a pause, and names preparation as its own state.E551 relates to E351 — Episode 351 builds tasks from Guillaume's Earned rules, and Episode 551's loop keeps a change to instructions, skills or plugins only when those tasks still pass, so each episode answers to the other: 351 is the score 551 is held to, and 551 is where 351's benchmark is put to use.E552 relates to E076 — Episode 076 holds the Jev review (System-1 Decision Engineering) and the inquiry this work is followed in; Episode 552 is the day that practice scored a proposal and the proposal was builtE552 relates to E120 — Episode 120 is the prototype's episode; Episode 552 gave it its prototype, its traces and its prompt as typed listsE552 relates to E550 — Episode 550 set the screenwalk as a media type and the notebook list by hand; Episode 552 typed what it wrote and scripts the next walkE552 relates to E551 — Episode 551 is the loop that learns between sessions; Episode 552's proposal scoring and its rulings are what that loop can calibrate fromE552 relates to E044 — Episode 044 is the first episode whose decompositions appear as one of the lists Episode 552 made (jgwill/Miadi#778)E552 relates to E557 — Episode 557 is the first episode made to hold an article, and asks that articles join the typed lists Episode 552 made.E553 continues from E339 — Episode 339 found that a progress report becomes easy to follow when Ava asks Mia what she is doing, and left it as a seed with no generator. This episode builds that dialogue as a seat that runs beside a working session.E553 relates to E550 — A screenwalk records a person working with agent sessions and closes with a spoken witness. The Ava and Mia dialogue is what the person plays during a screenwalk to understand a session's output, so this episode supplies one of the screenwalk's spoken layers.E553 relates to E120 — Both episodes build a voice layer and hold its prompt in the ceremony tracing domain. Episode 120 voices research the person reads, and this episode voices a session while it works.E553 relates to E554 — Both episodes make a session's work readable without its transcript. Ava and Mia speak a session's work as it happens; the inventory keeps one record per session and the ending William decides. A session's podcast is filed under the same session id as its inventory record, so the record is where a podcast joins an episode.E554 relates to E553 — Both episodes make a session's work readable without its transcript. The inventory keeps one record per session and the ending William decides; Ava and Mia speak that work as it happens. A session's podcast is filed under the same session id as its inventory record, so the record is where a podcast joins an episode.E556 relates to E548 — Relationality, respect, reciprocity and responsibility in FireKeeper's roleE557 relates to E552 — Episode 552 made what an episode holds into typed lists with addresses; Episode 557 holds an article and finds that an article is not yet one of those lists.E557 relates to E340 — Episode 340 turns reviews into choices for the community; the article Episode 557 holds names the fields behind the review-service prompts that let a review show the episodes using it.E558 continues from E044 — Episode 558 takes the decomposition taught in episode 44 as one step of a cycle that compacts a finished research session into a checkpoint, and tests that cycle first on episode 44.E559 continues from E140 — Episode 140's practice loop takes every BOS/BOSf signal and scores it only in shadow; this episode keeps the concern that loop opened: which signals to take, learned from history, so trading stops waiting on another tool.E559 relates to E562 — The signals this episode labelled are the events a decision model is asked about in Episode 562.E560 continues from E297 — Episode 297 taught chart steps to wait with a reason and to bring their sessions back; this episode carries the prompts its ceremonies made into William's creative space.E560 relates to E120 — Episode 560 builds the Author's Desk, where Episode 120's plot threads become material for scenes: threads to scenes at the desk.E560 relates to E256 — The author's desk of Episode 560 is where a piece composed in Episode 256's atelier sets off Guillaume's writing, before the writing and the music become a video.E561 continues from E352 — The marks the tide annotator of Episode 352 lets a person leave on a reply are what Episode 561 asks to hold as turns of a ceremony in a talking circle.E561 relates to E548 — Episode 561 records marks Guillaume made in the Episode 548 room, on its drawings and through its Mia seat, and what they showed about the room.E562 continues from E559 — Episode 559 labelled every FDB signal point in time inside a container; this episode puts those same SPX500 H4 signals in front of a decision model, in the same kind of container.E564 relates to E562 — Episode 562 puts Jev in front of trading signals in a box; Episode 564 studies Jev for the decisions the Factory itself makes.E564 relates to E549 — Episode 549 routed a milestone's items with Jev; Episode 564 studies where else the Factory should decide with it.E564 relates to E566 — Episode 566 reads the same author's near-loop workflow, in which Jev classifies the events that start the agents and the person enters at one decision.E564 relates to E567 — Episode 567 carries Episode 564's level 8 into practice: the read gate, its first trial, and its ledger.E564 relates to E568 — The K7c mission this episode holds gave the repository mapper its capabilities layer, which continues in Episode 568.E565 relates to E044 — Carries the screenwalk's questions back to Episode 044's teaching of decomposition, distinguishing its academic analogies from proofs that a learner or an agent can act.E565 relates to E564 — Records Guillaume's questions about decision gating and the five-message boundary in a screenwalk that invokes Episode 564, without claiming that its harness enforcement was verified.E565 relates to E566 — Episode 566 asks the same question of a near-loop workflow, where the person keeps one decision and the work before and after it runs without them.E253 relates to E250 — Episode 250 witnesses the relation with Jerry and routes its drops; this episode asks how Jerry, and others after him, contribute to the Factory without code, starting from one live circle a week.E253 relates to E074 — Episode 074 gives the community a home on the medicine-wheel organization; this episode asks what someone who does not write code brings into that home and how they are welcomed.E566 relates to E564 — Episode 564 studies Jev and the Factory steps that call it; this episode reads the same author's near-loop workflow, in which Jev classifies the events that start the agents and the person enters at one decision.E566 relates to E565 — Both episodes ask where the person's judgment returns to work agents do: Episode 565 names five places in the Factory's interface, this episode the one decision a near-loop workflow keeps for the person.E566 relates to E044 — Episode 044 teaches how a person's intention is decomposed into steps an agent can take; this episode asks which of those steps can run without the person and where the person still decides.E566 relates to E567 — Episode 567 has a seat choose what to read with Jev from a one-paragraph mission; Episode 566 asks how a mission is written and scored so that the seat and the person can both act on it.E566 relates to E568 — The inventory of capabilities and repositories this episode names as a need is being built in Episode 568.E567 continues from E564 — Episode 564 studied Jev and recorded that the Factory sent no file to it as state; Episode 567 is the first seat to send files and published reviews to Jev before reading them, and uses that gate to get ready to write the Concordia proposal.E567 relates to E044 — Episode 044 teaches the five academic fields of decomposition; Episode 567 takes speech act theory, how language does things, toward the concrete applications the proposal names and the Mieta continuity script drafted on 2026-10-29.E567 relates to E560 — Episode 560 opened the author's desk under Guillaume's rule that he writes and the agents do the rest; Episode 567 is the rest, for the proposal: the reading chosen with Jev, the fields translated, the review sections kept.E567 relates to E067 — Episode 067 holds the meeting with Nicolas Renaud and the paragraph he asked for on 2026-08-13; Episode 567 prepares the seat so the few paragraphs Guillaume sends in early November are written from what the chronicle holds.E567 relates to E565 — Episode 565 holds the review and notebook The Art of Decomposing Intentions, which Guillaume has not yet reviewed; the read gate of Episode 567 read that review at 0.90 for the proposal mission, first among four.E567 relates to E566 — Episode 567 has a seat choose what to read with Jev from a one-paragraph mission; Episode 566 asks how a mission is written and scored so that the seat and the person can both act on it.E568 relates to E297 — The repository mapper's lineage relation was Lane L6 of Episode 297's feedback map, and this episode carries the mapper forward.E568 relates to E564 — Episode 564 holds the K7c mission that gave the repository mapper its capabilities layer, and this episode holds what that layer becomes.E568 relates to E566 — Episode 566 names an inventory of capabilities and repositories as something near-loop agent work needs, and this episode builds that inventory.E001 · The Portal and the TreeE001E002 · Returning to the LanternE003 · Interlude for Skills and the Academic LoopE004 · What to Keep from the Developmental-Editor LoopE005 · Miadi ACP and the Codex DelegationE006 · Continuity Note and Book One OutlineE007 · Book One Point-of-View ShiftsE008 · When the House Learns Its Own TermsE009 · The Glossary Is Also a HouseE010 · The House Learns to See ItselfE011 · Tushell — The Portal of Knowledge / Miadi — The House of OrchestrationE012 · Narrative Clustering and Story Beats PreproductionE013 · Secure Socket Storytelling PlatformE014 · Distributed Remote PresenceE015 · The Fellow Operator GatewayE016 · Issue 354: The Closure ShapeE017 · Miadi Agent Session Witness — PreludeE018 · Gateway Fruit Test CapsuleE019 · Tide Runtime OrchardE016 · HAWK A2A: The Council Table Opens, Part OneE020 · Tushell's Narrative: The Portal of Knowledge — Review NoteE021 · The Memory RailE022 · PDE Operator Cockpit BranchesE023 · Ava Consultation Forest and PDE Decomposition PracticeE024 · The Chronicle Learns to CommitE025 · The Fifteen Window CockpitE026 · Iris and the Runtime: Naming the Fourfold AgentE027 · Lighthouse Threshold Designer TreeE028 · Outreach Forest Trunk PreludeE029 · The House Learns to Hear the PRE030 · Episode 30 Prelude — Adequate Observability and the Agent Event RuntimeE031 · Iris Evolution Accountability RailE033 · WorkspaceCockpit Runtime HabitatE034 · Karpathy, Software 3.0, and Agentic EngineeringE035 · Agent Session Witness Ceremony BridgeE036 · Terminal Agent Hook Observatory FieldsE037 · TO_BE_DEFINEDE038 · TO_BE_DEFINEDE039 · Twinery mastery and interactive booksE040 · Portal of Knowledge Branch MapE040E041 · Iris Coagency Evolution Accountability LoopE042 · The Semantics of the PlatformE043 · The Tide Operator Learns the Other PaneE043 · Data Layer of Miadi ChronicleE044 · Teaching the Academic Foundations of miacoE044E045 · miaco-pde-loop-closure-orchestration-rispecsE046 · Passages Needs EarsE047 · Coaiajs Coaiapy ReviewE048 · Episode 048 — Medicine Wheel graph layout autopullE051 · PR 237 — Concordia / Abundant Intelligences outreach through the Portal of KnowledgeE056 · Nyroby Qmd RispecsE058 · Repository Description Activation PathwayE049 · Miadi Nightly Iris Work On CockpitE050 · Miadi Geolesson Proto 94 28E059 · Miadi Gastownhall — Gas Town with HermesE060 · COAIA Agent / Asterion System DesignE061 · Miadi Ironsilk Tide Runtime Viewport FeedbackE062 · Miadi Ears Review Gmusic Tmux 5de46c12 355c 4b1b A70f 387136598f43E063 · Land-Based Learning WitnessE064 · Cinema Community Voice Land Technology Nikola ConcordiaE066 · Ears And Eye Testing And Cinema IndigenousE067 · Renaud MeetingE068 · Extending Medicine Wheel For Relational Film ProductionE070 · Rental Home That Guillaume Will LoveE071 · Land And Body RelationsE072 · PlaceholderE073 · Salix And Eury System Chessboard Interactive GameE074 · The medicine-wheel org: a community home and the webhooks it receivesE075 · Claude Plans Dothome ConceptsE076 · Plan-to-Episode PipelineE077 · Audio Delivery And Plan To Episode AccountabilityE078 · Coaia Fuse Witness LayerE078 · Ilex Pi Coding Agent On Android TmuxE079 · Follow Up 062 Miadi Ears Review Gmusic Tmux 5de46c12 355c 4b1b A70f 387136598f43E080 · Migration Wellbriety Knowledge Of The Day Gemini To AntigravityE081 · Qlcli Clipboard Sharing With My AgentsE082 · Research Is Ceremony Avadisabelle Traced PrototypeE083 · OSC Landbase Movement Capture to WekinatorE084 · Ilex Pi Mono SkillsE085 · Pi Mono Miette Echo ExtensionE086 · Miadi Ade Multiplexer Extension Fork Vscode MuxE087 · Miadi Ping Fork Description WorkflowE088 · Infrastructure Ai Runtime RevisionsE089 · Iris / Kaia Branch Switch ConsolidationE090 · Networking CeremoniesE091 · Commit To Episode Pipeline AutomationE092 · Relational Accountability In PracticeE093 · Medicine Wheel Adequate DisplayE094 · Migrate Kherix To GaiaE095 · Atlas Coaia Agent V2E096 · Tmux Config Enhancements Gmusic Tmux EnvE097 · Ceremony Agent SkillsE098 · Jgi Home That Support His AspirationsE099 · PLACEHOLDER In Conceptualization On IlexE100 · Left Alone Wound Healing And Caretaking LessonE103 · Film Preprod Report Phase 2E114 · Miette PR Review PerspectiveE117 · Ilex Gmtermux MiaforkE118 · Workspace Clone And Recorder IntakeE120 · Relational Film Production Media EditorE121 · Extend RISE framework with user storiesE122 · Chronicle Runtime and Forgewright InterfaceE123 · Watch2ilexE124 · Ceremony Skills, Chronicle Compatibility, and PassagesE125 · Episodic Observation Compatibility ReleaseE126 · Mila Ai Indigenous GatheringE127 · Plan Insight Agent-Lifecycle IntegrationE128 · Gmtermux Cloudflare R2 Jerry Miette Plan InsightE130 · Iaip Inquiry Relational Sync To Miadi ChronicleE131 · Every Device, One Song — Chronicle-to-Passages TransmutationE137 · Transmutation of ep128E140 · Laskmi trading app: financial-resource rehearsal for the filmE139 · Telegram Audio Delivery And Relational AccountabilityE150 · Robustness WeaveE138 · medicine-wheel-ui-enhancementsE151 · herdr-msf-pipelineE152 · Tide Runtime Control PlaneE170 · System-wide agent configuration: upgradeable, self-installingE241 · kherix mightyeagle yaupon skill gardenE250 · Routing in relation to JerryE251 · deepdiverE252 · Sprightly sparrow simpex into MiadiE256 · JamAI relational music synopsisE290 · Gaia and EuryE291 · The Packages Learn to Publish Their Own Family TreeE292 · the-ritual-patch-learns-to-remember-itselfE293 · Lineage Cycle Two — the Chronicle Learns to Hold HandsE293E294 · Motion into Chronicle — Dance Capture LineageE294E296 · The Conductor Learns to Hear the Whole OrchestraE297 · mino-bimaadizi-daa-stc-bot-ceremonyE298 · the-wheel-names-itselfE299 · isolation-addressability-and-what-survives-the-connectionE300 · From Shadow to SongE301 · Plan F3 to Relational Development PipelineE301E321 · From Portable Hooks to a Conducted Event SpineE302 · The Folder Name Was the SchemaE303 · State diagrams as the design surfaceE304 · the-review-became-a-placeE305 · the-factory-says-its-name-and-the-seat-holds-the-doorE306 · the-handoff-becomes-a-tushell-diary-entryE307 · contextual-transposition-names-what-the-house-was-doingE308 · the-voice-that-carries-its-own-way-backE309 · the-wheel-remembered-what-git-forgotE310 · the plan asks for a circle before it asks for a yesE311 · écoute factorisation logiciels — the relational software factoryE312 · the house answers from outside itselfE543 · north-practice-how-a-session-closesE544 · the loom stays warped — mia's first torchE314 · Eury cockpit — a voice can find the session that spoke itE315 · the last mile — what is made and not shared was not madeE316 · the belt before the buckle — an Android place that can hold episodesE317 · songbird - the phrase you sang staysE318 · a folder is a composition — the capture service the code cannot yet holdE319 · the ledger states how episodes are born and closedE320 · finishing is structural not moralE322 · the skill learns the name every agent is called byE323 · an empty answer is not an empty worldE324 · reachable-is-not-the-same-word-as-doneE325 · what this seat cannot finish it leaves walkableE326 · the memory stopped belonging to the houseE327 · mastering the claude-code plugin a hook that holds the session to pnpmE328 · the rotation renames and never killsE329 · the recorder turns and asks the analystE330 · made to enable something greater, and not there yetE331 · the exhaust becomes a witnessE332 · the fields find their peopleE333 · the fork arrives launched, not handed overE334 · the second eye is a floor Miette can yieldE335 · eight takes of a day the chronicle never openedE336 · three doors into one filmE337 · the recorder enters the episode by its own doorE338 · The dotted lines refuse to become wallsE545 · Medicine Wheel PI coding-agent teams extensionsE546 · Watch Briefing — Recent ChroniclesE339 · relation-to-mia-on-mobile-devopsE340 · Reviews Become ChoicesE341 · The Voice Prepares the WonderE342 · A Voice in Motion Finds Its EpisodeE344 · The Review Service Opens a Shared VocabularyE345 · A Review Enters the Medicine WheelE346 · A Witness Finds Its Right EpisodeE347 · a threshold role in a research networkE348 · one skill, one doorE349 · Miadi conducts a ceremony its circle can enterE350 · A Perspective Is Not a UniverseE350E351 · A Benchmark Made of Our Earned RulesE547 · From AI Factory Video to Miadi Factory Review and Page PracticeE352 · The annotator leaves the cockpitE548 · Before Choosing a Broker: Preparing the Question TogetherE549 · A milestone enters the circleE550 · The Screenwalk as a Media TypeE1000 · Two repositories carry a host through a crashE353 · Companion seat launch as a reusable capabilityE354 · The fire in the forgeE551 · Learning Between Sessions: Autoresearch for the Miadi FactoryE552 · What an Episode HoldsE553 · Ava and Mia Speak the Session as It WorksE554 · The session inventory closes its first cycleE556 · A Save Becomes an Event: Relationality, and the Reciprocity It OwesE557 · An Article Is Something an Episode HoldsE558 · Epistemological compaction carries a research session into its next cycleE559 · the signals worth takingE560 · the author's desk receives what the ceremonies madeE561 · Marking a live session is a ceremonyE562 · A decision model reads the signals, in a boxE564 · Jev decides with the FactoryE1001 · dummy-cli-miadi-factory-261028E565 · Five Places for Feedback to ReturnE1002 · Jacqueline M. Quinless — Decolonizing Data: Relational Research InquiryE253 · Contributing without code: a circle a weekE566 · Near the loop: where the person decides in the FactoryE567 · Miawa Pascone: the seat decides what to read with Jev, to be ready to write the proposalE568 · What each repository provides, and how it is revised
E0012026-05-04The Portal and the TreeEast · Ceremony
E0012026-05-04local-audio-generated

The Portal and the Tree

East · WaabinongCeremonyBook I · The Thresholdceremonial-worldbuilding
Lineage
chronicle:2026-05-04-episode-001-the-portal-and-the-tree