§2257 records

§2257 record-keeping hangs off models and is enforced at distribution time. Today, one field is live — the rest of the records subsystem is coming soon.

Live today — the records2257 flag

Each model carries a records2257 boolean: whether a §2257 record is on file. Set it when you create or update a model — toggling it writes an audit event on the model (“§2257 record marked on file” / “cleared”).

curl -X PATCH https://api.jetwild.com/v1/models/mia-quinn \
-H "Authorization: Bearer $JETWILD_KEY" \
-H "Content-Type: application/json" \
-d '{ "records2257": true }'

The flag also appears on POST /v1/models and on the Model object. Requires the models:write scope.

Coming soon — the records store

A full record store (attach and list per-model §2257 records, with a workspace Custodian of Records) is Coming soon. The endpoints below describe the planned shape — they aren’t callable yet, and the in-app Records page is disabled until the store ships.

Records will live at the workspace level and be shared across every site — so a network never fragments compliance across its brands.

Bind & enforce (coming soon)

When distribution ships, Jetwild will bind each identified model to their record and block any scene with an unresolved record from shipping — a critical verdict at the distribution gate. Until then, records2257 is an informational flag you set and read.

Data security

• Records will be encrypted at rest and access-logged with an immutable audit trail, on a 7-year retention aligned to §2257 requirements.
• Masters are processed in-region; you control scene deletion via the API.