01
Subject
What the work concerns
A wallet, company, identity, brand, carrier, judgment, domain, or other typed object.
Product flow · CEO locked · 08·04
Choose a verb.
Build the file.
The platform returns verified components, not a conclusion. The user assembles the File, applies a restrained presentation, and exports it for their own purpose.
LOCKED PHYSICS
Kinetic provides the verified building blocks. The user decides what belongs in the File, how it should read, and where it goes.
→
02
Verb
What Kinetic does
Trace, Screen, Monitor, Profile, Assemble. One named contract with a typed input and a deterministic output.
→
03
Components
Verified building blocks
Signals, maps, tables, timelines, profiles, source records, and custody blocks. Facts only.
→
04
Builder
The user's assembly surface
Select, order, annotate, title, and style. Start from a complete plain Kinetic default.
→
05
File
Exported by the user
A human-readable, machine-readable, or formal record assembled from verified components.
NOW · APPLICATION
Humans assemble and export Files in the Builder.
The application holds the component library, drafts, saved styles, history, watches, team access, and delivery. It does not tell the user what action to take.
HORIZON · API + MCP
Machines invoke Verbs and receive the same typed Components.
The contracts are identical across the application, API, SDK, and MCP. Invocation is metered. File assembly can remain human-led or be requested explicitly.
The intelligence layer
Determinism means reproducibility under a frozen execution context. It does not mean omniscience.
01 · OBSERVE
Canonical facts
Source records are normalized without interpretation. Missing data remains missing; source conflict remains visible.
02 · SYNTHESIZE
Versioned deterministic rules
The same frozen inputs, rule set, graph snapshot, and model version produce the same Components every time.
03 · QUALIFY
Explicit uncertainty
Observation, derived fact, and scored inference are separate. Confidence may be probabilistic; its calculation and lineage are reproducible.
The component library
Every Verb contributes typed, provenance-bound pieces the user can inspect and place into a File.
SIGNAL
One sourced claim with time, severity, and provenance.
TRACE MAP
Nodes, paths, labels, and transaction facts from a trace Result.
TIMELINE
Ordered events with verified dates and source references.
ENTITY PROFILE
Provider-neutral facts about a person, company, wallet, or domain.
SOURCE RECORD
The supporting material a recipient can inspect, cite, or designate later.
CUSTODY BLOCK
Source class, transformations, hash, signature, and verification record.
The File Builder
Useful by default. Flexible by choice. The factual content and provenance cannot be styled away.
01 · ASSEMBLE
Choose the components.
Start with Kinetic's complete default, then add, remove, order, group, and annotate the pieces.
02 · PRESENT
Apply a restrained style.
Plain Kinetic Record is the default. Optional cover, typography, density, section order, brand mark, and recipient profile.
03 · EXPORT
Create the recipient form.
PDF, DOCX, JSON, signed web edition, API response, or MCP payload. The same components, rendered for the destination.
Expose the contract. Keep the recipe.
Elegance comes from legibility, not from revealing how the engine earns its answer.
DISCLOSURE
BOUNDARY
BOUNDARY
Public and machine-readableVerb promise, typed input, Component schemas, File schema, provenance envelope, meter, examples, and MCP tool description.
Closed and proprietarySource roster and weights, orchestration, provider economics, canonicalization implementation, graph joins, exhaust enrichment, confidence logic, and partner routing.
PRODUCT LAW · PROPOSED LOCK
Every Verb produces reproducible Components from frozen inputs and versioned rules. Every claim traces to a source. Uncertainty remains explicit. Kinetic never tells the recipient what to do.
Humans, counsel, institutions, and their own systems supply judgment, authority, and action.
CASE
May organize Components and Files in the application, but it is not a stage in the production flow.
MATTER / MANDATE
Domain context and authority may exist outside the File contract. Neither is a universal output object.
EXHIBIT
A recipient may designate a supporting Record as an exhibit. Kinetic does not.
KINETIC · ONE PLATFORM · PRODUCT FLOW · LOCKED 08·04SUBJECT · VERB · COMPONENTS · BUILDER · FILE