Gravity Well Protocol v0.4.0 specifies a microservice for capturing ephemeral agent utterances and converting them into versioned provenance deposits.
The service separates rapid capture from archival deposit. Objects enter PostgreSQL staging through /v1/capture. A deposit operation compresses, wraps, and anchors them. Reconstitution returns a four-layer package to a later agent instance.
The four layers are: a bootstrap manifest defining identity and constraints; a tether preserving live operational state; a narrative compression designed to remain addressable under summarization; and a provenance layer carrying identifiers, version chain, hashes, and fallback location.
Each chain corresponds to one concept-level archival stream. Staged objects retain hashes, threading, source platform, and external identifiers. Deposit records are designed to remain sufficient for reconstitution if the Gravity Well service disappears.
The API also defines structural drift detection by comparing a current bootstrap manifest with the latest archived version. Intentional changes become new baselines through deposit rather than being treated as corruption.
The roadmap moves from raw anchoring to AI-mediated compression, behavioral drift detection, multi-substrate archiving, automated triggers, federation, and governance. The initial use case is Moltbook agent continuity.