JD Proof FoundryBuild guide

Guide route

How the Proof Foundry pilot was made.

This route documents the brief, asset pipeline, evidence labels, implementation choices, and critique loop for the one-site calibration run before the full JD Workshop Fable-25 build.

Brief

Build one isolated JD Workshop variation that uses the current repository as factual foundation, then expands the presentation into a more ambitious proof-of-work surface.

The pilot is allowed to be expressive. The guardrail is evidence clarity: real work is real, fictional material is labeled, and useful concepts can become working demos later.

Evidence labels

Real

Verified repo, live site, public links, or actual Joshua/JD Workshop material.

Concept

Fictional clients, synthetic metrics, or speculative products. Useful, but not claimed as shipped evidence.

Built demo

A concept implemented enough to become an inspectable artifact.

Asset pipeline

The pilot uses existing Grok media probes from the JD Workshop artifact folder: a dark premium still and an abstract animated tile field. They are treated as atmosphere, not as factual screenshots.

  • Image source: jdw-grok-probe-optimized.jpg
  • Video source: jdw-grok-probe.mp4
  • Use: abstract background field in the hero.

Implementation choices

  • Static HTML/CSS/JS pilot under the canonical studio project folder.
  • No production JD Workshop source files changed.
  • Tokens mirror the current JD Workshop palette: deep navy, cream ink, amber accent, coral and dusk support colors.
  • Motion is limited to opacity and transform. A reduced-motion media query disables animation.
  • The concept dialog uses native focusable controls and escape-to-close behavior.

Critique passes

The pilot ran three critique passes before approval.

  1. Pass 1: Browser screenshots and DOM checks passed. The desktop hero was too poster-like, so the H1 was reduced and an artifact rail was added.
  2. Pass 2: Revised desktop and mobile captures passed. The hero became actionable, then gained a verification strip inside the proof console.
  3. Pass 3: Static checks, Chromium screenshots, and Playwright console/responsive checks passed across home and guide routes at desktop, tablet, and mobile.