exhibit

Exhibit release decisions

Prepared: 2026-07-30 · Updated: 2026-07-31 · Owner: unassigned

Decisions taken on 2026-07-31: MIT licence, memory-only evidence retention, and GitHub for security and support reporting. All are applied in the code and documentation.

The remaining literal values were supplied on 2026-07-31 and are applied:

Value Value used Lands in
Copyright holder’s legal name Kayumuzzaman LICENSE
Privacy contact address i.kayumuzzaman@gmail.com docs/PRIVACY.md
Policy effective date 2026-07-31 docs/PRIVACY.md

The effective date is the date the policy becomes reachable at its public URL, not the date the store approves the listing. Review can take weeks, and a policy dated after users could already read it would be wrong.

The privacy contact is a personal address rather than the dedicated alias originally chosen. It appears in a public listing, will be scraped, and changing it later means editing a published listing rather than the code.

Nothing in this repository blocks submission. The listing was entered in the Chrome Web Store dashboard on 2026-07-31 and the policy URL is live. What remains is the review outcome, the optional product video, and first real users.


Decision State
Licence terms MIT, applied to LICENSE and package.json
Store publisher Developer console account created
Legal owner name Kayumuzzaman, applied to LICENSE

MIT is effectively irreversible once published: anyone who obtains the code under it keeps those rights permanently.

2. Contacts and a hosted policy URL

File State
SECURITY.md Done — GitHub Security Advisories, 7-day acknowledgement
SUPPORT.md Done — GitHub Issues, current release only, best effort
PRIVACY.md Done — contact and 2026-07-31 effective date applied

Done. GitHub Pages serves the policy from main under /docs with HTTPS enforced:

https://kayumuzzaman.github.io/exhibit/PRIVACY

It must stay reachable for as long as the item is listed. Note that Pages publishes everything under docs/, including the business model, the competitive landscape, and the historical planning records — all already public in this repository, but now presented as a browsable site.

3. Persistent retention — settled, no action

On-disk evidence retention is removed from the published build. Evidence is held in browser-session memory only and never written to disk, so there is no unencrypted evidence at rest to disclose or defend.

Enforced rather than asserted: the package audit fails the release if an evidence-capable persistent storage API appears in the shipped bytes.

The visible cost: users lose captured evidence when the browser session ends. Export before closing the browser.

4. Product video

A concise fixture-only walkthrough, uploaded to YouTube, with the URL pasted into the listing. Screenshots and the promo tile are generated and tracked; the video cannot be produced from this repository.

Chrome treats the video as optional in the form. It is listed here because the release checklist has always required it, not because submission will fail without it.

5. First real users — the one that actually matters

No target-segment participant has used Exhibit. Every quality gate in this repository measures whether the code does what it was told to do, and none of them measures whether anyone wants it.

The cheapest way to fix that without waiting on the rest of this list is to publish unlisted: a shareable link, no public discovery, no reviews, no ratings. Give it to five frontend developers working on Next.js applications, watch them use it, then decide on public listing.

ROADMAP.md Stage 2 has the full research script. The wedge claim to test first: show a Server Action or an RSC request and record whether the participant understands it unprompted, and whether Chrome’s Network panel left them unable to.


Already prepared — no decision needed

Area State
Quality gate pnpm verify green; see VERIFICATION.md
Release artifact Built and hashed from a clean commit; recorded in VERIFICATION.md
Listing copy Name, summary, description, category, permission justifications
Data-use answers Behaviour mapped to the disclosure categories
Screenshots Five 1280×800 PNGs, Server Action frame leading, regenerable and deterministic
Promo tile 440×280, generated by pnpm promo-tile, byte-identical across runs
Icons 16 / 32 / 48 / 128 PNG
Privacy policy text Contact and effective date applied; needs only a public URL
Compatibility claim Narrowed to what was actually tested — see COMPATIBILITY.md

The ordered submission steps live in RELEASE_CHECKLIST.md.