Documentation · v0.1.0
Building an instrument that can be argued with.
The reason unexplained sightings stay unexplained is almost never that the object was exotic. It is that nobody measured it properly. Everything documented here exists to change that: hardware, firmware, database, analysis, and these pages in one repository on one version, with a drift check that fails the build when any of them disagree. Documentation that has quietly stopped matching the hardware is worse than none, because it is trusted.
Bands defined
14
Bands with a part
13
Entry build
$504
Tier 2 draw
12.8 W
Shortest path
Depending on what you are trying to do
Three routes through the same material. Every page also links to the next in reading order, so following any of these straight through works.
Deciding whether to build one
Building one now
Reading the data
Start here
What the platform is and whether you want one.
The fourteen bandsWhat each band physically detects, how far it reaches, what weather kills it, and what it costs to open.for: Deciding whether to build oneHow verdicts workKnown-source subtraction, hypothesis scoring, and the four gates guarding the top of the ladder. Runs live.for: Anyone who wants to trust the archive
Build
Everything needed to put a node in the sky.
Hardware and BOMThree build tiers, every part priced from a named vendor page, and the diagrams generated from that same registry.for: Pricing a buildBuild guideTen ordered steps, each ending in something you can verify before spending money on the next.for: Mid-build, soldering iron downSoftware and configFlashing, the configuration file, trigger thresholds, and calibration.for: Node running, changing behaviourVariant registryEvery part the grid knows how to calibrate, including community substitutes, and how to register one.for: Building with different parts
Reference
The contracts everything else is written against.
Live data
What the grid is doing right now.
Participate