Product coordination
Operate the Studio release control plane.
Studio owns durable creator, project, release, access, operation, index, library, preservation, and projection state while exact chain and browser verification remain independent.
Data and state model
Creator work and public release state are persisted separately from native contract state.
Artifact state
Artifacts bind source, canonical manifest, digest, deployment intent/receipt, active revision, chain binding, prepared files, and retrieval metadata.
Release state
Launch releases contain creator/project/artifact identity, public slug, lifecycle, sale/drop binding, ordered stages, access lists and members, public page sections, operations, eligibility results, and authorization issuances.
Projection state
Indexer tables cover blocks, collections, objects, presentations, creator profiles, markets, replication, anchors, Vault state, mint campaigns, OneMint drops/stages/mints, and library policy/use records.
Reads, writes, and authority
Every transition identifies who is allowed to request it and what external proof completes it.
Creator writes
Authenticated creators create projects, attach work, edit public identity and release copy, choose supported access/stages, request review, and prepare publication. Profile completion and creator control are publish gates.
Collector reads and writes
Collectors read public release, live eligibility, current price/supply/timing, and exact authorization requirements. A mint or market action crosses to the wallet only after simulation/review and is confirmed from exact receipt fields.
GET /api/releases/slug/:slug
GET /api/releases/slug/:slug/eligibility?account=:address
POST /api/releases/slug/:slug/authorization
POST /api/releases/:releaseId/confirmOperator writes
Operators may run bounded launch, automation, and reconciliation actions. Operations are journaled so retries distinguish an included transaction from a request that never landed.
Indexer reads
Indexers accelerate search, feeds, history, and projections. The viewer and transaction preflight re-read current commitments instead of trusting the projection as authority.
Failure and security boundaries
The product must display incomplete external state without inventing a successful substitute.
Prepare is not publish
A draft, compiled release, quote, upload plan, or prepared wallet request remains pre-publication state. Only exact chain receipt confirmation advances the release projection.
Access fails closed
Public and allowlist flows are implemented. Holder/custom rules that lack a complete automatic adapter remain blocked or manually reviewed rather than silently public.
Identity remains creator-owned
ENS, Tezos Domains, and wallet labels may enrich display. They do not replace the saved creator profile or attribution evidence.
Server state is not render authority
The database, indexer, listing feed, and server signature cannot authorize sandbox wallet calls or replace exact manifest/object/presentation verification.
Ethereum and Tezos realizations
The same product vocabulary can target both families while their readiness remains explicit.
Ethereum
Studio has KeelHold planning/reads, generated ABIs, factory/mint/market preflights, EVM wallet actions, FRAY contract/indexer reads, and exact receipt confirmation.
Tezos
Studio can prepare portable manifests, Tezos wallet envelopes, recursive/OnchFS carriers, OBJKT exports, Tezos contract views, and chain context. Missing transaction adapters or unfunded/unapproved release lanes remain blocked.
SDK, APIs, and product surfaces
The control plane is split by audience rather than exposed as one technical console.
Public product
Drops, release pages, collections, artists/profiles, gallery, market, FRAY, activity, leaderboards, library, modules, trust, and preservation.
Creator Studio
Dashboard, projects, work, public page, release, access, review, preparation, and receipt confirmation.
Operator surfaces
Launch, automation, reconciliation, indexer operation, health, and system inspection.
APIs
Artifacts/import/content, manifests, upload plans/chunks, deployment plans, releases/access/eligibility/authorization, modules/library, anchors, presentations, IP downloads, preservation proofs, FRAY, search, and indexer endpoints.
Exact evidence
Source and focused tests demonstrate the current durable product model.
Release and identity tests
Schema, eligibility, public identity, creator profile, project schema, mint evidence, and Postgres identity behavior have focused coverage.
Browser product tests
Studio, mint UI, customer platform, library, Keel viewer, and Keel market have separate browser suites whose environment requirements must be satisfied before claiming a loaded result.
Deployment boundary
This content inventory does not establish that any particular Studio build is the currently public deployment.