What is Operational State?
Operational State is the sourced, statused, permission-aware projection of what holds now for a purpose — distinct from documents, chat logs, and raw claims.
Operational State is Tinor's name for the projection of real-world information that an organization is prepared to treat as current for a purpose: sourced, statused, attributable, and bounded by disclosure rules. It is not a synonym for "everything we ever uploaded," and it is not a synonym for "whatever the model remembers from training."
Why the word "operational" matters
Many systems store knowledge. Fewer systems maintain a disciplined answer to: what holds now, for whom, under what evidence class, and what happens when that standing changes? Operational State is that disciplined answer. The adjective "operational" emphasizes use: decisions, disclosures, partner replies, and agent assistance all depend on a projection that can be wrong in known ways (Unconfirmed, Conflict) rather than wrong in invisible ways.
Operational State is not a document
A PDF certificate is evidence. A spreadsheet of SKUs is a record. A chat transcript is interaction history. Operational State may be supported by those objects, but it is a separate layer: claims with status, scopes, principals, and current projections. When the PDF is revoked, the document may still exist in an archive while Operational State changes.
Operational State is not raw claims
A claim can be asserted by anyone with a keyboard. Operational State requires standing: confirmation rules, authority, and often human gates. Tinor distinguishes claim, evidence, fact (claim with standing after rules), and Current (the projection used for answers today). Collapsing those words into one "knowledge" blob is how agent demos look smart and production systems look reckless.
How Current relates to history
Current is a projection, not the only truth the system keeps. History retains prior versions and transitions. Revocation does not require deleting the past; it requires updating what is projected as Current and keeping the event trail attributable. Partners who cited an older statement can be answered with honesty: here is what held then; here is what holds now.
Permission and audience
Operational State is always potentially audience-scoped. Public capability summaries and restricted diligence annexes are different projections of related materials. An agent that cannot see disclosure tags will paraphrase restricted language into public channels. That is not a model failure alone — it is a state-model failure.
How agents should use Operational State
External agents should:
- read maintained presence surfaces grounded in Current,
- request missing materials through reception entry points rather than inventing fillers,
- escalate commitments when confirmation is required,
- cite evidence class instead of performing certainty theater.
Tinor's commercial Business Presence and Business Response products are applications of this idea. The platform category — Real-World State Runtime — is the longer-lived substrate.
Common anti-patterns
- Treating search ranking as standing.
- Treating "last updated" timestamps as revocation awareness.
- Treating bilingual duplicates as independent truths without conflict detection.
- Treating chat memory as Operational State.
- Treating a single "verified" badge as a substitute for evidence class.
Closing definition (short)
Operational State = sourced + statused + attributable + audience-aware projection of what holds now for a purpose, with history retained when standing changes.