Security and production use

Request boundary

Production applies these controls before /mcp and /v1:

1. Explicit Host validation and optional browser Origin allowlisting.
2. Constant-time bearer-key verification.
3. Per-instance identity/IP rate limits, request IDs, schema bounds, and timeouts.
4. Structured JSON logs that exclude tokens, query strings, and document bodies.
5. Public liveness and release-aware readiness with graceful draining.

Secret handling

• Keep API keys in a secret manager or client password store.
• Prefer environment-variable references in MCP configuration.
• Never embed a bearer key in documentation, source control, screenshots, or agent prompts.
• Rotate by adding the replacement key, verifying clients, then removing the old key.

Static keys are appropriate for the current single-tenant production proof. A public multi-tenant product should use OAuth 2.1 and shared gateway quotas without changing the tool contracts.

Publication trust

Directory contents are never a production trust root. The runtime accepts only a promoted, policy-approved, hash-verified release with compatible schema and attestation bindings.

Engineering trust

Errata helps retrieve and audit evidence. It does not transfer responsibility for:

• selecting the correct physical order code and package;
• checking all fact conditions against the design;
• reviewing normative publisher documentation;
• validating board-level analog, timing, thermal, and EMC behavior;
• obtaining missing package- or revision-specific guarantees;
• deciding whether a residual gap is acceptable.

When the service returns blocked, partial, not_indexed, or no_match, resolve the evidence gap before sign-off rather than substituting a nearby claim.

Report a security issue

Send a private report to Tyler Gibbs. Include the affected service version or corpus release, reproduction steps, impact, and a safe way to follow up. Do not include live credentials or confidential customer data.