spacing:
baseline:
value: 8
unit: px
role: rhythm
scale:
- 1 # 8px · inline gap
- 2 # 16px · element padding
- 3 # 24px · block separation
- 5 # 40px · section rhythm
- 8 # 64px · hero rest Knowledge-backed product development
Your knowledge system and your product system do not talk to each other.
We connect them. Structured domain knowledge in. Working product surfaces out. Marketing site, design system, runbooks, app screens — all rendered from the same source.
- Source
- Corpus stays named.
- Structure
- Agents write to one shape.
- Surface
- Site, MCP, proof, and runbooks stay aligned.
Perpetual context The team is already briefed
Two words. Begin KBPD
Stop compacting. Stop starting over. Perpetual context for frontier coding models — built around your product's actual decisions, not just its current file tree.
-
Today, mode 1
One long conversation
A single Claude or Cursor session running for hours. The agent compacts older context as the window fills.
You lose: earlier decisions, earlier nuance, earlier "we already discussed this" — quietly. Each compaction is a small forgetting.
-
Today, mode 2
Multiple small projects
Several smaller sessions, each starting fresh from
CLAUDE.md+git log+ recent files.You lose: continuity across the journey. Session 7 has no idea what was decided in session 2. Project context only captures the now, not the path.
-
With KBPD
Perpetual context
A single source of truth that carries every decision, every reviewer's note, and every open question across every session — without you re-typing them.
You get: each session starts with the team already briefed. Accuracy compounds. Misfires drop.
You're not asking the model to remember more. You're giving it a structure that remembers for you.
Agent input → structured data → real components Not "just generate some CSS"
KBPD compiles structured knowledge into deployable artifacts
Agent prompt
> Add a primary CTA on the pricing page using our brand colors and rhythmic spacing.
Without KBPD the agent invents fresh CSS values every time — different paddings, off-brand reds, one-off shadows. With KBPD it writes structured data against the same design source, and the data compiles into matching surfaces below.
-
CSS
--space-1: 8px; --space-2: 16px; --space-3: 24px; --space-5: 40px; --space-8: 64px; -
Tailwind
spacing: { 1: '0.5rem', 2: '1rem', 3: '1.5rem', 5: '2.5rem', } -
Component prop
<Button size="lg" /> // → padding: var(--space-3) // gap: var(--space-2) -
Rendered output
padding: var(--space-3) · gap: var(--space-2)
Same shape every time. The agent isn't writing CSS — it's writing structured data against your design source. CSS, Tailwind, component props, runbooks, API contracts all compile from the same primitive deterministically.
What changes
The first purchase should make the work inspectable.
KBPD is not a mood board for AI process. The first product is a local system you can open, run, inspect, and adapt to your own product work.
Starter kit
Before A blank repo and scattered prompts.
With KBPD A local KBPD workspace with working commands.
Proof Studio
Before A demo that has to be narrated by hand.
With KBPD Cases, evidence, limits, and source artifacts in one frame.
Local MCP
Before Copy-paste context for every tool.
With KBPD Search, health, diagnostics, and context reads from the same corpus.
Launch support
Before A generic onboarding call.
With KBPD A focused review of the knowledge system you already have.
Problem
Gap nobody talks about.
A regulator publishes a change at 9am. By 11am, legal has read it. By Friday, it has been mentioned in three stand-ups, two Slack threads, and a steering memo. By the following Thursday, somebody opens a planning ticket. Three sprints later, a developer writes the code that satisfies the regulation.
Fourteen weeks. Five handoffs. Zero persistence.
The regulation hasn't changed. The interpretation hasn't changed. The architectural commitment hasn't changed. But every team rediscovered it fresh, every handoff stripped context, every artifact got recreated from memory. Next quarter, when an auditor asks "why was this decision made?", nobody can point at the artifact.
This is not a failure of any one team. It is a structural failure: the knowledge system (legal, product, design, ops) and the delivery system (planning, code, design, release) don't have a shared substrate. Every handoff is a translation. Every translation loses signal.
KBPD is that substrate. Same file format for the legal interpretation, the design decision, the API contract, the change ticket. The handoffs stop being translations and start being references.
Proof
Numbers that already exist.
We didn't invent the problem. The cost of the gap has been measured for years. We invented the substrate that closes it.
- $2.41T
Annual cost of poor software quality
Most of it from rework, schedule slip, and post-release defects.
CISQ 2022
- 52%
Projects experiencing scope creep
Almost always traced to context that was never written down.
PMI Pulse of the Profession
- 41%
Code now AI-generated globally
Without a knowledge substrate, AI accelerates the wrong things faster.
GitClear 2024
- 35–45%
Code-generation improvement with AI
When the AI has structured context. Without it: closer to 0%.
McKinsey 2024
- 135%
Five-year ROI on a design system
And the design system is just one surface a knowledge system generates.
Smashing Magazine / Speicher & Wehrmann 2022
Pipeline
Six steps. Same shape every time.
Whether you're shipping marketing pages, a design system, an internal app, or a regulatory runbook — the pipeline doesn't change. Only the inputs.
- 01 Domain discovery
Capture
Interview, intake, observation. Knowledge enters as text, YAML, or markdown.
- 02 Information architecture
Structure
The captured material gets a schema. Reusable shapes emerge.
- 03 Architecture decision records
Decide
Each choice gets a record. The record outlives the decider.
- 04 Design token governance
Tokenize
Color, type, spacing, motion become named values. Files, not opinions.
- 05 Build pipeline
Resolve
Generators consume the structured inputs and emit working artifacts.
- 06 Shipped product
Surface
Marketing pages, app screens, design systems, runbooks — all from the same source.
Personas
The system ships. The personas decide.
Each KBPD instance ships with a roster of specialised perspectives — domain experts that read the same shared source but pull different conclusions out of it. Eight examples from the founding roster, with one concrete sample of what each produces.
-
Hephaestus
Solution architect
Decides what to build and how. Buy / build calls, stack selection, infrastructure design — written down before code happens.
What Hephaestus records as a decision
"Decision, recorded: codebase indexing and perpetual context are one product, not two. We market it as perpetual context and build it as a single index every project reads from. Anyone who joins later sees why — the record outlives the decider."
-
Hermes
Content generation
Generates copy that obeys your brand system. Same prompt produces consistent surfaces across every channel.
What Hermes writes from one structured prompt
"A regulator publishes a change at 9am. By 11am, legal has read it." → home hero · launch email · investor memo · Reddit post — same voice, same point, different surface.
-
Janus
External legibility
Reads your own work the way a buyer who has never heard of you reads it. Catches jargon before it ships.
What Janus flags on a draft
"The hero leads with three coined terms a first-time visitor has never seen — and never explains them. A new buyer bounces before the second paragraph. Define each one in plain English on first use, or cut it."
-
Cassandra
Adversarial verification
Pre-mortems your plans. Claim-audits your marketing copy. Refuses to be talked out of a real concern.
What Cassandra asks of a claim
"You're saying 'nothing forgotten.' How literally? Define the audit trail. Where does memory actually live, and what happens when a record goes stale?"
-
Apelles
Art direction
Decides where the page should feel beautiful, where it should stay quiet, and which single accent should carry attention.
What Apelles changes in a proof page
"The evidence is strong but visually flat. Give the source cards restraint, let the synthesis resolve in one accent, and make the limitation label impossible to miss."
-
Terpsichore
Motion systems
Turns state changes into motion grammar. Movement reveals the product logic instead of decorating the page.
What Terpsichore asks of an animation
"Source appears first, lanes settle second, synthesis resolves last. If motion does not teach the sequence, cut it."
-
Mnemosyne
Memory across sessions
Carries every decision, every open question, every dead-end across every session. Nothing falls.
What Mnemosyne surfaces at session start
"In session 7 the team chose Astro over Next because the marketing site is fully static and bundle size mattered. The current task touches that decision — flagging."
-
The Stranger
Cold-audience lens
Tests every surface against the confused-mind test. If a first-encounter reader gets lost, the surface fails before it ships.
What the Stranger says about this page
"You introduced eight personas in twelve seconds. Do I need to remember them? Tell me which one matters to me right now, or none of them stay."
Seven more personas ship in the full roster — domain experts for compliance, accessibility, design tokens, deployment governance, and others. The pattern is the same: each one a structured intelligence, not a free-text prompt.
v7 working draft
Knowledge-Backed Product Development, laid out in 30 pages.
How structured knowledge compiles into product surfaces — methodology, tooling, governance. Working draft of v7. Free.
Pick a path
Three doors. Same room.
For builders
Begin KBPD
Skip the demo. We'll prepare something specific to what you're shipping.
For technical evaluators
Explore the technology
Open formats. Real artifacts. No proprietary runtime.
For consulting partners
See the founding pricing
Launch window. Four SKUs. After the window, prices revert.