- Input
- A document collection
- Action
- Compile and review once
- Output
- A portable World and retrieval projection
Sample source · inspect the workflow →
Start with the work you need to do.
Five ways teams put the compiler to work. Choose the input you have and the output you need, then inspect the workflow, sample evidence and limits.
- Input
- PDFs and scans
- Action
- Read the regions and review uncertainty
- Output
- Source-linked text with inspectable locators
Sample source · inspect the workflow →
- Input
- Facts in your documents
- Action
- Inspect objects and evidence-bound relations
- Output
- Turtle, JSON-LD and CSV exports
Sample source · inspect the workflow →
- Input
- A question and the current World
- Action
- Ask, then inspect the returned evidence
- Output
- A version-bound answer and source locators
Sample source · inspect the workflow →
Knowledge operations
Review a revision before it becomes current.
For: Knowledge owners and security reviewers
- Input
- A new or updated collection
- Action
- Compile a candidate, review and activate explicitly
- Output
- A reviewed revision with change history
Sample source · inspect the workflow →
Working with a design partner.
What an early partner works with:
- A compile of your own corpus, arranged with us.Rather than a self-serve upload, we set the collection up with you and run it.
- The limits for your formats, in writing, before anything runs.The same capability manifest TAVONEL validates every upload against, read against the files you actually have.
- Your result with its receipts.Every compiled fact carries the source location it was read from, and the package is verifiable with the published scripts rather than on our word.
- A direct line to the people writing the compiler.What you find changes what gets built next, and you see the change land.
No name, logo or quote on this site belongs to a customer, and none will until a customer signs off on the exact wording. Availability is a conversation, not a checkout: request access and say what you are trying to compile.
Next: the guides, samples and research in the resources hub, or the exact product contract in the documentation. These five pages describe how the compiler is used, not completed customer engagements.