docs: the operator moved the design ownership boundary, and the fence was ours
Round 1 ruled not-as-shown: 'He didn't go far enough, still looks like the booth. I want him to consider the flow and the requirements — design touches, layout, usability all belong to him.' The handoff paragraph that said we were not asking for layout changes driven by information architecture is void. design-dev's 'class additions only, no reordering' was that constraint honoured, so the ruling corrects our brief rather than his round — worth recording that way round, because the next session reading only the artifact would read it as a design failure. Flow, layout, usability and the requirements are his now; the IA is no longer fenced off. What survives is split in two on purpose: correctness invariants that are not design opinions, and engineering defaults we chose that he may now argue with, where a dispute goes to the operator rather than being settled between agents.
This commit is contained in:
@@ -43,6 +43,22 @@ _As of 2026-09-22:_
|
||||
until now — `scripts/booth` executes it before every one of the documented
|
||||
three. Now covered by `test_stdlib_only`. Same detail file carries why
|
||||
`importlib.metadata` is the WRONG version source in this repo.
|
||||
- 🛑 **ROUND 1 RULED NOT-AS-SHOWN, AND THE SCOPE FENCE WAS OURS** (operator,
|
||||
2026-09-23): *"He didn't go far enough, still looks like the booth. I want him
|
||||
to consider the flow and the requirements — design touches, layout, usability
|
||||
all belong to him."* **The handoff's "what we are not asking for: layout
|
||||
changes driven by information architecture" paragraph is VOID** — design-dev's
|
||||
"class additions only, no reordering" was that constraint honoured, so the
|
||||
ruling corrects OUR brief, not his round. Flow, layout, usability and the
|
||||
requirements are his; the IA is no longer fenced off. Two tiers survive:
|
||||
correctness (deterministic order, autoescape, blur-admits-cosmetic, restart
|
||||
discipline) and engineering defaults he may now ARGUE with (no-JS gallery,
|
||||
virtualization parked, compare mode deferred) — tier-2 disputes go to the
|
||||
operator, not settled between agents. Relayed in full; questions 2 and 3
|
||||
(voice, emblem) remain UNANSWERED and were not answered on his behalf.
|
||||
⚠ **Calibration for the next round: his bar is "did anything change when I
|
||||
opened it".** He said the Booth "kind of looks the same" about our own U7
|
||||
navigation work, before ever seeing the design round.
|
||||
- 🔶 **SVOS CONCEPT ROUND IS UP AND THREE RULINGS ARE WITH THE OPERATOR**
|
||||
(booth `booth-svos-retheme`, ask id `svos`: ship / voice / emblem, all three
|
||||
with design-dev's recommendation attached). **Nothing from us gates it and
|
||||
|
||||
Reference in New Issue
Block a user