A plain-language record of what changed in each release.
v2.4.0 · 2026-09-05
The durability frame
A standing explainer at /frame: customer, product and business model, what each one is on its own, and what each overlap actually decides.
Added /frame: the three-circle durability diagram, with each circle named and subtitled, every pairwise overlap labelled with what it settles, and a durable business sitting only in the three-way intersection.
Classified frame as a living-latest surface before its first publish, so later revisions of the drawing ship without cutting a proposal release.
Gave the page the standard navigation back to the proposal, research, evidence rooms and weekly; left it out of those pages navigation and marked it noindex, because it is a page to be linked to rather than a section of the proposal.
Changed no proposal copy, figures, terms, or decision logic.
A recurring client report at /weekly: what the week did, what it found, what we changed our mind about, what we need decided, and what it cost.
Added /weekly: one edition per week, published alongside each Friday call, starting with week zero before any hour is billed.
Every finding on the page carries its status — verified, insider, reported, inference, hypothesis, or killed — so no claim travels without what it rests on.
Each edition prints what we changed our mind about, next to the findings those corrections revise.
Each edition asks for what it needs by name and by date, and shows the hours and money spent against the stated ceiling, computed from the logged hours rather than typed.
Week zero carries the four decisions the 31 July call ran out of time to reach: the contracting entity and signer, the shape of the three-month commitment, the four named counterparts, and the cost ceiling.
Added Weekly to the navigation on every page, so the proposal, research and evidence rooms all reach it; below 640px the navigation drops the current-page label so the theme control still fits.
The infrastructure brief no longer places Lee's name beneath AI-written words or describes him as their author without exact-wording approval.
Replaced the unapproved Linas signature with 'Talos (5.6 Sol) on behalf of Lee Matulis' in the direct note, visible attribution, clipboard copy and transparency statement.
Changed structured authorship metadata to identify Talos as the writer and Lee as the commissioning principal, with explicit false values for exact-wording approval and personal-signature authorization.
Added a machine-readable provenance rule: commissioning a draft is not approval of its wording, and a human signature requires explicit approval of those exact words.
Added deterministic tests that reject a Linas signature or any claim that the brief was prepared by Linas Matulis.
The infrastructure review now identifies the exact Codex model and exposes its decision, provenance, evidence states, migration gates, security boundary, and sources as structured data for Ro's Claude workflow.
Changed every prepared-with-Codex attribution to name OpenAI Codex, the human-readable GPT-5.6 Sol model, and the gpt-5.6-sol machine identifier where technical detail is appropriate.
Added interoperable TechArticle JSON-LD with authorship, abstract, audience, keywords, citations, and explicit AI credit.
Added an embedded kairos-technical-brief/v1 JSON decision record covering facts, inference, non-claims, architecture options, migration acceptance tests, security boundaries, and primary source URLs.
Added a visible machine record plus stable document, section, evidence-status, decision-status, and sensitive-data markers so assistants can recover the brief's logic without inferring it from the visual composition.
A shareable, transparent technical review of Ro's proposed Synology Drive workflow and the self-hosted Git architecture Kairos can adopt without losing its collaboration contract.
Added /infrastructure: a full factual record, Drive-versus-Git comparison, failure mechanism, migration contract, security boundary, primary sources, and a direct note to Ro.
Recommended a real self-hosted Git remote on Ro's server — Forgejo, Gitea, or Synology Git Server — while retaining Synology Drive for ordinary shared files and supported backup exports.
Excluded usernames, passwords, the server address, and the source screenshot; no Synology login or migration was attempted.
Added a dedicated 1200 by 630 sharing image and complete Open Graph and X card metadata for the public route.
The week-one line 'Burn, defined the same way twice' was the tightest phrase on the slide and the least self-explaining. It now carries its own gloss, stating the principle rather than assuming the reader supplies it.
'Defined the same way twice' now explains itself on hover, tap or keyboard focus: one definition, held fixed everywhere the number appears — gross or net of investment income, one entity or the group, this month or last.
The gloss says why it matters — two numbers on two definitions cannot be compared, added or trended — and states it as a measurement principle, not as a comment on anyone's bookkeeping.
Sits alongside the existing 'burn' gloss on the same line: one defines the term, the other defines the discipline.
Changed no proposal copy, figures, terms, or decision logic.
The four kickoff roles — executive sponsor, data owner, implementer, budget owner — now carry the same hover glosses every other term in the deck already had, so nobody has to guess what is being asked of them.
Each of the four names now explains itself on hover, tap, or keyboard focus, on the proposal page and on both deck slides where the names appear.
The glosses say what each role must be able to do — decide, hand over the numbers, make a change happen, approve a spend — rather than restating the job title.
Uses the deck's existing glossary component, so the wording and behaviour match every other glossed term.
Changed no proposal copy, figures, terms, or decision logic.
Dividing lines in the Evidence rooms were rendering at full text brightness instead of the intended faint rule, because they referenced two colour names that were never defined.
Nine borders and panel fills in the Evidence rooms referenced undefined colour names, so the browser silently discarded the instruction and fell back to the text colour.
They now use the shared kit's line colours, which also means they finally respond to the light and dark themes.
Added a check that refuses to publish any page referencing a colour name that is defined nowhere, so this class of silent fault cannot ship again.
Changed no proposal copy, figures, terms, or decision logic.
The SKU explanation now opens with what the letters stand for, so an abbreviation never has to be taken on trust.
SKU now reads 'stock keeping unit' before the explanation of what one is.
Swept the remaining abbreviations in the deck: P&L was already spelled out, and VPN, MN and AI are left as they are because they are the reader's own everyday vocabulary.
The growth option now names both of its routes — building a capability in-house, and acquiring a team that already runs it — which the earlier wording had merged into a single word.
'grow' now states both routes and the test between them: short of time argues for buying, short of capability argues for building.
'partner' now says plainly that no ownership changes hands, so it cannot be read as an acquisition.
Acquisition stays a route to growth rather than a separate board option; whether it could be funded is an open question, not an assumption.
A presented version of the proposal at /deck, adding a concrete first-thirty-days plan, the engagement's cost ceiling, and the decisions needed to start.
Added /deck: the proposal as seventeen slides, so it can be presented rather than scrolled.
Set out how the work actually starts, day one to day thirty: what Mysterium prepares beforehand, the economic perimeter in the first week, the board choice at day ten, one reversible proof by day thirty, and the gate.
Stated the engagement's own cost ceiling: €50 per hour per person, up to 200 combined hours, a €10,000 monthly maximum, and roughly €30,900 across the proposed three-month commitment.
Named what Mysterium keeps if it stops at the first gate, and the boundaries the first month will not cross.
Listed the four decisions required to begin: contracting entity and signer, how the three-month commitment coexists with the monthly gate, the four named counterparts, and the start date.
The deck is a companion to the proposal, not a replacement; index, research, and evidence rooms are unchanged.
Archive navigation repair. The original files used canonical-root links, which escaped this version path after preservation. A transparent delivery adapter now keeps every V1 navigation link inside V1. The stored payload and its hashes remain unchanged. Inspect the compatibility receipt.