A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I1600
The challenge is one recorded run, and every public surface replays it
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
3of3
Moves
plan.transitionWhat it is
- Objective
- Record one scenario in which a worker strays outside its scope, claims it is done, hands over, and is refused until the repository's own test passes; render that run on the homepage and on /challenge/; make README.md's first transcript a step of it; and verify the public site serves it after publication.
- Why
- The tool's differentiator is what it refuses to accept, and the site showed that only as disconnected command illustrations. A newcomer needs one story, and a link from outside needs a page. Every public sentence about it must stay a projection of a run that happened, which is why each surface is held to the recording by a gate.
- Now
- No use case shows check refusing a file outside scope, because a scenario step could only invoke the tool. The homepage hero is the lifecycle console. There is no /challenge/ route. README.md's first block is hand-written. catalogue.json carries no scenario, so maturity reads described everywhere.
- Wanted
- Use case catch-an-agent-that-says-it-is-done runs with worker steps; site/data/generated/challenge.json is its run; /challenge/ and the homepage replay it; site-check, the derivation and scripts/pages verify --smoke hold each surface to it.
- Done when
- unknown: the record declares no `completion`
- Risk
- The derivation now runs one more scenario and the homepage replaces its hero console; the console moves under how it works rather than leaving, so the gate that holds every recorded lifecycle panel to the homepage is unchanged.
Acceptance
- usecase validate refuses a worker step in a live scenario, beside run, and without an exit code
- the challenge scenario's recorded run shows a scope refusal, a finish refusal on a failing verification, a handover resumed through context, and an accepted finish
- scripts/site-check fails when /challenge/ or the homepage misses a recorded line, renders a different number of steps, or does not link a guarantee a comparison row stands on
- scripts/generate-site-data refuses a challenge that does not pass, refuses nothing, does not end accepted, leans on a claim that is not guaranteed, or whose README transcript is not a recorded step
- finish prints one blocking doctrine per line
- Validation
bash test/run.sh 632_a_scenario_shows_the_worker_it_judgesbash test/run.sh 103_obligationsscripts/generate-site-data --checkscripts/site-check- Evidence required
challenge_recordedsite_holds_the_runpublic_site_serves_it- Evidence present
challenge_recordedsite_holds_the_runpublic_site_serves_it
Scope
- Touches
lib/usecase.shlib/finish.shshare/schemas/majordomus/use-case.ai/repo/use-casestestscriptssiteREADME.mddocs/USE_CASES.mddocs/LAUNCH.mddocs/README.md.ai/repo/ci/pages.yaml.github/workflows/pages.yml- Not
Analytics, testimonials, adoption numbers, or any claim the repository cannot derivePer-page generated social images- Depends on
- none
- Priority
- p1
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-15
- Updated
- 2026-10-11T04:40:59Z
- Started
- 2026-10-11T04:18:57Z
- Verified
- 2026-10-11T04:40:44Z
- Completed
- 2026-10-11T04:40:59Z
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.