Design system

Tokens authored at the theme.json schema level, and the patterns that consume them. Each makes a structural claim: status is verified, not asserted; outcomes resolve into artifacts; testimony never outranks the work.

Proof bar

One anatomy, three states. Only the rule color and dot change.

release: tagged

defect: fixed

proposal: in review

Artifact row

The terminus of a Work entry. Each cell is labeled by what it verifies.

Artifacts

release

diff

live

Client pull-quote

Capped at body scale. The ceiling is the ranking.

The governance layer did exactly what we needed: every status was traceable to an artifact we could open ourselves. Nothing was asserted that wasn’t also verifiable.

— Client name, Role, Organization

Work entry (ledger)

The spine the other components attach to. One row anatomy; state is the left rule plus a redundant status word, never color alone.

Merged

Token-driven status ledger

Shipped the governance layer: every status on the page resolves to an artifact a reader can open. State is the rule color, not decoration.

Artifacts

release

diff

live

In review

Proposal: artifact retention policy

Open for review. Nothing is asserted here that the linked diff does not already show.

Pending

Scheduled: search index rebuild

Not yet started. The slot is reserved so the gap is conspicuous, not merely absent.

Evidence First case board

For non-visual proof — releases, issues, pull requests, reviews. A site-owned operations surface, not a screenshot.

Evidence first

Operational proof before presentation

Use this board when the work is best verified by releases, issues, pull requests, reviews, docs, or policy records rather than screenshots.

release

Tagged build shipped

Link the release, changelog, or versioned artifact that proves the work is complete.

source

Repository or pull request

Link the diff, branch, issue, review thread, or source record that supports the claim.

review

Maintainer or stakeholder review

Use this row when the honest state is still in review, pending confirmation, or awaiting merge.

Proof + Product hero

For visual work. A compact evidence board paired with a framed product-media slot, so client visuals prove the work without becoming the palette.

Proof + Product

Finished surface, verified path

Use for visual client work, plugin UI, frontend interfaces, or cases where screenshots materially prove what shipped.

live

Production surface

Link the live site, admin surface, demo, or published interface.

source

Build artifact

Link the repository, release, diff, or deployment record.

Replace this note with a real screenshot image block before publishing. Use classes hp-shot hp-shot--browser for desktop surfaces or hp-shot hp-shot--phone for mobile surfaces.

live

published surface

src

source linked

Operational Story feature

The featured narrative reserved for the Flavor Agent governance and demo pages, where evidence, signals, and diagrams recur as one demonstration.

Flavor Agent feature

Governance, demo, and proof as one operating surface

The AI Governance and Demo pages describe one Flavor Agent demonstration: AI proposes changes, WordPress records the trail, and approval stays with the site owner.

Feature state

Operational checks

governance

Policy path visible

The governance page states the review, audit, bounded-action, and rollback contracts in production terms.

demo

Product flow visible

The demo page carries the walkthrough evidence and activity-log surface for the same plugin.

01

governance page

02

demo page

FA

same plugin demonstration

Wapuu homepage hero

The portfolio landing treatment: the HPerkins Wapuu as signature artwork with restrained proof chips. It owns the page h1, so it is shown live on the home page rather than embedded here.