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.
Ontology Reference
The ontology is the source of truth for TattooAPI.Canonical Source
- Typed package:
packages/domain-ontology - Generated reference pack:
project-context/ontology - Narrative phase docs:
project-context/TattooAPI - Vision + Ontology - Intake workspace:
project-context/source-packs
Phase-Two Core Baseline
TattooDesignTattooStyleArtistStudioClientBodyPlacementCulturalReferenceJobSession
Phase-Two Expansion Lanes
- Creative and Design Craft
- Cultural, Historical, and Lineage
- Body, Skin, and Healing
- Studio Operations and Compliance
- Supply Chain and Equipment
- Market, Community, and Ecosystem
- Commercial Services and Software
- Media, Distribution, and Acquisition
- Capital, Ownership, and Transactions
- Law, Jurisdiction, and Public Policy
Current State
- all 10 external lanes are closed at
100/100in the repo-native source-readiness control surface - the runtime bridge now projects all 10 closed lanes into the bounded internal
convexmapping layer - runtime execution is now modeled as an internal-only pipeline: raw source packs -> normalized records -> governed runtime objects -> workflow and audit execution
- self-hosted Convex is the target runtime authority for workflow runs, review queues, recertification tasks, lane refreshes, ranking, trust, proof, and transaction-readiness snapshots
- persisted file runtime state is now bootstrap, degraded fallback, fixture, and maintenance compatibility support, not the intended normal execution truth
- pricing is now treated as a cross-lane financial infrastructure program spanning studio quote ops, market pricing intelligence, and capital or payout rails
- legal and cultural coverage are still internal governance assets, not a public advice or compliance surface
- public SDK and API expansion remain intentionally blocked until runtime-backed internal workflows and operator loops are stable
Generated Outputs
The generated pack includes:- object catalog
- object maturity matrix
- domain lane map
- taxonomy catalog
- relationship matrix
- governance matrix
- action catalog
- function catalog
- action execution catalog
- policy catalog
- workflow catalog
- legacy crosswalk
- projection gap matrix
- lane scorecard
- lane completion roadmap
- semantic completion matrix
- source readiness matrix
- lane source-pack report
- resource registry
- evidence index
- source disposition report
- creative + portfolio gap sheet
- requested domain coverage
- seed registry index
- U.S. state law coverage matrix
- software and service catalog
- media and acquisition catalog
- market archetypes and travel catalog
- capital transactions catalog
- industry lexicon catalog
- unmapped noun check
- normalization backlog
- normalization playbook
- Wave 1 normalization artifacts
- source-readiness program
- source-pack registry
- normalization rules
- exception queue
- source-readiness wave plan
- lane dependency map
- lane normalization rulebook
- lane exception rulebook
- lane sample records
- SDK projection plan
- legacy package status
- operator workbench roadmap
- agent profile roadmap
- closed-loop control plane
- platform wave roadmap
- canonical sample records
- studio and artist field crosswalk
- API contract reference
What Changed in the Current Expansion
The ontology now freezes breadth and shifts into a source-readiness phase without changing the public HTTP surface.- new internal Phase 2 actions exist for style normalization, rights/reuse, skin-placement fit, session estimates, sterilization/compliance, recall impact, equipment loadouts, lineage mapping, and market signal summaries
- new depth-ready objects now anchor techniques, lineages, skin profiles, credentials, manufacturers, product catalogs, and convention events
- projection readiness is now documented explicitly as
mappable now,needs new source, orfuture only - creative and portfolio nouns are now evidence-linked back to repo-owned resources, with backlog and external-validation flags preserved where prose should not become runtime truth
- lane scorecards now separate
semantic 100from real source readiness, and the lane roadmap shows which source packs still block runtime-grade coverage - active source-readiness tracks now focus on creative/portfolio/stencil, studio/compliance baseline normalization, supply-chain catalog normalization, and the Wave 2 body/healing plus market/community lanes
- Wave 1 now includes actual repo-backed style alias bindings, portfolio/stencil sample corpus, projected service/session records, and normalized manufacturer/product samples
- source-pack registry entries, normalization rules, exception queues, and canonical sample records now make the next ingestion cycles explicit and testable
- strict Wave 1 ingestion contracts now exist for creative claims, portfolio assets, stencil workflow, service/session/quote/appointment/license exports, and manufacturer/supplier/recall catalogs, with fixture-backed templates and validators checked into the ontology package
- repo-owned source-pack content now exists under
project-context/source-packs, including spreadsheet templates for all 11 Wave 1 pack types, public pilot batches for Track A creative claims, Track B service menus, and Track C manufacturer/supplier/recall intake, plus private-export Track B workflow pilots for sessions, quotes, appointment windows, and license claims - the current checked-in public pilots stay conservative on purpose: public portfolio captures do not imply reuse rights or healed/process evidence, public service pages do not imply private workflow exports, and supplier SKUs remain evidence only rather than canonical product identity
- Track A now treats
TransferMethod,StencilMedium, andSizingPassas normalized support nouns, Track B now includesEstimateQuote,AppointmentWindow, andLicenseCredentialin the strict boundary, and Track C now keys product identity bymanufacturerBrandId + canonicalProductSlug + sourceCatalogIdwith SKU kept as evidence only - Wave A source-readiness is now complete across Creative, Studio/Compliance, and Supply, and the wave-based roadmap now tracks how the remaining lanes reach
100/100, including dependencies, exit criteria, per-lane rulebooks, and lane sample records - Wave 2 now has its first fully closed lane:
Body, Skin, and Healingreached100/100after adding consent-aware healed portfolio evidence on top ofplacement_reference_pack,client_skin_profile_pack, andhealing_followup_pack Market, Community, and Ecosystemis now an active ingestion-backed Wave 2 lane with strict source packs for geography, mobility, signals, community relationships, and internal lexicon supportCommercial Services and Software,Media, Distribution, and Acquisition, andCapital, Ownership, and Transactionsnow use real pilot source packs, promotion gates, blocked reports, and intake guides instead of remaining scorecard-only backlog lanes- the current business-lane closure uses conservative public pilot batches and repo-held first-party payment-policy exports, not broad production datasets
- the internal data SDK now reads both Wave 1 and Wave 2 score state from generated reports, so body/healing progress can be consumed without importing domain-ontology internals directly
- Cultural and Law now have first-class source-pack contracts, ingestion reports, blocked reports, and intake guides, with stewardship posture and citation freshness enforced in the ontology control surface
- the repo now includes a bounded
convexruntime bridge atconvex/ontology/map.tsandconvex/schema.tsthat projects all currently closed lanes and carries governance/provenance fields forward into runtime tables - the runtime execution layer now exists as internal-only action bindings, workflow bindings, and pipeline stages so runtime-backed operator tooling can consume ontology-defined actions and policies without inventing a second model
- the internal SDK and dashboard layers now expose operator-safe Convex-backed runtime mutation contracts so operators can advance workflow runs, mutate review queues, update recertification tasks, and refresh lanes without treating full-document rebuilds as the normal path
- pricing depth is being expanded on existing nouns first, with enriched quote, appointment, payment, payout, financing, and market-economics semantics tracked through the pricing-gap audit before any new pricing family is allowed
- internal platform nouns such as
AgentThreadare excluded from external market completion scoring - new noun layers now cover software and services, media and acquisition, capital and transactions, law and state-level jurisdiction placeholders, market archetypes, guest-travel destinations, legends, historical contributors, and stencil workflow stages
- typed seed registries now anchor named examples such as software products, media outlets, legends, brands, and all 50 U.S. states plus DC without claiming those catalogs are already runtime-backed datasets
- the ontology now includes a Palantir-style kinetic layer: deterministic functions, stricter action execution contracts, executable policies, and internal workflow schemas
- internal Data SDK and Action/Workflow SDK projections are now defined from the ontology/runtime layer, while
api-clientandshared-typesare explicitly treated as legacy transitional packages - workspace-native internal SDK packages now exist for data, actions, and workflows, generated from the ontology layer rather than from legacy public-client assumptions
- six internal operator workbenches are now part of the Wave E proof surface: Studio and Session Normalization, Marketplace Trust and Proof, Creative Review, Supply Catalog and Recall, Market and Media Intelligence, and Law Profile Review
- the generated pack now also maps the internal agent classes, future public-read gates, governed dataset readiness, and specialized tattoo intelligence evaluation posture that come after runtime and operator proof
Mintlify summarizes the ontology. The generated files in
project-context/ontology remain the authoritative human-readable projection from the typed manifest.