01 / FOLLOW AN APPLICATIONEXECUTED ON THE PUBLIC SOURCE SNAPSHOT
A private request. A useful record. A controlled reveal.
An intake or CRM application needs to remember a request without scattering private text through its shared history.
We ran the published Cairn CLI with four Rust-built WebAssembly guests and a fresh synthetic store. The request was accepted, a blessed storage node wrote a safe reference, and only an authorized owner could reveal the private body.
Application code transforms data. Cairn’s runtime-owned blessed effect nodes hold the authority to touch storage or the outside world. An AI-authored transform does not receive an unrestricted database password.
01 / RECEIVE
Keep the body private.
The synthetic contact returns a safe receipt. Raw input is absent from public content-addressed storage.
POST 200
02 / PERSIST
Grant a specific effect.
Pure guest logic connects to blessed storage. Shared application state retains a private-blob reference, not the message.
1 safe row · 1 effect
03 / REVEAL
Check the viewer.
No session refuses. The authorized owner reveals the body, with an access record that does not retain plaintext.
401 denied / 200 allowed
EVIDENCE INCLUDES THE LIMIT
The served list query refused with 400 because its required ledger source was absent. The operator’s direct query found one row; that is not a successful served-list request. Five contact-safe surfaces were checked for synthetic private text; the privacy scan reported no findings.
This local run does not exercise distribution, PostgreSQL compensation or external delivery. Those mechanisms have separate source and evidence boundaries.
Different jobs. The same separation of computation, authority and evidence.
IMPLEMENTED MECHANISMS / LOCAL FLOW PROOFS
A useful app. Less exposed data.
Customer intake, internal casework and CRM need useful state, not private text scattered through shared history. Keep sensitive inputs sealed; give each step only the access it needs.
Privacy still depends on the application’s reviewed flow. Pure computation does not automatically declassify its outputs.
IMPLEMENTED / MANIFEST-BOUND REVIEW
Generated logic. Deliberate authority.
An AI can propose application transforms and wiring without receiving a general-purpose host credential. Review the actual graph, capability set and registered cost before promotion.
Capability review narrows authority; it is not a proof that arbitrary generated application logic is correct.
SEPARATE HOSTED EXPERIMENTS / JULY 2026
Reach the service. Respect the writer.
Geo-distributed, high-availability applications need more than extra copies. Cairn combines election, lease, writer-fencing and readback components with capacity-aware placement and policy-governed elastic planning.
Hosted drills are separate evidence. Elastic planning is not an always-running production autoscaler; this is not a durable-before-ACK, whole-region recovery or SLA claim.
RESEARCH APPLICATION / NOT FLIGHT-QUALIFIED
Far from a link. Not beyond scrutiny.
Remote instruments and redundant workers could share approved observations, inspect the same identified work and keep physical actions behind separate authority. Ground systems could inspect the retained trail later.
An application pattern to engineer and test, not an implemented voter. Synthetic inputs are not sensor evidence, and matching outputs can share a fault.
Rust-compiled kernels run here. The database, observations and network are a session-local simulation.
No computation coordinate yet
New compute fuel
0 work units
Sandbox database
No decision
Delivery pending
0
Pure cache
0 / 24
Forward effect journal 0 EVENTS
No writes or deliveries.
Real WebAssembly and BLAKE3; simulated authority, storage and delivery. Fuel is this kernel’s explicit work-unit count, not Wasmtime instruction fuel or physical propellant. Rewind changes inspection, not the world. No values leave this tab.
03 / BEYOND THE DATA CENTERA RESEARCH DIRECTION, NOT A FLIGHT CLAIM
Auditable work. Redundant execution.
On a spacecraft, separate computers may need to cross-check a decision before anything acts. The useful unit is the execution chain: what was observed, which code ran, what it concluded, and what was allowed to change.
Cairn separates observations and effects from pure computation. That creates a foundation for giving redundant workers the same approved, recorded inputs and comparing their work without asking each worker to repeat a physical action.
The same pattern could connect a remote instrument to Earth: send identified work and retained evidence across an intermittent link, then inspect or recompute on arrival. Local authority must not depend on a real-time round trip. These are research applications of the architecture, not a released spacecraft voting system.
Repeat the computation, not the physical action. Recorded observations keep their origin and access policy; synthetic mocks stay synthetic. Agreement is neither sensor truth nor permission to actuate.
CONTENT-ADDRESSED IMMUTABLE REIFY NETWORK
Remember. Return. Move forward.
Rewind a versioned state. Compensate supported effects with a new authorized, metered action. Keep the original evidence.
Build the CLI, run a pure WebAssembly DAG, then repeat it and inspect the cache. No account, provider key or public server is needed.
Cairn and Perffection source are public under AGPL-3.0-only, with documented MIT exceptions and third-party notices. Read the code, run it locally, and build from the evidence.
For people. For agents. For source readers. Start with the architecture and evidence map, then follow the runtime contracts, app-authoring guide and implementation paths. The browser lab is not the full engine.
Perffection is a separate product built on Cairn. Its application guests, documents and interface evolve in their own repository; the runtime stays generic. Both source snapshots are public, with the product pinned to its exact engine.
07 / THE REASON WE BUILDJOSHUA 4 · STONES OF REMEMBRANCE
Built to serve. For the glory of God.
Cairn takes its name from memorial stones: a visible reminder of what happened, and why it matters.
Our deepest hope is not in software. God loves us; we have sinned and need His forgiveness. Jesus Christ died for our sins and rose again. Salvation is His gift, received by grace through faith, not earned by our work. Turn to Him and trust Him.