> ## 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.

# Private Worker And Hydration Boundaries

> How TattooAPI uses private review tooling and source packs without exposing unsafe public surfaces.

# Private Worker And Hydration Boundaries

TattooAPI uses private review tooling and source-pack workflows internally, but they are not public product surfaces in this phase.

The public rule is simple:

* private tools can help review, validate, and prepare data
* source packs can stage evidence
* TattooAPI runtime remains canonical only after governed promotion
* public writes, public legal advice, public SEO pages, and public datasets stay gated

## Private Review Layer

Private review tooling can help with:

* studio and artist normalization
* marketplace trust review
* creative and portfolio review
* source-pack review
* law/compliance review preparation
* promotion previews
* SDK-oriented creative seed generation

It does not:

* replace TattooAPI runtime truth
* create public write routes
* publish ads or spend money
* turn scraped data into canonical records automatically
* bypass approved identity or TattooAPI actor mapping

## Ontology Guidance

Ontology guidance is read-first support for acquisition and review tooling.

It can answer:

* which ontology nouns a record might map to
* which fields are required
* which lane and review queue apply
* which data classes are blocked
* whether a record is shaped well enough for staging

It cannot:

* promote records into TattooAPI runtime
* create public API routes
* bypass review queues
* expose secrets or raw protected data

For portfolio work, private tools must treat `PortfolioAsset` as a core ontology pillar, not as loose media. Portfolio records need source lineage, owner tenant, artist attribution, rights posture, consent posture, review status, and distribution state before they can be used outside internal review surfaces.

## Source-Pack Model

External acquisition systems, including scraper machines, should emit source packs.

Source packs must carry:

* source system
* source URL or file id
* source hash
* captured timestamp
* target ontology nouns
* rights, consent, and provenance posture
* review status
* public surface activation state

Staged source packs are evidence, not truth.

## Law And Compliance Data

Law and bloodborne-pathogen records are handled with extra caution.

* official sources outrank third-party summaries
* citation-backed rows go to review first
* sync diffs flag new, changed, missing, and unchanged citation units
* missing citations are review warnings, not deletion instructions
* no public legal advice surface is active

## Public Readiness

Private review and hydration outputs can support future public surfaces only after:

* runtime truth exists in TattooAPI
* source lineage is reviewed
* rights and consent posture is acceptable
* privacy and redaction rules are clear
* operator rollback/audit paths exist

Until then, these systems remain internal infrastructure.

See [Data Hydration Source Packs](/guides/data-hydration-source-packs) and [Future Wave Gates](/guides/future-wave-gates).