Build Standards

01 · Integration Patterns (DEC-003)

4 locked patterns

Every system interaction uses one of these patterns. No new pattern without a DEC-NNN register entry — pattern discipline is the governance mechanism.

• mgp-api

  System/automation caller. Service principal. All DB/Xero/Stripe calls. No UI touches data stores directly.

• mgp-mcp

  AI model caller. OBO/delegated auth. Explicit tool allow list. Class 3 default.

• mgp-webhook

  Inbound event ingress. HMAC verified. Sub-pattern of mgp-api.

• mgp-portal-api

  Authenticated human REST. WorkOS AuthKit / CF Access. No AI. Define before portal build.

02 · Build Package Standard

Tier 1 / 2 / 3 file checklist

Every package scaffold starts from templates/new-package/. Tier 1 is mandatory; Tier 2 & 3 apply when the package deploys an agent or integrates external systems.

03 · GitHub Projects Lifecycle

Work-item conventions

Shared vocabulary across every Mandantis repo. Principal-only actions highlighted.

04 · Kill-switch Pattern (DEC-004)

Every Worker has a kill switch

Read-only check against a Cloudflare KV key. The key lives in the shared mandantis-platform namespace; the Worker never writes to it. /health is exempt so oncall can probe during maintenance.

// src/middleware/kill-switch.ts
import type { Context, Next } from 'hono'

export const KILL_SWITCH_KEY = 'service:<package>:enabled'

export interface KVGetter {
  get(key: string): Promise<string | null>
}

export async function killSwitchMiddleware(
  c: Context<{ Bindings: { KILL_SWITCHES: KVGetter } }>,
  next: Next,
): Promise<Response | undefined> {
  if (c.req.path === '/health') {
    await next()
    return
  }
  const value = await c.env.KILL_SWITCHES.get(KILL_SWITCH_KEY)
  if (value === 'false') {
    return c.html(maintenanceHtml(), 503)
  }
  await next()
}

05 · Monorepo Commands

Run from repo root