Platform

The machinery every route sits on and no user can point at. A page in this folder documents something that has no owning screen: the Control-Tree engine two pages share, the id and route surface three pages hang off, the state that survives a navigation, the locale bundles behind every label, the gate in front of the whole app, and the host process under all of it.

The boundary with Conventions is which side of the page the reader is on. Conventions holds a rule a page author must follow; Platform holds machinery a page author must understand and never touches.

Two of these are ordinary routes rather than mechanisms — /login and /preference/log. They sit here because what they document is the platform surface, not a step in a machining workflow.

Ordered from the machinery a page sits closest to, outward to the host process beneath it.

Pages

• Control Tree — The engine both tree pages share: the node shape, the item-type registry, branch building, the selection gate and the panel host
• Tree Ids and Routes — The URL surface: the route table, the redirect-only paths, and how a ?tree= id is migrated and landed on the page that owns it
• Session State — The project epoch behind the keep-alive, the stores and module singletons outside it, and what is device-local
• Internationalization — Three locales over one English schema: the bundles, the single switch point, the build-gating lint, and the strings that never reach a bundle
• Login and Authentication — The optional login gate: the sign-in screen, the config switch that turns it on, the cookie scheme and fallback policy it registers, and the router guard in front of them
• Log Viewer Page — The read-only /preference/log screen: today's server log file, its auto-refresh, and the daily file sink behind it
• Program and Hosting — The ASP.NET Core host: the HiAPI start/stop pair, the all-singleton container, the SignalR hubs, the SPA fallback, and the configuration that pins the listening address

See Also

• Conventions — the other cross-screen folder: the rules an author follows rather than the machinery an author reads
• Anatomy by Source Directory — the inverse index, for entering by the directory a change landed in