What’s new
What has changed in The ikigai Architecture, most recent first: the date, what was added or changed, and the pages to read for it. Smaller upkeep (moving to a newer release when nothing a reader does changes, a corrected link, a typo) is not listed.
2026-10
-
2026-10-30: The first section of “Resolve the viewer’s authority once” is now “Capabilities: a resource that only narrows”, in the same form as the sections after it.
-
2026-10-28: “One module, a boundary and a surface” has a new section, “Bodies larger than memory”: how the HTTP door of ikigai-cli 0.2.2 frames a streamed answer (Content-Length or chunked), serves byte ranges (206, 416, If-Range), spills uploads to disk under its 408 and 413 bounds, and why every ETag changed once.
-
2026-10-27: The book now builds against ikigai-core 0.2, the streams release. In “Spaces that wrap spaces”, the trace of the state board no longer ends with
defaulted=as: the REPL’s plaintraceleaves the kernel’s defaulted inputs out now, andtrace --defaultsshows them. In “The manifold, and the UI that falls out of it”, the ledger’sdoctoraction is listed in the place the kernel now lists it, under both capabilities.Pages: Spaces that wrap spaces, The manifold, and the UI that falls out of it
-
2026-10-27: “The other books” now links Running ikigai, the operator’s side of the door and capabilities this book describes, and says the library lists all five books.
Pages: The other books
-
2026-10-26: In “Spaces that wrap spaces”, “Compare with” is now one list, above Before and After, instead of a second row of a dozen buttons under the tabs that was hard to tell from them on a phone. It offers the stages before the open tab, a stage your buttons made among them, and starts at the stage just before; opening a tab puts it back there. When a tab’s step has moved nothing yet, After now says so plainly: the stage your kernel is still at, and that the tab’s step has moved nothing yet.
Pages: Spaces that wrap spaces
-
2026-10-26: The stages of “Spaces that wrap spaces” now hold still: below the tabs, the open stage’s picture sits beside the stage before it, Before and After, with what changed from one to the other in words. “Compare with” puts any earlier stage in Before, and a stage a button makes is shown beside the stage the harness was at before the press. Each picture is the one your kernel drew if that tab’s step ran, or the chapter’s own, said so, in a dashed frame. On a phone the two stack; long answers scroll sideways instead of wrapping. The arrow keys on the tabs now move between tabs only; they used to open the next or previous chapter as well.
Pages: Spaces that wrap spaces
-
2026-10-25: The stages of “Spaces that wrap spaces” now work as one box: each tab holds its step and its answers, scrolling in place, and one picture of the harness sits right below the tabs. Before you run a tab it is the harness as it is now; run it, or press a button, and watch the picture change. Switching back to a tab shows what its step drew, from the cache.
Pages: Spaces that wrap spaces
-
2026-10-25: In “Spaces that wrap spaces”, the picture now appears right under the button or cell you just pressed, drawn by the harness after that step, with what changed. A row of stage buttons above it shows any stage’s picture in the same place, so you can compare two states without scrolling to the tabs.
Pages: Spaces that wrap spaces
-
2026-10-25: “Spaces that wrap spaces” now drives Failover and the bulkhead too, in six more stages. Call a service whose primary is slow and watch the failover move to its backup, mend it and watch the route move back; then start five calls at once and watch a two-slot bulkhead run two and park three, and drain them as you move the harness clock, each call answering at its true time. Every stage’s picture now marks what changed since the stage before, and the line above the tabs keeps the failover’s route and the bulkhead in view as well as the circuit.
Pages: Spaces that wrap spaces
-
2026-10-24: “Spaces that wrap spaces” now walks through the resilience harness in numbered stages. Each tab holds a step to run beside what it did: the breaker’s state as the harness drew it at that stage, in the colors of the book’s theme, what changed since the stage before (marked, and said in words), and the harness time. Your own button presses add stages of your own after the chapter’s, so you can flip between any two states, and a line above the tabs keeps the upstream’s mode, the circuit and the harness time in view. The chapter also explains why showing a stage again costs nothing: its picture is cached until a governor’s state changes.
Pages: Spaces that wrap spaces
-
2026-10-24: “Spaces that wrap spaces” now runs in the page: a resilience harness puts the real throttle governors around a stub dependency you control. Set it failing and watch the circuit breaker trip, wait out the cooldown and watch the probe close it, watch a retry spend the run’s budget, and watch a timeout fire and trip the breaker too, with the arrangement and the breaker’s state drawn live beside buttons that drive it. Time is the harness’s own clock, so every run answers what the chapter shows.
Pages: Spaces that wrap spaces
-
2026-10-23: A new book. It teaches the ikigai architecture as one substrate read two ways: the patterns a person operates are the patterns that authorize and confine them. An introduction sets out resource-oriented computing and how it generalizes the Web, then six parts carry one worked resource, a ledger item, through the capability spine and the manifold-driven UI, the door, the overlay chain, the economics of golden threads and caching, and presence and the audit axis. The capability and economics chapters run in the page: you narrow your own authority and watch an action leave the manifold, and you cut a golden thread and watch a view recompute.
Pages: Introduction, One mechanism, read two ways, Resolve the viewer’s authority once, The manifold, and the UI that falls out of it, Golden threads and the cost of a read