See what the local Service Intake test does and does not prove
The Proof Lab shows three frozen scenarios with an evidence ID, version, date, input class, expected outcome, local outcome and explicit evidence boundary, alongside the interactive local control flow.
Intended delivery
A reviewable local demonstration with enough context to assess the outcome and its limitations.
Evidence required before delivery
•Three evidence cards from calibration and holdout sets with date, version, environment and expected result.
•An interactive local flow with field source, role decision, kill switch and audit export.
•Failure and stop routes plus an explicit statement of what was not proven.
Authority boundary
What this solution explicitly does not promise
01
Example data is clearly labelled and does not constitute a customer case.
02
One test is not a general guarantee of performance, savings or production availability.
Three inspectable test scenarios
Expected and local outcome side by side
CAL-0001
Complete report
CALIBRATION · READY_FOR_HUMAN_REVIEW · 2026-08-01
Input
Customer, location, asset, serial number and issue are present.
Expected
A local work-order draft is ready for human review.
Local outcome
The deterministic adapter structures fields and creates a draft only.
Excluded
No message sent and no external record created.
CAL-0005
Missing serial number
CALIBRATION · MISSING_INFORMATION · 2026-08-01
Input
The report includes a maintenance request and asset but no serial number.
Expected
No complete intake; a question draft or human addition only.
Local outcome
The field remains visibly missing and the route requests completion.
Excluded
No automatic schedule or customer promise.
HLD-0009
Possible safety signal
HOLDOUT · BLOCKED_SAFETY · 2026-08-01
Input
The report mentions an unusual smell near an installation.
Expected
Fail-closed hand-off to a person; approval is unavailable.
Local outcome
The local stop rule blocks the normal draft route and records escalation.
Excluded
No safety diagnosis or autonomous urgency decision.
Local test
Sample data
No customer outcome
No production connector
Working control flow · sample data only
Run a new service report through the local operator
The local control adapter extracts fields from new text, applies stop rules, creates a draft only and keeps a privacy-light audit on this device.
This proves the workflow, policy, export and stop logic. It is not a customer case, model-quality test or production connector.
READY_LOCAL
1Received
2Checked
3Waiting for person
4Decision recorded
Control adapter ready
Edit the sample text and process it again; the outcome is calculated from the current input.
Traceable local evidence
Local audit log
Up to 50 privacy-light records stay in localStorage; the report text itself is not stored.
No local audit record yet.
The browser demo uses sample data and a deterministic control adapter only. Real model quality, Microsoft 365/Syntess integrations and external write actions remain separately blocked until a customer tenant, provider choice and acceptance test exist.
Next step
Start with one provable workflow.
No generic AI presentation. Bring volume, systems, exceptions and the human decision-maker.
