Architecture overview
Tinor organizes long-lived platform work as a Real-World State Runtime. Commercial applications such as Business Presence and Business Response sit on top; they are not the whole platform identity.
Tinor Platform
Real-World State Runtime.
Make reality legible, verifiable, and actionable for humans and AI. Tinor turns scattered, changing, and permission-constrained real-world information into representations with explicit sources, status, semantics, and action boundaries.
Tinor is not merely a Business Presence page or a response agent. Those are commercial applications of a longer-lived runtime.
Platform capabilities
Interpret.
Resolve.
Trace.
Govern.
Reusable platform capabilities — not industry verticals, and not separate products.
Interpret
Identify business entities, relationships, declarations, and candidate facts from records, documents, and unstructured materials.
Resolve
Form formally acceptable state under explicit semantic contracts, sources, permissions, and confirmation workflows.
Trace
Maintain attributable links among events, sources, evidence, versions, history, and state changes.
Govern
Manage principal authority, formal acceptance, disclosure, revocation, and audience boundaries.
Conceptual continuum
From interpretation to authorized use.
Illustrative flow. Actual steps vary by workflow.
- 01Semantic Interpretation
- 02Authority / Confirmation
- 03Owner Commit
- 04Current State
- 05Authorized Access / Response
Platform topics
What the runtime must explain.
The core concepts behind the runtime — interpretation, principals, events, evidence, current state, and disclosure — and the limits of what it does.
Semantic Runtime
Interpretation turns records and unstructured materials into candidate entities, relations, and claims. Candidates are not yet operational facts. Acceptance rules and confirmation decide what may be projected as current.
Principal / Authority
A principal is an attributable actor — person, organization, or agent identity — that can assert, confirm, disclose, or revoke. Authority answers who may accept state for a purpose, not merely who uploaded a file.
Claim, Evidence, Fact, Current
A claim is an assertion. Evidence is supporting material. In Tinor, a fact is a claim that has standing under confirmation rules. Current is the projection used for answers today — distinct from historical versions.
Events and state evolution
Atomic events attribute what happened. Transitions update projections. Resolved state is what holds after rules run. The model, in short: Event → Transition → Resolved State.
Conflicts, revocation, and history
Late evidence, withdrawals, and incompatible scopes are first-class. History remains; current answers change. Conflicts stay visible until authorized resolution — they are not silent overwrites.
Disclosure and access boundaries
Govern manages who may read or cite which projections. Public capability summaries and restricted diligence annexes are different audiences. Agents do not invent permission.
How agents use accepted facts
External agents should read maintained presence, request missing materials through reception entry points, and receive responses grounded in accepted state — escalating commitments and gaps to humans.
Current capability vs future directions
Today's purchasable applications are Signal (Business Presence, including basic Request Inbox) and Pulse (Business Response, including AI-powered Reception & Response). Relationship Network, Assurance, and Product & Batch Network are Planned.
Boundaries
What Tinor does not claim.
Not an oracle of truth
Tinor does not unconditionally judge objective reality. It structures attributable, source-linked state under known rules and human confirmation where required.
Developer documentation
Developer documentation is published separately from this website. For integration questions, please contact us.