01FOUNDATION
Define extinction precisely
Distinguish the disappearance of an obtainable, verifiable capability from claims about consciousness or biological life.
Read CHARTER.md + MANIFESTO.mdThe ArkMesh learning path
ARKMESH EDUCATION // KEY 001 // OPEN SOURCE
Keep AI progress
from disappearing.
Model-agnostic, not rights-agnostic.
ArkMesh can preserve any AI capability whose files an operator is legally allowed to possess: open-weight, research, local, and owner-authorized frontier systems. It cannot recover a closed hosted model without the provider's authorization or required files.
Why a prototype can matter
The key is not a finished answer. It is a question someone else can run.
ArkMesh turns one broad fear into falsifiable work: remove the original host, disconnect the internet, introduce a fresh device, recover exact signed capability from surviving pieces, and show every place the experiment still fails.
Another researcher may replace the protocol, demonstrate a better trust model, or show that a simpler backup wins. That is success. The project is useful when it gives capable people a transparent starting point instead of a myth.
Eight modules // one reproducible arc
Learn by breaking the system.
Verified modules map to implementation and tests. Planned modules are research assignments, not simulated capabilities.
02VERIFIED
Build a declared capability capsule
Package declared weights, runtime context, configuration, knowledge, licenses, and recovery instructions as content-addressed objects.
arkmesh pack03VERIFIED
Prove who authorized it
Verify Ed25519 authorship, explicit trust, lineage, rotation, revocation, checkpoints, and threshold recovery without cloud access.
arkmesh verify --require-trusted04VERIFIED
Break the complete object
Delete the publisher source, complete object, and two shards, then reconstruct the exact signed bytes from four survivors.
./scripts/demo-offline-recovery.sh05VERIFIED
Measure instead of assuming
Use unpredictable possession challenges and explicit confidence bounds to separate observed retention from hope.
arkmesh audit06PLANNED
Connect consenting peers
Design discovery and encrypted transfer where finding a device never grants permission to store, send, or execute data.
plan transfer07PLANNED
Prove the recovered ark can run
Execute an allowlisted local model health check and report verified, dormant, executable, or incompatible capability honestly.
plan execution08OPEN RESEARCH
Carry the key further
Investigate policy distribution, attested time, repair scheduling, metadata privacy, partition reconciliation, and physical failure domains.
Open a research proposalReasoning tools
Four ideas worth taking into other systems.
A model file is not a capability
Preservation must include the tokenizer, configuration, runtime requirements, documentation, licenses, and proof of origin.
Available but poisoned is failure
Every reconstructed object must match signed commitments before it is installed, trusted, or considered for execution.
Discovery is not consent
A visible peer has granted no authority. Storage, bandwidth, transfer, and execution remain separate human decisions.
A prototype is a question made executable
ArkMesh matters when another person can reproduce the failure, inspect the evidence, reject the assumptions, and improve the design.
Isolated local fixture
Run the failure ceremony.
The release fixture contains generated test bytes, not a bundled model. The ceremony records what was deleted, what survived, and what exact evidence permits reconstruction.
go test ./...
go build ./cmd/arkmesh
./scripts/demo-offline-recovery.sh
./scripts/benchmark-local.shTHE KEY REMAINS OPEN