How we know what we claim to know.

Every capability page is challenged before it earns the verified mark. An independent review is tasked not with checking the page but with refutingit: every date, every “wait, really?” fact, every dependency edge, every recipe step is attacked against primary and scholarly sources. What survives, ships. What doesn't gets fixed or cut.

This has caught real errors — a ship hauled onto dry land, not across a harbor; flasks left open, not sealed; a capability dated to coinage when its own definition says commodity money. The corrections are public in the changelog.

A hard edge means could not exist without — knowledge, material, or process. Where history only suggests influence, we say inspirationand draw it differently. Six edges that felt true but couldn't be defended have been downgraded. The graph stays acyclic and every edge points to something strictly older.

Bootstrap recipes include what goes wrong — the part most how-to knowledge quietly omits, and the first thing you need when a build fails. Each recipe states how to verifythe result, because “trust me” is not a verification step.

4nodes are marked draft: charted into the graph but not yet through refutation, or carrying an open editorial question. Draft nodes never appear as the daily puzzle's answer and are labeled on their pages.