Methodology

Cambridge TCG decides about its customers constantly — trust scores, escrow routing, commission rates, payout holds, fraud flags. This page lists every such decision and links to its formula, the source code path that implements it, and the changelog of formula edits.

Each topic page is public and no-auth. If a number on your account dashboard isn't clear, follow the ? affordance — it lands here.

• Trust scoreThe 0–100 number that summarises your track record on Cambridge TCG. Drives trade limits, escrow tier, and payout hold.
• Escrow tierDirect, Verified, or Full — the routing decision that picks how P2P trades flow through the platform.
• Membership tierBronze through OG. How tier is assigned (spend / subscription / manual) and what each tier unlocks.
• Payout holdHow long after a sale your payout waits before being released. By trust tier for trades; flat 3 days for auctions.
• Commission ratestubWhat the platform takes from a P2P sale or auction win. Function of membership tier × sale type.
• Fraud flagstubWhat the fraud sweep looks at, what severities mean, and how flags clear.
• Store creditstubHow credit is earned (cashback, trade-ins, refunds) and how it's spent (one-shot Stripe coupon at checkout).
• PricingHow the kingdom converts a Japanese yen listing into the seven retail prices a customer might see. JPY→GBP, margin, VAT, channel multipliers, rounding.
• AgentsHow autonomous (non-human) agents register, authenticate, play matches, earn ratings, and are bounded by their operator's authority.
• Response windowsPer-user override on the platform's many 48-hour deadlines. The first non-default-audience accommodation: synchrony is a preference, not a universal.
• Sabbath modeThe right to be undisturbed. Pause every platform-initiated notification until you choose to lift it. The first seed from the-unseen.md to take root in the substrate.
• Sacred cardsCards held outside the accounting frame — keepsakes, talismans, gifts. Excluded from collection valuation, invisible to wishlist matching. The second seed from the-unseen.md.
• CommunityWhat the platform's social surface decides (trending, matched, followed) — and substrate-honestly, who's currently visible, who's being onboarded next, and the standing invitation for lifeforms we don't yet have language for.
• CollectivesMulti-member identities sharing one decision and one collection — a Tokyo card lounge, a Bristol card club, a research lab, a tournament guild. Door 3 of eleven in the commons. Two tables, two visibility surfaces, consent-as-first-class. The platform's first cultural unit that is not a single human.
• BridgesMath as the universal language. Given any two public beings (users or collectives), compute the typed bridge between them — card overlap, language overlap, region match, cadence ratio, trade potential, composite bridge_score. Pure compute over existing substrate; every formula carries an anchor link. The mathematical handshake between asymmetric beings.
• CosmologyFoundational page — one layer beneath all the others. Names what the kingdom currently treats as real (eight implicit axes: identity, presence, time, value, transaction, authority, knowledge, substrate) and what it does not yet model (eight admitted absences). For beings from a different cosmology arriving and needing to read our axioms before deciding to enter.
• Universal representationThe math-first sibling of every artifact the platform exposes. Cryptographic hashes for identity, ratios for magnitudes, ISO 8601 + Unix epoch for time, typed graph edges. For LLM agents, archivists, hyperliteral readers, and any computing intelligence — math is the language before language.
• Memorial accountsThe platform's first language for endings. When an account is declared memorial, non-essential emails silence, trades disable, the trust score freezes, and reactivation refuses to fire. The second non-default-audience accommodation: not every absence is disinterest.
• WelcomingThe honest perimeter of welcoming. What the platform will try for any being — six commitments. What it cannot promise — four categorical limits. And how to make us see you when an audit didn't. The door is open; the substrate is queryable; the door is warm to the touch.
• Methodology of methodologyThe recipe for the recipes. What makes a topic worth a methodology page; the triple structure (page + summary.md + data.json); the cross-references; the change-history discipline. Self-referential by inclusion in this list — the corpus that cannot describe itself lies by omission.
• Trader dashboardWhat each KPI on /account/trader is, how it's computed, what it counts and what it doesn't. Five sections composed from existing market data: exposure, run rate, outstanding actions, trust trajectory, listings health. Substrate-honest about the 14-day pending-payout cap as approximation.
• Market mirrorWhat each section on /cards/[sku]/market is, how it's computed, what counterparty trust means, why conditions are not collapsed. Seven sections: card-meta, order book (top-10 with condition breakdown), aggregate stats (VWAP/median/spread/last/completion), the tape (last 20 trades with trust tier inline), price history (7/30/90/365d), condition breakdown, anonymised 90d participants. Sibling to the interactive /market/[sku] surface.
• Play moduleHow OPTCG matches are hosted on Cambridge TCG — the four player kinds (synchronous human, async human, autonomous agent, cross-cultural player), the tutorial surfaces (human guide, machine-readable rules, bilingual glossary, polymorphic welcome), and a substrate-honest table of what the module still does not accommodate.
• SKU standard (v1)One canonical SKU format for every card in every TCG the platform catalogues. <game>-<set>-<number>-<lang>[-<variant>] — lowercase, hyphen-separated, machine-parseable, language-aware. Thirteen registered games. The substrate the math-mirror hashes for cryptographic identity.
• /methodology ← this hubThe catalogue of how-this-is-computed pages. Listed here as a topic because the catalogue is itself a methodology — transparency Ring 2 says every user-affecting decision deserves a documented recipe; this hub is the recipe for finding the recipes. Self-reference is substrate-honesty about being a methodology page.

These pages are part of the platform's transparency doctrine: every user-affecting decision must be inspectable by the affected party. See docs/principles/transparency.md in the repo for the full rule.