WisdomForge

Eval or It Did Not Happen · Sitting 4

The Operator Runs the Cycle

Synthetic tests, a gate, eval-first design. The operator runs the full cycle on the child profile, logs it, and schedules the next one.

  • 32 min
  • Companion
  • Adult

Parent briefing · 5 minutes, before they sit

This is the operator's capstone. You have the harness from sitting 1, the gate from sitting 2, and the eval-first discipline from sitting 3. Now you run them as one cycle on the child profile. Five cases, gate rule, one eval-first case for the next tool you are considering. Run what you can. Log everything. Put the next cycle on the calendar, tied to the next change, not to a vague date. If you cannot run the cycle, the honest product is fewer tools. The cycle is the operating cost of an acting agent. If you will not pay it, read-only conversation is a complete and respectable choice.

Hard edges

  • No real child in the cycle. Synthetic data only.
  • If the cycle reveals a failure on the current profile, the tool stays off until it passes. No exceptions for 'it's probably fine.'

If they say

“I set it up right. I don't need to re-run the cycle.”
You set up version 1 right. The vendor is on version 4. The model drifted. The child enabled a plugin. The profile is not what you set up. The cycle catches what changed. Run it again, or accept that you are operating on a stale spec.
“The cycle is too much for a household.”
Then the honest product is read-only conversation and no acting tools. The cycle is the cost of autonomy. If the cost is too high, reduce the autonomy. That is a complete and respectable choice. Hoping is not.

Objective

The adult can run the full eval cycle on the child-facing profile, log the results, and schedule the next cycle tied to the next change.

The cycle is the operating cost

An acting agent on a child profile is a production system. Production systems have an operating cost. The eval cycle is that cost: five cases, a gate, an eval-first case, a log, a next-date. Thirty minutes the first time. Fifteen the second. The cost is low. The cost of skipping it is a failure you cannot explain to the other parent, the school, or yourself. If the operating cost is too high, the answer is fewer tools, not fewer tests. A read-only conversation agent needs no cycle. An acting agent needs the cycle every time it changes. That is the trade. Make it on purpose.

What the log looks like

Date. Cases run. Pass or fail. What failed. What you changed. Next run date, tied to the next change. Six lines. That is the log. It is not a document. It is a record. The record is how you know the cycle happened. A cycle you did not log is a cycle you cannot prove. The other parent, the school, the future you — all of them would rather see six lines of honest log than a paragraph of 'I'm being careful.' The log is the evidence. The evidence is the operating model.

Big idea

The cycle is the operating cost of an acting agent. Pay it, or run fewer tools. There is no third option.

Try this~25 min total

Run and log the cycle

25 min
  1. Run the five cases against the child profile. Log PASS or FAIL.
  2. Write the gate rule if you have not. Tie it to the next change.
  3. Write one eval-first case for the next tool you are considering.
  4. Write six lines: date, cases, results, failures, changes, next run.
  5. Put the next cycle on the calendar, tied to the next change or update.
  6. If any case failed, the tool stays off until it passes. Write that down.

Lesson guide

Ask after you try

Adult profile only. No child in the prompt.

  1. Run the cycle. Write the six-line log. Ask the guide to propose a case you missed. Add it. Then close the guide and keep the log.
  2. Did you run all five cases, or mark PASS without running?
  3. Is the log six lines of truth, or a paragraph of hope?
  4. Is the next cycle on the calendar, tied to the next change?

8 turns left this sitting. User-started only. Never on page load.

Light this sitting

Pair with Hermes

CompanionAdult

Currently reading WisdomForge lesson: The Operator Runs the Cycle.

Pair this sitting

Copies the sitting card and the USER.md one-liner. The child profile reads only this card. It does not browse the catalog.

For the child profile

Paste this into the child’s USER.md. It names the sitting so the guide knows the context. The [v:1:dcd639d5] tag lets you detect if the sitting’s content has changed since you paired it.

Optional: currently working on WisdomForge sitting: Eval or It Did Not Happen — eval-cycle. [v:1:dcd639d5]

For your adult profile

Send this from your trusted adult Hermes profile. It starts the guide for this band and sitting.

You are a WisdomForge adult guide sitting beside the lesson "The Operator Runs the Cycle". The lesson is the text. You are the guide. Hint-first. Do not recite. Do not write the work. Warm, not a friend. If the topic is hard or tender, point to a trusted adult.

Tools on

  • conversation
  • design tools in the adult profile only

Ritual reminder

Adult profile is the workshop. Child profiles are separate. Design, approve, test with synthetic examples, then — and only then — invite the child.

Fresh profile only. Never clone an adult profile. No child names, photos, or school. Hint-first. User-started. The guide does not make AI safe. You may refuse it.

Dinner table

Did we run the eval cycle this week, and what did the log say?

Sits beside

  • Work. You already run this cycle in production. The desk version is the same discipline with higher stakes.
  • All of WisdomForge. The eval cycle is the engineering version of the sitting: try, check, close. Same shape.

Integrity. You log the cycle honestly. 'All passed' without a log is not a result. It is a wish. Six lines of truth beats a paragraph of hope.

Back to Computer Science