Demo seed data — the product working on first boot

[os-warren]

pnpm dev on an empty database should show a system that is obviously working, not five empty grids. This is the first thing every evaluator sees.

Blocked-by: #1 (period keys must be spelled by the shared engine, not hand-written).

Files you own

• src/data/*.seed.ts (new), added to dulySeeds in src/data/index.ts
• test/seed.test.ts (new)

Use defineSeed. Do not touch objectstack.config.ts.

What to seed

Org. A three-level sys_business_unit tree — one company, three sites, two teams under one of them — with manager_user_id set at each level so hierarchy scopes have something to resolve.

People. ~12 sys_user records with manager_id set, spread across the units. Ordinary names, plausible emails on a clearly fictional domain.

Catalog. ~20 duly_catalog_item rows across 3 position codes, with a realistic frequency mix: several monthly, a few weekly, two quarterly, one semiannual, two annual, and two standing. Fill regulation_ref on most of them — it is what makes the catalog read as an audit answer rather than a to-do list.

Duties. Instantiate the catalog onto the people. Include a handful of source: 'self' duties so the caliber split is visible, and at least one paused duty.

Tasks. Backfill roughly 6 months so the views are not all empty. Deliberately include:

• a majority done, so the on-time rate is plausible rather than either 0% or 100%
• 3–4 late tasks (past due_date, still open) so the Late view has content
• 2–3 stalled tasks (open, last_update_at older than 14 days) so the Not-moving view has content
• one skipped with a real reason
• tasks spread across units, so unit rollups differ from each other

Assignments. Two, one fanned out to four people with mixed completion, one with needs_collection.

Work log. ~15 duly_log_entry rows for two of the people, mostly private. They exist to show the module, and to demonstrate that nothing about them feeds a metric.

Rules

• Period keys must come from the period engine (Period engine — period keys, boundaries and due dates, timezone-correct #1), not be typed by hand. A seed with a hand-spelled 2026-W4 instead of 2026-W04 teaches the wrong spelling to everyone who copies it.
• Standing duties must have zero tasks. If your seed produces one, the dispatcher contract is being broken in the fixture.
• No real company, person or regulation names.
• Nothing in the seed may imply a ranking or comparison of item counts between people.

Acceptance

• pnpm dev on an empty DB renders every view in the app with non-trivial content
• My week, Late, Not moving and Calendar are each non-empty for at least one seeded user
• no duly_task exists whose duty is form: 'standing'
• re-running the seed on a populated DB does not duplicate

Gates

pnpm validate && pnpm typecheck && pnpm test && pnpm build.

[os-warren]

Blocked-by: #32 — added by the PM after round 1, before this card is dispatched.

#3's dev established that a duly_task cannot be inserted directly in status: 'done': completed_at is readonly, beforeInsert stamps only last_update_at, and completed_at_required_when_done therefore refuses the insert for any non-system caller.

That is correct for the dispatch path and fatal for this one. This card asks for ~6 months of backfilled history with a majority done, plus late, stalled and skipped rows. None of the completed ones can be written until #32 settles how a seed writes history — and the failure would not be subtle: every view this seed exists to fill would come up empty, which is the opposite of the card's whole purpose.

#32 is queued and is expected to resolve as "a system-context insert may carry completed_at, a caller's may not". Whoever takes this card should read #32's outcome first and use the sanctioned path, not work around the rule.

---

Generated by Claude Code