OKF Studio v0.9.1

A patch release with one fix.

A bundle that links back up opens again

A folder index usually ends with a tail back to where it came from:

# See also

* [All groups](../index.md)

A link to a reserved index.md is a link to that directory, so the parent lists the child and the child links to the parent. The sidebar's index tree followed that in one direction only and never stopped, until it ran out of stack and the window went blank. A bundle written this way could not be opened, and if it was the bundle open when Studio last closed, the app came up blank on launch.

A row for a folder that is already above it in the tree now stops there. It keeps its name and still opens that folder, it just does not unfold a second copy of the folder you are standing in.

Upgrading

Nothing to do. No change to the bundle format, to retrieval, or to agent behaviour.

OKF Studio v0.9.0

The reader's Aa control has owned reading comfort since it shipped: size, measure, leading, font, reading aids. This release gives it a second half, reading pace. Two modes, one engine, and neither starts on its own.

A minor, not a patch. A new mode with its own keyboard map, a reader header that no longer looks the way it did, and a set of deliberate refusals a reader should meet in release notes rather than mid-sentence.

Speed reading

Focus clears the screen and shows one word at a time. Each word is positioned so the letter your eye recognizes it by, slightly left of centre and further right the longer the word, sits at the same horizontal position in every frame. Removing the jumps between words is the whole mechanism, so the word itself must never drift: a story measures the pivot's centre across sixty frames and several sentence boundaries and asserts it does not move.

Guided leaves the concept where it is and sweeps a marker through the real text.

Start either from the new Speed read action in the reader header, or press S. Inside the player, space plays and pauses, the arrows move, + and - change pace, and Esc leaves. Closing the focus player scrolls the prose to the block you reached, so the mode hands back a position rather than a scroll to the top.

Rereading is inside the mode, not outside it

Serial presentation removes a real cost, and it removes something you need along with it. A large share of eye movements in ordinary reading go backwards, and most of those regressions exist to repair a sentence parsed wrongly the first time. Reviews of the evidence (Rayner et al., So Much to Read, So Little Time) attribute the measured comprehension deficit of one-word-at-a-time presentation to exactly that: a forward-only player takes the repair mechanism away with the wasted travel.

Studio does not promise the deficit away. It puts the repair back:

• The sentence you are on stays printed beneath the frame, whole and legible.
• The arrows step a word (left/right) and a sentence (up/down), and each pauses the player. A deliberate move backwards should not be racing a clock.
• Resuming rewinds a few words rather than restarting where your attention lapsed.

What the player refuses to do

Shred a block that means nothing as words. A table, a fenced code block, an equation, or a diagram makes the player stop, render the block as itself, and wait. Sentence jumps stop there too. The stop is fully keyboard-operable, because it is the point where the player hands control back: focus moves to Continue reading, and the block is a named focusable scroll region, so a long code fence can be read to the bottom with the arrows.

Hide what speed costs. The rate defaults to 300 wpm and ranges from 100 to 800. Comprehension generally holds through roughly 400 to 600 wpm and falls away above that band, so past 500 the player says so in a quiet line rather than letting the number climb silently. The rate stays yours to choose.

Claim the word-start cue makes you faster. The optional emphasis on each word's opening letters ships off and makes no speed claim. A 2024 replication and a 2,000-reader field test found no reading-speed or comprehension effect for typical readers; the signal is more consistent among ADHD and dyslexic readers, and some people simply find it easier to look at, so it is offered as comfort and labelled as comfort.

Keep running. Auto-advancing text is auto-updating content under WCAG 2.2.2, so no pacing mode is persisted (the rate, frame size, and cue are), opening another concept ends the session, pause is always one press away, Reduce motion opens the player paused and never animates between frames, and the ticking frame is hidden from assistive technology while the prose itself never is.

The reader header is regrouped

Speed read and Aa now sit together as reading controls, Work with agent stays in view, and Move and Retire move into a More concept actions overflow at the right edge. Five peer buttons in one row is past the point where a toolbar is scanned rather than read. An overflow costs discoverability, which is what decided which two: both are infrequent maintenance that open a dialog rather than acting on click. Cancelling either still returns focus to the control that opened it.

Also

• Agent turns stream in smoothly instead of arriving in blocks.
• Transcript text can be selected and copied.
• Fixes: the pace sliders were 16px hit targets, under the 24px floor; two shipped strings carried em dashes.

