See what DreamerOS recorded.
DreamerOS records available integrity, routing, and prompt-shaping events. The record you see depends on your tier, route, and connected client.
This is what sets DreamerOS apart from raw AI. You can see the recorded checks and decisions that apply to your response instead of guessing what happened between question and answer.
Why this matters: when an AI answer turns out to be wrong, "the model said so" is not a real answer. Available records can show the engine, the prompt-shaping event, and the checks or verification fields that ran. You can use that record with a colleague, regulator, or your future self.
What gets logged
Here are the event types the audit record can show. Availability depends on tier and route.
Before the engine responds
- Intent and input checks
- Available risk signals
- Check status for that route
After the engine responds
- Available output review results
- Drift signals that the route recorded
- Flagged follow-up information
Prompt restructuring
- Original prompt vs restructured prompt
- Intent detection
- Domain classification
Model selection
- Which engine was chosen
- Why that engine was selected
- Routing confidence score
Claim checking
- Temporal claims flagged
- Live source lookups
- Verification status per claim
Append-only when created
When DreamerOS creates a receipt, database triggers reject changes or deletion. Other audit fields depend on the route that recorded them.
Audit log access by plan
The app exposes an audit record to signed-in tiers. The fields differ by tier and route. The complete customer walk on every tier remains In Beta 2.0.
Light pre-check record
- Light includes the pre-check before an answer
- Available receipt and audit metadata
- Pass or flag information from that route
- Checks after the answer are not part of the Light promise
Solo and higher checks after the answer
- Checks after the answer start with DreamWeaver Solo
- Available prompt and routing details
- Available verification results
- Fields vary by the route that produced the record
Elite audit access
- More audit fields, when the route records them
- Available cost and routing metadata
- Available verification source details
- Trace fields recorded by that route
Why this matters
Most AI tools are black boxes. You type something. You get a response. You have no idea what happened in between. DreamerOS makes it visible.
Was your prompt restructured? Where the route records it, see prompt-shaping information and why the system changed the request.
Did the integrity layer flag anything? Light includes a check before the answer. Checks after the answer begin with DreamWeaver Solo, when that route records them.
Which engine responded and why? Where routing applies, the audit record can show the selected engine and recorded decision fields.
Was any claim verified against live sources? When verification runs, its recorded status can show whether a source check took place.
What confidence information is available? Review the confidence or flag fields that the route recorded for that response.
Integrity principles
These are examples of the principles used by available checks. The exact set depends on the route and tier.
Accuracy over completeness
Say less if it means saying it right. Never pad a response to seem thorough.
No false guarantees
If the system is not certain, it says so. No confident-sounding guesses.
Surface hidden assumptions
Detect what the user assumed and expose it before answering.
State uncertainty
When confidence is low, say so explicitly. Never hide doubt behind fluent prose.
Depth matching
Match the depth of the response to the depth of the question. Simple questions get simple answers.
Third Eye
Intent, Integrity, Intuition. Available routes can apply these three lenses before processing begins.
Input as raw signal
Input shaping can treat a request as raw signal to clarify, not as a finished instruction to follow blindly.
Showing seven examples. Check availability and recorded fields vary by route and tier.
Append-only guarantee
Your audit trail cannot be edited
Log entries can never be modified or deleted. This is an architectural constraint, not a policy.
Database triggers reject any UPDATE or DELETE on the audit log at the database layer. Once an integrity event is recorded, it exists permanently.
The rejection happens inside the database itself, not in application code - there is no code path that can modify a written row. Your audit trail cannot be rewritten, redacted, or erased.
See exactly what happened between your question and the answer
See what the route recorded. Start free. No credit card required.