Every other platform in our space holds static data and ages. We get more right every week. That is the moat in the AI era.
The RSI Heartbeat is the platform. One self-improving knowledge graph per garden, ingesting source data on a domain cadence, re-verifying every entity, surfacing freshness on every claim, learning from use. The platform doesn't hold knowledge — it improves itself.
— Live signal — per-garden cadence —
HKG
Healthcare Garden
Cadence · monthly
PKG
Parenting Garden
Cadence · weekly
BKG
Builder's Garden
Cadence · continuous from contractor activity
OKG
Orchid Garden
Cadence · quarterly from Ecuagenera + AOS
The Architecture
One picture. The whole platform.
Every garden inherits this skeleton. The skin changes per domain — codes versus species versus compounds versus case law — but the lanes, the surfaces, the heartbeat, and the federation contract do not.
Four umbrella lanes. Three surfaces. One self-improving graph beneath them all.
The Pattern
Four lanes ✕ three surfaces ✕ one graph.
Every garden in the platform composes from this skeleton. Sub-lanes nest inside the four umbrella lanes per domain — BKG has eight sub-lanes, HKG has five, OKG has six — but the four umbrella lanes are universal.
The Four Lanes
01
Administrator
Hospital admin · GC · Nursery operator · Ops — the buyer of operations SaaS
02
Professional
Doctor · Contractor · Grower · Lawyer · Advisor — the practitioner
AI agents · EHR vendors · integrators — first-class citizens, never afterthought
The Three Surfaces
Surface 01 · Gold
Dream Machine
aspirational · concierge · warm
Primary Lane
Public
Cardinal Feature
Emotional Arc
Surface 02 · Green
Knowledge Garden
scientific · verified · citation-rich
Primary Lane
Professional
Cardinal Feature
TrustStrip · Three-Source Rule
Surface 03 · Red
Killer App
operational · urgent · status-aware
Primary Lane
Administrator
Cardinal Feature
Tempo Adapt
The Pattern Language
Twenty pieces. Composes anywhere.
Christopher Alexander cataloged 253 patterns across scales. The Knowledge Gardens language is much smaller — sixteen sixteen-ths the size — sized for a small team to specify, build, and inherit across every garden. Hover any piece to see what it does.
Constitutional · 01
Invitation Card
One plain question, one primary action, optional pro subtitle, optional whisper.
Constitutional · 02
Emotional Arc
Sequenced flow matched to the user's emotional state.
Constitutional · 03
Whisper
One-time, one-sentence self-introduction near an element on first encounter.
llms.txt + JSON-LD on every entity. MCP endpoint per garden. The agent is a first-class user.
Rendering · 12
Infinite Descent
Variable-floor engagement depth per workflow. Floor 0 plain question, descending to agent payload.
Rendering · 13
Modality Mirror
Visual, voice, gestural, agent-API renderings of every workflow.
Rendering · 14
Tempo Adapt
Primitives breathe differently under different pressure — leisurely to emergency.
Rendering · 15
Cultural Render
Language, units, jurisdiction, conventions as first-class data — not settings.
Rendering · 16
Accessibility Adapt
Color, motor, cognitive, neurodivergent profiles operationalized — not posture.
Rendering · 17
Cross-Surface Bridge
Context flows Dream → Garden → Killer App without retyping.
Rendering · 18
Lifecycle Memory
Same project, same user, multi-year. Surface context across stages.
Rendering · 19
Trust Posture Adapt
Platform defensiveness scales inversely with user trust. First-time visitor gets reassurance; long-term user gets shortcuts.
Rendering · 20
Stance Card
The operational mechanism. 14-axis snapshot of where the user sits in state space. Every primitive reads it.
Constitutional (7) — locked April 16Platform (4) — federation contractRendering (9) — new for 2026
How to read this section
A piece is a reusable design pattern — like "always show a save button" but more specific. Build a workflow with the right pieces and it works for every kind of user, on every kind of device, in every kind of moment.
An axis is a way users differ from each other. There are fourteen. A homeowner and a master plumber differ on the skill axis. A worker logging from a muddy job site and a financier reviewing on a laptop differ on the device, modality, and tempo axes. The Stance Card is the live snapshot of where each user sits on all fourteen.
Each piece below shows: a plain-English explanation, three real examples from the Builder's Garden, which axes the piece touches (14 dots — lit = relevant; double-ring = primary), and why it matters.
01The Constitutional Primitives — locked April 167 pieces
01Invitation CardConstitutional
A page leads with one clear question and one clear next step. No menus, no options, no fork in the road. One welcoming door in.
/intro hero
A homeowner arrives and sees one question, one mic-or-type input, nothing else.
contractor onboarding
A new GC signs in and sees only the three soonest-expiring credentials, sorted by urgency.
Dream Machine · Oracle
A first-time homeowner sees one input, one alternative path. No style picker grid to choose from.
Axes touched
1234567891011121314
Primary: Lane and Trust posture. Also touches Surface, Skill, Modality, Tempo.
A user who knows what to do next is a user who keeps going. The number-one cause of bounce is "I don't know where to start."
02Emotional ArcConstitutional
The flow through a task is sequenced to match how the user feels at each step — curious at first, building confidence in the middle, committed by the end.
Equipment Schedule walkthrough
A homeowner moves from worry to confidence to commitment over three Floor levels — same page, three emotional gears.
renewal flow
A contractor moves from worry (red) to control (green) to celebration (gold) across the renewal pipeline.
/intro cinematic
The 90-second cinematic intro is an emotional arc encoded as scroll position — mood as timeline.
Axes touched
1234567891011121314
Primary: Emotional state. Also touches Surface, Stage, Tempo, Time horizon, Trust posture.
People remember how something felt, not what it said. A platform that respects emotional state earns repeat visits.
03WhisperConstitutional
The first time a user meets a feature, a single sentence quietly explains what it is. After that, the whisper disappears forever — the feature speaks for itself.
Dream Machine · Oracle
First time you see the input, one quiet line tells you it accepts voice. Second visit, it's gone.
budget cockpit
First view of the budget cockpit shows one line explaining how the numbers connect. Then the whisper retires.
Time Machine icon
First time a user hovers the rewind icon, one sentence. Forever after, the icon is enough.
Axes touched
1234567891011121314
Primary: Trust posture (the first-time signal). Also touches Surface and Skill.
A user shouldn't have to read a manual to understand a button. But after they've used it once, they shouldn't have to re-read the manual either.
04Time MachineConstitutional
Anywhere in the Builder's Garden, you can step back in time to see what changed, recover what you abandoned, or undo what you regret. Fear of breaking something is the number-one reason users hesitate.
Estimating session
The Estimating flow keeps a stateful breadcrumb of every decision. Rewind to any point and continue from there.
Daily Field Log
A foreman signs off the wrong field log. One tap returns it to draft. No audit flag, no escalation.
Dream Machine returning user
A homeowner abandons Dream halfway through. Coming back weeks later, every draft waits in the drafts tray.
Axes touched
1234567891011121314
Primary: Time horizon and Trust posture. Also touches Surface, Stage, Emotional state.
Fear of breaking something keeps people from clicking. The Time Machine removes the fear; the platform becomes safe to explore.
05Ask AnythingConstitutional
A search-and-ask box that's always one tap away and that knows what page you're on. You never have to leave the screen to ask "what does this word mean?"
Equipment Schedule
Ask "what's a Manual J?" on the Equipment Schedule page. Answer appears inline with sources, without leaving.
AIA Pay Application
On the Pay App, "what's a retainage release?" answers with the contractor's own contract numbers filled in.
Dream Machine
Ask Anything pivots between aesthetic questions and budget questions fluidly. Same box, different intents.
Axes touched
1234567891011121314
Primary: Skill. Also touches Surface, Stage, Modality.
Most user friction is "I don't know what this word means." Ask Anything kills that friction wherever it appears.
06Pro ToggleConstitutional
A single visible switch at the top of every page. Flip it: labels change from plain language to pro vocabulary, ordering changes from human-default to operational. The underlying data doesn't change.
Equipment Schedule
Same number, two labels. Homeowner sees the first; MEP sub sees the second.
project pipeline
Human mode: three friendly cards. Pro mode: Gantt-style critical-path timeline. Same project.
Daily Field Log
Plain-spoken in human mode. Structured CSI codes in pro mode. The pro doesn't sacrifice clarity to gain precision.
Axes touched
1234567891011121314
Primary: Skill (continuous signal). Also touches Lane and Cultural frame.
A 9-year-old and a 30-year master plumber can both use the same screen without either feeling patronized.
07Progressive RevealConstitutional
Advanced controls only appear after the user has used the basic controls a few times. Power features earn their way onto the screen — they don't ambush newcomers.
Daily Field Log
First log: one question. After three logs, weather and crew and materials sections appear.
Dream Machine Oracle
First visit: just describe. After first successful render: style mixer, palette extractor, scale slider appear.
AIA Pay Application
First pay app: just the amount. By the third, three power controls appear at the top — earned.
Axes touched
1234567891011121314
Primary: Skill and Time horizon (within-project tenure).
New users get a clean room. Power users get a workshop. The room becomes the workshop as the user proves they want one.
Every important fact on a page wears a small badge showing where it came from, when it was last verified, and whether anyone disagrees. Provenance is visible without being noisy.
Equipment Schedule
The HVAC sizing claim wears a small green strip: 3 sources, freshness, primary citation.
Code Compliance Lookup
Three verified, one contested. The user sees the disagreement instead of a fake-confident answer.
supplier marketplace
A material spec on a supplier listing also wears a TrustStrip. Sources, freshness, safety-cited concerns surface.
Axes touched
1234567891011121314
Primary: Trust posture. Also touches Domain, Lane, Skill, Cultural frame (jurisdiction).
Without provenance, AI-generated knowledge is rumor. With provenance, it's evidence. The TrustStrip is how the platform earns the right to be trusted.
09Three-Source RulePlatform
Nothing in the Builder's Garden renders as a fact unless three independent sources agree. If the sources disagree, the user sees all sides — not a single confident wrong answer.
HVAC sizing rule
UPC, ACCA, and ASHRAE all agree on the rule of thumb. Three sources converge → the claim renders.
Marin permit fee
Three sources agree on a range, not a single number. The platform shows the range, not a fake-precise figure.
when sources are insufficient
When fewer than three sources corroborate, the platform doesn't hide it. The user sees the caveat and the path to real verification.
Axes touched
1234567891011121314
Primary: Domain and Trust posture. Also touches Cultural frame (jurisdiction-specific sources).
"I asked the AI" is not a source. Three independent sources are. This is what separates a knowledge graph from a chatbot.
10Federation ContractPlatform
Every page on every garden follows the same shape — same header, same fonts, same JSON-LD, same cross-link discipline. Users moving between gardens never feel lost.
cross-garden navigation
A user jumps from BKG to OKG and the header, type, and rhythm are identical. Different content; same building.
contractor profile
A specialty contractor's profile pre-anchors cross-links to a future EdKG. The federation contract is the wire.
MCP endpoint
An agent calls BKG's MCP endpoint and gets JSON-LD in the same shape as OKG, TKG, HKG. Federation for machines.
Axes touched
1234567891011121314
Primary: Surface (cross-garden continuity) and Lane (Machine especially). Also touches Domain.
Cross-garden navigation is the platform's superpower. The federation contract is what makes a 55-garden constellation feel like one native experience.
11Machine-Legible EverythingPlatform
Every page, every entity, every claim has a version a robot can read. The agent is not an afterthought — it's a first-class user, with the same access humans get.
MCP endpoint
An agent pulls the entire Equipment Schedule as structured JSON. Same data the human page renders; no scraping.
third-party integration
A Procore-replacement system reads BKG's AIA Pay App via JSON-LD and ingests it as a structured transaction.
agent on user's behalf
An agent acting for a homeowner reads the structured permit data, submits the renewal via API, and reports back.
Axes touched
1234567891011121314
Primary: Lane (Machine) and Modality (agent-API). Also touches Surface and Device class.
AI agents are becoming users. Plan for them — or lose the user who delegated their work to one.
03The Dimensional Renderings — new for 20269 pieces
12Infinite DescentRendering
Every workflow has floors. Floor 0 is a plain question. Each successive floor goes deeper into the math, the code, the procurement, the agent payload. Every user finds their floor without being gated.
Equipment Schedule
Six floors. A homeowner stops at F2. A GC stops at F4. An MEP sub stops at F5. An agent reads F6. Same page.
AIA Pay Application
A GC stops at F3 to confirm variance. The bank reviewer stops at F5. The agent submits at F6.
Permit search
A homeowner: "I need permits." The platform descends through checklist, pre-filled forms, code, API submission.
Axes touched
1234567891011121314
Primary: Skill (depth-scaling). Also touches Stage and Lane.
A homeowner stops at Floor 2. A GC stops at Floor 4. Same page. Both happy. No one is gated. No one is patronized.
13Modality MirrorRendering
Every primitive renders in four registers — visual, voice, gesture, and agent-API — and they mirror each other. What you can tap, you can also speak; what you can speak, an agent can POST.
Daily Field Log
A foreman speaks the log walking to the truck. A super taps it. A wearable webhooks the same shape. One entity, three doors.
Project setup
Voice in the truck, keyboard at the desk, curl from the procurement bot. Same fields, same validations, same audit trail.
Equipment Schedule
An MEP reads the table. A site super asks "what's RTU-1 sized at?" out loud. A procurement agent pulls the JSON. Same schedule.
Axes touched
1234567891011121314
Primary: Modality and Device class. Also touches Accessibility, Surface, and Lane.
The user picks the door, not the platform. A wet glove, a quiet car, a kitchen counter, an automation queue — all valid entry points to the same primitive.
14Tempo AdaptRendering
Primitives breathe per time pressure. The same card shows its full self at 32 days out; at 2 days out it strips to one button and one number.
Compliance alerts
Day 32: dimensional, calm, full hierarchy. Day 2: one number, one button. The card is the same primitive — it just learned to whisper less.
Daily Field Log
Calm morning: four sections, full notes. Lightning in the sky: one question. Everything else waits.
AIA Pay Application
Day 25: every field, every checkbox. Day 30 at 12:18pm: timer, total, one button. The draft is already saved.
Axes touched
1234567891011121314
Primary: Tempo (time pressure). Also touches Emotional state and Time horizon.
Cognitive load is highest exactly when time is shortest. A platform that adds chrome under pressure loses the user. A platform that strips chrome under pressure earns the user for life.
15Cultural RenderRendering
Language, units, jurisdiction, and currency are data — not branding. The same primitive renders in US tons and 240 volts for Phoenix, in kilowatts and 220 volts for Monterrey, with no separate codebase.
Equipment Schedule
12 tons becomes 42 kW. 240 V becomes 220 V. IBC becomes RCDF. Same primitive, different render — and the JSON underneath carries both.
Permit search
A search for "occupancy classification" returns CBC Chapter 11A in Oakland and IBC Chapter 4 in Austin. Same question. Locally correct answer.
Pay Application
G702 / USD / retainage / notary in Phoenix. CCDC 12 / CAD / holdback / statutory declaration in Toronto. Same primitive. Different country's math.
Axes touched
1234567891011121314
Primary: Cultural frame (locale). Also touches Domain and Economic position.
Localization isn't a translation file. Jurisdiction, currency, contract template, and code reference are first-class fields on every entity. The platform crosses borders without a rebuild.
16Accessibility AdaptRendering
Color, motor, cognitive, and neurodivergent profiles are operational settings — not afterthoughts. The same primitive ships at default, then re-renders at 1.4× type, one-task-per-screen, or thumb-sized tap targets without losing any function.
Budget cockpit
Default: dense, four numbers, a hairline bar. Low-vision: same numbers at 1.4×, sharper contrast, hairline bar becomes a real bar.
Estimating flow
Default: six fields on one screen. Quiet mode: one question per screen, no peripheral chrome. Same six answers reach the same record.
Mobile Field Log
Default: nine icons in a grid. Motor-impaired: three full-width thumb targets. The hand in a glove gets the same log.
Axes touched
1234567891011121314
Primary: Accessibility. Also touches Device class and Modality.
Accessibility is not a compliance audit done at the end. It is a render mode declared on the Stance Card, the same way locale is. Build it into the primitives or pay forever to retrofit.
17Cross-Surface BridgeRendering
Context flows Dream Machine → Knowledge Garden → Killer App and back, without retyping. A sketch on Saturday becomes a phase anchor on Monday becomes a pay-app line in June.
Dream → Pay App
The homeowner's napkin sketch becomes the phase the GC bills against six months later. The provenance line never breaks.
Garden → Plan
A code citation in the Knowledge Garden auto-populates the Plan-stage compliance worksheet — with the source link still attached.
Log → Supplier
"Countertop slab cracked at corner" — the platform tags it, links it, and surfaces three matching suppliers without anyone typing a search.
Axes touched
1234567891011121314
Primary: Surface. Also touches Stage and Lane.
Three surfaces with no bridge are three tools. Three surfaces with shared entities are one platform. Every piece of context the user gave once should never be asked for again.
18Lifecycle MemoryRendering
Projects live for years. The platform remembers everything it promised and shows it back, so today's decision sits next to yesterday's estimate.
Reflect stage
A year later, the homeowner sees April 2026 next to April 2027. The promise next to the outcome. No spin. No deletion.
AIA Pay App
The roofing line on the pay app is annotated with the June estimate it grew out of. Variance is shown, not hidden, and the GC can speak to it before the owner asks.
Crew timeline
The framer sees last project's four-day pace next to this project's three-and-a-half. The platform remembers what they're capable of.
Axes touched
1234567891011121314
Primary: Time horizon. Also touches Stage and Lane.
Construction tools forget the moment the punch list is signed. A platform that remembers across the lifecycle is the only one that compounds. Memory is leverage.
19Trust Posture AdaptRendering
Defensiveness scales inversely with user trust. The first time you do something, the platform double-checks. The fiftieth time, it gets out of the way.
Submit confirmation
First submission: a modal, a summary, two buttons. Fiftieth submission: a toast that says "submitted." The platform knows who knows what they're doing.
Listing rollout
A new contractor's first listing goes through four review steps. A tenured contractor's fiftieth publishes in four seconds. Trust earned is friction removed.
Export caveats
The first export ships with three warning bands. The fiftieth ships clean — the platform has watched the user do this enough times to trust the output.
Axes touched
1234567891011121314
Primary: Trust posture. Also touches Skill and Time horizon.
A platform that never relaxes treats every veteran like a beginner. A platform that adapts trust earns the right to be the system of record.
20Stance CardRendering
The operational mechanism: a 14-axis snapshot every primitive reads before it renders. Domain, surface, stage, lane, skill, modality, device, tempo, emotion, locale, accessibility, economic, horizon, trust — fourteen fields, one structured truth.
Homeowner · Saturday
Lane: public. Device: phone. Tempo: leisurely. Skill: 0.2. The Stance Card resolves to F0 — a warm, sparse invitation card. Nothing else fits.
Contractor · Friday 5pm
Lane: pro. Device: desktop. Tempo: urgent. Skill: 0.9. Same Stance Card mechanism resolves to F4 — a dense procurement worksheet ready to fire.
Agent · 2:14 UTC
Lane: machine. Modality: agent-API. The Stance Card resolves to F6 — a signed JSON-LD payload, no chrome, no prose, ready to be acted on.
Axes touched
1234567891011121314
Primary: Lane and Surface — but the Stance Card is the only primitive that reads all fourteen axes at once. Every other piece reads a subset of what this one assembles.
The Stance Card is not a feature — it is the operational mechanism that makes the other nineteen pieces possible. Every primitive reads it. Every agent reads it. Every render is a function of it. This is what "all four lanes always" means in code.
The Stance Card
Fourteen axes. One structured truth.
Every primitive reads the Stance Card before rendering. Every agent reads it to act on the user's behalf. This is what "all four lanes always" means in code.
construction · botany · toxicology · law · health · …
02
Surface
garden · dream · killer-app
03
Lifecycle stage
domain-specific stages
04
User lane
admin · pro · public · machine
05
Skill level
zero-knowledge → master
06
Modality
visual · voice · gesture · agent
07
Device class
phone · desktop · xr · agent endpoint
08
Time pressure
leisurely → emergency
09
Emotional state
curious · anxious · confident · mournful
10
Cultural frame
language · jurisdiction · units
11
Accessibility
vision · hearing · motor · cognitive
12
Economic position
$0 DIY → institutional
13
Time horizon
this minute → my life
14
Trust posture
first-time skeptic → long-term advocate
The Frontier
Fifty-five gardens. One template.
Three deployed. Two building. Ten industry-scoped post-seed. Forty research-grade frontier gardens parked behind a strict gate — frontier gardens do not get built until HKG and BKG generate MRR. Every garden inherits the same skeleton; the skin changes per domain.
0
Gardens in the roster
3
Deployed
Proof the pattern deploys. Live in production with real users, real data, real revenue paths.
OKG · BKG · TKG
2
Building
The cash engine and its consumer gravity well. MLP in progress, data layers wiring.
The Pattern Language gets its first comprehensive application on the surface that pays for everything else — the Administrator lane on the Red Killer App.
Every rebuilt surface composes from the twenty pieces. Every workflow answers the four umbrella lanes' Floor 0 questions before code. Every primary claim wears a TrustStrip. Every authoritative claim cites three sources. The GreenFlash CRM reward loop — particle effects and Web Audio chimes — survives the rebuild intact.
Claude Design (pending enablement) or Cowork with parallel agents on the existing Next.js codebase
Hard gate
Every spec answers four umbrella lanes' Floor 0 questions before any code is written
Wisdom of the Ages
Eight teachers underwrite this work.
Each names a load-bearing principle. Together they form the intellectual scaffolding of the Pattern Language.
Christopher Alexander
A Pattern Language
Patterns of user action cannot be separated from the lane, surface, and stage where they occur. The central metaphor.
Edward Tufte
Small multiples
Same shape, different content, side-by-side. The eye learns the shape and then sees variation. The smallest effective difference.
Donald Norman
The Design of Everyday Things
Every element announces its function to every body, in every culture, in every modality.
Bret Victor
Direct manipulation
Stop drawing dead fish. Build tiny live instruments at every floor of every workflow.
Frank Lloyd Wright
Compression and release
The platform breathes the user through compression and release at the architecture-of-experience scale.
Mister Rogers
Look for the helpers
The platform surfaces helpers. It never replaces them. This is brand-defining.
Toyota Production System
Jidoka and Poka-yoke
Automate with a human touch. Design errors out of the system. The "eight Floor 0 questions" rule is poka-yoke for spec drift.
Steve Jobs and Jony Ive
The embodied constraint
Design relentlessly to the single most primal user constraint. For us, that constraint is the arrival stance in state space.
The ground truth AI needs to survive.
The investor line. The internal line is "the pattern that builds products." Both are true. The platform is one architecture, fifty-five gardens, four lanes, three surfaces, and one self-improving knowledge graph that gets more right every week. Frontier gardens stay parked until the cash engines (HKG, BKG) generate MRR. The current focus is the BKG Killer App rehaul, the first comprehensive application of the twenty-piece Pattern Language.