‹ ALL SURFACES

The Salt House · Draft 2

25 · TICKETS

TICKETS — the docket · lifecycle categories in declared order, product statuses as sub-headers · unknown statuses file under the fallback, never dropped · unknown types coerce to bug, shown with their raw value · the resolver never invents

THE DOCKETstory-widgets10 tickets · 7 open
triage2
Triage
#6?Seal Ledger: liveSeals() projection upstream?round 13 quarry → engine stream0dtk_2a6c8…
Blockedunknown status — filed under the fallback category, never dropped
#9·!Engine repos read-only — enforce in CIhouse rules → unassigned1dtk_0d7a4…
backlog2
Backlog
#3+–Grammar-aware completion for the Caretroadmap → unassigned2dtk_c530a…
#4+˘Witnessable-region shading on the Moment Sheetoperator@agileworks.ca (email fallback) → unassigned3dtk_77e4c…
unstarted1
Todo
#5·–Port the per-widget drive scripts to scripts/cdp.tsround 16 → unassigned0dtk_e19b3…
started2
In Progress
#7+!Tickets docket (this widget) — build + drivethe loop → the loop0dtk_b8d1f…
In Review
#8✗was:rfc˘Second platform surface after launchpadoperator → the loop0dtk_5c3e9…
completed2
Done
#2✗‼Caret: landing a batch wipes the ink receiptCDP drive → the loop0dtk_4b81d…
#1✗!Masthead surface count drifts from TABSfleet drive → the loop0dtk_9f2e7…
canceled1
Canceled
#10·Thumbnail-truth pass each build roundround 8 → unassigned0dtk_31f5b…
RESOLVE A STATUS
the tickets board, re-expressed: the lifecycle table (status name → closed category enum, in declared order), the type coercion (unknowns become bug, shown with their raw value), the resolve discipline (reporter falls back to the denormalised email; the assignee never falls back), server-owned stamps, and the 8-char id truncation are the BFF's own rules (kv2-tickets, cited in types.ts) · priorities are typographic marks, not colors — the docket's one amber is the started category rail

the second platform re-expression: the tickets board's own rules (kv2-tickets, cited by line) as a docket — lifecycle categories in the status set's declared order, product statuses as sub-headers, rows by priority then sequence · the meta-docket: these are the loop's own tickets about this gallery · #9's status is 'Blocked', unknown to the product — it files under the fallback category with a red note, never dropped; #8's raw type is 'rfc' — coerced to bug and shown with its raw value, the guard.rs rule made visible · the reporter of #4 renders by email fallback; unassigned tickets say so, because the assignee never falls back · filter by type, and type into RESOLVE A STATUS — Done, in progress, anything — and watch category_for answer with a declared category or the fallback, never an invented enum value · the one amber rail marks started · flip LIVE and the docket renders a read-only snapshot of the kapable org's real tickets through the same rules, ages derived from the snapshot instant