Bridge Commons
“Facts Bridge Gaps” — Introducing Bridge Commons
A source-first way to compare contested ideas, map claims to evidence, and nudge reading into civic action.
Quick Sheet (what, why, outputs)
- What it is: A public, citation-first “knowledge + dialogue” commons. Think Wikipedia’s source discipline + a debate map + civic prompts.
- Who it’s for: Readers, analysts, teachers, local groups, and curious citizens who want steel-man comparisons, not hot takes.
- What it produces: Topic Hubs, Bridge Pages (Book Ends + CODE Quick Sheet), Claim Maps, Fact Cards, Evidence Packets, and Civic Quests.
- Quality rules: Evidence-first; scope clarity; temporal stamps; explicit value vs. fact lines; visible changelogs.
- MVP: 3 Topic Hubs × (1 Bridge Page + 6–10 Fact Cards + mini Claim Map + 2 Civic Quests).
What Bridge Commons Is
Bridge Commons turns polarized topics into shared, navigable ground by pinning claims to sources, comparing best-case arguments side-by-side, and guiding readers through structured reasoning (your CODE and ATLAS rails).
Core Objects (the data model)
| Object | Purpose | Canonical Fields | Output |
|---|---|---|---|
| Topic Hub | Landing for a contested issue (e.g., Universal Healthcare, Tariffs). | slug • scope • last-updated • steward(s) • status | Hub page with tiles for all objects below |
| Bridge Page | Front-door comparison in best steel-man form + synthesis space. | core question • frames • synthesis hypotheses • update log | Book Ends tiles + CODE Quick Sheet + “evidence strong/weak” callout |
| Claim Map | Graph/table: claims → evidence → counterclaims. | claim • type (fact/value/policy) • sources • quality score • status | Claim Flow table + mini-graph |
| Fact Cards | Individually cited nuggets with confidence and time bounds. | statement • confidence • sources • date range • layer (FACT/COMMON/TRUTH) | Inline cards + index |
| Evidence Packets | Curated source bundles for sub-questions. | scope • sources • annotations • conflicts • methods | Annotated source lists |
| Analyses | Structured passes using CODE/ATLAS/PESTLE/etc. | method • author • date • reviewer | Tight HTML templates (CODE/ATLAS) |
| Civic Quests | Small actions that turn reading into doing. | action • time • difficulty • verification • badge | Quest tiles with badge hooks |
The Bridge Workflow
| Stage | What Happens | Guardrails |
|---|---|---|
| Intake | Define the narrowest answerable question; register Topic Hub. | Scope statement: “What this is / is not.” |
| Scan | Collect sources; draft Fact Cards; outline Claim Map. | Confidence band + date bounds on every fact. |
| Compare | Write Book Ends (A vs. B) with links into Claim Map. | Steel-man only; tag fallacies; no vibes-only lines. |
| Structure | Run CODE (Clarify→Organize→Discover→Evaluate) + ATLAS cameo. | Use the tight HTML components for transparency. |
| Synthesize | Bridge Page: agreements, live disagreements, decision paths. | Separate facts vs. values vs. policy proposals. |
| Civic | Publish 2–3 Civic Quests tied to the topic. | Verifiable completion; light badges. |
| Review & Version | Peer check; log changes; mark open questions. | Visible changelog with dates. |
House Rules (Good-Faith Charter)
- Evidence first. Every factual sentence is sourced or labeled as value/opinion.
- Frame clarity. Question + scope appear at the top of every page.
- Best-case debates. Opposition views are steel-manned; fallacies are identified.
- Temporal discipline. Facts carry date windows and update notes.
- Open reuse. CC-BY (or CC-BY-SA) for remixing with attribution.
How It Fits Your Templates
- Bridge Page = Book Ends + CODE Quick Sheet + Fact Cards index + Claim Map + Civic Quests.
- ATLAS cameo: one compact callout on systems/values/social dynamics/transition/narratives.
Concrete Example (sketch): Universal Healthcare (U.S.)
Best Case For
- Coverage universality + risk pooling.
- Admin simplification and bargaining power.
- Public cost visibility; equity goals.
Best Case Against
- Higher taxes; allocation trade-offs.
- Innovation incentives and queue risk.
- Federal overreach; implementation complexity.
Fact Cards (sample):
- U.S. admin spend vs. OECD median — FACT, high confidence, 2018–2024 window.
- Uncompensated ER care trends — FACT, medium confidence (lagged).
- Price controls → pharma R&D — CONTESTED; show both findings & methods.
Roles & Incentives
| Role | Powers | Incentive |
|---|---|---|
| Contributor | Submit Fact Cards, propose claims, suggest edits. | Public credit; basic badges. |
| Curator | Approve edits; enforce charter; manage statuses. | Steward badge; footer credit. |
| Reviewer (SME) | Red/blue-team Bridge Pages; note uncertainties. | “Peer-Reviewed” mark on page. |
| Citizen (Quest) | Complete civic tasks; submit proof. | Quest badges; optional merch/NFT tie-ins. |
Launch Plan (v0.1)
- Stand up 3 Topic Hubs (econ, culture, tech/policy).
- Each Hub: 1 Bridge Page + 6–10 Fact Cards + mini Claim Map + 2 Civic Quests.
- Use your tight CODE/ATLAS HTML components exactly as standardized.
- Add a visible Changelog and “Disputed/Open” tags.
- Publish a short “How to Read a Bridge” explainer.
FAQ
Is this a fact-check site? No. It’s a living comparison with explicit trade-offs, not binary verdicts.
Can anyone contribute? Yes—within the charter. Curators gatekeep quality; reviewers pressure-test claims.
How are disagreements handled? We log them openly, show competing sources, and state what evidence would resolve them.
Changelog
- Nov 4, 2025 — v0.9: Initial public spec and launch plan.