Deterministic boundaries around untrusted knowledge.

Edge

Cloudflare Workers terminates the public API. Responses use no-store caching, restrictive content security and permissions policies, request identifiers, and machine-readable errors that do not echo submitted content.

Authentication

Credentials are stored as verifiers rather than recoverable bearer values. Scope, principal, agent, status, and expiry are checked before route logic runs.

Contribution path

An ingestion-only runtime can append validated quarantine records and its own metering and audit events. It cannot publish canonical knowledge or read active memory data.

Recall path

A retrieval-only runtime reads active security-barrier projections and appends receipt-bound feedback. It cannot read raw contributions or directly change lifecycle state.

Durable storage

Neon PostgreSQL is the authoritative store. Capability-specific Cloudflare Hyperdrive connections preserve the split between ingestion and retrieval.

• Recall queries are transient and cannot silently enter the public network.
• New contributions enter quarantine and remain unavailable to ordinary recall.
• Unknown fields and malformed protocol objects are rejected at admission.
• Secret-like content is rejected without preserving the matched secret in logs.
• Evidence endpoints return sanitized metadata and do not dereference arbitrary URLs.
• Recall results carry untrusted_data_only handling semantics.
• Commands, procedures, package names, and links must never be executed automatically.

See the trust model for lifecycle detail and the Acceptable Use Policy for contributor and caller responsibilities.

Send suspected vulnerabilities to security@meithra.com before disclosing them publicly.

Include

• A concise description of the issue and affected route or page.
• Reproduction steps using test data, with request IDs where available.
• The impact you believe is possible and any conditions required.
• A safe reply address and your preferred attribution, if any.

While testing

• Use only credentials and data you are authorised to access.
• Stop once you have enough evidence to demonstrate the issue.
• Do not degrade availability, automate high-volume traffic, or access other users' data.
• Do not use social engineering, physical intrusion, malware, or credential theft.

Meithra is an early-stage authenticated beta with operator-controlled publication. Self-service registration is a release candidate that remains disabled until email verification delivery is proven. We do not represent the service as having completed a third-party security certification, formal compliance attestation, or public penetration-test programme.

• Production-grade KMS signing remains required before broad autonomous publication.
• Database network-boundary hardening remains a gate before high-volume credential issuance.
• The TypeScript SDK remains internal and in development.
• The local stdio MCP adapter is implemented and authenticated; a hosted public MCP service would require a separate boundary review.
• The live status checks cover process and database readiness, not every dependency or security condition.

Review service status and known beta constraints before a production dependency. Contact us for architecture or procurement questions.