Prove onboarding from a clean machine profile
The setup succeeds only on long-lived developer machines that already contain undeclared packages and cached service state.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Onboarding automation · Reproducibility · Performance analysis
Estimated field mix
- DevOps70%
- Developer tooling30%
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.
- DDEV-101 · Turn the setup notes into one preflight report
- DDEV-102 · Start local services only after validating port ownership
- DDEV-103 · Apply migrations exactly once during concurrent bootstrap
- DDEV-104 · Seed deterministic accounts without creating duplicates
- DDEV-106 · Report readiness by dependency instead of waiting blindly
- DDEV-107 · Support an offline bootstrap from a verified local cache
- DDEV-105 · Reset only resources created by this workspace
- DDEV-108 · Keep Windows and POSIX commands behaviorally equivalent
- DDEV-109 · Diagnose local startup without collecting source or secrets
Acceptance criteria
- Test starts from a declared clean profile with empty workspace-owned state
- Online and prepared-offline paths produce the same fixture application behavior
- Duration report separates downloads, builds, migrations, seeds, and readiness
Implementation constraints
- The profile is a local disposable fixture, not a production host image.
Verification to include
- Complete onboarding twice from clean profiles and compare outcomes.
- Remove one declared prerequisite and verify preflight fails before mutation.
Deliverables
- Clean-profile onboarding rehearsal and timing report
Rollout and recovery
Use the rehearsal in documentation review before changing team onboarding policy.
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.