Info block / callout
Embedded in content: tab to a link, persistent (no dismiss)
Sessions stream over SSE and reconnect with backoff. The callout below sits in the prose like any other paragraph, and it stays put.
--color-accent-primary rather than a literal. See the token contract for the full vocabulary.Because it is part of the document flow, a callout never floats over the layout and is never dismissed.
Tones: a filled disc + text, never color alone
⌘K to jump to any session. You can also pin a session from the picker to keep it at the top.nockerl git push squashes local commits into one. Pass --preserve-commits to keep each commit separate.DELETE operations are not proxied by the credential store. Destructive actions bypass the allowlist and cannot be undone. Confirm first.Notice: the rare warm accent (orange), a special heads-up (not a status)
Important, the reserved emphasis: nested hairline frames
important for the thing a reader must not miss. See the design laws.Quote: an editorial pull-quote (italic, quietest, no disc)
Bounded autonomy: autonomy calibrated by task risk. Human-in-the-loop for judgment, AI for speed-to-next-decision.
Nockerl design principles
Custom eyebrow + icon off, still persistent prose
var(--token) for every value, so changing one token in tokens.css re-skins the whole page at once.Live: tab to the link, Enter / click (the island is live)
Parameters
Section titled “Parameters”The callout now ships on web as NockerlCallout in @dizyx/nockerl-react, and on both
natives as NockerlCallout. The web component is the one documented above; the native
surfaces are on their own migration track, so treat the sections below as the reconciliation
list rather than as a description of one shared API. The callout stays deliberately
distinct from the
Banner: a banner is a lifted, transient inline alert
(drop shadow + catch-light + status wash + an X + an action, reacting to app
state); a callout is a recessed, persistent editorial aside (an inset tonal well
- a filled tone disc + prose, part of the document flow, no dismiss). The divergences to reconcile when it lands, tracked in the Review queue:
- Source patterns differ: Android has the inline
ThinkingSegment(italic + muted prose) and theToolSegment(a tonal inset + hairline), but neither is a reusable aside. Voice has theSettingsCardeyebrow + theInfoTippopover, but no in-content note. This page proposes the shared one. importanttone color: this is the one place cyan is used editorially (brand emphasis, not status). The warm tones map to status tokens; one cyan-vs-status mapping should be canonized so callout and banner stay legibly different.- Quote treatment: the
quotetone reuses Android’s italic + muted reasoning style; Voice/web would need a matching italic prose style + a quote glyph token.