Upgrading

Nothing to migrate. No change to the bundle format, to retrieval, or to ACP wire behaviour. Speed reading does nothing until you start it, and it never arms itself for the next concept.

Installers for Windows (.msi, .exe) and Linux (.deb, .AppImage) are attached below, each with its update signature. There is no macOS build; the release matrix has never included one.

OKF Studio v0.8.0

Attested computations become usable rather than merely parsed, and retrieval starts preferring knowledge that has been reviewed and is still current.

A minor, not a patch. This release visibly reorders retrieval results and moves the exported retrieval manifest to schemaVersion 2, alongside five new features. A patch number would have understated all three.

Attested computations

An Attested Computation exists so a reported number can be traced to the query a business actually sanctions, rather than to an agent writing plausible SQL. That check now runs.

• The computation is visible. One stored in a file renders in the reading column under the same # Computation heading an inline one uses, so a reader cannot tell which form the producer chose.
• A run can be checked. The computation panel gains a Check a run… dialog: paste the receipt a run returned and Studio compares it against the bundle's copy. Required evidence fills in as you paste.
• An agent's claim is gated. A turn that ends with an okf-receipt fence is checked before its number is taken at face value, and the verdict renders beside the figure. The agent supplies only its receipt — what it is checked against is read from the bundle, because an agent that could supply both sides could always make them agree.

What Studio does not claim. It checks provenance: that what ran is the sanctioned computation with its parameters bound. It cannot check fidelity — re-reading the authoritative result by job id — because only the executor's runtime can, and it says so rather than implying a run was fully verified. Studio never executes a computation, an executor, or an attester.

Retrieval prefers reviewed, current knowledge

Retrieval reads OKF v0.2's status, stale_after, verified and sources, and marks rather than excludes.

A deprecated concept is ranked below current knowledge and carries a caveat saying so. Searching it by name still returns it first — OKF keeps deprecated concepts for links and history, and a retriever that hid them would break exactly what the status preserves. Human review and declared sources lift a concept over an otherwise identical peer; trust is a bonus and never a penalty, so bundles predating v0.2 are not punished for the spec moving.

Also

• The ACP SDK moves to 2.0. This is a Rust API change, not a wire change — nothing an agent negotiates is affected.
• A worked Attested Computation ships in Studio's own docs bundle, with its example receipt pinned by a test so it cannot rot.
• Fixes: retrieval treated a concept dated only by generated.at as undated; vitest run with no project filter ran nothing at all.

Upgrading

• Retrieval results will reorder for bundles declaring v0.2 lifecycle fields. Nothing is dropped; demoted items carry a caveat explaining why.
• The exported retrieval manifest is now schemaVersion 2. It gained fields; anything reading only v1 fields is unaffected.
• No change to ACP wire behaviour.

Installers for Windows (.msi, .exe) and Linux (.deb, .AppImage) are attached below, each with its update signature.

There is no macOS build: the release matrix has never included one. An earlier draft of these notes claimed otherwise, which was wrong.

OKF Studio v0.7.0

OKF Studio 0.7.0 supports OKF v0.2, the spec revision Google published on top of v0.1.

v0.1 answered "what does an agent need to know?" v0.2 adds "should the agent believe it, and is it still true?" Provenance, trust, and freshness stop being prose and become fields a consumer can compute over. Studio now reads all of it.

Your existing bundles keep working. v0.2 has two breaking changes and both keep a fallback, so a v0.1 bundle opens exactly as before — and validation stays quiet about fields it never declared rather than nagging you to migrate.

Whether to believe a concept

• The Concept Reader now shows a trust tier above the producer metadata: unverified, machine-confirmed, or human-reviewed. It is derived from who actually confirmed the concept, so a bundle cannot simply assert that it is trustworthy.
• Who wrote it and who confirmed it are separate. A concept generated by an agent and confirmed by nobody reads as unverified, however complete its provenance. That distinction is the point of v0.2, and collapsing it would hide the only signal separating reviewed knowledge from generated knowledge.
• Sources carry credibility signals — who produced a source, how often it was used over what window, and when the source itself last changed. A usage count is always shown with its period, because 5,000 uses over a week and over five years mean opposite things.

Whether it is still true

