Skip to content

build-set: a product page generated from the set's modelled stakeholder views - #24

Open
afflom wants to merge 2 commits into
claude/set-compact-suitefrom
claude/product-ui
Open

afflom wants to merge 2 commits into
claude/set-compact-suitefrom
claude/product-ui

Conversation

@afflom

@afflom afflom commented Nov 15, 2026

Copy link
Copy Markdown
Owner

build-set now writes site/product/index.html for a prompt set that has a product record (prism/product.json). It also writes prism/builder.lock, which names this builder as the source and records the page's sha256.

The page renders only what the record models: each stakeholder's persona, jobs to be done, primary question (answered first), journey stages, and information architecture with disclosure levels. Its CSS tokens come from the record's design system (WCAG 2.2 AA), and it draws five components. Every answer comes from the verified holo in the browser, which loads after its archive identities verify and its acceptance vectors replay.

afflom/prism-kat uses it, live at /prism-kat/product/. That instance's audit-prism reads prism/builder.lock as a third Prism lock, so the generated page counts as Prism output.

Known gate issue: this branch adds builder/ui.mjs and builder/ui/product.html. This repository's own only-Prism ratchet refuses new non-Prism files, so acceptance will fail on audit-prism until the owner decides how the builder's UI generator is accounted for.


Generated by Claude Code

When the set has a product record (prism/product.json), build-set writes
site/product/index.html, a page generated from the set, its prompts and the
record, whose every answer comes from the verified holo the Pages workflow
publishes beside it, and prism/builder.lock, naming this builder as the source
and the page's sha256, so an instance's only-Prism audit can count the page as
Prism output.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3Ns5C7CRWRVtEQBxEq
…delled UX

Each view renders the product record's persona, jobs to be done, primary
question (answered first, with only its inputs), journey stages and
information architecture, whose disclosure levels decide what is open,
summarised or closed. The CSS tokens come from the record's design system
(type, spacing, radius, light and dark colour, WCAG 2.2 AA), and only its five
components are drawn.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3Ns5C7CRWRVtEQBxEq

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants