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

# Future Wave Gates

> How TattooAPI moves from internal runtime proof to public reads, SDKs, datasets, and intelligence surfaces.

# Future Wave Gates

F+ means future public activation after the internal runtime and operator layers are proven.

This is not a broad launch switch. Each surface has to pass a specific gate before it becomes public, SDK-facing, dataset-ready, or model-ready.

## Current Rule

TattooAPI can prepare future surfaces now, but activation stays blocked until the underlying proof exists.

| Layer  | Current posture            | What can happen now                                                              | What stays blocked                                          |
| ------ | -------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| Wave F | Readiness and preview only | public read previews, SDK request contracts, page candidates, free-tool concepts | public writes, public SDK launch, public SEO generation     |
| Wave G | Manifest readiness only    | governed dataset planning and eligibility review                                 | dataset harvest without rights, consent, and review lineage |
| Wave H | Evaluation readiness only  | task specs and eval shapes                                                       | model training or autonomous truth promotion                |

## Wave F Gate

A public read, page candidate, SDK tool, or free-tool surface needs:

* TattooAPI runtime truth for the subject family.
* Review lineage that explains why the record is usable.
* Rights and consent posture.
* Publish-state or redaction rules.
* Owner and cross-studio privacy checks.
* Rollback and audit posture.
* No public mutation authority.

Best first candidates:

* public studio directory projection
* public artist directory projection
* public published portfolio projection
* public published design projection
* read-only SEO page candidates generated from reviewed demand mappings

## Wave G Gate

A governed dataset candidate needs:

* source record lineage
* reviewed provenance
* rights and consent posture
* eligibility state
* operator decision history
* blocked-use notes
* audit and rollback path

First-party sheets, approved media sources, SEO demand, and public observations can help build candidates, but raw source data does not become training data just because it exists.

## Wave H Gate

An intelligence task needs:

* allowed inputs
* blocked inputs
* expected output shape
* evaluation source
* human review requirement
* rollback and audit posture

Examples that stay gated:

* style/market demand intelligence
* artist discovery ranking explanations
* image metadata assistance
* ad creative angle generation from reviewed portfolio context
* free tools like sketch or design helpers

## Practical Next Step

The highest-leverage F+ task is a read-only public-preview layer over already-reviewed canonical data.

Start with:

1. `Studio`
2. `ArtistProfile`
3. `PortfolioAsset`
4. `Design`

Local commands:

* `npm run generate:wave-f-public-read-preview-pack`
* `npm run verify:wave-f-public-read-preview-pack`

The preview pack is an internal artifact. It can summarize candidate public fields and redaction rules, but it must keep public activation, public writes, public SDK launch, and public SEO page generation disabled.

Do not start with:

* bookings
* payments
* legal advice
* trust/proof raw details
* compliance claims
* public write intake

## Activation Checklist

Before a surface moves from preview to public:

* `verify:wave-d-runtime` is green.
* `verify:wave-e-operator` is green.
* `verify:wave-f-readiness` is green.
* `verify:future-waves-readiness` is green.
* public write guardrails remain green.
* the surface has a documented privacy and redaction rule.
* the surface has a documented rollback path.

## Public Boundary

Public users can read only intentionally published projections. Internal teams, owners, private workers, and operators use authenticated beta routes with TattooAPI actor mappings.

Another studio must not see another studio's draft portfolio, private design metadata, raw model observations, pricing history, client records, proof disputes, or operator notes.