Pattern · Applications
Database Workbench
Application recipe composed from public TermRock building blocks; domain state and effects remain host-owned.
- Kind
- pattern
- Input
- interactive
- Canvas
- 120×40
Live preview
Static terminal poster. Choose Run live to start the Rust demo.
01 · Purpose
What it is for
Application recipe composed from public TermRock building blocks; domain state and effects remain host-owned.
Best fit: Applications · application · CommandPalette · HistoryPicker · ObjectInspector
02 · Behavior
What the mounted story proves
- 01
DatabaseWorkbench
Representative 120×40 terminal state.
- 02
Passive paint
No keyboard or pointer action is claimed by this representative story.
- 03
Evidence stays explicit
0 covered · 9 partial · 5 missing axes.
03 · Implement
Install, then start from exact code
Install
cargo add termrock --git https://github.com/tailrocks/termrock.git --rev 5283c2acf9154d0cfcd37b1ffe821c00faf90ea2Add TermRock once. Keep domain effects in the host application.
Minimal implementation
Exact Rust setup used by database-workbench/basic.
Open to load code.
04 · Adapt
Variants and composition
Public building blocks
CommandPalette · HistoryPicker · ObjectInspector · Panel · StatusBar
Supporting types
CommandEntry · HistoryEntry · InspectorField · NavItem · NavItemStatus · StatefulWidget · StatusRegion · StatusSlot · Widget
05 · Reference
API, tokens, accessibility
API
DatabaseWorkbenchOpen source ↗Tokens
DesignSystemInspect exact story code for roles and capability projection.Accessibility
Input contract mountedNo input claim in the representative story.Contract
Evidence in progress0/23 axes covered06 · Go deeper
Advanced guidance
Ownership boundary
TermRock owns reusable terminal rendering and interaction state. The host owns domain data, policy, persistence, authorization, and side effects.
Evidence status
0 covered, 9 partial, and 5 missing contract axes. Missing evidence is not a behavior claim.