• A concept past its stale_after date says so, and a deprecated one says that instead — they are different claims, so they read differently.
• Knowledge Health gains findings for a concept past its staleness date, and for a current concept that links to deprecated knowledge, which is how a reader arrives at retired material without being told.
• Freshness now reads v0.2's generated.at as well as v0.1's timestamp, so a migrated bundle is no longer reported as undated for having adopted the newer field.

Attested computations

v0.2 adds a concept type for a sanctioned computation, so a consumer can check that a reported number came from the blessed query rather than from an agent writing plausible SQL. Studio reads and validates these contracts, and reports one that cannot gate anything — no runtime, no receipt fields, no attester.

Running an attestation is not wired up yet. Studio can compare a run's executed query against the stored computation without executing anything, and that check is built and tested, but nothing yet lets you invoke it. Tracked in #28.

For agents

The OKF methods Studio serves to agents are updated to v0.2, including two new ones: attest for defining a computation an agent may run but not write, and migrate for moving a bundle from v0.1.

Fixes

• A sidecar's digest check reported tampering on an untouched file on Windows, because the checkout rewrote the file's line endings and changed the bytes the digest covers.
• Component status stopped rendering in design-system bundles.
• Buttons that look like links rendered unstyled in the sidebar and type filters in some views.
• A source link in the reader opened inside the app window instead of your browser.

Notes

Screenshots on the download page still show 0.5.0's appearance and will be refreshed separately.

OKF Studio v0.6.0

OKF Studio 0.6.0 is a presentation release. It changes how the app looks and how quickly you can find things in it, rather than what a bundle can hold. Light and dark are rebuilt from the ground up, concept colors carry equal weight for the first time, code and diagrams belong to the app instead of to their renderers, and the two surfaces you reach for by keyboard have been reworked.

Light and dark, rebuilt

• Surfaces now follow one depth order — recessed canvas, app frame, window furniture, docked panes, and floating layers — so a dialog reads as a layer above the panel it covers and the title bar reads apart from the content it holds.
• Hover works correctly in dark. Every hover fill used the recessed surface, which is right on light and backwards on dark: a hovered control went darker than the pane behind it and read as a hole punched in the surface rather than a control lighting up. That affected 63 rules.
• Text selection, the caret, and the native controls the webview draws itself now follow the theme instead of a fixed platform blue.
• Every text-carrying color clears WCAG AA on every surface, and on the state fills stacked on them. That last part was the gap: the palette had only ever been checked against resting surfaces, and a highlighted row is a surface too.

Concept colors carry equal weight

• Type colors are generated in OKLab rather than HSL. HSL's lightness is not perceptual, so ten concept types spanned 4.3:1 to 11.8:1 against the dark canvas — a few colors shouted and the rest turned to mud. Holding perceptual lightness fixed collapses that spread below 1.0, so a legend reads as one family.

Code and diagrams belong to the app

• Code blocks sit on the app's own surface. A syntax theme ships a background of its own, and it was overriding ours: a light code block was white on white, and a dark one was lighter than the reader pane it sat in.
• The syntax palette was chosen by measuring against that surface — One Dark Pro on dark, github-light-default on light, both with comments lifted over the readability threshold.
• Mermaid diagrams are drawn from the app's own color roles instead of Mermaid's stock palettes.

Finding things

• The global search launcher opens with no folder open. Ctrl/Cmd + K on the empty state used to do nothing at all.
• Opening it no longer lists every command. Typing ranks concepts and commands against each other by how well each matches, and the matched characters are marked, so an abbreviation finding its concept reads as a hit rather than a guess.
• Search now covers descriptions and tags, result groups carry counts, each result shows its concept type, and a query that finds nothing says what was searched and what you can still do.
• Result snippets quote prose instead of raw markdown.

The keyboard-shortcuts sheet

• Four bindings that work in the app were missing from it, and one chord rendered as garbage.
• The whole keymap now fits without scrolling, chords line up, and a filter narrows forty bindings to the one you want.

Reading and navigation

• The reader's markdown body reads as prose rather than boxed data.
• Sidebar metadata, states, and the glyph column line up.
• Both typefaces ship with the app, so the chrome renders identically on Windows, Linux, and macOS.
• New releases are badged quietly on the Settings icon. Installing stays an explicit action, and the check can be turned off.

Notes

Screenshots on the download page still show 0.5.0's appearance and will be refreshed separately.

OKF Studio v0.5.0

