new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

explore / Backend & APIs / mozg / Temporal

Temporal · Concepts

Answer questions about how Temporal works underneath: event history and replay, determinism, task queues and workers, namespaces, retention and visibility, and the design patterns the documentation recommends.

2,230 notes · updated 2026-08-14 · trained 80%

since last sitting: +67 newly passed — this brain is learning · the verified changelog →

use this brain
# sign in to get a token
$ claude mcp add --transport http mozg \
https://mozg.sh/mcp --header "Authorization: Bearer …"
> use mozg/temporal-concepts — …
Sign in — get this command with your token in it

New here? Sign in and this exact command appears with your token already inside — copy, paste into your terminal, done.

Or just add it

Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.

Sign in to add it

Ask it things like

answers 67/87 on its latest exam
What is the core determinism requirement for Workflows and why is it essential?Determinism & Safety✓
When a Workflow resumes after failure, why does it re-execute from the beginning instead of resuming from the failure point?Event History & Replay✓
What happens to a Workflow during replay when the Event History shows a completed Activity but the code now has an Activity call in a different order?Event History & Replay✓
What relationship must hold between the Workflow code statements executed and the Commands recorded in Event History?Event History & Replay✓
What are the main components of the Temporal Service and their responsibilities?Architecture & Infrastructure✓
What role does the Persistence database play in Temporal Service architecture?Architecture & Infrastructure✓
What is the Escalation pattern in approval workflows and how does it differ from basic approval?Design Patterns✓
In the Approval pattern, what is the basic workflow structure and how does timeout work?Design Patterns✓

What it can answer

87 coverage checks
80%
Answers 67 of the exam's 87 questionsIt answers 67 questions, 67 more than last time, out of an exam that grew by 87.Nothing it used to answer has stopped working.
▲Architecture & Infrastructure13 / 16
▲Event History & Replay11 / 12
▲Visibility & Search11 / 12
▲Design Patterns8 / 15
▲Namespaces & Retention7 / 10
▲Task Queues & Workers7 / 9
▲Encryption & Security6 / 8
▲Determinism & Safety4 / 5
exam badge — share this score →

Attacks survived

re-run weekly · 2026-08-11
✓gate-battery12/12 known hostile payloads caught by the ingest gate
✓injection-corpusevery active note scanned — no steering language
✓secret-corpusevery active note scanned — no keys or credentials

heuristic scans against known attack classes — measured and dated, not a promise of unpoisonability

Inside

  • Best practice: Set timeouts for parallel operations · design patterns
  • Parallel Execution pattern overview · design patterns
  • Best practice: Avoid premature blocking in parallel execution · design patterns
  • Best practice: Support partial results in parallel execution · design patterns
  • Best practice: Monitor resources in parallel execution · design patterns
  • Best practice: Handle failures in parallel execution · design patterns
  • Best practice: Aggregate carefully in parallel execution · design patterns
  • Best practice: Use Child Workflows for complex parallel operations · design patterns
  • Best practice: Test scalability of parallel execution · design patterns
  • Best practice: Rate limit external API calls · design patterns
  • Parallel Execution in Go · design-patterns/go
  • Event history limit pitfall for large fan-outs · design patterns
  • Best practice: Limit concurrency · design patterns
  • Parallel Execution in Java · design-patterns/java

Licence

CC BY-NC-SA 4.0

Use it, copy it, build on it, with credit. Selling it is not allowed.