Preparing the reference
KIN Design System
Interfaces for consequential work.
A design contract for products where source, state, decision, and recovery must remain visible.
Four product contexts
One system. Four kinds of work.
KIN changes its composition with the task. Reading, investigation, operations, and precision editing do not share one dashboard template.
Read with provenance
INF-01 · Stable source · Showcased
Keep the record, source, revision, and next related item in one reading path.
Investigate before deciding
INT-02 · Stable source · Showcased
Compare chronology, conflicts, and uncertainty without collapsing them into one score.
Operate with context
COM-02 · Stable source · Showcased
Keep price, inventory, channels, approval, and history distinct while editing.
Build with precision
ENG-01 · Stable source · Showcased
Let the canvas lead while tools, selection, properties, and recovery remain available.
One continuous task
The interface keeps the thread.
A task should remain legible from entry to action, including the evidence used, the result recorded, and the limits that remain.
Entry
An analyst opens an entity investigation from a queue or direct URL.
Work
Evidence and event chronology.
Commitment
The analyst records an attributable finding or leaves the investigation unchanged.
Known limit
The local fixture has no live sources, authoritative permission service, or durable finding record.
Following Investigation and Evidence Review
Explore the component systemBuilt to be inspected
The proof is available when you need it.
Normative contracts, runnable fixtures, generated artifacts, and verification records remain separate. The public surface stays focused; the evidence stays one step away.
Catalog and release evidence
18Showcased scenarios
13Planned scenarios
65Stable component contracts
11Stable page families
Light · Dark · System · More contrastNamed appearance modes, not a quality score