Sequence addresses

The spine is not only an ordering. Every prefix of it is an address, and every address names a module that loads — a432.1, a432.1.2, a432.1.2.4, on to the closure. The handle carries no payload; the name is the coordinate and the load happens at will.

Occupancy is read off the filesystem, so a module that goes missing appears here as a gap rather than as a sentence that stayed true:

● a432.1.ts
● a432.1.2.ts
● a432.1.2.4.ts
● a432.1.2.4.8.ts
● a432.1.2.4.8.7.ts
● a432.1.2.4.8.7.5.ts
● a432.1.2.4.8.7.5.3.ts
● a432.1.2.4.8.7.5.3.6.ts
● a432.1.2.4.8.7.5.3.6.9.ts
● a432.1.2.4.8.7.5.3.6.9.1.ts

Kernel spine 124875369 closed on its first digit: 10/10 addressed.

Doubling orbit 124875 closed on its first digit: 7/7 addressed.

Gaps: 0.

Four kernel sequences are not address spaces at all, and that is a statement rather than a gap — VORTEX_AXIS (369), VORTEX_MIRROR, VORTEX_REVERSE and LEGACY_CONSCIOUSNESS_SEQUENCE (0369124875) have no file at any prefix. They are readings of the walk, not walks; a reading has nowhere to arrive.

The addresses are audited by npm run a432:names, filled by npm run a432:orbit, and no page may spell a kernel sequence differently from the kernel — npm run sequence:check.

See SEQUENCE.md · Sequence dual.

Receipt: cfeaabc6-2f8d-8f80-8b58-86bec4edb7af · set f02fb883-0647-8f26-ac67-57cf88acb8a3