0→1Technical Fluency
The Story Path/Act IV of IV

The Week After

The week afterThe missing split, the audit, and the machinery drawn in full.15 scenes · ~40 min

A missing split nobody can explain, an audit, and the machinery finally drawn in full.

Previously

3 claims the story has made so far, with a piece of each left out. Reach for it before you read on; if you have not met them yet, the answer tells you where they happened.

  1. Sam's 1:14 a.m. lesson from the load test: adding capacity anywhere except the blank changes nothing.

  2. At 10:52 the map went coarse so timing could stay perfect. Dropping the optional to protect the essential is blank.

  3. Sunday asked a question nobody had predicted, and the answer was findable on the spot. That property is blank.

The scenes

  1. The empty cellTuesday, 9:00 a.m. Row 11208, one cell holding nothing.2 min
  2. The suspectsTwo alibis, one twist, and a doorman who never saw the guest.3 min
  3. Ask the backupWednesday standup. The hopeful question gets a real answer.2 min
  4. What the photos knowA million frames, each carrying a hidden second photograph.2 min
  5. The audit arrivesThree lanyards, one laptop, and nobody asks for a password.3 min
  6. People and machinesThursday opens with a login, and the striking part is what Finn does not type.3 min
  7. The padlock, openedA promise from Act I, kept at last.3 min
  8. FingerprintsShow me one runner's password. Nobody can, and that is the pass.2 min
  9. What we keepFriday opens with a compliment and closes with an inventory.3 min
  10. The second mysteryMonday. A five-hour runner, a 3:58 projection, and a box never opened.3 min
  11. The assistantEleven words in the help widget, and everything they ride on.3 min
  12. Wrong, with confidenceTuesday, 8:40 a.m. Exhibit A: a policy that never existed.3 min
  13. GroundedWednesday's fix does not touch the model at all.2 min
  14. Another LedgerlineWhere the assistant lives: nowhere in the building.3 min
  15. The whole machineFriday, twelve days after the gun. Forty minutes, no interruptions.3 min

What lights on your story map here

0/60concepts lit

one cell per scene · width is its conceptsreading a scene lights its cell

51 fluency — say them in a meeting1 recognition — nod when you hear them8 named technologies

Show all 60, scene by scene
NULLdata qualitydata validationduplicate dataPostgreSQLMongoDBbackuprestoremetadataidentitypermissionrolerole-based access controlleast privilegesession mechanicstoken mechanicssingle sign-onmulti-factor authenticationservice accountencryptionencryption in transitencryption at restTLSpublic keyprivate keyhashingencodingkey rotationvulnerable dependencypersonally identifiable informationdata retentionartificial intelligencemachine-learning modellarge language modeltraininginferenceGPUSnowflakeKafkaSparkprompttoken (LLM)context windowoutput generationhallucinationprobabilistic behaviorevaluationguardrailshuman reviewfine-tuningretrieval-augmented generationembeddingsAI APIAI as a third-party serviceAI latencyAI costAI privacy considerationsReactNode.jsDjango

Act IV — the boundary

The half-second at the matAll of it at once

480 msMolly's phone shows the split.

  1. 0 msThe chip wakes inside the mat's field.
  2. 2 msIt sends one number: 11208.
  3. 9 msThe mat's reader asks Traversal to record the crossing.
  4. 31 msTraversal writes the split down, and it stays written.
  5. 34 msThe write joins a queue, so nothing waits on what comes next.
  6. 38 msTraversal answers the reader: recorded.
  7. 120 msA worker takes the split off the queue.
  8. 190 msThe leaderboard's cached copy is refreshed.
  9. 240 msThe projected finish is recalculated.
  10. 300 msA notification fans out to everyone following 11208.
  11. 480 msMolly's phone shows the split.

The whole half-second, all 11 steps of it.

At 240 ms the projection updates, and at 300 ms the notification fans out. Reading the mat's steps one last time, which parts of the half-second happen inside someone else's service, where Traversal's control ends at a contract?