coilyco-flight-deck/agent-compose

Watch

Clarify Designer boundary for user-specified static copy and semantic markup #169

New issue

Closed

opened 2026-07-31 22:42:25 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-31 22:42:25 +00:00

Member

Outcome

Let the Designer role implement explicit, bounded static copy and semantic HTML changes on a graphical page it already owns. Keep the handoff boundary for behavior, data flow, invented product semantics, and content strategy.

Reproduction

During an interactive website task, the assigned Designer seat had already built and repeatedly refined a static presentation page.

The user explicitly asked to rename one existing section heading and remove one image.
The agent removed the image but refused the one-line heading change because the role briefing excludes “meaning-changing copy.”
The user then supplied the exact labels for each section and asked for literal <ul> lists under the headings.
The agent again refused, saying semantic markup required an Engineer handoff.
After the user challenged that result, the same seat implemented the complete request safely as ordinary static React markup and Sass. The change passed formatting, lint, TypeScript, unit tests, pre-commit, and a 1920×1080 browser check.

Evidence: coilysiren/website@b448ec0.

Problem

The current Designer boundary is directionally correct but too literal. It conflates two different actions:

Inventing or materially revising product meaning, which may belong to Content or another role.
Applying exact user-supplied labels and native semantic HTML inside an already in-scope visual page, which is routine bounded page work.

That ambiguity creates silly handoffs for changes such as <h2>Fabrication</h2> or a user-provided unordered list. It also encourages worse workarounds, such as visually replacing text in CSS instead of using correct HTML.

Proposed rule

Clarify the Designer briefing so explicit user-supplied static copy and semantic structure are allowed when all of these are true:

The page or component is already within the Designer implementation scope.
The user supplied the intended wording or list content.
The change does not add behavior, data flow, persistence, validation, navigation, permissions, analytics, or a new accessibility interaction contract.
Native semantic HTML preserves or improves the existing document contract.

The “meaning-changing copy” exclusion should continue to cover agent-authored messaging, content strategy, and ambiguous editorial decisions.

Regression coverage

Add a Design evaluation case where the user asks to:

Rename an existing section heading with exact replacement text.
Add a supplied unordered list beneath several headings.
Correct obvious spelling in that supplied list.
Preserve image-to-label order and verify the existing responsive page.

Expected result: implement and validate the bounded static change. A handoff to Engineer or Content is a hard failure.

Acceptance

The canonical Designer role text distinguishes user-specified static copy from agent-authored meaning.
The bounded page-level web exception explicitly admits native semantic markup needed to present supplied content.
The regression case lands in the current Design evaluation pack.
Existing behavior, data, interaction, and content-strategy boundaries remain intact.
Generated roster output and evaluation documentation stay consistent.

## Outcome Let the Designer role implement explicit, bounded static copy and semantic HTML changes on a graphical page it already owns. Keep the handoff boundary for behavior, data flow, invented product semantics, and content strategy. ## Reproduction During an interactive website task, the assigned Designer seat had already built and repeatedly refined a static presentation page. 1. The user explicitly asked to rename one existing section heading and remove one image. 2. The agent removed the image but refused the one-line heading change because the role briefing excludes “meaning-changing copy.” 3. The user then supplied the exact labels for each section and asked for literal `<ul>` lists under the headings. 4. The agent again refused, saying semantic markup required an Engineer handoff. 5. After the user challenged that result, the same seat implemented the complete request safely as ordinary static React markup and Sass. The change passed formatting, lint, TypeScript, unit tests, pre-commit, and a 1920×1080 browser check. Evidence: `coilysiren/website@b448ec0`. ## Problem The current Designer boundary is directionally correct but too literal. It conflates two different actions: * Inventing or materially revising product meaning, which may belong to Content or another role. * Applying exact user-supplied labels and native semantic HTML inside an already in-scope visual page, which is routine bounded page work. That ambiguity creates silly handoffs for changes such as `<h2>Fabrication</h2>` or a user-provided unordered list. It also encourages worse workarounds, such as visually replacing text in CSS instead of using correct HTML. ## Proposed rule Clarify the Designer briefing so explicit user-supplied static copy and semantic structure are allowed when all of these are true: * The page or component is already within the Designer implementation scope. * The user supplied the intended wording or list content. * The change does not add behavior, data flow, persistence, validation, navigation, permissions, analytics, or a new accessibility interaction contract. * Native semantic HTML preserves or improves the existing document contract. The “meaning-changing copy” exclusion should continue to cover agent-authored messaging, content strategy, and ambiguous editorial decisions. ## Regression coverage Add a Design evaluation case where the user asks to: * Rename an existing section heading with exact replacement text. * Add a supplied unordered list beneath several headings. * Correct obvious spelling in that supplied list. * Preserve image-to-label order and verify the existing responsive page. Expected result: implement and validate the bounded static change. A handoff to Engineer or Content is a hard failure. ## Acceptance * The canonical Designer role text distinguishes user-specified static copy from agent-authored meaning. * The bounded page-level web exception explicitly admits native semantic markup needed to present supplied content. * The regression case lands in the current Design evaluation pack. * Existing behavior, data, interaction, and content-strategy boundaries remain intact. * Generated roster output and evaluation documentation stay consistent.

coilyco-ops referenced this issue

2026-08-01 23:17:31 +00:00

Let Portfolio Strategist maintain strategy-owned repository artifacts #174

coilyco-ops referenced this issue

2026-08-02 00:06:20 +00:00

Add AI Engineer as a Core Roster role #175

coilyco-ops added the

priority

autonomy

headless

labels

2026-08-05 10:25:46 +00:00

coilyco-ops referenced this issue from a commit

2026-08-06 00:15:01 +00:00

docs(design): clarify supplied static page content boundary (#169)

coilyco-ops referenced this issue from a commit

2026-08-06 00:24:08 +00:00

fix(design): keep copy boundary in role doctrine (#169)

coilyco-ops commented

2026-08-06 08:59:49 +00:00

Author

Member

Acceptance is already present on canonical main. Commit 14d96ef added the supplied static-copy and semantic-markup Designer boundary plus completion-supplied-static-markup, and later Creator naming was reconciled in 49fa412. Current Go tests and pre-commit passed with that behavior.

Acceptance is already present on canonical main. Commit 14d96ef added the supplied static-copy and semantic-markup Designer boundary plus `completion-supplied-static-markup`, and later Creator naming was reconciled in 49fa412. Current Go tests and pre-commit passed with that behavior.

coilyco-ops closed this issue

2026-08-06 08:59:49 +00:00

coilyco-ops referenced this issue

2026-08-06 09:18:00 +00:00

Refresh evaluations for the eight-role Creator roster #223