Skip to main content
Stories for experienced engineers

Fictional failures. Real engineering judgment.

Plausible incidents turn the concepts you use every day into precise vocabulary you can reach for under interview pressure.

Step 1 · Pick a school

Four questions. 14 subjects.​

Schools group the curriculum by the question they answer, so you can start from the problem in front of you instead of a tag cloud.

Step 2 · Choose your depth

Beginner to Professional.​

A level describes the reasoning a story asks of you—not how obscure its vocabulary is. Beginner stories are still exact and production-realistic.

Newest story

The most recent failure we wrote down.

The narrative carries the intuition. Definitions open only when you need precision.

School IVHow intelligent systems are built and governedBeginner

The package no technician had inspected

PackProof inspected every package through six cameras. Its weekly training table still invented physical evidence for packages no technician had examined.

Subject
11 · ML systems and decision quality
Content area
Label, outcome, and observation contracts +1 more
Outcome, observation, and labelUnknown versus negative labelLabel availability timeLabel lineage and revision
The curriculum

Four schools. 14 subjects. One visible production state.​

Research depth and story coverage are tracked separately, so you can see what has been mapped, explored deeply, commissioned, and published.

Open the curriculum status
01

Meet the problem first.

Business impact before vocabulary. The naive choice should feel reasonable.

02

Watch it fail.

A metric moves. A log line appears. The concept earns its name.

03

Open the definition.

Expand exact wording inline, then close it and stay in the story.