Bedrock is ShardStitch's local, append-only record of the evidence that survived a coding session. It gives a handoff more than a confidence badge: it gives it a trail back to what was recorded.
Bedrock stores captured events, decisions, summaries, and conversation slices on disk. Each entry includes its source and metadata, then is content-hashed and linked to the previous entry. Re-seeing the same captured event does not create a duplicate.
When ShardStitch verifies Bedrock, it re-derives each content hash and checks the full sequence. An edited, deleted, or reordered past entry breaks the chain from that point and is reported.
This is tamper-evidence, not a claim that someone with full local control cannot rewrite a database. It makes silent alteration detectable when the chain is checked.
For a project with a .shardstitch directory, Bedrock lives at .shardstitch/bedrock.db. Otherwise ShardStitch keeps a per-project record in its local state directory. Normal recovery does not upload the record.
Bedrock is the durable local foundation beneath recovery: project identity, state snapshots, evidence references, and the information needed to rebuild a continuation packet after the active chat is gone. It keeps continuity tied to the workspace rather than to one provider.
Before a risky reset, branch change, or tool switch, confirm the working tree and the last verified check. Bedrock preserves that context, but the next AI still needs to verify anything that changed after the snapshot.
Pair it with Git-Aware State and Session Vault.