Boards

Boards are views over process state, not the product center. Kiket's primary surfaces are the cases queue, the findings inbox, and the evidence center; a board is an optional, columnar lens on the same workflow states for teams that want a spatial picture of where cases sit.

Each column is backed by one or more workflow states, so a board never invents its own status model — moving a case between columns fires a real workflow transition with the same guards, approvals, and audit trail as any other transition. Boards don't own data; they're pure view config in YAML.

File location

.kiket/boards/*.yaml. One file per board. A workspace can have several (e.g. Engineering sprint, Compliance tracker, Support triage).

Minimum board

key: sprint
name: Sprint
workflow: engineering

columns:
  - key: todo
    name: To do
    states: [backlog, ready]
  - key: doing
    name: In progress
    states: [in_progress]
    wip_limit: 3
  - key: done
    name: Done
    states: [done]

Every column maps to one or more workflow states. Moving a case between columns fires a transition; if multiple transitions could apply, the board picks the first declared.

Swimlanes

Group rows by a field — assignee, priority, label, case type:

swimlanes:
  by: assigneeId
  labels:
    strategy: name-then-unassigned

Swimlanes are purely visual — they don't affect workflow logic.

WIP limits

Per-column ceiling. Setting a column's wip_limit makes the board surface a warning (and optionally block) when the limit is exceeded. Useful for continuous-flow teams.

columns:
  - key: doing
    name: In progress
    states: [in_progress]
    wip_limit: 3
    wip_policy: block   # or 'warn' (default)

Card templates

Control what each card shows. Pick from a field list, or write a template:

card:
  template: |
    {{title}}
    {{#if priority}}[{{priority}}]{{/if}}
    {{assigneeName}}
  badges:
    - sla_status
    - case_type

The built-in sla_status badge is green/amber/red; case_type shows the configured icon for the case kind.

Filters

Restrict which cases show on a board:

filters:
  labels: [customer-facing]
  case_types: [bug, feature]
  assignee: "@me"

Filters are YAML-declared so they live with the board's config, not hidden in each user's browser.

Fallback columns

If you haven't written a board YAML yet, Kiket auto-generates a view from your workflow's states. That's fine for demos; you'll want a real config to use swimlanes, WIP limits, or filters — and many teams never need a board at all.

Editing surfaces

The visual board editor lets you drag columns, configure swimlanes, and wire filters without touching YAML. Every save commits to your repo.

What's next?