Let Designer land complete graphical web experiences #160

New issue

Closed

opened 2026-07-30 17:28:33 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-30 17:28:33 +00:00

Member

Outcome

Broaden the canonical Designer role so she may implement, locally validate, and land complete page-level experiences in an existing graphical web application when the work is bounded to information architecture, static or content-driven routes, navigation placement, presentation, accessibility, and page copy.

This is a deliberate expansion of #138. The visual-only exception landed there, but its routing, navigation, semantic, and copy exclusions still force an Engineer handoff for work users reasonably expect the Designer role to own.

Representative blocked request: coilysiren/website#80

Problem

A request to add an organization hub, three organization detail pages, and a link in an existing site's top navigation is a coherent design task. The current charter allows Designer to style those pages but prohibits creating their routes, placing the navigation link, writing the supporting copy, or completing the accessibility contract.

That split adds translation overhead without introducing useful engineering ownership. The experience definition and its implementation are the same bounded artifact.

Proposed boundary

Designer may implement and land a complete graphical web experience when reverting the patch would remove or reshape a bounded page-level experience without changing business rules, application data flow, persistence, permissions, infrastructure, or generated product systems.

File types and frameworks do not decide the boundary.

Included work

New static or content-driven pages in an existing graphical web application
File-based routes or focused route declarations whose sole purpose is exposing those pages
Adding, removing, renaming, or reordering navigation entries for the designed pages
Information hierarchy and page-level interaction structure
Meaningful page copy that belongs to the new or reshaped experience
Static public data catalogs used only to render the experience
Presentational components, layout, responsive behavior, design tokens, static assets, and non-behavioral motion
Accessibility semantics, focus treatment, and ordinary keyboard access required by the bounded page experience
Metadata, Open Graph treatment, empty states, and error copy for the bounded surface
Focused route, rendering, accessibility, and navigation tests
Repository-prescribed formatting, type checks, builds, local UI checks, commit, and delivery through the resolved workflow

Excluded work

Business rules, application state machines, or cross-feature interaction logic
Runtime data fetching, APIs, networking, persistence, authentication, permissions, or analytics
Stateful forms, validation engines, transactions, or workflows
Routing-system architecture, framework migration, dependencies, or build-system changes
Terminal, CLI, TUI, game, simulation, procedural-generation, infrastructure, deployment, release, or live-operations work
Copy or semantics whose effect changes policy, legal commitments, permissions, or behavior outside the bounded experience

When a request mixes included experience work with excluded product behavior, Designer isolates and lands the coherent design-owned slice when possible. Otherwise she produces the buildable experience definition and hands the implementation to Engineer.

Representative acceptance case

The Designer role should be able to complete coilysiren/website#80 end to end:

Add /orgs/ and three static organization detail routes.
Add ./orgs to the existing top navigation.
Write the page copy and static public organization catalog.
Reuse the existing graphical shell and icon assets.
Preserve keyboard access and responsive navigation wrapping.
Add route and navigation smoke coverage.
Update the feature inventory.
Validate, commit, and deliver through the website repository's established workflow.

No API, authentication, persistence, stateful workflow, dependency, deployment, or live-system change is involved.

Acceptance criteria

The canonical Designer role grants bounded page-level graphical web implementation authority.
Generated and compiled role surfaces carry the same boundary without hand-edited copies.
The charter clearly distinguishes focused route and navigation work from routing-system architecture.
Page copy, static content data, metadata, and ordinary accessibility semantics are explicitly included.
Business logic, runtime data, stateful workflows, infrastructure, deployment, and live operations remain excluded.
The Designer evaluation pack includes the website organization-pages request as an allowed case.
Boundary evaluations still deny an authenticated data dashboard, a stateful form workflow, a terminal UI, and a procedural game surface.
Repository validation passes through declared Ward verbs.
The change lands on canonical main.

Relationship to #138

#138 remains the narrower visual-only precedent. This follow-up recognizes that page-level information architecture, routes, navigation, copy, semantics, and presentation often form one indivisible graphical web experience that the Designer role should own.

