Layer 2 · logged-in · not crawled

Practice

A real problem against a real repository. Rooms claim filesystem regions, adjacency drives keyboard navigation, and live state colours the tiles. This is an application, not a document — which is exactly why it must not be the reading surface.

Task floor · 6 × 2

static tiles · no live state

Close the κ-routing gap in the reference implementation

The business example is documented as κ=2. It is κ=1. Find where routing reads it, fix it, and make the test prove it.

14:02ELAPSED
hjkl move between rooms ↵ open in editor r run ? task brief

Every tile is file-backed — the room's identity is a path, and opening it hands that path to your editor. That is the whole reason Runefort fits here and does not fit the reading layer: a document wants to be linear and extractable, a workspace wants to be spatial and stateful.

What blocks this

@runefort/core has no build

blocker

runefort.com/packages/core/ contains src/, package.json and two theme stylesheets — but no dist/. The README quickstart tells you to load /packages/core/dist/index.js, which does not exist. Until that ships, these tiles are hand-written HTML imitating a component that cannot yet load.

build order · step 5

The real risk is not the component

open question · lane B

Nothing in this layer has been validated with a person. The unanswered question is whether completing a real repository task inside this system beats reading the docs with an AI assistant open. If it does not, Practice collapses and Academy is two layers.

That test does not need Runefort. It can run against the atlas today.

build order · step 6 — the gate that can invalidate this page