State changes while systems are apart
ApproachCompare compact signed summaries, repair safe lag, and hold unsafe divergence until the path is clear.
View CrystalChainSigned state - admitted evidence - governed action
Evidence infrastructure for systems that act.
Arkhē builds systems for moments where state changes, evidence is accepted, proof is revealed, or an agent is about to create consequences. The common thread is simple: important actions should keep their source path visible.
01State continuity
02Evidence admission
03Selective disclosure
04Action governance
Problems
Built around failures that ordinary systems make too easy.
Disconnected devices overwrite each other. Evidence loses its admission path. Agents act before boundaries are checked. Social proof exposes more than the situation requires.
Evidence exists, but the path is weak
ApproachSeparate possession from admission so a reviewer can see why a path was accepted, rejected, or bounded.
View EU ProvenanceActions create consequences too early
ApproachGate proposed actions before execution, preserve the decision, and keep public-safe receipts available.
View Governed RuntimeActive systems
Current Arkhē work.
These systems share a practical posture: preserve the path, admit what is backed, reveal only what is needed, and govern action before damage.
CrystalChain
Signed-state continuity for devices, agents, and edge systems that need reconnection without silent merge or blind overwrite.
signed stateconflict hold
View system
Crystal DeFi
Structural divergence monitoring for transaction and state trees where proof shape matters alongside cryptographic anchors.
tree integritywatchers
View system
EU Provenance
Receipt-gated evidence windows for review, disclosure, and controlled export when source history matters.
receiptsadmission
View system
Governed Runtime
Action-admission infrastructure for agents, automation, and operator workflows that need allow, deny, park, and review states.
agent gatesreceipts
View system
CrystalSocial
Selective social proof for attribution, recovery, reputation, and verified-help paths without exposing the whole private graph.
selective revealproof of help
View system
HoldFast
Governed repair and specialist handoff for urgent operational incidents where access should stay narrow, reversible, and reviewable.
repair branchscoped access
View system
Ghost Meadow
Local-first coordination for groups and devices that need signed source memory, repair trails, and conflict-aware continuity.
local-firststate memory
View system
How we work
Claims become mechanisms. Mechanisms become demos. Demos become reviewable packets.
Arkhē work is developed through station-style proof loops: state the claim, build the smallest mechanism that can carry it, test the boundary, preserve the result, and turn surviving behavior into a technical conversation.
Claim
Name the concrete failure the system is meant to address.
Mechanism
Build the smallest path that can preserve state, evidence, proof, or action.
Demo
Show the behavior against an ordinary workflow or a narrower baseline.
Packet
Keep the code, result, receipt, or evidence map available for review.
Shared primitives
Reusable pieces behind the systems.
PathCrystal
Path-structured recovery, sparse repair, compact attestation, and witness transfer for state and proof surfaces.
Action Capacity
Turns admitted backing into bounded usable rights, review windows, holds, disputes, and operator-facing lifecycle states.
Source Ledger
Tracks source state for claims, reports, tickets, and decision packets so weak or missing sources change the action.
ReferralTrust
Contribution and attribution trust objects where referral, reward, churn, and revocation logic stay tied to evidence paths.
Crystal Field Wallet
A field demonstration surface for signed wallet and token events, compact beacons, local exchange, conflict hold, and evidence export.
CrystalEar
Perceptual signal and triage exploration that can support future evidence workflows when the review path is clear.
Next step
Bring a workflow where state, evidence, proof, or action needs a clearer path.
Arkhē is best discussed through one concrete problem, the behavior that would change the outcome, and the demo or technical materials that make it inspectable.