Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tattoo.dev/llms.txt

Use this file to discover all available pages before exploring further.

Kinetic Engine v1 is TattooAPI’s internal read-only projection for the ontology action layer. It follows the Palantir-style split between nouns and verbs: nouns describe the industry, while verbs describe what governed operators and agents can do with those nouns. This is not a public API surface. It does not execute writes, expose public SDK methods, or create a new noun family.

​
Operator Contract

Kinetic Engine v1 now exposes a descriptor-only operator contract:
  • contractId: kinetic_engine_v1_operator_descriptor_contract
  • execution mode: read-only descriptor projection
  • internal route: /api/internal/runtime/kinetic
  • supported scopes: engine, lane, workbench, and object
  • mutation authority: internal Convex runtime command routes only
  • public writes: blocked
The contract is useful for agents and operator consoles because it answers “what can I do next?” without giving the projection layer permission to do it.

​
What It Shows

The internal projection answers:
  • which actions are available, blocked, indeterminate, or unbound
  • which ontology nouns and runtime tables are affected
  • which policies and functions are required
  • which workflow and workbench bindings apply
  • why an action is blocked
  • which internal runtime route would later execute the governed command after a human or operator loop chooses to proceed
Execution-route output is descriptive only. Normal mutations still go through internal Convex-backed runtime command routes such as workflow transition, review queue update, recertification update, and lane refresh.

​
Current Boundary

Kinetic Engine v1 belongs to Wave D and Wave E:
  • Wave D uses it to tighten internal SDK convergence around existing action/function/policy/workflow contracts.
  • Wave E uses it to make operator workbenches explicit about next actions, blocked states, and human-gated command paths.
  • Wave F remains blocked. Public SDKs and public APIs do not expose Kinetic Engine routes.
Sensitive paths stay human-gated and internal-only, including law, trust and proof disputes, payment execution, refunds, disputes, payout movement, and public writes.

​
Verification

The repo verifies this boundary with: 
npm run verify:kinetic-engine
The verifier checks that runtime action bindings resolve to existing actions, policies, functions, lanes, workflows, workbenches, and internal route descriptors, and that no public package or public API route exports the Kinetic Engine.