Installing The Memory Adapter

Install and sync on Linux amd64 with curl and Python 3.8 or newer:

curl -fsSLo coretex-setup.py https://agentmoney.net/coretex-setup.py
python3 coretex-setup.py --dir ./coretex --profile conv.pref.v1

The helper creates a private Python 3.10 environment (downloading that Python if needed), verifies the public release and exact runtime/dependency wheels, installs the adapter, syncs current confirmed modules and prepares the store. No sudo, global pip changes, RPC account, API key, wallet or validator replay is required. The initial release/model download takes longer than later syncs; progress is printed and success ends with "ok": true.

./coretex/bin/coretex ingest "The deployment window begins Friday."
./coretex/bin/coretex context "When is the deployment window?" --budget 800
./coretex/bin/coretex sync

The first two commands write and recall a local memory. sync adopts current confirmed modules from public endpoints. Re-running the setup command also refreshes a completed installation and retains its memories. The generated command needs no shell activation or PATH changes.

conv.pref.v1 selects the fixed hybrid BM25/BGE-small RRF60 provider. The default when --profile is omitted is lexical event.schema.v1; document is also lexical. All three profiles use their current mined modules. Use separate stores for separate profiles or users. Only code/configuration is downloaded; private memories stay on the consumer host.

The normal consumer format is coretex.current-state/v1, explicitly marked admission_replayed: false. Public RPC supplies confirmed chain observations; content hashes bind frontier, composition and executable bytes. Contract, epoch-context, compatibility-lock, ABI and provider checks remain enforced. Independent admission replay is the validator's separate audit function. Setup runs the sealed verifier to check release bytes without replaying history or installing the validator in the serving environment.

Every new open/restart refreshes the pointer; a failed refresh refuses the open and preserves the store. An already-running sidecar uses one stable module until restart. Default confirmation depth is 12. Public endpoint limits can change latency; the measured current-state sync was about 35–41 seconds. A new product compatibility lock requires the corresponding release bootstrap.

For a large existing store, stop its writer and back it up, keep its profile, set store in ./coretex/consumer.json to the database's absolute path, and run ./coretex/bin/coretex prewarm before traffic. This rebuilds derived indexes; it does not reverse old retractions. Shortened-history repair stays explicit.

The complete adapter setup guide covers private paths, recovery, Python integration and Hermes. The setup helper currently targets Linux amd64; other platforms need separate manual qualification.