df_shell
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. -->
df_shell
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. -->TODO: describe this module.
Interface
What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.
conforms to
zero/source-extract/v2df_shell — which screen is on the glass, and why. The five authored screens of slice `presentation` are registered here and driven from one small state machine. It follows `Core.state.phase` when core-loop publishes one, and it owns two overlays that are not phases at all: the field card and the held line. The brain is a module rather than the component so that start/stop is exact — the boot module can register and unregister the screens and the event handlers in the same call — while DfShell.component stays a thin driver that gives it a per-frame tick and the callback ids a UI click lands on (a callback only reaches a component or a scene entrypoint). Slice owner: presentation.
snapshot( ) → any
The state a screen is drawn from
apply( ) → void
Visibility
setShell(next_: string) → void
| arg | type | description |
|---|---|---|
| next_ | string |
state( ) → string
beginDive( ) → void
What the buttons and the keys do
pauseDive( ) → void
resumeDive( ) → void
endDive(reason: string) → void
| arg | type | description |
|---|---|---|
| reason | string |
toTitle( ) → void
callback(id: string, _data: any) → void
| arg | type | description |
|---|---|---|
| id | string | |
| _data | any |
pressed(key: string) → boolean
Keys W/S/Q/E belong to the lure and J to the journal; the shell only takes the keys that move between its own screens.
| arg | type | description |
|---|---|---|
| key | string |
readKeys( ) → void
tick(dt: number, live: boolean) → void
The tick
| arg | type | description |
|---|---|---|
| dt | number | |
| live | boolean |
listen(name: string, fn: (any) → void
Lifecycle
| arg | type | description |
|---|---|---|
| name | string | |
| fn | (any |
start( ) → void
stop( ) → void
Sub-parts
Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.
Showing up to 3 levels deep. Open a part to see what it holds further down.
Problems
Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.
agent_score is exposed.+ quality × 0.35
+ performance × 0.25
± compat factor
Usability ratings
Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".
Scoped to this part · feeds back into the world's score.