A world your AI can reason about.

Published World · one filing arrivingOpen the change view

10-Q · filed 2026-07-3138 of 40 pages compiled · 186 regions · accession 0000320193-26-000020

Source revisions
+1 · 4 unchanged
Objects
+443 new · 456 rebuilt · 5,411 untouched
Relations
+897 new
Evidence regions
+186 new

sha256 76eda2ed02003…sha256 aff67d5c6d0e3…

Both Worlds above are complete compiles of their corpus, compared after the fact. What a compile promises when a source changes, and the state each promise holds here, is set out clause by clause in the Compiler Contract.

Inside the public sample

One World. Files you can inspect.

These are the files emitted from the Apple filings behind Explore, with their formats and content digests.

Emitted files
16
Lifecycle
candidate · not activated
Signing
external signer required
source/1 fileTrace the input document versions and their digests.
  • source/collection-files.json

    application/json · 1,562 bytes

    Full file content digest
    sha256:78fea134dc2732db66aae599d9f7edd4486d141cca8a79390243b4706ef06636
canonical/1 fileRead objects, relations and evidence together as JSON.
  • canonical/model.json

    application/json · 4,404,542 bytes

    Full file content digest
    sha256:8d4c8589d86f4edc5585d96d3b4ac33744bdd5f44bd36fec11346c216f69c741

    Truncated preview · opening content

    Scroll to read this JSON. The digest above identifies the full emitted file, not this preview.

    {
      "schemaVersion": "akc.canonical-knowledge-model.v1",
      "collectionId": "collection-3fd4ce9cafd301bf479601c3df26e95e",
      "blueprint": {
        "id": "generic-mixed-corpus",
        "version": "1.0.0",
        "roots": [
          "Sources",
          "Topics",
          "Entities",
          "Claims",
          "Evidence",
          "Assets",
          "MOCs",
          "Packages"
        ],
        "maximumDepth": 3,
        "namingPolicy": "stable-id-title",
        "preserveExistingFolders": true,
        "ontologyClasses": [
          "Document",
          "Topic",
          "Entity",
          "Claim",
          "Evidence",
          "Asset"
        ],
        "ontologyRelations": [
          "discusses_topic",
          "mentions_entity",
          "supported_by"
        ]
      },
      "nodes": [
        {
          "id": "evidence-5a70ec70f7b1a1726a25ed51a5dc716a",
          "kind": "Evidence",
          "label": "public/explore-sample/apple-2026-proxy-def14a/aa84ce73eb0f181844ccd0bb8a4a53f670fae6a007c086ccdb55f705f8d7a0c2/text-layer-public-slice.json",
          "documentId": "apple-2026-proxy-def14a",
          "evidenceIds": [
            "evidence-5a70ec70f7b1a1726a25ed51a5dc716a"
          ]
        },
        {
          "id": "document-5a70ec70f7b1a1726a25ed51a5dc716a",
          "kind": "Document",
          "label": "Table of Contents UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, DC 20549 SCHEDULE",
          "documentId": "apple-2026-proxy-def14a",
          "evidenceIds": [
            "evidence-5a70ec70f7b1a1726a25ed51a5dc716a"
          ]
        },
        {
          "id": "topic-b696d75511dc16f2b52563e3113a4983",
          "kind": "Topic",
          "label": "Finance",
          "evidenceIds": [
            "evidence-5a70ec70f7b1a1726a25ed51a5dc716a",
            "evidence-274e80464ffc891ce2ed3077e7d67934",
            "evidence-f5f769e9c7e871dcf8cc3272d0478979",
            "evidence-ce79c52fe7ae8aa0e89a31c6233ab331",
            "evidence-0dffdde3c8def7d25da7d9eb4bd303d3"
          ]
        },
        {
          "id": "topic-86f8a694159b712f78f3b3c032028b92",
          "kind": "Topic",
          "label": "Governance",
          "evidenceIds": [
            "evidence-5a70ec70f7b1a1726a25ed51a5dc716a",
    
obsidian/6 filesBrowse the source notes as Markdown.
  • obsidian/Home.md

    text/markdown; charset=utf-8 · 567 bytes

    Full file content digest
    sha256:f1c07273830abd72d7cb6006dbf13b90047986646ab3db4ed630a884bcef0791
  • obsidian/Sources/apple-2026-proxy-def14a.md

    text/markdown; charset=utf-8 · 290,860 bytes

    Full file content digest
    sha256:954aa3fdcbf50f42cefaa457590e9deecab0c9883c50bffa7e4bbe41b30d3067
  • obsidian/Sources/apple-2026-q1-10-q.md

    text/markdown; charset=utf-8 · 57,411 bytes

    Full file content digest
    sha256:9f2107dadb9f7341a5e50dff8a105d43d0a6d172dbe8d25ffdf0b09db104c4ff
  • obsidian/Sources/apple-2026-q2-10-q.md

    text/markdown; charset=utf-8 · 85,262 bytes

    Full file content digest
    sha256:c78ed4c8e51bf73c14f33b1d51ec156a8e2d2bc543c43aaea411677621b424a9
  • obsidian/Sources/apple-2026-q3-10-q.md

    text/markdown; charset=utf-8 · 83,400 bytes

    Full file content digest
    sha256:003f45df72cc96fa5b5122404220d802d781a5a590ab381c75c4cf30f73b75bc
  • obsidian/Sources/apple-form-10-k.md

    text/markdown; charset=utf-8 · 275,083 bytes

    Full file content digest
    sha256:d7187f93738a0977cd7f70c85b284f2848fdd8c1c8314a601090a22af12e5f4f
ontology/2 filesRead nodes and edges in Turtle; read node records with evidence IDs in JSON-LD.
  • ontology/knowledge.ttl

    text/turtle; charset=utf-8 · 2,235,160 bytes

    Full file content digest
    sha256:16bc8a61e5033028ade60256e89c0b5cf21892a772f3ae462b5eab65d5458a9a
  • ontology/knowledge.jsonld

    application/ld+json · 1,980,307 bytes

    Full file content digest
    sha256:9b3df602bc9d12659a7acff7de2fab513da05b75c5b7c001837cca78e1eda852
graph/2 filesInspect the node and relationship tables as CSV.
  • graph/nodes.csv

    text/csv; charset=utf-8 · 1,119,762 bytes

    Full file content digest
    sha256:4a111d5b291dc1b786cc1cbe6a10ffebd3615ef3a6cff059849972b3dce39a2d
  • graph/relationships.csv

    text/csv; charset=utf-8 · 1,480,752 bytes

    Full file content digest
    sha256:f41e199f4fbcf12b29397bc5c1cfd09127acf908daf09c0299392db6e53310d0
rag/2 filesRead the retrieval corpus with source, page and region references.
  • rag/documents.jsonl

    application/x-ndjson · 593 bytes

    Full file content digest
    sha256:f3c520439b6c6606a8c073d827fe706080db5721eb778e5ca3408dd2d6b7a853
  • rag/chunks.jsonl

    application/x-ndjson · 2,029,748 bytes

    Full file content digest
    sha256:3a870c3287c6de1f1ea20311ff85c28c0ccb10d72ebff6f44b9d3791a020e80c
provenance/1 fileInspect the recorded OCR input events.
  • provenance/activities.jsonl

    application/x-ndjson · 1,594 bytes

    Full file content digest
    sha256:284a6209fed0877cf026aee3f3589db43cb9e06263a02165a207382de388633e
validation/1 fileCheck the validation results and review reasons.
  • validation/report.json

    application/json · 1,668 bytes

    Full file content digest
    sha256:dc9b83d6244655d6e4b62cb9854ee9935f3ead348b049c3807185625023c9838
Sample sources and integrity

This is a public sample compiled by the TypeScript sample engine, not a customer compile or an activated customer World.

Engine
tavonel-collection-compiler-ts-v1/explore-sample
Manifest digest
sha256:aff67d5c6d0e3e119433446ed003545a942ad5638de8e7b51c93c6ca1a847091
Signing status
external_signer_required

The sample requires an external signer. Its file and manifest digests identify content; they do not verify a signature.

The compiler reads the representations linked below. A reference render is a representation of the acquired source, rather than an original SEC PDF.

The output of a compile is a Compiled World: objects, relations, evidence, versions and the artifacts that project them. One world, used by retrieval, agents, MCP, APIs and applications.

OBJECTS

The things themselves

Entities, claims and the documents they were read from get a stable key derived from their content, so recompiling the same source lands on the same object instead of a new one. Two different strings for one real-world thing — FP-200 and Feedwater Pump 200 — are not merged automatically: where the evidence does not settle identity the compiler leaves it unresolved for a person rather than guessing, and automatic resolution across sources is a direction.

Stable semantic identity in the Compiler Contract

RELATIONS

What connects to what

Every edge is typed and carries the evidence ids that justify it — an edge naming no evidence is not a row the compiler can produce. A claim is supported_by the one exact document version it was read from, and mentions the entities named inside it. Two claims that disagree on a number, or on whether something is the case, inside one topic and one time reference are emitted as a contradicts candidate and sent to review: the compiler flags the pair and a person resolves it.

Typed dependencies in the Compiler Contract

EVIDENCE

Where a fact came from

Every qualified claim points at a source version and its exact location inside it. In TAVONEL that location takes one form for every accepted format — a numbered page of the sanitized PDF and a box on it — because a spreadsheet, a slide deck and a Word file are all converted to PDF before anything reads them. A world holding an unresolved link is not emitted at all.

VERSIONS

What changed, and when

A compile produces a candidate version. A person activates it, and the version it replaced stays intact and readable.

PROJECTIONS

How it is consumed

Ontology, graph, retrieval corpus, directory and validation artifacts, written into one package from one world. Every Ask answer names the retrieval path that produced it, so which projection an answer came from is reported rather than assumed.

PACKAGE

What you can take

A signed package, hash-verified on the way out. The public key is published at /api/export/trust, so a recipient can verify it without asking us.

Every compile emits the same package shape, so a world built today can be read by a tool written against one built last month. The formats are set out in the ontology output, how a fact is bound to its source in Evidence, and how to consume a world from an assistant in Use the result with AI.