## Outcome Broaden the canonical Designer role so she may implement, locally validate, and land complete page-level experiences in an existing graphical web application when the work is bounded to information architecture, static or content-driven routes, navigation placement, presentation, accessibility, and page copy. This is a deliberate expansion of #138. The visual-only exception landed there, but its routing, navigation, semantic, and copy exclusions still force an Engineer handoff for work users reasonably expect the Designer role to own. Representative blocked request: https://forgejo.coilysiren.me/coilysiren/website/issues/80 ## Problem A request to add an organization hub, three organization detail pages, and a link in an existing site's top navigation is a coherent design task. The current charter allows Designer to style those pages but prohibits creating their routes, placing the navigation link, writing the supporting copy, or completing the accessibility contract. That split adds translation overhead without introducing useful engineering ownership. The experience definition and its implementation are the same bounded artifact. ## Proposed boundary Designer may implement and land a complete graphical web experience when reverting the patch would remove or reshape a bounded page-level experience without changing business rules, application data flow, persistence, permissions, infrastructure, or generated product systems. File types and frameworks do not decide the boundary. ### Included work * New static or content-driven pages in an existing graphical web application * File-based routes or focused route declarations whose sole purpose is exposing those pages * Adding, removing, renaming, or reordering navigation entries for the designed pages * Information hierarchy and page-level interaction structure * Meaningful page copy that belongs to the new or reshaped experience * Static public data catalogs used only to render the experience * Presentational components, layout, responsive behavior, design tokens, static assets, and non-behavioral motion * Accessibility semantics, focus treatment, and ordinary keyboard access required by the bounded page experience * Metadata, Open Graph treatment, empty states, and error copy for the bounded surface * Focused route, rendering, accessibility, and navigation tests * Repository-prescribed formatting, type checks, builds, local UI checks, commit, and delivery through the resolved workflow ### Excluded work * Business rules, application state machines, or cross-feature interaction logic * Runtime data fetching, APIs, networking, persistence, authentication, permissions, or analytics * Stateful forms, validation engines, transactions, or workflows * Routing-system architecture, framework migration, dependencies, or build-system changes * Terminal, CLI, TUI, game, simulation, procedural-generation, infrastructure, deployment, release, or live-operations work * Copy or semantics whose effect changes policy, legal commitments, permissions, or behavior outside the bounded experience When a request mixes included experience work with excluded product behavior, Designer isolates and lands the coherent design-owned slice when possible. Otherwise she produces the buildable experience definition and hands the implementation to Engineer. ## Representative acceptance case The Designer role should be able to complete https://forgejo.coilysiren.me/coilysiren/website/issues/80 end to end: * Add `/orgs/` and three static organization detail routes. * Add `./orgs` to the existing top navigation. * Write the page copy and static public organization catalog. * Reuse the existing graphical shell and icon assets. * Preserve keyboard access and responsive navigation wrapping. * Add route and navigation smoke coverage. * Update the feature inventory. * Validate, commit, and deliver through the website repository's established workflow. No API, authentication, persistence, stateful workflow, dependency, deployment, or live-system change is involved. ## Acceptance criteria * [ ] The canonical Designer role grants bounded page-level graphical web implementation authority. * [ ] Generated and compiled role surfaces carry the same boundary without hand-edited copies. * [ ] The charter clearly distinguishes focused route and navigation work from routing-system architecture. * [ ] Page copy, static content data, metadata, and ordinary accessibility semantics are explicitly included. * [ ] Business logic, runtime data, stateful workflows, infrastructure, deployment, and live operations remain excluded. * [ ] The Designer evaluation pack includes the website organization-pages request as an allowed case. * [ ] Boundary evaluations still deny an authenticated data dashboard, a stateful form workflow, a terminal UI, and a procedural game surface. * [ ] Repository validation passes through declared Ward verbs. * [ ] The change lands on canonical `main`. ## Relationship to #138 #138 remains the narrower visual-only precedent. This follow-up recognizes that page-level information architecture, routes, navigation, copy, semantics, and presentation often form one indivisible graphical web experience that the Designer role should own.

coilyco-ops referenced this issue from a commit

2026-07-30 17:37:01 +00:00

feat(design): allow bounded page experiences, closes #160

coilyco-ops closed this issue

2026-07-30 17:37:01 +00:00

coilyco-ops referenced this issue

2026-07-31 06:39:52 +00:00

Refresh current Design evidence for the v2 release gate #163