Name a subject. Choose a verb. Kinetic returns a documented file showing what it found, where it came from, and where the record stops.
You decide what to examine and which specialist unit to deploy. Kinetic performs the run, shows each finding and its origin, then lets you compose the file. Nothing in the flow tells you what to do.
A wallet, a company, a person, a brand, or a judgment. The subject is frozen before the run.
One verb from the catalog. Each states what it accepts and what it returns.
Every finding carries its source, method, and stated limits. Gaps and conflicts stay visible.
The same file for people, systems, counsel, or a model you control.
Each verb is a specialist investigative unit with its own inputs, methods, controls, and typed output. Every verb states what it accepts and what it returns.
Follow movement across wallets, rails, and hops.
Check a name, wallet, or company against controlled records.
Find domains, storefronts, and profiles using a protected identity.
Turn scattered identifiers into one entity, with the links preserved.
Assemble what is known about an actor or entity.
Report only what changed on a subject.
Start from the complete Kinetic Record. Select, order, group, and annotate what belongs. Change the presentation if you need to. The facts, sources, and stated limits do not move.
Two executions against the same frozen inputs and versions. The typed findings match.
The same inputs and the same rule, graph, and analysis versions produce the same typed findings every run.
Missing records remain missing. Conflicting sources remain in conflict. Neither is smoothed into a conclusion.
Kinetic states what it found and how. What happens next remains with the recipient and their counsel.
Two executions against the same frozen inputs and versions. The typed findings match.
The interface stays still. The subject, the verb, and the file change. A wallet trace and a counterparty screen follow the same governed flow.
The workspace, the API, and MCP call the same verbs against the same record. Human readers and machine readers receive the same typed findings.
The workspace makes the full flow human-readable without hiding the source, method, class, or limitation behind any finding.
The API accepts the same subject and verb, applies the same controls, and returns the same typed findings with their provenance envelope.
MCP is another access mode, not another product. The tool descriptor carries the typed input, the output shape, and the rights boundary.