Evidence and limits
What GMAN does not claim.
This page states exactly what a GMAN session record establishes today, and what it does not. Every claim on the rest of the site is written against this boundary.
What is supported today
- Claude Code sessions, at the level demonstrated by the session on the homepage.
- A metadata-scoped cloud record, delivered from the machine the agent runs on.
- Two capture sources: native Claude Code hooks and OpenTelemetry.
One runtime today. GMAN is built for custom agents across models and frameworks, and each additional runtime is claimed here when a session on this site can demonstrate it.
What a session record can establish
- That an activity row was recorded, and which of the two sources evidenced it.
- The decision recorded against a tool call: accepted, denied, unavailable, or not applicable.
- The execution state recorded against a row, including states that are not failures.
- Which fields were removed before delivery, disclosed per event rather than in a policy statement.
- Where a value is absent, that its absence is typed — a recorded zero and an unreported field are different things and are shown differently.
What a session record cannot establish
- Whether the task succeeded. Task outcome is not derivable from cloud evidence, and the homepage says so inside the frame rather than in a footnote.
- Why something happened. Co-occurrence in time is not causality, and GMAN never presents a cluster of related moments as an explanation.
- What the agent was asked or what it answered. Prompt and response text never leave the machine, so no reading of intent is available.
- How many distinct subagents ran. Lifecycle moments are recorded; the identities behind them are not reconstructed from counts.
- That the record is exhaustive. GMAN reports what was evidenced, and labels what was not.
Privacy boundary
The cloud record carries metadata about an event, not its content. Removal happens on the machine, before delivery — it is a construction rule, not a detection step applied afterwards.
- Prompt text, response text and content previews are absent by construction.
- Command text is never carried. A tool's target is recorded only for the file-shaped tools, and only as a path relative to the working directory or a bare basename — never an absolute path.
- A fixed list of identity fields is dropped before anything is projected: account and user identity, organization, terminal type, transcript paths, and the working directory. Which of them were present is recorded on the event, so a removal is visible rather than silent.
- Values GMAN does not recognize never leave the machine. An unrecognized field travels as its name and its primitive type, and nothing else.
- The small set of strings that does travel is bounded to 128 characters and passed through one redactor that recognizes common secret shapes — API keys, bearer tokens, JWT-shaped values, long hex strings — and replaces a match with a redaction marker.
That redactor recognizes known shapes. It is not a general secret detector, and GMAN does not claim to identify every possible key or token. The guarantee carrying the weight here is the boundary above it: command text and unrecognized values are excluded from the record outright, so pattern matching is a second line over a small allowlisted surface rather than the thing standing between a secret and the wire.
Withholding and absence are recorded as different things. A field GMAN chooses not to publish is not the same as a field the record never had, and the two are never collapsed into one label.
Not claimed at all
- GMAN observes. It does not approve, block, or alter what an agent does, and it is not a control surface.
- GMAN is not a legal or regulatory artifact, and nothing it produces is offered as one.
- The record is not sealed or independently attested. It is a record, and it says where it came from.
- There is no scoring, grading or health colour. Eight readings stay independent and are never fused into one number.
- No recorder package is offered for installation from this site.
Every figure on the homepage comes from one sanitized Claude Code session, and the limit lines above are the same ones the product renders inside its own frames.
See the session this page is about.