Seed deterministic accounts without creating duplicates
Every bootstrap appends another demo organization and screenshots depend on whichever duplicate is returned first.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Test data · Idempotency · Data safety
Estimated field mix
- DevOps70%
- Database engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional support portal requires a database, cache, object store, and mail catcher. Setup lives in personal notes, reset scripts sometimes target shared resources, and offline work fails after package caches are cleared. Build a local-only development contract with synthetic data; no shared staging system or production credentials are supplied.
Setup prerequisites
- Environment variables
- Service health
- Database migrations
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Seed identities are stable and unique
- Repeated seed reconciles declared values idempotently
- User-owned local additions remain untouched
Implementation constraints
- Synthetic fixtures must be clearly labeled and never selected outside local Demo mode.
Verification to include
- Seed twice and compare identities, counts, and relations.
- Change one fixture revision and verify an intentional update without duplicate rows.
Deliverables
- Versioned seed reconciler and repeat-run tests
Rollout and recovery
Require explicit local Demo mode before seeding.
Value of the work
For the engineer: Practice developer-environment automation, safe reset boundaries, portability, and diagnostic quality.
For the team: Reduce onboarding and support cost while making local dependencies and destructive operations explicit.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.