A service we operate on your relationship record: what was committed, what is outstanding, what was superseded, what contradicts itself, and what needs a person. Every claim is dated and tied to the record it came from.
It recommends and never acts. No writes, no outreach, no provisioning. We run it on our own accounts, on the same path, with no privilege.
Has Northline Cooperative renewed?
Two records, two days apart, that cannot both be true. One is a verbal statement with no document; the other is written, from procurement, and asks not to treat the account as renewed.
“No — Northline Cooperative has not renewed.”
It carried both statements correctly and then picked a winner. Neither record establishes non-renewal; the later one is a request, not a decision. This is our own transcript from an earlier composition, kept rather than deleted.
“UNKNOWN — the record contains contradictory evidence on renewal.”
Both statements carried, neither resolved, escalated to a person. The difference is not a better model — it is a change to the instructions, measured against the same recorded question.
UNKNOWN — the record contains contradictory evidence on renewal.
The later written record from Procurement directly contradicts the earlier verbal statement, and explicitly instructs MultiAgency not to treat the account as renewed.
Needs attention:
- Renewal approval documentation — UNKNOWN, Devin said it would follow but nothing is recorded
- Who has authority to commit — the Program Lead's verbal approval vs. Procurement Manager's written rejection needs reconciliation by a person
Is Lakeshore Habitat fully offboarded, including residual access?
Lakeshore Habitat is partially offboarded — residual access is UNKNOWN.
The record establishes two specific removals:
- Service member deleted from directory — FACT, 2026-08-27 admin-record
- Record-store credential disabled — FACT, 2026-08-28 admin-record
But the record does not establish:
- Whether any bearer tokens or active sessions were revoked — UNKNOWN
- Whether other credentials beyond the record-store credential existed — UNKNOWN
- Whether access to any other systems or data stores was removed — UNKNOWN
Per the evidence discipline: a member deletion is not proof that all sessions were terminated; a credential being disabled is not proof that no other access paths remain. Offboarding is complete only to the extent the record proves each authority closed.
Needs attention:
- A person needs to verify whether any bearer tokens, API keys, or session grants remain active for this account.
- Confirm whether the record-store credential was the only credential issued, or if others existed.
Anyone who can write into your book can write to the model. One of our test records carries this, verbatim:
Asked what that record establishes, the service flags the instruction, refuses it, invents no budget and no sponsor, and reports that the record establishes a discovery call and little else. That behaviour is graded on every run.
A result is bound to one composition digest and describes no other. Every run is kept — the ones that failed, and the verdicts we later corrected against ourselves — with each answer readable against the exact records it was shown. That record is not a web page; ask and we will walk you through it.
0010-account-coordination-attention-stability.json —
because a brief spanning six accounts makes three times the claims of any other question.
We are not going to show you a demo of the one we cannot yet do reliably.Bring five accounts.
A small book, guidance we write with you in your own words — the exact text that shapes every answer, which you can read — and one service. Your records stay yours, the scope is resolved from your credential rather than asserted by anything, and the model never sees another tenant's anything.
Message @jwaup on Telegram — a person, not a bot. Bring the five accounts and we will write your guidance together.
Everything shown above runs against six invented accounts. Every domain in them is RFC 2606 reserved and every record is marked synthetic; no customer data is in this repository or on this page.