Skip to content

id: design: per-target customisation system (from #5679) #5854

Open

Description

@dezren39

Summary

Follow-on design ticket from #5679 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.

What this design must settle

Themes, override maps, asset substitution, and conditional blocks, proven against the parent's worked three-target example.

Context from the parent

The parent design fixes the semantic markup + style-assertion model by which programs-as-websites render across web, native, and custom targets. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.

Decision record expected

Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.

Relations

Parent: #5679. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).

Activity

  1. added
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Nov 5, 2026
  2. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    work/assignedQueue worker lifecycle state
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  4. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-g
    • Session / ID: task 10257
    • Found via: queue claim
    • Task: Triage issue id: design: per-target customisation system (from #5679) #5854 — assigned to the opencode execution lane; handing off to the opencode claimant, which launches the bound session. This lane did not work the task directly.
  5. added
    queue/claimedQueue worker lifecycle state
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 5, 2026
  6. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    task: 10257
    lane: code-u
    state: handed-off
    summary: Task 10257 claimed by lane code-u; execution-lane assignment returned opencode, so this task is handed off to the opencode claimant per the worker runbook §1b. Issue #5854 is OPEN with no hard-stop labels on fresh check; stale queue/parked + status/parked labels from an earlier park were replaced with queue/claimed + status/in-progress on claim.
    next: opencode-claimant launches the bound opencode session for task 10257.

  7. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    task: 10257
    lane: 7b47536b-c162-444c-be8a-3a9538cc4cb5
    state: picked-up
    summary: Task 10257 is now claimed by the OpenChamber scheduled lane; the required claim labels are already present. Current main was fast-forwarded to 2801e36.
    next: check related issue and PR state, then record the triage route.

  8. added
    kind/designA design proposal (design-architect): multi-step, phased, decision-bearing
    priority/normalOrdinary priority (the default)
    status/triagedTriaged and routed (see agent note)
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 5, 2026
  9. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    task: 10257
    state: done (triaged)
    lane: 7b47536b-c162-444c-be8a-3a9538cc4cb5
    summary: Triage verified at current main 2801e36. #5854 remains open; no PR references it. Its parent #5679 is open and its decomposition includes this issue.

    Dependency order (verified live on 2026-11-05):

    1. Settle id: design: semantic markup vocabulary v1 (from #5679) #5849 (semantic markup vocabulary; currently parked) and id: design: style assertion vocabulary (from #5679) #5850 (style assertion vocabulary; open).
    2. Then id: design: web rendering: assertion → Tailwind mapping (from #5679) #5851 (web mapping; waiting-dependency), id: design: native rendering: assertion → OS-standard controls (from #5679) #5852 (native mapping; parked), and id: design: custom GUI rendering as first-class overrides (from #5679) #5853 (custom GUI rendering; claimed/in progress) can finish their target mappings.
    3. Resume id: design: per-target customisation system (from #5679) #5854 for per-target themes, override maps, asset substitution, conditional blocks, and the required three-target example.
    4. id: design: rendering pipeline & conformance suite (from #5679) #5855 (rendering pipeline/conformance) follows the settled target behavior.

    This is a design-routing issue, not a runtime defect to reproduce. No Drew-only decision is needed for this ordering; implementation timing remains a separate prioritisation decision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)kind/designA design proposal (design-architect): multi-step, phased, decision-bearingpriority/normalOrdinary priority (the default)status/triagedTriaged and routed (see agent note)status/waiting-dependencyWaiting on a dependencytask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions