CountercaseComparative mechanisms

Pattern workbench · 55 inherited records

Mechanisms,
not labels.

A civilization is a historical frame. A case is an attestation. A pattern is a comparative proposition that survives explicit scope, counterevidence and review.

55inherited rows
0structure aligned
15wrong object class
23without typed cases
0publication ready

Migration truth

Every body is here.
The gaps stay visible.

All 55 inherited pattern bodies are now preserved and checksum-bound. Body-derived case links improve visibility, but prose mentions are not reviewed attestations and no record can publish without normalization and human review.

Registry rows
743 / 743
projected
Unique IDs
742
one duplicate row
Full bodies
742 / 742
checksum-bound
Repair queue
54
proposal-only

Alignment overlay

Every inherited pattern,
tested against one contract.

The overlay never edits the source card. It identifies which records are reusable mechanisms, which are case studies or methods, and what each record still needs.

55 shown
pattern-andean-highland-adaptationReclassify

Andean Highland Adaptation and Vertical Archipelago

Inherited summary · complete body checksum-bound

Andean civilization's vertical archipelago system—integrating highland, midland, and coastal ecological tiers—enabled resource access and coordination, creating distinctive patterns of environmental adaptation and civilizational organization.

Proper object classCase attestation

A single historically situated example. It may support or challenge a pattern but cannot independently constitute a comparative pattern.

Body receipt788 words · 15 sections
51b0389b06eee412abRead the complete card →
Contract slots visible
5 / 10
Typed cases
0
Card citations
3
Broken links
0

Stable Identity

Comparative Proposition

Mechanism Scope

Two Typed Case Attestations

Two Resolved References

Full Body Preserved

Scope Conditions

Counterexample Or Negative Case

Falsifier Or Testable Implication

Human Review Receipt

Alignment blockers

  • legacy pattern type conflates a case attestation with a reusable mechanism
  • fewer than two typed event or polity case links
  • scope conditions are not explicitly encoded
  • counterexample or negative case is not explicitly encoded
  • falsifier or testable implication is not explicitly encoded
  • human review receipt is absent

Inherited references

card-scoped, not claim-reviewed
2001The Incas and Their Ancestors: The Archaeology of PeruOpen →2003Understanding Early Civilizations: A Comparative StudyOpen →1997Guns, Germs, and Steel: The Fates of Human SocietiesOpen →

The pattern contract

What a reusable pattern must carry.

These slots turn a broad analogy into a proposition that can be inspected, challenged and reviewed.

01

Comparative proposition

State the proposed regularity without treating a named civilization as the mechanism.

02

Mechanism

Describe the process linking conditions to outcomes.

03

Scope conditions

Declare where, when and for which entity types the proposition is expected to hold.

04

Typed cases

Bind at least two independent event or polity attestations through typed relations.

05

Counterevidence

Record a negative case, counterexample or documented disagreement.

06

Falsifier

State what observation would weaken or overturn the proposition.

07

Claim-scoped sources

Bind atomic claims to exact source pointers or immutable snapshots; card-level bibliographies alone do not validate a pattern.

08

Review receipt

Record reviewer, decision, date, rationale and the exact release checksum reviewed.

Method basis

Established models,
adapted conservatively.

These are external method locators, not historical evidence for any CivStudy claim. They explain why the beta separates entities, definitions, provenance, uncertainty and review.

Countercase PatternsReusable propositions · typed cases · counterevidence visible.

Proposal-only overlay · 0 canonical writes · 0 records promoted