WIKI³ STUDIO — Shared Context Infrastructure

WIKI³ STUDIOShared Context Infrastructure

One repository record. Three ways to act on it.

Wiki³ Studio macOS prototype showing the Wiki³ project in its developer lens with decisions, architecture, and operating rules — Real macOS interface · verified unsigned local prototype

01 / System

The record stays put. Every surface is derived.

The architecture begins with plain files and ends with focused read surfaces. Validation, freshness, and behavior checks sit between them.

SourceRepository MarkdownTyped pages beside code
BuildTyped validation + indexClosed kinds, links, search
CheckAnchor + executable-assertion checksFreshness and selected behavior
ReadBIZ / DEV / BOT viewsOne record, three jobs
DeliverNative app / static archive / MCP contextHuman and machine surfaces

02 / Lenses

The facts do not fork with the audience.

Each lens answers a different job from the same canonical record. Vocabulary and hierarchy change; identity, relationships, and evidence do not.

BIZ

Decide

Outcome, ownership, risk, affected people, and the evidence required for the next move.

DEV

Trace

Architecture, interfaces, dependencies, source anchors, failure modes, and verification points.

BOT

Execute safely

Inputs, hard rules, protected boundaries, stop conditions, exact identifiers, and completion proof.

One canonical record. Three reading contracts.

The genius is not three copies of the truth.

Wiki³ changes the reading contract around one record. Each audience gets the hierarchy it needs, while identity, relationships, and evidence stay anchored to the same source. That cuts the quiet semantic drift created when business briefs, engineering docs, and agent prompts are maintained separately.

BIZ · Decide

See the decision, not the plumbing.

BIZ foregrounds why the record matters, the decisions it protects, and the operating ideas shaping the next move.

DEV · Trace

Follow every claim back to the machinery.

DEV foregrounds architecture, interfaces, dependencies, source anchors, failure modes, and verification. The real DEV surface appears in the System chapter above.

BOT · Execute safely

Turn context into bounded action.

BOT retrieves governing decisions and exact dependencies, then must stop on hard-rule conflicts or stale evidence and report the blocker exactly.

Wiki³ native macOS prototype showing the Wiki³ system record with the BIZ lens active and decision, architecture, and operating-rule summaries — **Same record · BIZ lens active**Open full-size BIZ view

Wiki³ native macOS prototype showing the Wiki³ system record with the BOT lens active and a bounded retrieval and stop sequence — **Same record · BOT lens active**Open full-size BOT view

Same identity. Same relationships. Same evidence. Different job.

03 / Freshness

A matching hash is useful. It is not the truth.

Wiki³ separates two questions that an earlier prototype collapsed into one.

Anchor

Did the bound code region change?

Path, symbol, and sealed hash resolve to fresh, drifted, broken, or unknown. This makes stale bindings visible.

Executable assertion

Does this selected behavior still hold?

A reviewed command and expected result can fail even when no anchored region changed.

Anchor freshness is not truth verification. Anchors detect movement under a claim; executable assertions test selected behavior. Neither proves completeness.

04 / Bundles

Spend the context budget on the costliest mistakes first.

An agent states its intended change and touched paths. Retrieval can rank useful background, but it cannot quietly bargain away the rules.

Input

Intent + exact touched paths

Rank

IDs + anchors + language + graph neighbours

Rules are charged before optional knowledge.

PINNED · MUST / NEVER

Applicable hard rules enter before ranked prose, even when their cost exceeds the requested budget.

RANKED · OPTIONAL CONTEXT

Relevant decisions, concepts, architecture, and status follow until the whole-artifact budget is spent.

Every omission is declared. The manifest names what was dropped, records shortfall, and caps the list with a remaining count. “Nothing else was selected” never means nothing else exists.

05 / Governance

Contribution without self-certification.

Agents can notice missing context. They cannot turn their own observation into the record that another agent will trust.

Agent notices a gapValidated draft proposalHuman review decides the record

Agents propose. Humans approve the record. Drafts stay outside agent search, lookup, graph, rules, resources, and bundles by default.

06 / State

Working locally, with the boundary left visible.

Current evidence

Verified unsigned local prototype

Local receipts cover the Go core, CLI/API/MCP surfaces, corpus checks, generated archive, native macOS build, routed lens states, and the real interface shown above.

Not claimedSigning and notarization
Not claimedPublic hosting and distribution
Not claimedProduction deployment
Not builtiOS
Not builtIn-app editing
Not builtSync and real-time collaboration
Not builtPermissions
Not builtGraph UI
No claimAdoption or independent audit