Let Designer implement visual-only web UI changes #138
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#138
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Outcome
Amend the canonical Designer role so she may implement, locally validate, and land changes whose only product effect is visual presentation in an existing graphical web application.
React and comparable browser UI surfaces are the intended case. This is a narrow exception to the handoff-only boundary established by #85, not general repository implementation authority.
Canonical role-skill shape: #121.
Problem
The current Designer charter says:
That correctly keeps Designer out of product logic and infrastructure, but it is too broad when the approved experience change and the implementation are the same visual adjustment. Handing a pure layout, styling, or presentation patch to Engineer adds translation without adding useful ownership.
“Visual” must remain an effect boundary, not a synonym for anything a person can see and not a file-extension allowlist.
Boundary test
A Designer implementation qualifies only when reverting the patch would change presentation while leaving all non-visual behavior and generated system output unchanged.
The file type does not decide the scope:
When a requested change mixes visual presentation with behavior, Designer may isolate and land the visual-only slice. Otherwise she stops at a buildable handoff to Engineer.
Included work
Excluded work
A role skill still grants no commands, credentials, mounts, network access, model selection, or executable permission. The runtime and repository workflow remain authoritative.
Proposed charter behavior
Designer owns experience definition everywhere. In an existing graphical web UI, Designer may also implement and land a change when its complete product effect is visual presentation. She locally verifies that visual slice and follows the repository’s established delivery workflow.
When the work changes behavior, semantics, data, generated systems, terminal experiences, games, infrastructure, or deployment, Designer produces the experience definition and hands implementation to Engineer.
Acceptance criteria
main.Relationship to #137
#137 remains an Engineer implementation. Its visible output is a terminal launch interaction, which this exception explicitly excludes.
Engineer checkpoint
caed7d4is pushed on issue-138-designer-visual-web. It adds the canonical effect-based visual-only web exception, native and compiled delivery proof, explicit behavioral, terminal, and procedural-game denials, authority-boundary tests, docs, and a Designer evaluation prompt covering one allowed case plus three denied cases. ward exec pre-commit and ward exec smoke pass. ward exec test stops only because evaluations/latest/designer-codex.yaml is correctly bound to the prior pack digest. Independent QA must generate fresh serial frontier and OSS responses from exact revisioncaed7d4, score every rubric criterion, and return the v2 Designer result. The branch is intentionally not landed and #138 remains open until that evidence validates.