Company State

A company that knows itself.

Every serious decision starts with “what's true right now?” — and in most companies, nobody can answer without a week of archaeology. Company State is that answer, held live.

Problem

Truth, scattered.

Your truth is scattered across eleven tools and four heads. Dashboards show numbers without context; documents show context without freshness. The company’s actual state — what’s known, assumed, promised, at risk — exists nowhere. So decisions run on vibes wearing a spreadsheet costume.

Mechanism

Sources become typed claims. Claims become a graph.

Sources flow in — connectors, conversations, uploads, the AI Suite’s own products — and become typed claims: FACT, INFERENCE, ASSUMPTION, PREDICTION, TARGET, CONSTRAINT, PREFERENCE. Claims link into entities; entities into the graph; the graph into answers.

StateClaim

subject: Customer segment
value: B2B SaaS product leads, 20–200
epistemic type: ASSUMPTION
confidence: 0.8
sources: 12 interview summaries
observed: 2d ago · valid from Aug 12
sensitivity: internal
depends on it: 2 strategies · 4 missions

Dispute any claim and see everything it touches.

Worked example

Aster, minute 4.

The founder’s three answers have become 14 claims — 5 facts, 6 assumptions, 2 constraints, 1 target. The two assumptions with the highest blast radius are flagged for evidence missions before any strategy is drafted.

Control

Corrections are first-class.

Tenant isolation per workspace · sensitivity levels gate who and which agents see what · corrections are first-class (dispute → review → supersede, never silent edits) · freshness decay is visible, not hidden.

UnderstandDecideDeliverVerifyLearn

State feeds the World Model; outcomes update the state.

Hard question

What happens when my data conflicts?

It stays visible. Two sources disagree on MRR → both claims persist with sources; the conflict is flagged; you (or a rule you set) pick the authority. Brainis never silently averages your reality. And when data is missing, you get an honest gap — “utilization is inferred; connect time-tracking to firm it up” — not a confident zero.