Mode disclosure
All modes use one coherent workspace; only disclosure and guidance change. Project mode keeps the persistent brief, milestones, notes, saved intermediate queries, validation checklist, and report export together.
Parcel Operations Reliability Investigation / capstone step
P03-S01 - Parcel Operations Reliability Investigation: Operational schema map
Operational schema map. An operations team believes delivery reliability worsened. The learner must reconstruct event journeys, calculate SLA performance, and isolate operational bottlenecks without trusting denormalized status fields blindly.
- Result grain
- one row per Parcel Ops table in the schema map
- Exact columns
- table_name; row_grain; key_columns; reliability_role
SQL editor shortcuts: Ctrl or Command Enter runs the query, Ctrl or Command Shift Enter checks it, Alt H opens the next hint, Ctrl or Command slash toggles a line comment, Ctrl or Command Shift F formats the SQL, and Escape closes transient UI.
Cursor at line 1, column 1.
Project Evidence Contract
- Grain declaration
- one row per Parcel Ops table in the schema map
- Key uniqueness
- table_name is unique in the operational schema map.
- Dependency gate
- First milestone
Validation Checklist
- Verify shipment, package, route, facility, carrier, service level, scan, and exception tables appear.
- Flag scans as event chronology source.
- Flag shipments as denominator source.
Required Snapshots
- operational schema map
Journey reconstruction and SLA reporting depend on these table grain declarations.
Project notes and intermediate queries
Notes and saved intermediate queries stay local to this project milestone.
Scenario
An operations team believes delivery reliability worsened. The learner must reconstruct event journeys, calculate SLA performance, and isolate operational bottlenecks without trusting denormalized status fields blindly.
Parcel Operations Reliability Investigation / capstone step
One-sentence task
Operational schema map. An operations team believes delivery reliability worsened. The learner must reconstruct event journeys, calculate SLA performance, and isolate operational bottlenecks without trusting denormalized status fields blindly.
Project mode disclosure
Persistent brief, milestones, notes, saved intermediate queries, validation checklist, and report export stay together.
Structured output contract
- Result grain
- one row per Parcel Ops table in the schema map
- Exact columns
- table_name; row_grain; key_columns; reliability_role
- Source population
- Use the prompt setup plus FROM, JOIN, WHERE, and subquery predicates as the source population. Visible rows are only examples.
- Grouping
- Do not collapse rows unless the contract explicitly asks for aggregation, distinct tuples, or set semantics.
- Ordering
- No display order requirement unless Check reports one.
- Validation
- select-only; hidden deterministic variants.
Relevant tables
Time and difficulty
- Estimated time
- 8 minutes
- Difficulty
- 5/5
Objective and concepts
Produce operational schema map evidence with SQL, validation, assumptions, and bounded snapshots.
Glossary links
Concept material
Reconstruct event journeys, calculate SLA performance, and isolate bottlenecks.
Why this works
Reconstruct event journeys, calculate SLA performance, and isolate bottlenecks.
Edge cases
Duplicate scans Same-time events Missing pickup/delivery Delivered then reopened/corrected events Exact SLA boundaries No-volume routes Reassignment Denormalized status conflict
PostgreSQL note
Project SQL runs locally with PostgreSQL-compatible semantics and project-specific hidden variants.
Assumptions, dialect notes, and common traps
- Duplicate policy
- Preserve duplicate facts unless the prompt explicitly asks for distinct tuples or set semantics.
- Null policy
- Preserve NULL, empty string, zero, and false as distinct values unless the contract says to display a fallback.
- Tie-breakers
- Use every ordering rule in the contract and end tied business metrics with deterministic secondary keys when needed.
- Zero-related entities
- Do not invent zero rows unless the contract asks for preserved parents, missing entities, or complete periods.
- Numeric tolerance
- Use exact semantic comparison unless the activity explicitly declares a numeric tolerance.
Opened hints
No hints opened yet.