Verification / dated evidence
What I tested, and what I did not.
These checks use synthetic material. They describe a tested release at a point in time, not a guarantee about every future answer.
Open Operations DeskOperations Desk / connected project
Inspect a result and its execution receipt together.
The root workspace connects one fictional project to evidence checks, business registers and processing tasks. Its Activity view records each task's state and source IDs. A reused output names its original execution; a failed call remains unsuccessful.
The intake checks distinguish five accepted records, four held records, one duplicate and one no-progress marker in an eleven-record batch. Five additional source documents support twelve business-register rows. Seven authored references support correspondence, staffing, code, safety, voice, meetings and image tasks.
These are synthetic correctness checks, not customer outcomes. The service self-test checks the deterministic ledger and storage path. Individual AI-task receipts provide separate evidence that their processing service ran. An availability check alone does not establish answer quality or complete launch acceptance.
Earlier engine evaluation / meeting notes
The result was compared with a written answer key.
13.09.2026
Synthetic recordings
Three meetings with known decisions and actions
The evaluation matched eight of nine action-owner pairs, all nine decisions and all nine explicit deadlines. One action was assigned to the wrong owner. The recordings, scripts and expected answers were created for the test; they are not customer meetings.
14.09.2026
Live release
A production browser completed a synthetic transcript
The result contained two decisions, two assigned actions and their deadlines. A separate bounded live request saved an owned result, allowed its Markdown export and rejected another session and an unauthenticated caller. These checks do not establish that speaker labels identify real people.
Portfolio / public surfaces
The public pages were checked at three widths.
22.09.2026
Browser audit
Eleven pages, 33 page-and-viewport combinations
The portfolio and ten demo landing pages passed 198 of 198 checks at 1440, 768 and 390 pixels. The checks covered page load, visible heading and control, horizontal overflow, uncaught browser errors and same-origin static resources. This audit did not click controls, sign in, upload material or make model requests.
Ongoing
Availability
Availability is separate from answer quality
View current service status. Health checks can detect outages; they cannot decide whether an AI answer is correct for your material. Review generated decisions and dates before using them.
Limits
Use safe inputs and review the result.
Use synthetic or public inputs only. Do not upload confidential, employer, customer, personal or restricted material. Model providers and exported copies may have retention rules different from the demo’s active storage. Read the privacy and demo-data notice.
The earlier engine and landing-page counts retain their original dates. They are not acceptance evidence for the combined workspace. Current run receipts and service state are available from Operations Desk.