| # Frontend Guide | |
| ## Current Frontend | |
| The GitHub Pages frontend is a static HTML/CSS surface in: | |
| - `docs/index.html` | |
| Its job is to: | |
| - explain the legal domains | |
| - show the kernel team | |
| - show the reasoning fabric | |
| - show the trust deed layer | |
| - let a user explore the interaction flow before runtime wiring exists | |
| ## Interaction Scaffold | |
| The current scaffold adds: | |
| - module navigation | |
| - kernel / fabric / deed mode buttons | |
| - a visible request path | |
| - static output cards for each mode | |
| - a separate Shakespearean presentation page | |
| It does not submit to runtime modules yet. | |
| ## What To Wire Next | |
| 1. deed generation form | |
| 2. summon route controls | |
| 3. kernel lane selector | |
| 4. WORM receipt viewer | |
| 5. runtime bridge for external engine attach | |
| ## GitHub Pages Fit | |
| This frontend stays GitHub Pages friendly because: | |
| - no server is required for the base scaffold | |
| - everything renders from static HTML/CSS/JS | |
| - docs and UI ship together | |