01
decision boundaryFrame the decision
State the consequential claim, desired outcome, time horizon, and what would change your mind.
Countercase · historical decision intelligence
History should challenge
a decision before it decorates one.
Test the historical analogy behind a consequential decision. Countercase shows the cases that support it, the countercases that strain it, and the evidence limits that should change the recommendation.
Public betaBuilt for decisions that deserve a harder testAdvisory review packets · explicit sources · no autonomous approval
decision under review
01Claimwhat must be true?
02Caseswhat belongs?
03Mechanismwhy is it comparable?
04Evidencewhat survives review?
742complete recordscontent-addressed source bodies
24scoped claimseach kept separate from the conclusion
4review-ready packetshuman authority remains explicit
Read onlyevidence corpusthe website cannot rewrite its source
The decision path
One stable method.
Four visible moves.
Evidence stays attached throughout. Human judgment remains the final authority.
- 01Frame↗
Name the decision, the claim, the horizon and what would change your mind.
- 02Compare↗
Build a reference class with included, excluded and negative cases.
- 03Challenge↗
Test mechanisms, decisive disanalogies, complements and falsifiers.
- 04Review↗
Leave claim-level verdicts, evidence limits and an advisory recommendation.
The product
One consequential decision.
One inspectable challenge.
Countercase turns a decision and its historical premise into a bounded, reviewable artifact. It is designed to expose where the analogy fails—not to add historical decoration to a conclusion already chosen.
02
countercase analysisChallenge the analogy
Compare candidate cases, exclusions, mechanisms, and decisive disanalogies instead of searching for a flattering precedent.
03
evidence + receiptLeave an inspectable record
Receive a versioned review packet with citations, uncertainty, review posture, and a bounded recommendation.
Commercial promiseFind where historical reasoning changes the decision.
Not “provide more history.” Not “generate a prettier memo.” The product must expose a weak analogy, change the reference class, identify a failure mechanism or refuse an unsupported conclusion.
Who it is for
One packet.
Three jobs around it.
Countercase is organized around the decision episode: one person owns the choice, one builds the challenge, and one needs to inspect the basis for action. The same evidence stays legible to each.
Pressure-test the claim before commitment.
- Bring
- A live strategy, investment, policy or adoption decision and the historical premise behind it.
- Leave with
- A bounded recommendation that shows which claims survived, changed or should be refused.
Build the comparison the decision deserves.
- Bring
- Candidate precedents, mechanisms, assumptions or a reference class that needs a harder test.
- Leave with
- Included, excluded and negative cases with decisive disanalogies and source-bound reasoning.
Inspect the boundary before sign-off.
- Bring
- A recommendation that needs independent challenge, evidence lineage or a review record.
- Leave with
- Claim-level confidence, visible uncertainty, packet provenance and an explicit human-review state.
Designed to test reasoning across
- Strategy
- Investment
- Public policy
- Technology adoption
- Institutional design
Usefulness must be demonstrated decision by decision; historical similarity alone is never treated as forecast authority.
Countercase Review Packet
The answer is an artifact,
not a chat transcript.
The packet is versioned, evidence-bound and advisory. It can support, weaken, reframe or refuse. It cannot approve the underlying investment, strategy or policy choice.
Open the example review →- 01Decision
Name the claim, intended outcome and horizon.
- 02Reference class
Show candidate, included, excluded and negative cases.
- 03Mechanisms
Test causal matches and decisive disanalogies.
- 04Evidence
Bind each consequential assertion to source and uncertainty.
- 05Review
Support, weaken, reframe or refuse—with a human receipt.
Live evidence cases
Start with claims
that can be opened.
These dossiers expose inherited argument, evidence classes, confidence and cautions. They are product substrate and evaluation candidates—not finished commercial packets.
01 · eventlow confidence
1775–1789 CEUnited States Independence
The inherited card combines the 1776 declaration, the 1775–1783 war and the 1787–1789 constitutional settlement into one foundational event claim.
The Declaration was adopted in 1776.
4 claim receipts · 6 relationsOpen case →
02 · eventlow confidence
1789–1799 CEFrench Revolution
The inherited card describes the transformation from monarchy to republic and connects it to rights, republicanism and nationalism across Europe.
Revolutionary change transformed French political institutions after 1789.
4 claim receipts · 7 relationsOpen case →
03 · politylow confidence
1644–1912 CEQing Dynasty
The inherited polity card identifies the last imperial dynasty, Manchu rule, territorial expansion and pressure from Western powers.
The Qing was established by Manchu rulers and lasted until 1912.
2 card citations · 17 relationsOpen case →
Research substrate
One evidence base.
Six ways through it.
Search the corpus, follow chronology, test a pattern, open a case, inspect an estimate or trace a source. The atlas is now presented as the product’s evidence substrate—not the commercial offer by itself.
01full records + graph
Atlas
Read 742 complete historical cards and move through 6,828 declared relationships.
Explore →02claims in timeTimeline
Trace 43 events across fifteen civilizational frames without forcing one universal periodization.
Explore →03comparative propositionsPatterns
Compare mechanisms and expose where a framework, method or single case has been mislabeled as a pattern.
Explore →04argument workbenchCases
Open 24 scoped propositions with evidence, estimate semantics and claim-level confidence attached.
Explore →05reconstructionsData
Inspect long-run estimates with their original units, time ranges and analytical boundaries.
Explore →06referencesLibrary
Search 844 cited works and distinguish bibliographic stubs from mature source records.
Explore →Evidence lens
“Strong” is not
a magic word.
Countercase separates the kind of evidence from confidence in a claim and the publication decision made after review.
See the evidence lens in use →What is it?
Authority assertionSource observationPublished reconstructionInterpreted transcriptionExpert-coded estimate
How was it made?
Direct attestationBounded rangeCentral estimateDerived metricInterpolatedExtrapolated
How well supported?
IndeterminateVery lowLowMediumHighVery high
Evidence boundary
Every conclusion
shows its limits.
- Complete bodies
- 742
- Preserved words
- 455k
- Priority source locks
- 4/5
- Specialist reviews
- 0
Coverage is not confidence. A source, estimate, or historical case can remain useful while its publication or recommendation authority is explicitly withheld.
Inspect the method →