Where every fact lives
A readable map of where each kind of protocol knowledge lives in The Syndicate, what each system owns, and how a fact moves from a live on-chain projection into durable memory. This page describes structure — not live values.
The Knowledge Map shows where each kind of protocol knowledge lives and how a fact moves from live projection into durable memory — structure, not live values.
Two kinds of truth
The protocol may know a fact in one system before that fact belongs in the Institutional Register. Knowing is not the same as remembering — and both are kept honest by three rules.
Knowledge is a live projection
Most of what the protocol knows is recomputed every load from on-chain truth. Member numbers live in the Holder Index. NFTs live in the Archive. Treasury values live in the asset / treasury reads. Nothing is stored twice — each fact is read from its one canonical home.
Memory is a durable overlay
Institutional memory lives in the Institutional Register. It records an assertion and its on-chain anchor — never a live value — and a fact only enters it by promotion or seed. Everything else is held in its knowledge home until then.
Each fact has exactly one source-of-truth layer. Every other layer references it; nothing keeps a second copy.
The Institutional Register records an assertion + anchor, never a live value (never the live LP balance, current member count, or rank).
A fact enters durable memory only by promotion (lineage-covered) or by seed (a discrete config anchor). Otherwise it is held, and remains fully available in its Protocol-Knowledge home.
18 knowledge homes · projected from the code registry · structure, not live values
Live Protocol Knowledge
Read live from on-chain truth on every load — a projection of what the chain already knows, never a separately asserted institutional record.
Truth / Foundation
LIVEThe base layer: deployed contracts, addresses, and immutable protocol constants that every derived layer reads from.
src/lib/syndicate-config.tssrc/lib/protocol-truth.ts/transparency/tokenomicsdocs/canon/00_AUTHORITY_MAP.mddocs/canon/05_FOUNDATION_FREEZE.mdIdentity / Member (Holder Index)
LIVEThe canonical registry of who is a member and in what order — member numbers, first purchase, first seat.
src/lib/holder-index.ts/members/my-syndicatedocs/canon/02_SOURCE_OF_TRUTH_TABLE.mddocs/canon/05_FOUNDATION_FREEZE.mdRank / Progression
LIVEStructural recognition tier derived from cumulative USDC. Recognition only — confers no rights, returns, or discounts.
src/lib/syndicate-config.tssrc/lib/holder-index.ts/ranks/my-syndicatedocs/canon/06_FINANCIAL_TRACE_AND_GUARDRAILS.mddocs/canon/01_FOUNDER_INTENT_MAP.mdChapter / Era
LIVECohort classification by member-number range (e.g. Genesis Signal #1–#333) and chapter transitions.
src/lib/chapters.tssrc/lib/protocol-truth.ts/chaptersdocs/canon/05_FOUNDATION_FREEZE.mdArtifact / NFT (Archive1155)
PARTIALOn-chain commemorative artifacts (Archive1155): ID 1 The First Signal, ID 3 Patron Seal, and their mint/ownership state.
src/lib/archive-config.tssrc/lib/archive-indexer.tssrc/lib/syndicate-config.ts/nft/nfts/archivedocs/canon/02_SOURCE_OF_TRUTH_TABLE.mdArchive1155 deployed and live; ID 1 (First Signal) & ID 3 (Patron Seal) active/mintable, ID 2 reserved/disabled (future SeatRecord721). Evidence: src/lib/archive-config.ts and ARCHIVE_CONTRACT_STATE in src/lib/syndicate-config.ts.
Activity / Events
LIVEThe raw, complete, automatic chronological stream of on-chain protocol events (what happened).
src/lib/protocol-events.ts/activitydocs/canon/05_FOUNDATION_FREEZE.mdSignals
LIVEA deterministic prioritization projection: Signal = Type × Tier × Subject derived from events.
src/lib/protocol-signals.tssrc/lib/signal-registry.tsdocs/canon/05_FOUNDATION_FREEZE.mddocs/canon/06_FINANCIAL_TRACE_AND_GUARDRAILS.mdMemory
PARTIALThe gateway that persists worth-keeping facts toward the Activity / Chronicle / Recognition / Ledger / Reports stores.
src/lib/memory-candidates.tsdocs/canon/05_FOUNDATION_FREEZE.mdCandidate derivation live; some durable MEMORY sub-stores (Recognition/Ledger/Reports) are partial. Evidence: src/lib/memory-candidates.ts.
Recognition (partial)
PARTIALDerives recognition candidates (e.g. patron-seal-holder, early-chapter-member) from on-chain facts — a memory OUTPUT, distinct from the Rank attribute.
src/lib/recognition-candidates.ts/my-syndicate/ranksdocs/canon/01_FOUNDER_INTENT_MAP.mdDerivation logic live; advanced alias/public recognition tiers are reserved and not built. Evidence: src/lib/recognition-candidates.ts.
Economic / Routing
PARTIALThe 70/20/10 inflow split rule (Vault / Liquidity / Operations) and revenue attribution by stream.
src/lib/syndicate-config.tssrc/lib/protocol-truth.ts/vault/tokenomicsdocs/canon/06_FINANCIAL_TRACE_AND_GUARDRAILS.md70/20/10 split is LIVE and on-chain for the Membership Sale stream; other revenue streams (NFT mint proceeds, LP fees) are PARTIAL/PENDING. Evidence: USDC_ROUTING in src/lib/syndicate-config.ts.
Treasury / Vault
PARTIALThe destination of routed value: the Vault Wallet (70% USDC) and Vault Reserve (25% SYN).
src/lib/syndicate-config.ts/vaultdocs/canon/06_FINANCIAL_TRACE_AND_GUARDRAILS.mdVault Wallet and Vault Reserve resolve to the SAME EOA today; a programmatic Vault contract is PENDING. Evidence: src/lib/syndicate-config.ts.
Asset
LIVEWhat the Vault actually HOLDS right now — live multi-asset balances (AVAX / USDC / BTC.b / WETH.e). Formally named here for the first time.
src/lib/treasury-hooks.ts/tokenomics/vault/transparencydocs/canon/06_FINANCIAL_TRACE_AND_GUARDRAILS.mdReal RPC balance reads via useTreasuryAssets (src/lib/treasury-hooks.ts) are the only Vault asset data the site shows — surfaced via TreasuryComposition on /vault and /transparency. No illustrative or mock Vault balance-sheet data remains in the codebase.
Liquidity
PARTIALThe SYN/USDC liquidity pool (Trader Joe v1): pair reserves, spot price, and the LP creation event.
src/lib/syndicate-config.tssrc/lib/sale-hooks.ts/liquiditydocs/canon/06_FINANCIAL_TRACE_AND_GUARDRAILS.mdPair reserves/price reads are live; LP fee accrual is reserved/planned with no live data-link. Evidence: useLpStats in src/lib/sale-hooks.ts.
Wallet-linked
LIVEThe connected wallet's normalized session and a client-side cache of its on-chain reads (balance, allowance).
src/lib/wallet-session.tssrc/lib/wallet-reads-cache.ts/my-syndicate/wallet/$addressdocs/canon/05_FOUNDATION_FREEZE.mdMetrics / Verification
PARTIALThe canonical dictionary of every protocol metric — its id, formula, and verification path. The 'don't trust, verify' home.
src/lib/protocol-metrics-registry.ts/registrydocs/canon/02_SOURCE_OF_TRUTH_TABLE.mdRegistry is live; some metrics carry documented ceilings / PARTIAL verification status rather than a live value. Evidence: src/lib/protocol-metrics-registry.ts.
Durable Memory
Written once and curated. Records an assertion and its on-chain anchor — never a live value, and only ever by promotion or seed.
Chronicle
PARTIALCurated, gated, append-only record of what MATTERED — protocol-centric primitives only (chapters, artifacts); member subjects forbidden.
src/lib/chronicle-entries.tssrc/lib/chronicle-review-candidates.tssrc/lib/chronicle-promotion.ts/chronicledocs/canon/05_FOUNDATION_FREEZE.mdPromotion pipeline live; public Chronicle curation is gated and human-approved. The admission → entry edge derives DRAFT institutional entries only; publication is a human / governance act. The entry → chronology edge orders entries by verified block height (unprovable order is held, never invented); verified block timestamps are now threaded onto anchored entries as read-only metadata (one getBlock per block), never as an ordering input and never estimated. The full event → … → chronology → timestamp journey is exposed end-to-end by the pure, read-only Protocol Lineage projection (/labs/protocol-lineage, src/lib/protocol-lineage.ts) — a visibility re-expression that creates no new intelligence. Evidence: src/lib/chronicle-promotion.ts, src/lib/chronicle-entry.ts, src/lib/chronology.ts, src/lib/chronology-timestamps.ts, src/lib/protocol-lineage.ts.
Institutional Register
LIVEThe durable, identity-blind overlay that records protocol-institutional FACTS (assertion + anchor) — not live values, never member-living.
src/lib/institutional-register.tssrc/lib/institutional-register-registry.tssrc/lib/institutional-register-genesis.ts/institutional-register/chronicle/activitydocs/canon/05_FOUNDATION_FREEZE.mddocs/canon/08_PROTOCOL_OPERATING_PRINCIPLE.mdEach register entry's full provenance — promotion → review → memory → signal → event → tx/block, plus the lawful genesis seed for facts that predate the scanner — is carried verbatim on the entry's lineage trail and exposed read-only by the Protocol Lineage projection (/labs/protocol-lineage, src/lib/protocol-lineage.ts). The projection re-expresses the carried trail; it creates no new intelligence and mutates nothing.
Reserved / Future
Named and reserved in code, not yet built. No live data — listed so the map stays honest about what does not exist yet.
Seat Record / Identity Record (reserved)
PENDINGA future optional per-member ERC-721 identity record (SeatRecord721). Today the 'seat' is the SYN membership position itself; no record contract exists.
src/lib/syndicate-config.tsdocs/canon/07_FOUNDER_PRINCIPLE.mddocs/canon/02_SOURCE_OF_TRUTH_TABLE.mdNo SeatRecord721 contract deployed; ERC-721 identity record reserved (Archive1155 ID 2 disabled, held for it). Evidence: src/lib/syndicate-config.ts (Reserved Seat Record Reference).
Every number here is on-chain.
Read the contracts, follow the addresses, check the transactions. The Protocol Registry lists every wallet, every status, every explorer link.