The protocols described elsewhere in this portfolio are the ones that built this site. Formwork governs every session. Savepoint marked every turning point. The voice protocol caught the first draft when it read as marketing copy. This page shows what those protocols produce.
Governance
A CLAUDE.md at the root carries the site’s institutional memory: the three-tier architecture, the voice rules, the SEO strategy, the current state of every open workstream. Every session, human or AI, reads it before work begins. That’s Formwork Protocol in practice.
Savepoint Protocol marked the cognitive turning points throughout the build: when the three-tier structure locked, when the voice protocol crystallized, when the vocabulary system emerged.
The site was built with AI as a thinking and implementation partner: ChatGPT, Gemini, and Claude Code each handling different phases. Not generative AI producing content. Cognitive extension: brainstorming, structural planning, and engineering execution governed by the same methodology as every other project.
The protocols were tested by their own creation process. Formwork governed the build, catching the failure modes it was designed to prevent: decisions contradicting across sessions, naming conventions overwritten, architectural choices drifting because no contributor could see what the previous one had decided.
What the Governance Produces
Three tiers, organized by intent. Governance (governing logic), Infrastructure (maintained platforms and tools), Output (delivered and produced work). The organizing principle is why the work exists, not what it produced.
Frontmatter that forces specificity. Every project opens with four fields: context (what was broken), drift (the gap between intent and execution), scaffold (the structural fix), fidelity (what held). You can’t fill in “context” with marketing language. The field demands a concrete problem.
A voice protocol with enforcement. The first complete draft of this site read as marketing copy. Abstract concepts announced before any real situation was established. The response: a codified writing system where fabrication gets caught before it ships. Three evaluation lenses keep it honest, tracked over time.
Cross-links by concept. Encore links to Formwork because the institutional memory accumulated across twelve years of that platform became the protocol. The vocabulary page links to every project that demonstrates each term.
Machine-readable metadata. Altitude (01/02/03) and faculty (design, engineering, UX/IA) on every project. JSON-LD structured data for search engines and LLMs.
Tech Stack
| Element | Specification |
|---|---|
| Generator | Jekyll 4.4.1 (native SCSS compilation) |
| Styling | Custom SCSS (no utility framework) |
| Typography | Rubik (body), Chainprinter (structural headings, self-hosted), Space Mono (monospace) |
| Layout | Fixed 250px sidebar + main content, always side-by-side |
| Collections | _governance/, _infrastructure/, _output/ |
| Data | JSON (navigation, index, vocabulary, contact) |
| Structured Data | JSON-LD (Person, CreativeWork, BreadcrumbList, FAQPage) |
| Automation | Liquid templates driven by navigation.json |
| Hosting | GitHub Pages, deployed on push |
| Collaboration | AI-assisted: ChatGPT, Gemini, Claude Code |