Proof Surface
Proof Page Rewrite With a Strict Privacy Boundary
A proof section that shows real build evidence — workflow screenshots, architecture diagrams, owned-system shots — while a typed proof-status model and a CI check keep any client-identifying or fabricated material off the page.
HMX Zone
Next.js Image
Verified HMX-owned case
Outcome signals
These are the real outcome statements attached to this HMX case study.
- Boundary
- client-identifying material can't be published
- Typed
- each item declares why it is safe to show
- CI-checked
- non-compliant proof fails the build
- Credible
- real owned evidence instead of stock filler
Case architecture
Proof Page Rewrite With a Strict Architecture
6 nodes
a proof-item type with
Classify each existing asset
TypeScript typed proof model
Next
Fallback Path
Boundary client-identifying
- 01a proof-item type with
A proof section that shows real build evidence — workflow screenshots, architecture diagrams, owned-system shots — while a typed proof-status model...
- 02Classify each existing asset
Classify each existing asset as owned, redacted, public-URL, or build-note
- 03TypeScript typed proof model
TypeScript typed proof model (lib/data/proof.ts) supports the route, form, or data boundary for Proof Page Rewrite With a Strict so public UX and backend state stay connected.
- 04Next
Render only items that pass the privacy boundary, with honest captions
- 05Fallback Path
When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.
- 06Boundary client-identifying
Boundary client-identifying material can't be published; Typed each item declares why it is safe to show; CI-checked non-compliant proof fails the...
Problem
The operating gap
A portfolio either shows nothing credible or leaks client names, private dashboards, and identifiable data into public screenshots. There is no system deciding what is safe to publish, so proof is either weak or a privacy liability.
Build
What gets built
Model every proof item with an explicit status and evidence type (public URL, redacted screenshot, owned-system shot, build note), and render only items that clear the boundary. A check:proof script validates each item against the rules in CI, so unverified or client-identifying proof cannot reach production.
Build steps
Proof Page Rewrite With a Strict Privacy Boundary uses a web app route, data, and conversion layer for Full-Stack Websites. A proof section that shows real build evidence — workflow screenshots, architecture diagrams, owned-system shots — while a typed proof-status model... The architecture connects a proof-item type with, typescript typed proof model, next, and boundary client-identifying with an explicit control path.
- 01Define a proof-item type with status and evidence-type fields encoding what is publishable
- 02Classify each existing asset as owned, redacted, public-URL, or build-note
- 03Render only items that pass the privacy boundary, with honest captions
- 04Serve approved images from a public Storage bucket via optimized Image
- 05Write a check:proof script that validates every item against the rules
- 06Add the check to the verify gate so non-compliant proof fails CI
Stack
Tools and layers
- TypeScript typed proof model (lib/data/proof.ts)
- Next.js Image
- Supabase public Storage bucket
- Proof-status enum + evidence types
- check:proof CI script
- Vercel
- Experience layer: Define a proof-item type with status and evidence-type fields encoding what is publishable
- Server layer: Classify each existing asset as owned, redacted, public-URL, or build-note
- Database layer: TypeScript typed proof model (lib/data/proof.ts) supports the route, form, or data boundary for Proof Page Rewrite With a Strict so public UX and backend state stay connected.
- Automation layer: Next.js Image handles routine steps while model every proof item with an explicit status and evidence type (public URL, redacted screenshot, owned-system shot, build note), and render only...
- Measurement layer: Boundary client-identifying material can't be published; Typed each item declares why it is safe to show; CI-checked non-compliant proof fails the...
Data flow
- 01Define a proof-item type with status and evidence-type fields encoding what is publishable
- 02Classify each existing asset as owned, redacted, public-URL, or build-note
- 03Render only items that pass the privacy boundary, with honest captions
- 04Serve approved images from a public Storage bucket via optimized Image
- 05Write a check:proof script that validates every item against the rules
- 06Add the check to the verify gate so non-compliant proof fails CI
Controls
- A portfolio either shows nothing credible or leaks client names, private dashboards, and identifiable data into public screenshots.
- Model every proof item with an explicit status and evidence type (public URL, redacted screenshot, owned-system shot, build note), and render only...
- When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.
Research basis
A route assembles through form, data, metadata, and deploy checks.
The same website operating path
Full-stack websites for service businesses and operators: route architecture, service pages, lead capture, metadata, proof boundaries, blog/database paths, analytics, and deployment checks.
Route map
Service architecture
Clear service routes
01active
Progress72%
Lead capture
Form and context flow
Lead capture that saves context
02active
Progress86%
Public metadata
SEO and schema layer
SEO and schema on public pages
03active
Progress64%
Launch QA
Analytics and deployment checks
Analytics events tied to CTAs
04active
Progress91%