LAST UPDATED · 05 AUG 2026 · 19:03 PT
KINETIC PLATFORM · INTERNAL WORKBENCH
The locked
system.
Permanent internal guide for the canonical taxonomy, engine architecture, object laws, decisions, and future workflow specifications of Kinetic Desk.
ACTIONS ASSEMBLE INTELLIGENCE OBJECTS · OPERATIONS PRODUCE SIGNALS · PEOPLE KEEP INTELLIGENCE FILES
01 · CANONICAL SYSTEM
One governed chain.
Subject anchors the work. Records preserve what Sources yielded. Intelligence Objects are the machine primitive. Signals are the intelligence primitive. Files are the human primitive.
SUBJECTThe primary person, company, wallet, domain, asset, document set, event, or question under examination.
02 · TWO-ENGINE ARCHITECTURE
Two compounding moats.
ACTIONS ENGINE
DATA UNIFICATION
SUBJECT + MANY SOURCES
→ ONE CANONICAL RESULT
- Acquire Records from authorized Sources
- Parse provider-native formats
- Normalize incompatible formats
- Normalize into canonical schemas
- Resolve and deduplicate typed objects
- Reconcile conflicts without hiding them
- Preserve conflicts, gaps, rights, and coverage
- Relate typed objects into a connected structure
- Bind every fact to Records and Citations
- Assemble a complete immutable Intelligence Object
Many Sources in.
One Intelligence Object out.
OPERATIONS ENGINE
SIGNALS INTELLIGENCE
ONE OR MORE INTELLIGENCE OBJECTS + VERSIONED RULES
→ TYPED SIGNALS
- Compare and connect Intelligence Objects
- Detect change and recurrence
- Identify contradictions
- Derive reproducible facts
- Preserve competing explanations and limits
- Emit typed Signals with full lineage
Intelligence Objects in.
Reproducible Signals out.
03 · CONSUMPTION PATHS
The application is optional.
The Intelligence Object contract is foundational.
APPLICATION PATH
Subject → Operation → Signals → File → Active File
Kinetic supplies workflow, interpretation, presentation, continuity, sharing, and export.
INFRASTRUCTURE PATH
Subject → Endpoint → Intelligence Object → Customer System
The customer may skip Kinetic Operations, Signals, Files, and Watch. API and MCP Intelligence Objects power its own products, agents, graphs, alerts, and workflows.
STRIPE LAWDashboard and API-first customers share the same underlying objects and rails. Desk and API/MCP customers share the same canonical Intelligence Objects.
05 · SIGNAL
What becomes meaningful.
A Signal is a discrete typed intelligence statement produced by an Operation from one or more Intelligence Objects. It is reproducible, source-linked, and explicit about epistemic class and limits.
SIGNAL · DERIVED FACT
The named owner changed, but the same signatory and domain administrator persisted across both changes.
NOT A DATASETNOT NARRATIVE PROSENOT ADVICENOT A VERDICTNOT AN OPAQUE SCORE
06 · FILE + ACTIVE
Persistent human intelligence.
A File organizes Signals and supporting Intelligence Objects around a primary Subject. File identity persists. File Versions append and pin exact Signals and Intelligence Objects.
FILE LIFECYCLE
DRAFT→BUILDING→READY
READY↔ATTENTION→ARCHIVED
WATCH MODE
OFF→WATCHING→PAUSED
Active File is the customer-facing derived state when Watch mode is Watching.
ON A SCHEDULEDaily, weekly, monthly
WHEN RECORDS CHANGEFiling, transaction, docket, domain
WHEN A CONDITION IS METAmount, match, relationship, severity
ON DEMANDRefresh now
OUTPUT LAWEvery Watch Run produces a new File Version, an explicit No Change event, or an inspectable failure. Nothing is silently overwritten.
07 · ACCESS MODEL
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.
ACCOUNTtenant + policy root
MEMBERSowner · admin · member · viewer
ENTITLEMENTSeffective grants
API KEYSscoped + revocable
SERVICE ACCOUNTSnamed machine identity
AUDITcomplete lineage
08 · TWO COMPLETE PRODUCT LAYERS
Portable truth.
Authorized action.
The Intelligence Layer is complete without enforcement. The Enforcement Layer is a separately activated, separately entitled use of selected intelligence by authorized professionals.
INTELLIGENCE LAYER
A complete horizontal product.
SUBJECT → OPERATION → INTELLIGENCE FILE → WATCH · SHARE · EXPORT · API · MCP
A customer may buy one File, maintain Active Files, run Operations, use API or MCP, export into another system, and never touch enforcement.
- The File is terminal-capable
- No Case is required for full value
- Enforcement language stays out of Desk
- External destinations are first-class
EXPLICIT AUTHORIZED HANDOFF
ENFORCEMENT LAYER
A separate governed system.
AUTHORIZED PARTY + PURPOSE + SELECTED FILES → CASE → MANDATE-GATED ACTIONS → PACKAGES → OUTCOMES
An authorized human deliberately links a signed File version into a separately contracted Case environment.
- Separate activation and entitlement
- No automatic graduation
- Case references the canonical File
- Kinetic never recommends legal action
SEPARATION LAWIntelligence produces portable truth. Enforcement is one authorized use of that truth.
09 · INTELLIGENCE PROGRAMS
The scalable commercial unit.
An Intelligence Program is a repeatable commercial deployment of the Intelligence Layer against a defined population of Subjects. It is not a vertical product, a Case workflow, or a new engine.
01Population100 to 10,000 eligible Subjects.
02CapabilityThe Operations that produce the intelligence.
03File StandardOne governed Intelligence File schema per Subject.
04Watch StandardWhat is monitored, cadence, and what constitutes change.
05Activation LayerPrivate reveal, claim, paywall, checkout, subscription, renewal.
06Sales PlaybookAudience, message, proof, sequence, objections, close.
07Program ConsoleSeeded Files, invitations, claims, subscriptions, renewals.
08Program OperatorThe authorized person or firm distributing the Program.
One Program Operator × one Intelligence Program × thousands of Subject Files.
10 · FIRST PROGRAM PORTFOLIO
Three Programs.
One platform.
PROGRAM 01
Creator Leak Exposure
- POPULATION
- Creators
- INTELLIGENCE FILE
- Exposure locations, recurrence, impersonation, distribution infrastructure.
- ACTIVE VALUE
- Continuous discovery and change monitoring.
- PROGRAM OPERATOR
- Creator protection specialist.
PROGRAM 02
Carrier Compliance
- POPULATION
- Trucking carriers
- INTELLIGENCE FILE
- CSA, authority, insurance, inspection, crash, enforcement, operating status.
- ACTIVE VALUE
- Ongoing regulatory change monitoring.
- PROGRAM OPERATOR
- Transportation compliance specialist.
PROGRAM 03
Brand Domain Exposure
- POPULATION
- Brands
- INTELLIGENCE FILE
- Impersonating domains, DNS, certificates, hosts, storefronts, payment clues, clusters.
- ACTIVE VALUE
- New-domain and infrastructure movement monitoring.
- PROGRAM OPERATOR
- Brand protection specialist.
PORTFOLIO LAWPrograms may differ in population, File Standard, Watch Standard, Activation Layer, and sales motion. They never fork the underlying intelligence architecture.
11 · PROGRAM ECONOMICS
Independent revenue systems.
A Subject can generate intelligence revenue indefinitely without becoming a Case. Enforcement begins only through a separate qualified buyer and explicit authority gate.
01 · PLATFORMProgram revenueThe Program Operator pays for capability access, production, Watch, controls, and Program Console.
02 · INSTANCEFile revenueSubjects pay to claim, access, and keep individual Intelligence Files Active.
03 · ENFORCEMENTCase revenueA separate qualified buyer pays for Case Builder, governed Actions, partner work, and Packages.
INTELLIGENCE PROGRAM LOOP
Find → Seed → Reveal → Claim → Activate → Watch → Renew
Complete inside the Intelligence Layer.
ENFORCEMENT HANDOFF
Explicit consent + authority → Link signed File version → Open Case
Separate product, entitlement, permissions, onboarding, contract, and pricing.
PAYMENT LAWPayment changes access, continuity, capacity, and permitted capability. It never changes truth, authority, or the evidentiary record.
12 · HUMAN COMMAND LAYER
Hide complexity.
Show power.
Desk is where the officer commands Kinetic. Hide the work required to operate the system. Never hide proof of what it did.
COMMANDAsk · approve Tasking · run · challenge · build · activate · share
POWERFactual receipt: Sources, Records, resolved objects, relationships, conflicts, Signals, coverage
REVEALFile → Signals → Intelligence Objects → Records + Citations
AUDITInputs, rights, versions, gaps, hashes, manifests, JSON, API/MCP
HUMAN COMMAND LOOP
Task → Direct → See → Reveal → Challenge → Build → Activate
The user owns intent, scope, judgment, composition, and continuity.
CORRECTED INTELLIGENCE CYCLE
Tasking → Objects → Signals → Review → File → Active → Outcome
Actions and Operations provide the force. Desk remains the human command layer.
DESIGN TESTIf a screen exposes Audit by default, it is too complex. If it cannot reach Audit, it hides proof.
13 · PLATFORM INVARIANTS
Laws, not preferences.
14 · DECISION LEDGER
Locked here.
15 · OPEN SPECIFICATION ITEMS
Deliberately unresolved.
NEXT METHODRepresent locked objects and laws in the interface. Validate relationships visually. Then specify workflows, permissions, failure states, and user interactions. Freeze contracts after that review.