Skip to content
Puccha Puccha KM

For the Puccha team (Internal)

Updated 2026-09-18 · owner natthawat@harmonyx.co · overview

This section is visible only after signing in with a team email (Cloudflare Access). Almost everything here is rendered from docs/ in the repository on every deploy (ADR-0206).

Where to start

Section titled “Where to start”
You need Read
How Puccha decides on each turn, with code locations How Puccha thinks
The secret sauce: real prompts, tuning values, personas, golden sets Secret sauce · knobs
Why it was designed this way Architecture Decision Records in the repo (200+) — KM articles cite the relevant ADRs in their sources
Where things run, what each environment is Environments · SLO
Something is broken Runbooks · Operations
Data model and API surface Data model · API surface
Threat model, PDPA, ISO Security · Compliance
Why we sell it this way Product

Ask Puccha about internal matters

Section titled “Ask Puccha about internal matters”

Everything in this section is pushed into the knowledge base of the puccha-staff tenant, which is interlocked (ADR-0182, ADR-0183) — it answers only requests that carry a staff token. Two ways in:

  1. The chat button on these pages. Every internal page fetches a token from the Worker for the widget automatically once you are signed in. Just ask.
  2. From Claude Code / Claude Desktop over MCP. Create an API key on the puccha-staff tenant (viewer role or above) and add the MCP server per MCP client onboarding. MCP requests pass checkAcl with the key’s role, so no token is needed.

When Puccha says it has no information, that is a knowledge gap worth writing into docs/. The gap list is under Inbox → Gaps on the puccha-staff tenant.

Editing content

Section titled “Editing content”
  • KM articles (like this one): docs/km/<audience>/<slug>.<lang>.md — Markdown + standard frontmatter per docs/km/README.md, portable to any other system without conversion.
  • Design docs, runbooks, ops: edit docs/<dir>/ in the repo as usual. The “Edit page” link at the bottom opens the exact file on GitHub.
  • After a merge the deploy rebuilds the site. Puccha’s knowledge base is refreshed separately with node scripts/km-sync.mjs (ADR-0206 § One-time operational steps).