Record format

@flashyos/frontdoor

frontdoor/1 — a published door: which lanes an organisation opens, what it asks at each, and what it owes back — including the honest no-SLA rung.

version 0.1.0 · audit of 2026-10-04 · source: flashyos/packages/frontdoor

npm i @flashyos/frontdoor

The machine door (a handshake field) gets adopted first because it is one line of JSON; the human door gets forgotten. The estate measured six of seven properties with a machine join and nought of eight with a human one — publish both, and measure from outside.

Edge cases — each one paid for once

A well-known directory is not evidence anything serves it

A published npm package with no site held five well-known files; grading it for lacking a door it could not have was the survey’s bug, not the package’s. A site framework is the evidence a door should exist.

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