Developer alpha available

Build agents that compound context, not errors.

OpenOntology turns retrieval into verified context. It resolves identity, chronology, authority, and proof before context reaches an agent, then returns exact evidence or a typed refusal.

Request a Tapestry demo View the open source release

Apache-2.0. Node.js 24+. Managed beta is in qualification.

11 / 11focused checks
12 / 12npm smoke checks
GCScanonical truth
Typedrefusal over guessing
How it works

Retrieval can propose. Only evidence can support.

Vector search is useful navigation, not truth. OpenOntology keeps the source system, the ontology, and exact source bytes separate so an agent can prove what it knows.

  1. 01

    Propose

    Retrieval produces candidate references inside an explicit source scope.

    Navigation only
  2. 02

    Resolve

    The Ont cross-walks identity, chronology, relationships, and authority.

    Proof obligations
  3. 03

    Verify

    Exact authorized bytes close the proof, or the request returns a typed refusal.

    Verified context
Full-corpus qualification

5.12 billion source bytes.
41.886 seconds.

One complete Tapestry source cut compiled into an exact deterministic row set. The canonical source was unchanged before and after.

108,388 deterministic projection records
2,588records / sec
122.3 MBsource bytes / sec
Canonical sources
87,726
Source bytes
5,120,804,841
Bounded requests
111
Configured ceiling
32 MiB
Source mutation
0 bytes
Independent runs
Exact match
Deterministic build receipt [VERIFIED] 2026-09-04
checkpoint
sha256:68b5a800d766b3d0d2060101aa9ebfb16ecc01daca7e451b837763cc25bcfbc1
exact row set
sha256:56986bcb68745da368cbe8d7cbb271ecd2ad7ff0b294703e96292b4563e9fbd6
result
sha256:5a75edd9ea78d5ed704e12757bffef0b3e7fc2a63850ca4614577e19ab6124b5

Throughput figures are derived from the measured byte count, row count, and elapsed time above.

Open engine, managed context

OpenOntology powers Tapestry.

Tapestry is DOSS's managed enterprise context layer. It connects source systems, agent runs, and operator outcomes around OpenOntology's verification boundary.

Release boundary

Developer release ready. Managed beta has two gates left.

Canonical storage is real and committed. Hosted retrieval is not claimed until live provider qualification and the cold-deploy canary both pass.

  • Verified

    GCS canonical storage + disposable Turbopuffer projection

  • Active work

    Live Turbopuffer provider qualification

  • Active work

    Single-tenant wrapper + cold-deploy canary

  • Production

    IAM, lifecycle, recovery, and garbage collection follow beta

Managed beta

Bring one context problem that cannot afford a confident wrong answer.

We will show how Tapestry maps the source, closes proof obligations, and returns a compact context packet an enterprise agent can use.

  • One tenant and one bounded source cut
  • Verified reads, refusals, and recovery path
  • Fit assessment for enterprise controls
Tapestry demo request Replies go to Wiley

By submitting, you agree to DOSS's Privacy Notice, including use of your data for follow-up and marketing.