PENDING
Referral attribution
SourceRegistryV1 exists, but no source records are active. Today, local attribution is recognition-only and creates no payout or entitlement.
Source attribution
Source attribution pending
SourceRegistryV1 exists and has zero source records. Referral, claiming, and public source-aware purchases are inactive.
Current status
No source records. No commission. No claim.
The live product is membership: buying SYN seats the wallet. MembershipSaleV3 can support source-attributed membership receipts later, but only after source terms are approved, created, read back, and activated.
PENDINGSOURCE RECORDS INACTIVERESERVED
The Syndicate can remember who introduced whom, but memory is not money. V3 public buys currently use ZERO_SOURCE_ID. Until a SourceRegistry record is created, activated, wired live, and publicly verifiable, no commission is accruing, no active source tier is live, no source balance is displayed, and no claim button appears.
Truth first
No live claim appears before source state can prove it.
No hidden balances
The interface will not imply money owed from browser state or off-chain memory.
Source without hype
Attribution may matter later, but membership remains the live product today.
Source policy observability
The source registry is visible before any source is usable
This read-only snapshot separates deployed infrastructure from active source policy. It is the truth layer future source records must pass through.
Registry
DEPLOYED
Records
0
Active
0
Paused / revoked
0 / 0
No source record has been created.
No referral/source commission is accruing.
No source claim UI is live.
No public source-aware purchase path is live.
Public/default MembershipSaleV3 buys use ZERO_SOURCE_ID.
Reserved systems
What can exist later
Future systems stay visible only as PENDING / RESERVED / REQUIRES SOURCE RECORD / PENDING DESIGN.
REQUIRES SOURCE RECORD
Source records
No source record has been created. Until source terms are approved, created, read back, and wired into the buy path, no acquisition commission accrues and no claim action can be shown.
RESERVED
Reputation records
Durable participation may become an institutional memory layer later. It is not a top-earners board and no scoring formula is live today.
Membership source boundary
Source attribution changes the receipt, not the seat
MembershipSaleV3 can calculate acquisition cost first, then split Net USDC Routed 70 / 20 / 10. Public/default buys still use ZERO_SOURCE_ID.
Today, every public MembershipSaleV3 purchase uses ZERO_SOURCE_ID: gross USDC becomes Net USDC Routed, then the receipt splits that amount to Vault, Liquidity, and Operations. If a future source record is approved and activated, a non-zero sourceId may attribute a MembershipSaleV3 purchase: gross USDC minus acquisition commission equals Net USDC Routed, then Net USDC Routed splits 70 / 20 / 10. CommissionRouterV1 is not the active V3 source engine.
Lifecycle
A source record must move through visible states
Creating a source record is not the same as activating it. Status changes must remain observable before they can affect a purchase.
PAUSED
Created, not usable
A source record exists for inspection, but cannot route commission until a separate activation action.
ACTIVE
Usable by approved source-aware paths
A source record can affect a source-aware purchase only when the product path explicitly passes that sourceId.
REVOKED
Permanently blocked
No new source attribution should be created. Historical receipts remain readable.
Module boundary
Future products need their own source-aware design
Archive1155, future ERC-721 identity/artifact systems, SwapRail, and premium products are not source-attributed today.
PENDING DESIGN
Archive and NFT mints
Archive1155 is not source-aware. A future NFT source path would need a source-aware Archive wrapper/router, Archive1155 V2, ProductSaleRouter, or separate approved NFT sale design.
PENDING DESIGN
SeatRecord / ERC-721
SeatRecord721 is not live and does not replace SYN as the seat. Future ERC-721 work must separate identity, memory, and recognition from financial rights.
PENDING DESIGN
Other products
SwapRail and future product commerce do not inherit source attribution automatically. Every new module must pass the Module Integration Standard before it can use source terms.
Verify
Every number here is on-chain.
Read the contracts, follow the addresses, check the transactions. The Protocol Registry lists every wallet, every status, and every explorer link before you act.