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.
Project Status
TattooAPI is currently in the internal-runtime and operator-proof phase. The ontology is broad enough to guide the product, but the public surface should stay narrow until runtime authority and operator workflows are proven.This page is a public-facing status summary. The repo control plane remains the source of truth:
project-context/ontology/platform-wave-roadmap.md, project-context/ontology/overnight-execution-workboard.md, and the PRD under project-context/TattooAPI - Vision + Ontology.Current Wave Posture
| Wave | Status | Meaning |
|---|---|---|
| Wave A | Closed | Source-backed ontology nouns, source-pack structure, and lane scorecards are established. |
| Wave B | Contract-complete enough | Deterministic functions, action vocabulary, and execution contracts exist for the internal platform layer. |
| Wave C | Contract-complete enough | Policies and workflow contracts exist for runtime-governed execution. |
| Wave D | Active | Convex runtime adoption, internal SDK convergence, and legacy runtime isolation remain the main bottleneck. |
| Wave E | Active | Internal operator workbenches are live against Convex-backed runtime truth and are being proven through executed loops. |
| Wave F | Blocked; readiness only | Public read SDKs, read envelopes, and website/free-tool concepts are being designed, not launched. |
| Wave G | Planned; manifest readiness only | Governed dataset manifests can be prepared from operator history, but harvest remains gated. |
| Wave H | Planned; evaluation readiness only | Tattoo intelligence tasks can be specified and evaluated later, with no model training dependency yet. |
Runtime Truth
The target runtime is self-hosted Convex. The active cutover goal is simple:- Convex is the normal read and mutation authority for internal runtime execution.
- File-backed runtime state is limited to bootstrap, degraded fallback, fixture, and maintenance compatibility use.
- Supabase-backed routes are legacy unless explicitly cut over to the runtime adapter or internal Convex admin surface.
- Internal SDK roots should expose operator-safe reads and mutations by default, with maintenance and reseed helpers kept behind explicit compatibility entrypoints.
- Some D3 routes are method-boundary cutovers:
GETreads may be runtime-backed whilePOST,PUT,PATCH, orDELETEremain explicitly blocked or legacy-only until a governed internal Convex mutation contract exists.
Public Boundary
The public API and docs should stay conservative while Waves D and E close.- No public write expansion.
- No public ranking formula API.
- No public proof, legal, or compliance mutation path.
- No public SDK launch until read envelopes and operator governance are proven.
- Public discovery docs should describe only supported current behavior.
- Kinetic Engine descriptors can describe internal actionability, blocked states, and governed route paths, but they do not expose public execution.
Cross-Wave Programs
Several programs now span the waves without creating new ontology noun families:- Marketplace trust, ranking, transaction-readiness, and portfolio proof.
- Pricing and financial-infrastructure depth on existing quote, payment, payout, financing, and market-economics nouns.
- Portfolio Hydration V1 for Sanity CMS, CRM exports, GPT Vision metadata observations, and Firecrawl or Perplexity evidence, all staging-only until operator approval.
- Future SDK, website, free-tool, tattoo.co integration, guest-spot marketplace, governed delist intake, and Ghostline or Tattoo Sketch ideas.