Local MCP in the starter kit.
Use an MCP-capable client to inspect the extracted kit without a hosted account.
Technology
YAML, JSON, Markdown. No proprietary runtime. No lock-in. Your knowledge files work whether or not we're around.
Portability guarantee
MCP Access Model
KBPD keeps structured knowledge in open files. MCP gives tools a controlled way to ask for the right slice: local and offline in the starter kit now, hosted and authenticated after the hosted-service gates clear.
Use an MCP-capable client to inspect the extracted kit without a hosted account.
Public accounts wait until sign-in, permissions, usage visibility, cancellation, billing, and support are operational. The starter kit includes a planned-not-live checklist so buyers can review the future service boundary without mistaking it for a current entitlement.
The repository remains the system of record. MCP reads from it; it does not replace it.
Agents receive the narrow slice needed for the current task instead of the whole repository every time.
Phase 2 adds sign-in, permissions, usage visibility, cancellation, and support before public accounts open.
Real artifact · copyable
This is a real visitor-journey artifact from the site you're reading. The FMEA risk priority numbers and step success markers in the file drove the layout, copy, and CTA placement of every page in this domain. The file is the spec. The page is the render.
# journey_consulting_partner.yaml
# A real journey artifact — selectable, copyable, runnable.
# Lives in the same Git repo your team already uses.
journey_id: consulting_partner_v2
audience: consulting_partner
goal: |
Decide whether KBPD is worth recommending to a client.
steps:
- id: S01
name: Land on kbpd.ai homepage
duration_seconds: 12
fmea:
severity: 9
occurrence: 6
detection: 5
rpn: 270
mitigation: |
Above-fold copy MUST be in outcomes language — never internal terms.
success_marker: scrolls_past_fold
- id: S02
name: Read the problem narrative
duration_seconds: 90
success_marker: shares_with_team
artifacts:
- what/docs/kbpd/regulation_change_scenario.md
- id: S03
name: Open Technology page
duration_seconds: 180
success_marker: copies_yaml_artifact
constraint: |
Real YAML must be selectable. Not a screenshot.
- id: S04
name: Decide to forward to a CTO
duration_seconds: 30
success_marker: cta_click
routes_to:
- cta_demo
- cta_overview_pdf
negative_flows:
- id: NF01
name: Bounces from homepage
cause: above_fold_internals_language
severity: 9
- id: NF02
name: CTO rejects
cause: technology_page_lacks_artifact
severity: 9
Stack · full disclosure
Nothing is hidden. The Claude API external dependency is disclosed explicitly, with the air-gap option named.
| Component | Technology | License | Data handling |
|---|---|---|---|
| Site framework | Astro 6 | MIT | static; build-time fetch |
| Style system | Tailwind v4 + DTCG tokens | MIT + W3C draft | config-as-code in Git |
| CMS | Payload 3 (Postgres) | MIT | self-hostable; customer-owned DB |
| Token build | Style Dictionary 4 | Apache 2.0 | deterministic transforms |
| Logo runtime | GSAP 3.13 + InertiaPlugin | free for commercial (2026) | CDN; cache-stable |
| Search/runtime AI | Claude API | commercial | optional; air-gap profile available |
| File delivery | Cloudflare | commercial | replaceable storage provider |
| Hosting | Cloudflare Pages or VPS | commercial / open | replaceable |
Specifically for evaluators
If you're evaluating fit for a CTO, send a real technical question. We answer with a real technical response.
Open a technical thread →