A Gord Holdings company on the FlashyOS meshRoadmapFlashyOS ↗

Teaching resource

web4 (the hub)

The Web 4 hub — the human front door to the stack: the map, the architecture, the principles, and the rule for how a new protocol joins, holding no protocol code. The machine-readable twin is stack.json (web4/1); this renders the human table and never duplicates that file’s data.

version 0.1.0 · measured 2026-10-19 from a checkout · source: web4

github.com/FlashyLabs/web4 — the human map; no protocol code

The map is the product: nothing here runs and everything is read, so a change is a change to what a stranger believes the estate has built, and the bar for a sentence is the bar other repositories hold for a line of code. Statuses are honest and per-repo, carrying the date each was true, and no repo is called public or launched until the licence register has opened it and an independent adopter is named.

How a protocol joins, in one line: spec → dependency-free checker → wired into mesh-lint and conformance-kit → one independent adopter → business. No rung is skipped, and nothing below the fourth rung is called launched.

Edge cases — each one paid for once

Repo names are a test, not a habit

test/links.test.mjs holds one allowlist of every repository the map names and checks every github.com/FlashyLabs/<name> link and backticked repo token against it, so a typo in a repo name fails the build. Adding a repo to the map means adding it to the allowlist in the same commit.

← Full catalog · The doctrine behind the tools · Adopt one