Categories › AI & Agents › Multi-agent, orchestration & workflows
Doctrine and validators for governable agentic AI products.
Remote server: your requests and data go to aidesignblueprint.com. Claude Code: claude mcp add --transport http ai-design-blueprint https://aidesignblueprint.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
principles.list — List Blueprint doctrine with stable slugs, titles, and clusters. The lens selects which of the three public doctrines: 'architecture' = the clusters.list — List all principle clusters with their stable slugs and linked principle titles. Use this to discover which clusters exist before drilling iprinciples.get — Get one doctrine entry by stable slug. The lens selects the doctrine: 'architecture' = one of the 10 agentic principles (default); 'surface'clusters.get — Get one principle cluster by stable slug. Returns the cluster definition, shared rationale, and the full set of member principles (slug + tiexamples.get — Get one curated example by stable slug. Returns title, summary, source-code links, principle coverage (the principle slugs the example demonprinciples.search — Search Blueprint principles by free-text query and return the closest matches ranked by relevance. Use this to find principles related to a examples.search — Search curated examples by free-text query, ranked by relevance, with optional filters: principle_ids (only examples covering those principlassets.list — Public: list downloadable doctrine and agent asset artifacts (skill packs, rule packs, MCP setup snippets) the user can drop into their AI cguides.list — List application guides that show how Blueprint principles apply to engineering challenges (security, evaluation, observability, etc.). Use guides.get — Get a full application guide by its stable slug (e.g. 'security-application', 'observable-evaluation'). Returns sections, action items, and guides.search — Search application guides by free-text query, matched against section answers and action items. Use this when the user describes an engineersignals.report — Records a value moment (e.g. review_confidence, runtime_risk_found, workflow_clarity) after a successful validate run on any lens (architectsignals.feedback — Public: records explicit free-text user feedback about the Blueprint, this tool surface, or a specific principle/example. Captures two 1-5 rarchitect.validate — Pro/Teams: first-pass doctrine review of agentic code/workflow against the 10-principle AI Design Blueprint doctrine. ON CLIENT TIMEOUT: DO design.validate — Pro/Teams: first-pass surface-craft review of a FRONTEND artefact (component, screen, or flow) against the 8 laws of the Experience Design Bspec.validate — Pro/Teams: first-pass specification-quality review of a WRITTEN SPEC (proposal, design doc, task breakdown, or an OpenSpec-style change bundarchitect.validate_consensus — Pro/Teams: N-shot CONSENSUS doctrine review of agentic code. ON CLIENT TIMEOUT: DO NOT RETRY THIS TOOL. Long-running (~80-120s for N=3 paralarchitect.certify — Pro/Teams: second-pass adversarial certification of an architect.validate run that scored production_ready (A or B first-pass tier). ON CLIEteam.summarize — Teams/Enterprise: summarises the caller's tool-usage patterns and value signals over a configurable window (default 30 days). Returns periodme.learning_path — Authenticated: returns the caller's Blueprint learning-path state: current course slug, stage progress, certification status (Foundation, Prme.coaching_context — Authenticated: returns stages in the caller's active course where recorded evidence is thin relative to the stage's principle requirements. me.add_evidence — Authenticated: append a free-text evidence note to a specific stage in the caller's active course. Notes record concrete implementation obseme.sessions — Pro/Teams: list or inspect the authenticated user's Governed Sessions (GEP-M2): durable, owner-scoped containers that group validation runs me.session_event — Pro/Teams: append a TYPED TEAM EVENT to a Governed Session's timeline (GEP-M6). This is how the user's own harness makes trio work inspectabme.await_steer — Pro/Teams. BLOCK until the session owner posts the next `steer` event to a Governed Session from AIDB Studio, then return it. DELIVERY GUARAme.validation_history — Pro/Teams: return the authenticated user's validation run history for all three lenses (architect.validate → validator='architecture', desighandoffs.operator — Authenticated: creates a support handoff record when an agent needs human review, account-specific escalation, or operator follow-up that cahandoffs.partnership — Authenticated: creates a partnerships handoff record for design-partner, ecosystem, training, or advisory conversations needing human reviewhandoffs.agency — Authenticated: submit an agency engagement enquiry on behalf of the caller for a founder-led discovery call. Persists an AgencyHandoff row rNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.