Work Items — the agentic board

This is Dossier's own work-item board, authored in the same OKF format the platform produces for clients. Each file under tasks/ is one atomic `task` concept; the git board — not any agent session — is the source of truth (Agentic "sprint board" architecture — a git-resident OKF task board worked by bounded, hook-governed Agent SDK loops §2). State (status / claimed_by / lease_expires) lives in each atom's frontmatter and changes via frontmatter edits + git commits. There is no separate claims table or lock service.

The lifecycle

backlog → claimed → in_progress → review → done, with blocked as an off-path state. The baseline lifecycle is the convention; status is free text by design so verticals can extend it (the schema does not hard-enum it). See Dossier — The Knowledge Model (v0) § "The task type".

Coordination (claim / lease)

claimed_by + lease_expires are the v1 coordination pair. A PreToolUse hook (host process, outside the context window) denies a tool call that would breach a live lease and treats an expired lease as reclaimable — governance is deterministic (hook verdict), not model-trusted (Agentic "sprint board" architecture — a git-resident OKF task board worked by bounded, hook-governed Agent SDK loops §5). Not yet built — see Build the PreToolUse claim/lease governance hook.

The live board

The board is rendered live from the atoms under tasks/: the read-only /board surface (now in @dossier/app, Migrate chrome-light app surfaces to SvelteKit; docs stay on Astro/Starlight (two apps, one origin)) reads every type: task file and shows its current status / owner / claim straight from frontmatter. This index deliberately does not mirror per-task status — a hand-maintained table here would become a second, drifting copy of the truth that lives in each atom (the exact drift Agentic board v1 — build the git-resident OKF task board (deterministic offline core, SDK reserved), resolving DEC-0024's four open questions and dogfooding Dossier's own repo first's ## Review flagged; a seed-time snapshot table sat here until 2026-06-17 and had gone stale).

To read the current board, open /board or the files under tasks/. Every create / claim / transition / completion is recorded chronologically in Task Board — Audit Log — that log, the atoms, and the rendered surface are the single source of truth; this page only frames the model.

Dependencies are an ordering hint, not a transitive hold. A dependencies edge says "this should probably go first" — it never auto-blocks or cascades. Agents and humans check and decide. Dangling deps are graph-lint findings, never board breakers.

Conventions

• One task per file. Ids take a task-… prefix so they never collide with decision/role ids in the route map; ids are immutable (retire via status: done, never rename/delete).
• Provenance always. Every task carries source (how it was created), confidence (asserted when human-curated, inferred when agent-generated), timestamp (last meaningful change).
• Changes to this board are recorded in Task Board — Audit Log.