Dashboard Lesson Hall

Operator Academy

An interactive training surface for strengthening how you operate Codex, OpenClaw, memory, automations, and routing. The point is not to absorb more concepts. The point is to make the live system narrower, truer, and easier to maintain.

Open lesson source Return to world dashboard

Lessons ready0

Exercises cleared0/12

Challenge accuracy0/12

Monthly audit rhythm

Report-only, first 7 days of the month

The `Monthly Operator Audit` automation is now the strategic drag check. Use the audit to see where the system is widening, then use lesson work or an Operator Reset session to reduce it.

Open monthly prompt

Week 1

Truthfulness Over Completeness

In progress0/3 correct

Learn to cut active claims faster than you add new system surface area.

ObjectiveBuild the reflex to classify what is actually live instead of letting documentation imply more health than the runtime proves.

Your main drag is not lack of intelligence or standards. It is allowing the system to remain wider than the evidence supports. This week trains ruthless honesty about current state.

Coach promptUse this lesson with Codex

Copy the lesson-specific coaching prompt or open the source docs that back this lesson.

Open lesson doc

docs/operator-behavior-audit-standard.md docs/prompts/operator-reset.md docs/system-governance-standard.md

Exercises

Do the work, not just the reading

Label the system surfacesClassify the major operating surfaces as `live`, `degraded`, `parked`, or `historical` without inventing softer labels.Find the top 5 overclaimsName the surfaces where docs, prompts, or active status imply more health than current evidence supports.Require proof for activenessFor each active automation or canonical claim, check whether a fresh artifact trail actually exists.

Interactive checks

Pressure-test your judgment

An automation is marked ACTIVE, but its memory trail is 23 days old and there is no fresh deliverable or dashboard evidence. What is the most honest label right now?

A doc says a memory layer is canonical, but the files are stale and not being curated. What is the correct operator move?

You discover a useful new workflow while several current surfaces are already stale. What should dominate the decision?

Deliverables

Visible outputs

A status map of live vs degraded vs parked vs historical surfaces.A shortlist of the top 5 overclaimed surfaces in priority order.

Pass criteria

What good looks like

Every important surface has a hard status label.

At least one overclaim is named directly instead of softened.

You can explain why a surface is active using fresh proof, not memory.

Reflection

Write the uncomfortable truth

Where did I confuse “documented” with “operational”?

Which surface is costing me the most credibility or attention simply by being overclaimed?

Confidence

Rate this habit

3 / 5

Score how confident you are that this behavior is becoming a habit instead of a one-off cleanup.