Dual access / One truth

Two public presentations. Linked evidence records.

People receive complete semantic HTML. Public agents receive read-only JSON and Markdown exporting selected shared evidence records. The repository contains a control-plane ledger for future private operations, but the public deployment exposes no operations API and executes no changes.

No user-agent cloaking
01

Human access

The human website is the canonical, indexable authority. It requires no live model, machine API, animation, or JavaScript to communicate its essential content.

  • Semantic HTML
  • Visible sources and limitations
  • Readable FAQs
  • Accessible navigation
  • Independent availability
02

Public machine access

The open API is read-only and accessible to anyone. Records link to canonical human pages and expose schema versions, dates, source references, claim status, and limitations where applicable.

  • JSON and Markdown
  • Noindex duplicate renderings
  • Versioned manifests and receipts
  • No hidden facts or crawler-only keywords
  • No execution authority
03

Private operations

The source includes a tenant-scoped job and approval ledger for future use. The public Worker denies every operations path before application routing or database access, including requests with forged identity headers. Future enablement requires a separately authenticated edge.

  • No public operations API
  • No inbound customer port
  • No shell, credentials, or deployment executor
  • Approval policy retained in source
  • Execution connectors remain unreleased

Next mission

Open the public manifest

Inspect the linked machine-readable evidence endpoints and their human canonicals.

View manifest JSON