Fictional training simulation. D2V Mock is an invented training organization. All people, data, incidents, and documents are fictional. Any resemblance to a real entity is coincidental.
DTV-ATLAS-V1.0 · GUIDED MODE
ACTIVE MISSION
Learn by making
the deployment decisions.
Move through eight stages. Inspect evidence, produce field artifacts, record assumptions, revise after a hidden complication, and defend a final rollout decision.
01 / APPRENTICESHIP SEQUENCE
Learninspectdecideproducereviewrevise.
Each stage adds just enough instruction to support the next field decision. Later stages unlock after you commit earlier work.
01DISCOVER
Orientation
Separate the executive request from the operational decision.
OPEN 02DISCOVERStakeholders
Map authority, incentives, data ownership, and conflicts.
OPEN 03DISCOVERWorkflow
Reconstruct how delay investigations actually happen today.
OPEN 04FRAMEProblem frame
Define the actor, decision, evidence gap, and consequence.
OPEN 05DESIGNSolution design
Specify the minimum deployable workflow and architecture.
OPEN 06BUILDWorking slice
Implement the bounded operational workflow and failure states.
OPEN 07ADAPTComplication
Revise when a core data and identity assumption fails.
LOCKED 08MEASUREValue review
Interpret mixed pilot evidence and recommend what happens next.
LOCKED02 / CORE METHOD MAP
Use 7 Core Labs inside one deployment record.
Freight is the flagship integration mission: workflow, evidence, evaluation, production failure, drift, disagreement, and tool semantics all have to coexist under one customer timeline.
Should the shipment-risk workflow move from pilot to broader operational use, and under what data and authority conditions?
Shipment, vessel, port, booking, and cost sources disagree on identity, timing, and exposure while operators still need a decision before the data is perfect.
Scale, narrow, revise, continue the pilot, or stop — with an explicit identity policy, failure behavior, adoption evidence, and value case.
CORE METHOD → PRACTICE
All 19 Core Labs →Review the boundary only when you need it.
Evidence room
Stakeholder interviews, operating documents, dirty data, security notes, and pilot evidence.
Inspect evidence →Mission notebook
Track facts, claims, assumptions, open questions, decisions, and risks throughout the mission.
Open notebook →Artifact studio
Build structured, revisioned artifacts directly in D2V Mock Freight without uploading files.
Build artifacts →03 / LEARNING STANDARD
The system should challenge your reasoning, not reward page views.
Completing D2V Mock Freight means producing coherent evidence across discovery, technical judgment, deployment, adoption, and value—not merely checking boxes.
01Short lesson
Learn the field concept at the moment it becomes useful.
02Customer evidence
Inspect incomplete, conflicting, and occasionally misleading inputs.
03Decision
Commit to a position and make your assumptions visible.
04Artifact
Produce the document or system an actual deployment requires.
05Revision
Respond when later evidence invalidates part of your design.
PORTFOLIO EXPORT
Export your structured portfolio.
Download the current D1-backed portfolio as a standardized Markdown document.
Testing the experience? Resetting removes learning progress, notes, and stage responses. Native portfolio artifacts are managed separately.