quiet trust infrastructure

Base anchoring.

Base can anchor release proof underneath Casset. It is not the product, the public category, or a token surface.

Status. Active support infrastructure. Keep absent from primary product navigation and investor lead language unless the context is release proof, provenance, or permission settlement.

Casset is an artist home and audiovisual identity product. Base is a trust substrate that can record proof that a canonical release manifest existed with a specific hash at a specific moment.

Base is not the product

The public Casset experience remains Profile Worlds, Hook Objects, Release Rituals, Listening Rooms, cinematic playback, and artist-native atmosphere. Listeners should not need wallets, explorer literacy, or token vocabulary to understand a release.

Do not frame Casset as a blockchain product.
Do not introduce creator coin, token, market, or trading language.
Do not make Base status more visually important than the release.
Do not expose protocol-heavy UI on public cinematic pages.

What Base can do

Base is useful when it strengthens the canonical release layer:

Anchor ReleaseManifest.canonicalHash so a release definition can be verified later.
Preserve proof references for provenance events and release publish milestones.
Support future licensing receipts and settlement references when a permission policy requires a route.
Give agents a trust signal without asking humans to inspect machine internals.

What stays offchain

Most release data stays in Casset's database and manifest payloads: tracks, artwork refs, contributor details, splits, permissions, provenance event JSON, room state, and audiovisual identity. The chain stores proof references, not the music world itself.

Implementation references

ReleaseAnchor stores chain, tx hash, canonical hash, status, attempts, and receipt metadata.
lib/base/release-anchor.ts queues, claims, retries, and records anchor jobs.
lib/releases/publish-runtime.ts ensures manifest snapshots and queues anchors during publish flows.
app/api/cron/releases/* handles release job processing and anchor health.

Current source of truth

Use the active docs instead of older protocol framing:

Product thesis for the narrative center.
Architecture for release manifest and Base anchor implementation context.
API reference for agent-readable release routes.

Internal note: Base anchoring is proof infrastructure under the release manifest layer. It should support provenance and permissions without changing the public mental model of Casset.

Base is not the product

Do not frame Casset as a blockchain product.

Do not introduce creator coin, token, market, or trading language.

Do not make Base status more visually important than the release.

Do not expose protocol-heavy UI on public cinematic pages.

What Base can do

Base is useful when it strengthens the canonical release layer:

Anchor ReleaseManifest.canonicalHash so a release definition can be verified later.

Preserve proof references for provenance events and release publish milestones.

Support future licensing receipts and settlement references when a permission policy requires a route.

Give agents a trust signal without asking humans to inspect machine internals.

Implementation references

ReleaseAnchor stores chain, tx hash, canonical hash, status, attempts, and receipt metadata.

lib/base/release-anchor.ts queues, claims, retries, and records anchor jobs.

lib/releases/publish-runtime.ts ensures manifest snapshots and queues anchors during publish flows.

app/api/cron/releases/* handles release job processing and anchor health.

Current source of truth

Use the active docs instead of older protocol framing:

Product thesis for the narrative center.

Architecture for release manifest and Base anchor implementation context.

API reference for agent-readable release routes.

Internal note: Base anchoring is proof infrastructure under the release manifest layer. It should support provenance and permissions without changing the public mental model of Casset.