The locked
system.
Permanent internal guide for the canonical taxonomy, engine architecture, object laws, decisions, and future workflow specifications of Kinetic Desk.
One governed chain.
Subject anchors the work. Records preserve what Sources yielded. Results are the machine primitive. Signals are the intelligence primitive. Files are the human primitive.
Two compounding moats.
DATA UNIFICATION
→ ONE CANONICAL RESULT
- Acquire Records from many Sources
- Normalize incompatible formats
- Resolve and deduplicate typed objects
- Preserve conflicts, gaps, rights, and coverage
- Map relationships and attach Citations
- Return a huge machine-usable dataset
One governed Result out.
SIGNALS INTELLIGENCE
→ TYPED SIGNALS
- Compare and connect Results
- Detect change and recurrence
- Identify contradictions
- Derive reproducible facts
- Preserve competing explanations and limits
- Emit typed Signals with full lineage
Reproducible Signals out.
The application is optional.
The Result contract is foundational.
APPLICATION PATH
Kinetic supplies workflow, interpretation, presentation, continuity, sharing, and export.
INFRASTRUCTURE PATH
The customer may skip Kinetic Operations, Signals, Files, and Watch. API and MCP Results power its own products, agents, graphs, alerts, and workflows.
Canonical objects.
| TERM | LAYER | DEFINITION | TYPE | VISIBILITY |
|---|
What becomes meaningful.
A Signal is a discrete typed intelligence statement produced by an Operation from one or more Results. It is reproducible, source-linked, and explicit about epistemic class and limits.
Persistent human intelligence.
A File organizes Signals and supporting Results around a primary Subject. File identity persists. File Versions append and pin exact intelligence objects.
FILE LIFECYCLE
WATCH MODE
Active File is the customer-facing derived state when Watch mode is Watching.
Capability is access.
Not machinery.
CAPABILITY
Entitlement and discovery grouping containing related Operations and Endpoints. It is never a synonym for Action.
ACCOUNT
Tenant, billing, entitlement, policy, Files, and credential root. An Account has Members with roles. API Keys belong to the Account.