14 — Assumption Tests

Don’t defend the assumption.
Test the assumption.

Our own beliefs, published as research objects rather than positions: a status that advances, a version history, and the condition that would defeat each one — written before any evidence exists.

The portfolio

What state the research is actually in.

3Total
3Under investigation

Every number here is counted from the published tests. There is no status a test has not earned, and no completed test yet.

Method

The same fourteen stages, used flexibly.

Not every test needs every stage. Two rules are not negotiable: the falsification condition is written before the experiment, and the counterarguments are made properly before the tests are designed.

  1. 01

    Assumption

    Stated so it can be attacked, not so it can be agreed with.

  2. 02

    Why do we believe it

    The honest reason, including "because everyone around us does".

  3. 03

    Historical origin

    Where the belief came from, and what constraint it was a reasonable answer to.

  4. 04

    Current system

    How the thing is actually arranged today.

  5. 05

    Evidence

    What is known, with sources. Empty when it is empty.

  6. 06

    Counterarguments

    The strongest cases against, made properly — including our own bias.

  7. 07

    The 1850 test

    Would we design it this way from scratch, with today’s technology?

  8. 08

    The today test

    What does present technology actually change about it?

  9. 09

    The future technology test

    What changes at the technological boundary, and what stubbornly does not?

  10. 10

    Alternative architectures

    Options compared on real criteria, including reversibility.

  11. 11

    Counterfactual

    If this assumption had never existed, what would the system look like?

  12. 12

    Experiment

    Specific and falsifiable. Method public; location and operational design are not.

  13. 13

    Result

    Published either way. A result against us is the most valuable kind.

  14. 14

    Updated assumption

    The next version, and what changed. The history is preserved.

Status lifecycle

A status has to be able to go backwards.

  1. Under investigation
  2. Evidence collected
  3. Challenged
  4. Experiment
  5. Resolved
Resolved means supported, partially supported, rejected or updated. Any of them can be reopened by a challenge.

If a challenge cannot move a supported test back to challenged, the status is decoration. So it can, and the first genuine rejection will be the most valuable thing this section ever publishes.

How these numbers are produced

The counts, the filters and the cards above are generated at build time from the test definitions themselves. There is no separate dashboard that could drift, and no way to publish a count that no test supports. Right now that means: three tests, all under investigation, no evidence collected.

Challenge one of these