OKF Studio 0.5.0 makes a bundle easier to use as a living workspace. It helps you pick up where you left off, find knowledge that needs attention, understand where information came from, maintain connected concepts safely, and prepare a focused copy for someone else.

Start with the work

• Bundle Home now brings together recent bundle activity, concepts from your current session, knowledge-health findings, and uncommitted Git work.
• Bundle identity, format, concept count, conformance, metadata, ignore rules, and advisory profiles now live in a persistent Bundle details dialog.
• External sources, relationship exchange, and interoperability diagnostics have a dedicated, scrollable Bundle Connections workspace. Opening Home no longer waits for those reports.

Maintain knowledge with context

• Move or retire a concept only after reviewing affected links, indexes, relationships, and log entries. Changes still pass through staged review, validation, and explicit Apply.
• Inspect typed relationships and multi-hop lineage to understand dependencies and downstream impact.
• Reliability, lifecycle, and evidence views show confidence, review state, replacement signals, and source provenance without presenting advisory metadata as fact.
• Knowledge Health can identify missing, stale, changed, or conflicting evidence and take you directly to the affected concept.

Share a focused bundle

• Create shareable bundle is available beside the bundle name from every topic and through the command launcher.
• Choose the knowledge to include, review linked additions and omissions, then save a separate validated copy. The source bundle is never edited.
• Optional audience, sensitivity, ignore-rule, and exact-redaction safeguards remain visible in the review instead of making the basic sharing task harder.

Work across OKF producers

• The Compatibility Clinic distinguishes OKF conformance from portability advice and producer-specific metadata. Safe link normalizations can be reviewed before they are staged.
• Local advisory profiles can describe additional fields, relationship types, access hints, evidence, and lifecycle conventions while remaining separate from core OKF validation.
• Producer-defined metadata is preserved and inspectable. Link parsing now handles encoded paths, reference links, balanced parentheses, autolinks, and escaped punctuation consistently across the graph and reader.
• Optional experiments cover explicit external bundle sources, multilingual variants, portable JSON-LD relationships, and contained sidecar resources. Network access and exports still begin only from a named user action.

Clearer structure and reading

• Authored index sections now drive the sidebar, treemap, sunburst, and circle-packing views. The visual hierarchy no longer repeats folder names as false levels, and the All view still includes every concept.
• Markdown tables keep useful column proportions and scroll within the reader when they cannot fit, instead of collapsing labels into narrow stacks.

Downloads

The release workflow builds and attaches:

• Windows MSI and NSIS installers
• Ubuntu/Linux DEB package and AppImage

The operating system may show an unverified publisher prompt because the installers are not OS code-signed.

Full changelog: v0.4.2...v0.5.0

OKF Studio v0.4.2

OKF Studio 0.4.2 fixes a Linux issue that caused the app to freeze when opening folder pickers.

Fixed

• Open a folder, Try another folder, and the destination picker used during bundle creation now open without blocking the WebKitGTK main thread.
• The affected Tauri commands now run asynchronously, matching the other dialog-opening commands.

Special thanks to @WhiteKr for identifying the cause and contributing the fix in #9.

Downloads

The release workflow builds and attaches:

• Windows MSI and NSIS installers
• Ubuntu/Linux DEB package and AppImage

The operating system may show an unverified publisher prompt because the installers are not OS code-signed.

Full changelog: v0.4.1...v0.4.2

OKF Studio v0.4.1

OKF Studio 0.4.1 fixes the Windows console-window regression introduced by Integrated Git in 0.4.0.

Fixed

• Repository discovery, live refresh, status, history, diffs, staging, commits, and explicit remote actions no longer create visible console windows on Windows.
• Every production Git invocation now uses one Windows-safe process constructor with CREATE_NO_WINDOW, including the availability check that runs before repository inspection.
• Git behavior, repository permissions, watcher scope, and remote-action boundaries are unchanged.

Windows users on 0.4.0 should install this update.

Downloads

The release workflow builds and attaches:

• Windows MSI and NSIS installers
• Ubuntu/Linux DEB package and AppImage

The operating system may show an unverified publisher prompt because the installers are not OS code-signed.

Full changelog: v0.4.0...v0.4.1

OKF Studio v0.4.0

OKF Studio 0.4.0 makes agent and repository work first-class parts of the OKF workspace. Agents now have explicit methods for understanding and improving knowledge, retrieval decisions can be inspected without cluttering the conversation, and the repository checkpoint loop stays beside the bundle.

