A research and reference document. It explains the ideas Common Credo (CC) rests on, the history it descends from, and why it is built the way it is. Companion to the Non-Technical Brief (what CC is) and the Session Notes (decisions banked). Where this updates the earlier need-validation work, it is noted.
Common Credo rests on a single claim, and the whole project stands or falls on it:
Creditworthiness is remembered trust. Trust is information a community already holds. CC gives that information a portable, verifiable form — without owning it.
CC does not manufacture trust, lend money, or hold a central file. It defines a shared format and provides the plumbing so that trust which already exists locally can travel. Everything below is the evidence and lineage for why that is both possible and worth doing.
The intellectual grounding comes from the credit theory of money — that money is fundamentally a record of who owes what, a social memory of obligation, rather than a valuable object. Felix Martin's Money: The Unauthorised Biography assembles the historical cases. They matter to CC because each one shows trust and credit operating without a central bank or bureau — exactly the gap CC works in.
The tally sticks (medieval England). For ~700 years the English Exchequer recorded debts on notched hazel-wood sticks, then split each stick lengthwise: the creditor kept one half (the "stock" — origin of "stockholder"), the debtor the other (the "foil"). The two halves matched only each other, so the record was self-authenticating and impossible to forge. These sticks circulated as money — transferable claims on the Crown. The lesson for CC: a record of obligation, made tamper-evident and portable, can itself function as trusted value. (Historical footnote Martin enjoys: when the obsolete sticks were finally burned in 1834, the fire got out of hand and destroyed the Houses of Parliament. The record outlived the institution, then took it down on the way out.)
The Yap stone money (Micronesia). Famously, the island of Yap used enormous stone discs as money — and crucially, ownership could transfer without the stone ever moving, by communal agreement. One stone, lost at the bottom of the sea, still counted as wealth because everyone agreed it did. Money as a shared ledger held in the community's head, not as a physical object you hold.
The Irish bank closure (1970). When Ireland's banks shut for six months, the economy kept functioning. People paid each other with uncleared cheques, and the local pubs and shops became the clearing system — because a publican who had served someone for years already knew whether they were good for the money. "One does not serve drink to someone for years without discovering something of his liquid resources." Trust already existed locally; the closure merely revealed who was holding the ledger all along.
These three are CC's deep ancestry: portable tamper-evident records of obligation (tally), value as communal agreement rather than a held object (Yap), and local nodes as the real keepers of creditworthiness (Irish pubs). CC is an attempt to give that ancient, proven logic a modern, portable, person-owned form.
The hardest problem CC faces is not whether local trust exists (it plainly does) but whether it can travel to a lender who knows none of the people involved. History has solved this before, without states or courts.
The Maghribi traders (11th-century Cairo). Documented through the Cairo Geniza records and analysed by the economic historian Avner Greif, a community of Jewish traders running long-distance Mediterranean commerce enforced honesty across vast distances with no formal legal system. They operated as a coalition: a member who cheated anyone was reported across the whole network, and all members refused to deal with them again. Reputation was multilateral — your standing was held by the community, and losing it with one member meant losing it with all. Honesty was rational because the network remembered.
Hawala. The centuries-old, still-operating value-transfer system across the Muslim world and South Asia, run entirely on trust between brokers, where money moves without money physically moving — settlement is reputational. Another live proof that trusted value transfer can run on relationships rather than institutions.
These are CC's closest functional ancestors. CC's two-step growth model — start inside one close-knit community, then let standing travel between communities via a reputation network — is the Maghribi mechanism, rebuilt with modern tamper-evident records. The Maghribi coalition is also the answer to the "why would anyone be honest" question: because the network remembers, and the cost of cheating is exclusion from all future trade.
CC intends to be free and owned by no one. That instinct sits inside a 50-year tradition with a clear through-line. Understanding it tells us who will recognise CC as one of their own.
The hacker ethic (1960s–70s, MIT). The original culture: information should be free, mistrust authority, decentralise, and judge people by their work rather than their credentials. Never written down by its practitioners — codified later by journalist Steven Levy in Hackers (1984). The grandparent of CC's egoless, judged-by-the-work instinct.
Free software and copyleft (Stallman, 1980s). Richard Stallman treated proprietary software as an ethical wrong and built a weapon against it: the GPL licence and the idea of copyleft. Copyright normally lets an owner restrict copying; copyleft inverts it — "anyone may copy and modify, on condition that they pass the same freedom on." It uses property law to build a commons that property law cannot capture. This is the legal machinery that makes "everybody's but nobody's" real rather than merely sincere: once released under copyleft, even the creator cannot take it back. CC's constitution is copyleft's idea applied to governance and mission rather than code.
Linux (1991–). Proof the model works at planetary scale. One student's free kernel grew, via open contribution, into the infrastructure running most of the internet, all Android phones, and the world's supercomputers. Three lessons CC takes directly: (a) the bazaar — building in the open with many contributors outperforms the closed cathedral; (b) governance by earned trust (maintainers, a clear owner of the core) rather than one-person-one-vote; (c) corporations fund what they cannot own, because depending on a shared commons is cheaper than building private infrastructure. Linux is CC's model for how it is governed, not for what it is.
TCP/IP (1970s–). The deepest precedent, and the better analogy for what CC is. Vint Cerf and Bob Kahn, working on US defence research funding (DARPA), designed a shared rulebook letting incompatible networks talk to each other. They deliberately did not patent it — understanding that a standard's entire value is universal adoption, which any restriction kills. It was developed in the open through "Requests for Comments" (RFCs — note the humility in the name) under the culture of "rough consensus and running code." In the 1980s it faced a rival, official, committee-designed standard (OSI) backed by governments and telecoms — and the free, simple, already-running TCP/IP crushed the heavyweight institutional alternative. This is CC's most important strategic precedent: the free, minimal, working commons beats the official, over-designed, institution-backed standard. CC aims to be the trust layer built the way TCP/IP built the connection layer.
Signal (today). The clean funding model: a nonprofit foundation, bootstrapped by one founder's loan, now running on donations — no ads, no investors, no corporate stake — yet trusted by millions who stake their safety on its integrity. Proof that infrastructure-grade, fully trusted software can run on the nonprofit-donation model without selling out.
One branch CC is NOT on. The piracy tradition (The Pirate Bay, Kopimi) shares the "information wants to be free" gene but is transgressive — it defies the law and takes what is enclosed. CC is on the opposite, generative-and-lawful branch (Stallman and the builders): it creates a commons using the law cleverly. This distinction is not academic — CC is asking regulators and lenders to trust it with people's reputations, which is incompatible with the outlaw branch. Same soul, opposite method.
Free is the winning move, not merely the noble one:
Two theories of money frame the bet:
Both are partial. Martin's synthesis, and CC's working position: money is fundamentally credit — transferable, recorded obligation — and the state is its most powerful issuer, but not its only possible anchor. Crypto is the modern evidence that value can arise without a state demanding it (which undercuts pure chartalism) — and the cautionary tale that throwing the anchor away entirely produces volatility, fraud, and harm to the very vulnerable it claimed to free.
CC's bet sits precisely here: not the coercive state anchor, not anchor-less cold math, but a humane, distributed, accountable anchor — community obligation given portable form. The pub, not the central bank, and not the blockchain-for-its-own-sake. Chartalism explains why anchors matter; crypto shows what happens without one; CC seeks a third, human anchor.
(Full version in the Non-Technical Brief; summarised here so this document stands alone.)
CC is a common standard / base layer — not a kernel in the hardware sense, not a lender, not a bureau, not an app. It is the free, shared rulebook plus the plumbing that lets others exchange proof of creditworthiness in one agreed way. It does four things — Define the record format, Verify a record is genuine, Enable others to collect and arrange (without CC itself doing so), and Protect the rules via the constitution.
Three structural commitments:
And one elegant consequence: because standing is held partly by the community, the mechanism that builds a reputation is also the one that recovers it if a wallet is lost — social recovery, free, exactly where it matters most (the displaced, the stateless).
The governance question is the keystone, because two layers depend on it: who governs the collective, and what is allowed into the shared core. The open-source world offers a spectrum, and the surprise is that almost none of the durable infrastructure projects use one-person-one-vote democracy:
The reframe for CC: the real question is not how do they vote but how do you earn the standing that gives you a voice, and who owns the final "no" on the core. A principled candidate blend: a small elected council (Python) for legitimacy and succession, sitting on earned-trust (Linux) for who is in the room, with proof-of-function (IETF) required before anything enters the core. The classic attack to design against is fake identities flooding any vote (a "Sybil" attack) — doubly important for an identity-and-trust project.
Governance also has layers banked separately: immutable commandments at the base; collective mission stewardship in the middle; hired professional legal custodians (lawyer, accountant/trustee) holding the legally-required named seats, which keeps the collective faceless while remaining accountable; and possibly a minimal founder backstop that sunsets.
A deliberate strategic choice — a property of how the project is built, not a personal brand to announce. CC is built patiently and without forcing scale. Concretely —
The honest counterweight (kept in view, not as an objection): even TCP/IP, the purest "make it free and it spread" story, did not win on free alone — it had a patient patron (DARPA) and a guaranteed first home (ARPANET) to prove itself on. So patience is right, but free is necessary, not sufficient: CC will still need a first real home (a warm-seed community where one actor is both first issuer and first verifier) and a patient backer who needs no return. Patience and that practical need are compatible — the growth is unforced, but it still needs a first foothold to grow from.
Stated plainly so this document is trustworthy rather than triumphant:
None of these is fatal; all are the real work ahead. The foundations (what CC is, why free, the historical proof that trust travels) are sound. The frontier (will distant lenders honour it, who attests and why, how the vote resists capture) is where the next work lives.
Status: research and reference. Updates and extends the earlier need-validation work (Common Credo Working Paper No. 1) with the architecture, governance and lineage developed since. To merge into a single master research dossier with the original's full citation base, the Working Paper would need to be brought together with this document.
Common Credo · this page is generated from its Markdown source in the project by build-site.js.