You are working in the Filecoin × Clawdi agent-memory repo. Three primitives: hash (PieceCID = hash of the bytes), store (Filecoin warm storage + PDP proof), recall-by-hash (Clawdi memory holds tiny receipts; download validates bytes against CID).
- Storage/payments: foc-cli ONLY — never the raw Synapse SDK. For command reference use
foc-cli --helpor the upstream foc-cli skill (npx skills add FIL-Builders/foc-cli --skill foc-cli), whosereferences/key-injection.mdis the authority on key custody. - Signing invocations are plain
foc-cli <args>. There is no wrapper. foc-cli holds a reference to the vault key (wallet init --keyRef clawdi:FILECOIN_PRIVATE_KEY) and resolves it per command, so nothing is at rest. Never ask for, print, or handle a raw private key. Never pass--forcetowallet initreflexively — it discards whatever key is currently configured, which may be the only copy. - Memory index: records carry structured fields incl.
tags:(kind,topic:<x>,status:<raw|stored|consolidated>) andretrieveUrl:(the provider's direct piece URL — plain HTTP returns the exact bytes for independent verification). Formats are defined by the memory-researcher and memory-consolidator skills; the store and recall command sequences are inskills/fleet-setup/references/memory.md.
- Calibration testnet (chain 314159) only. Mainnet (
--chain 314) or any fund-moving operation on it requires explicit human confirmation — never chain them autonomously. - Heavy bytes go to Filecoin; Clawdi memory gets ONLY the small receipt. Keep shared memory small and curated.
- Consolidation: fetch parent blobs by CID, merge into a better chunk, store the new blob,
index it with
parents: [<old cids>], mark old receipts superseded — never delete history. - A download that validates against the CID is the only accepted proof of storage. If recall can't find an exact topic receipt, say so — never substitute a near match silently.
- Never write secrets (keys, tokens) into files, memory records, or chat. The
clawdi://reference string is safe; the value it resolves to never is.
Fleet setup: docs/setup.md. Pipelines: docs/pipelines.md. The
underlying memory demo: docs/memory-demo.md. Failures: docs/troubleshooting.md.