OKF-native agent work

• A versioned capability pack gives generic chat and guided tasks the same OKF methods for inspecting, retrieving, creating, enriching, auditing, repairing, researching, assessing change impact, migrating, authoring, and revising bundles.
• Structured workspaces keep plans, reports, source inventories, research briefs, impact maps, migration plans, and writing revisions active beside the conversation.
• Artifact verification binds structured output to the current bundle revision, declared sources, and closed schemas before Studio treats it as trusted work.
• The writing path now protects facts, numbers, qualifiers, citations, links, formulas, and code while still improving structure and prose. Proposed edits continue through staged diffs, validation, review, and explicit Apply.
• Workspace memory, local routines, previously granted bundle sets, and one-shot MCP handoff make repeated OKF work useful without creating a Studio account or silently widening access.

Retrieval you can inspect

• Deterministic local retrieval combines exact, lexical, graph, and compiled-context routes with bounded context budgets and stable evidence receipts.
• Answers carry a compact provenance summary. Detailed evidence, route decisions, omitted candidates, conflicts, freshness, and provider use stay behind Inspect instead of bloating the transcript.
• Retrieval Lab can compare routes and export a diagnostic when evidence quality needs investigation.
• Conflict, temporal, authority, and incomplete-evidence states use plain user-facing explanations. Studio reports unavailable dense retrieval or reranking honestly instead of implying that a provider ran.
• Frozen-corpus and scale benchmarks separate retrieval quality from answer quality and keep route behavior deterministic across runs.

Git beside the bundle

• The new Git panel provides Changes and History, two-dimensional staged state, bounded diffs, stage and unstage actions, staged or tracked commits, recent history, and revision-bound soft undo.
• Fetch, fast-forward Pull, and Push run only from their named actions. Opening a bundle or watching repository files never contacts a remote.
• Bundles inside repository subfolders work without reopening the project. Studio asks once for native confirmation of the exact enclosing repository and keeps the active bundle open.
• Conflicts remain visible and recoverable without pretending Studio is a merge editor.

A calmer workspace

• Settings is now a searchable, categorized workspace that scales beyond one crowded dialog.
• Conversation events stay in chronological order, completed tool activity collapses, and live plans keep a stable readable area instead of being squeezed by transcript growth.
• Thread restoration, session choices, source context, evidence inspection, and structured work now retain their configuration and recovery actions more consistently across reopenings.
• Narrow-panel and error states are covered as first-class Storybook interactions and accessibility journeys.

Safety and upgrades

• Folder opening remains read-only. Network activity, repository remotes, agent connections, and writes still require explicit user actions.
• Cross-bundle retrieval adds evidence only; the active bundle remains the sole write destination.
• Existing OKF Studio 0.3 installations upgrade in place with the same application identity, settings, recent bundles, agent profiles, and updater endpoint.

Downloads

The release workflow builds and attaches:

• Windows MSI and NSIS installers
• Ubuntu/Linux DEB package and AppImage

The operating system may show an unverified publisher prompt because the installers are not OS code-signed.

Full changelog: v0.3.0...v0.4.0

OKF Studio v0.3.0

OKF Studio v0.3.0 turns the read-only viewer into a local-first workspace for creating, curating, and querying OKF bundles with agents.

Agent workspace

• Connect external ACP agents or use the built-in Studio Agent.
• Run parallel bundle-scoped threads with streamed responses, plans, tool activity, session restoration, and agent-advertised controls.
• Attach explicit bundle context and local sources without exposing unrestricted filesystem access.

Knowledge work

• Create conformant bundles from mixed sources.
• Stage agent changes for review, validate the proposed bundle, and apply the exact accepted revision.
• Navigate long conversations with stable transcript and live-work surfaces.

Safety and upgrades

• Restricted offline execution is available through Bubblewrap on Linux and AppContainer on Windows.
• Existing OKF Viewer installations upgrade in place. Settings, recent bundles, agent profiles, repository links, and updater identity remain compatible.
• Reopen each retained local folder once after upgrading so Studio can establish its Rust-owned folder grant.

Downloads

• Windows: MSI and NSIS installers
• Ubuntu/Linux: DEB package and AppImage

The release workflow builds and attaches the installers. The operating system may show an unverified publisher prompt because the installers are not OS code-signed.