fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

agents: correct "both clocks" -- there is ONE, and F4 tests whether it is right

Browse Source 
I wrote "whether the game snaps both clocks forward" into yesterday's F4 and the
human asked which clocks. There are none: authored/flow.json sets
`clock: "shared"`, so the title's two composited builds -- build 4 the artwork
(finishes t~=118) and build 2/3 the plate (full alpha t=236) -- run on ONE clock
started together. Left standing, that phrasing sends an agent hunting for a
second clock this corpus says does not exist.

Corrected in both briefs and in the playtest page, marked as a correction rather
than silently edited.

And the question is better than I first framed it. `clock: "shared"` is
AUTHORED, and the port's own plate-arrival-halves.md calls it "not falsified...
not confirmed to better than ~20 % either", with an unresolved anchor
disagreement inside one binary: the reconciliation picked t=118 while
settle_time() returns 160 and the boot prints "settles at t=160".

So F4 is a TEST OF THAT PREMISE, and the discriminator is observable -- press (A)
early, while the wordmark is still building in, and watch the ARTWORK rather
than the plate:

  advances the shared clock   -> the artwork SNAPS to finished
  only forces the plate       -> the artwork KEEPS ANIMATING its build-in

Both briefs now say to answer F4 before building on `shared`, and tell the port
not to choose what "jump" means.
This commit is contained in:
MechaCat02
2026-09-02 18:39:13 +02:00
parent 06f890361b
commit de5f04038d
3 changed files with 56 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
docs/agents/decoder-loop.md
View File

@@ -62,14 +62,30 @@ because the port is blocked on two of them.
the plate appears or when Ⓐ is accepted? ⚠️ A negative needs a positive
control (R4): show the method finding the *menu's* cue before concluding the
title has none.
4. **F4 — WHAT DOES Ⓐ DO TO THE CLOCKS?** In the real game, Ⓐ during the title
4. **F4 — WHAT DOES Ⓐ DO TO THE CLOCK?** In the real game, Ⓐ during the title
build-in **reveals the plate immediately** — so the boot takes three presses:
skip video, reveal plate, accept plate. Does the game snap both clocks
forward, or only reveal the plate? 📌 This is also a **cheap second route to
the plate-arrival question**: a press that skips to the plate tells you where
the game thinks the plate belongs. And it is a third input the boot title
accepts, which narrows `REFUTED.md`'s *"any title after the first refuses
input"* further.
skip video, reveal plate, accept plate.
🔴 **This is a test of `clock: "shared"`.** The title is two composited builds
— build 4 the artwork (finishes `t≈118`), build 2/3 the plate (full alpha
`t=236`) — and the port's `authored/flow.json` runs them on **one** clock
started together. That premise is **authored**, and the port's own
`plate-arrival-halves.md` calls it *"not falsified… not confirmed to better
than ~20 %"*, with an unresolved anchor disagreement inside one binary
(`t=118` from the reconciliation, `160` from `settle_time()`).
The discriminator is observable: **press Ⓐ early, while the wordmark is still
building in, and watch the ARTWORK, not the plate.**
| if Ⓐ … | the artwork |
|---|---|
| advances the shared clock | **snaps** to finished |
| only forces the plate visible | **keeps animating** its remaining build-in |
📌 It is also a **cheap second route to the plate-arrival question** — a press
that skips to the plate says where the game thinks the plate belongs — and a
third input the boot title accepts, narrowing `REFUTED.md`'s *"any title after
the first refuses input"* further.
⚠️ Deliver a **series, not a settled value** — see
[`TEMPORAL-VERIFICATION.md`](TEMPORAL-VERIFICATION.md), and note that the port's