Shipped — v1.0

One graph. Three grounding types.

Message House, Engineering Spec, and Policy Shield share one mechanism: typed entries, content-tier locking, and a cross-domain graph. Each one points that mechanism at a different kind of truth, from positioning statements to API contracts to legal language.

Grounding Type · Engineering

Engineering Spec

For when a copilot needs to know the real rate limit, not a plausible-sounding one. Five section types, each tied to something a developer actually has to get right.

api_contract

A specific endpoint behavior, parameter, or rate limit — the thing copilots most often hallucinate.

sla_commitment

An uptime, latency, or support-response commitment your team has actually agreed to.

versioning_policy

How long a version is supported, and what breaks when it's dropped.

deprecation_notice

What's going away, when, and what replaces it.

security_requirement

A security control or requirement — TLS version, auth method, logging requirement.

Grounding Type · Legal & Compliance

Policy Shield

For language that has to come out exactly as written, every time — no AI tool improvising a compliance answer.

legal_disclaimer

Language that must appear verbatim — never paraphrased, never summarized.

privacy_rule

A specific data-handling commitment tied to an actual policy, not a general privacy-page platitude.

compliance_assertion

A specific, reviewed claim about a certification or control (SOC 2, GDPR, etc.).

compliance_response

The pre-approved answer to a question customers or auditors actually ask.

One real example, not a hypothetical

This is live on the public demo instance right now, not a mockup: a Policy Shield entry depending on an Engineering Spec entry, across two different departments' domains.

Engineering Spec

api_contract

"Rate limit: 100 req/sec on all /v2/ paths."

DEPENDS_ON →

Policy Shield

legal_disclaimer

"Rate limits are subject to the terms in the current API contract."

Change the rate limit in Engineering Spec, and that legal disclaimer gets flagged outdated automatically — Legal doesn't find out about an API change from a customer complaint. See the full traversal on the grounding mechanics page.

Not just a marketing tool.

Message House, Engineering Spec, and Policy Shield run on the same self-hosted graph. Ground your own department's truth, or add a fourth.

See the Full Canon Model Read the Docs →