The Architecture of Trust.Sourced claims with provenance.
Documents, meetings, transcripts, recordings and email become atomic claims, each with its source, its date and how it was grounded.
/TRUTH
What the meeting decided, available by the afternoon.
- Today
- Sourced claims
- Loop with the record layer · Direction
The most valuable thing an organisation produces is the thinking in its meetings, and almost none of it survives the end of the call.
With /TRUTH, your organisational data isn't lost, it's leveraged: what was said in the room survives the room, sourced, verified and citable by anyone who was not there.
YOUR SECTOR
- 09:30The meeting
A planner, an intelligence analyst and a logistics officer meet on a secure call about a coalition resupply window.
- 10:14The call ends
They have agreed the position, sized the options and named the one constraint that matters: a partner clearance that lapses on the 20th. Then the call ends, and all of it survives as a memory in three heads and a recording nobody will replay.
- 10:15/TRUTH takes it in
The recording and the minutes go in. Sourced, verified claims come out, each with its source, its date and how it was grounded: the window, the routes, the airfield limit, the clearance date.
- 13:40The afternoon
A coalition partner nine time zones away pulls the clearance date into a movement brief, the source line showing which call set it. The meeting did not die.
- 09:30The meeting
A co-op agronomist, a grower and the grain marketer meet by video about a block of wheat showing stripe rust after two wet weeks.
- 10:14The call ends
They agree to spray the two worst paddocks now and name the one constraint that matters: the pre-harvest interval on the product already in the shed. Then the call ends, and all of it survives as a text the grower sends himself from the truck.
- 10:15/TRUTH takes it in
The recording and the agronomist's note go in. Sourced, verified claims come out: which paddocks, which product, which window, which interval, each in the project its owner granted.
- 13:40The afternoon
The co-op agronomist two regions away pulls the interval into the members' spray advisory, the source line showing which call set it. The meeting did not die.
- 09:30The meeting
A clinical lead, a pharmacist and the director of nursing meet about a change to the sepsis pathway after two near misses.
- 10:14The call ends
They agree to move the first antibiotic dose earlier, pick three pilot wards and name the one constraint that matters: the pharmacy stock rule that caps ward supply. Then the call ends, and all of it survives as a half-finished note in the pharmacist's inbox.
- 10:15/TRUTH takes it in
The recording and the minutes go in, inside your organisation's own dedicated instance. Sourced, verified claims come out: the pathway change, the pilot wards, the stock cap.
- 13:40The afternoon
A ward manager at another site pulls the stock cap into the pilot briefing, the source line showing which meeting set it. The meeting did not die.
- 09:30The meeting
A credit officer, a relationship manager and the head of risk meet about a counterparty's limit after a covenant breach.
- 10:14The call ends
They agree to hold the limit with a collateral condition and name the one constraint that matters: the breach is material non-public information (MNPI) and stays in the restricted project. Then the call ends, and all of it survives as a note in the relationship manager's file.
- 10:15/TRUTH takes it in
The recording and the committee minutes go in. Sourced, verified claims come out: the limit, the condition, the review date, the restriction, each readable only by the people granted that project.
- 13:40The afternoon
A reviewer in another office pulls the condition into the committee paper, the source line showing which call set it: a trail, not a reconstruction. The meeting did not die.
- 09:30The meeting
A product lead, a solutions engineer and an account director meet about a renewal that is at risk.
- 10:14The call ends
They agree to offer the migration at the current tier, pick a date and name the one constraint that matters: the customer's data residency requirement rules out the faster path. Then the call ends, and all of it survives as a half-finished note in the pipeline record.
- 10:15/TRUTH takes it in
The recording, the chat thread and the email go in. Sourced, verified claims come out: the tier, the path, the date, the residency constraint, each with its source and its date.
- 13:40The afternoon
A colleague halfway across the world pulls the date into the customer brief, the source line showing exactly where it came from. The meeting did not die.
WHAT /TRUTH IS
The organisational record, distilled into claims you can check.
/TRUTH is the document layer. Reports, chat, meeting minutes, transcripts, recordings, email and shared drives go in; sourced claims come out, each carrying its source, its date and how it was grounded. When two sources disagree, the conflict is listed with both sides cited. When a newer source supersedes an older one, the older claim stays in the record, marked, so what changed and why is never lost. Every page, search result and answer cites the claims behind it. Agents connect over MCP and act as the user, seeing only what that person may see; access is granted per project; systems connect over a REST integration API. It runs as a dedicated instance for your organisation, and every topic can be exported whole, claims included.
Today: shipping, in continuous use at Bluestaq for its own company strategy. Direction: joining these claims with the records governed in BLUESTAQ /ARQ™, with findings landing back as governed records. That loop is stated direction, not a shipped capability: /TRUTH does not read /ARQ today, and nothing is written back.
WHAT YOU GET
What the document layer gives your team.
Conflicts surfaced, both sides cited.
When two sources disagree, the conflict is listed with the claims behind each side, not averaged into a summary.
Newer supersedes, older kept.
A newer claim replaces an older one on the page; the older stays in the record, marked, so what changed and why is never lost.
Answers that cite.
Every rendered page, search result and agent answer cites the claims and sources behind it.
Your instance, your access rules.
A dedicated instance for your organisation; access granted per project; agents act as the user and see only what that person may see; every topic exports whole.
The loop with /ARQ.
Records and documents joined into claims with provenance, findings landing back in /ARQ as governed records. Not shipped: /TRUTH does not read /ARQ today.
THE ARCHITECTURE
How it fits together.
The organisational record in; sourced claims with provenance out, to people and apps. The amber dashed lanes are the loop with /ARQ.
CONTINUE EXPLORING