[C4 HL-029] Evaluate product surfaces and implement only the needed adaptation #39

Outcome

Choose surfaces through real presentation and authoring requirements.

Placement and activation

• Circle: C4 — Performance, space, and participation
• System responsibilities: Product / Platform
• Capability coverage: 02 Product Applications & Interfaces; 03 APIs, SDKs & Integrations; 08 Quality, Testing & Evaluation; 09 Developer Platform & Tooling
• Planning status: Conditional; activate only when the requirement below is met.
• Activation: A selected usage fails on the existing browser surface or requires independent packaging.
• Parent epic: [EPIC C4] Performance, space, and participation #7; master roadmap: [MASTER EPIC] Hole-loop: concentric evolution within Persona / Visual Form Canon #2.

Dependencies

• HL-004 #13
• HL-010 #20

Acceptance evidence

• Assess web/PWA mobile, desktop wrapper, admin console, customer portal, internal ops console, CLI, browser extension, and embedded/white-label surfaces in a decision matrix.
• Implement the selected surface only when browser reading, authoring, export, offline performance, or distribution has a demonstrable unmet need.
• Each implemented surface consumes versioned patch/score contracts, preserves edition identity, and has its own accessibility/input/release checks.
• Document lifecycle/deploy/permission distinctions before a surface becomes another repository; do not create nine clients from the ontology.
• Validate one end-to-end need on the target hardware/context, including installation/update/recovery only if that surface requires them.

Completion and scope

Attach the actual artifact or commit, relevant verification, limitations, and an artist decision where a composition changes. This issue plans authorized work; creation does not claim implementation or deployment. Preserve independent work/source identities and private source boundaries. Repository creation requires the extraction evidence in HL-004 #13 and HL-045 #14.