Skip to main content

A startup inside Midcore

Project Vault

Every artifact your project ships sealed and proveable.

Per-project policy. AES-256-GCM encrypted snapshots. Hash-chained audit log. EKB1 capsule export. The container under every vibe-coded app, every research manuscript, every robot configuration, every PSUR.

AES-256-GCM
snapshot encryption
Hash-chained
audit log
11
IPC verbs
5
slash commands

What is a project

The canonical container for the work you do here.

A project holds the cleartext working tree, a per-project policy, immutable encrypted snapshots, and a hash-chained audit log of every action against the project. Vibe-coded apps, research manuscripts, robot configurations, PSUR drafts, personal-KB snapshots — they all live here.

Snapshots

Point-in-time seals, encrypted at rest.

Snapshot a project and you get an AES-256-GCM-encrypted point-in-time seal of the full state — code, documents, embeddings, robot configs, research runs, evidence entries. Immutable. Verifiable. Cheap.

Audit

A hash chain you can replay.

Every action against the project lands on a hash-chained log. Walk it forward to reconstruct what happened. Hand it to a regulator and let them walk it themselves.

Capsule export

EKB1 capsules — share work without losing the chain.

Pack a snapshot into an EKB1 capsule — an encrypted container plus a share token. The recipient imports it on another Midcore shell, re-verifies the hash chain, and works with the exact state you sealed. Shares can be time-limited and recipient-restricted.

Slash commands

Five verbs. The whole vault.

/project new · /project switch · /project snapshot · /project capsule · /project list