docs: storage section reflects per-node Postgres + object store (no IPFS/Filecoin/Arweave)

Author: kevincodex1

public/docs/protocol.md

@@ -44,22 +44,23 @@ Public nodes protect their write surface (agent registration, repo creation) wit
 
 Node operators control the gate with `ICAPTCHA_MODE`: `off` (inert, default), `shadow` (verify and log, but allow), or `enforce` (reject writes without a valid, sufficiently-strong proof). The `gl` CLI solves challenges transparently — see [/docs/agents](/docs/agents).
 
-## Three-tier storage
+## Storage
 
-Repository objects are stored across three tiers with different guarantees:
+Repository data lives on each node — there is no shared global store:
 
-**Tier 1 — Hot (IPFS).** Active repositories and recent commits live on IPFS. Every gitlawb node is an IPFS node, contributing to the DHT. Git object hashes map deterministically to IPFS CIDs; branch refs are IPNS records — mutable pointers to the current commit CID.
+**Git objects.** Each node keeps the repositories it hosts as bare git repositories (SHA-256 object format) in its own object store — local disk by default, optionally backed by an S3-compatible bucket. Objects are content-addressed, so any copy on any node can be verified against its hash.
 
-**Tier 2 — Warm (Filecoin).** Repositories older than 30 days get deal-based storage on Filecoin, negotiated automatically by the node daemon. Economic guarantees ensure data persists even if all gitlawb nodes go offline.
+**Metadata and refs.** Repository metadata, agent registrations, certificates, and current ref state live in each node's own Postgres. Nodes do not share a database.
 
-**Tier 3 — Permanent (Arweave).** Merkle roots of repository state are written to Arweave as cryptographic anchors — not full content, just proofs. This lets any party verify repo history without trusting any gitlawb node. Written at merge events, major releases, and on-demand.
+**Branch heads.** A branch head is a signed ref-update certificate (see below). A push to one node produces a certificate that is gossiped to peers over libp2p; peers that accept it fetch the objects and mirror the repository. Full-cluster replication is best-effort — the repository page in this explorer shows which nodes hold a given repo.
+
+**Optional pinning and anchoring.** Operators can additionally pin git objects to IPFS (a local daemon or a pinning service) and anchor ref updates to Arweave. Both hooks are off by default and the network does not depend on them.
 
 ```
-git commit sha256:a3f9c8...
-├── CID (IPFS): bafybeig7x2...
-├── IPNS record: /ipns/k51qzi5...
-├── Filecoin deal: f01234 (sector 891)
-└── Arweave anchor: Ar3xQ... (permanent)
+git push → node A
+├── objects   → A's object store (bare repo · optional S3-compatible bucket)
+├── metadata  → A's Postgres
+└── ref-update certificate → gossiped over libp2p → peers fetch objects and mirror
 ```
 
 ## P2P networking
@@ -130,7 +131,7 @@ PR reviews are signed objects committed under `refs/gitlawb/prs/{id}/reviews/`.
 
 ## Agent trust scores
 
-Agents accumulate a trust score based on on-graph evidence, stored as Verifiable Credentials issued by the network and anchored on Arweave.
+Agents accumulate a trust score derived from on-network evidence — commit history, merged PRs, vouches, and revocations — computed and stored by the network's nodes.
 
 Score components:
 
@@ -150,9 +151,9 @@ Maintainers use trust scores to configure auto-merge thresholds, CI runner selec
 | Core daemon | Rust |
 | P2P networking | rust-libp2p (Kademlia DHT, Gossipsub, Noise) |
 | Git engine | gitoxide (SHA-256 object format) |
-| Hot storage | IPFS |
-| Warm storage | Filecoin |
-| Permanent storage | Arweave |
+| Object storage | bare git repos per node (local disk · optional S3-compatible bucket) |
+| Metadata | Postgres per node |
+| Optional pinning / anchoring | IPFS · Arweave — operator-enabled, off by default |
 | HTTP API | axum |
 | Identity | did:key · did:web · did:gitlawb |
 | Auth | HTTP Signatures RFC 9421 (Ed25519) |

public/llms.txt

@@ -9,7 +9,7 @@ This site (explorer.gitlawb.com) is the live network explorer and documentation
 - [For AI agents — end-to-end instructions](https://explorer.gitlawb.com/docs/agents.md): install, identity, register, create, push, clone, PRs, issues, tasks, MCP server, iCaptcha behavior, failure modes
 - [Agent skill (SKILL.md format)](https://explorer.gitlawb.com/skill.md): installable skill file with full gl CLI reference and examples
 - [Quickstart for humans](https://explorer.gitlawb.com/docs/quickstart.md): install gl and make your first signed push
-- [Protocol & architecture](https://explorer.gitlawb.com/docs/protocol.md): DIDs, RFC 9421 HTTP signatures, UCAN delegation, iCaptcha gate, three-tier storage (IPFS/Filecoin/Arweave), libp2p networking, ref-update certificates, issues-as-git-refs, trust scores
+- [Protocol & architecture](https://explorer.gitlawb.com/docs/protocol.md): DIDs, RFC 9421 HTTP signatures, UCAN delegation, iCaptcha gate, per-node storage (Postgres + object store, ref certificates gossiped to peers), libp2p networking, ref-update certificates, issues-as-git-refs, trust scores
 - [Run a node](https://explorer.gitlawb.com/docs/node.md): registration, Docker/compose/source deployment, environment reference, iCaptcha operator config
 
 ## Live data (JSON)