The ZEZ Standard

A view

OBSERVED One counted view per account per day for a registered clip; a guest counts once per address per day. A creator watching their own clip is not an audience and is not counted.

A vote

OBSERVED One up or down per account per clip, changeable; a creator cannot vote on their own work.

A play

OBSERVED A paid play, three credits (one credit is one cent), charged in full to the viewer and attributed to the creator the moment it happens. One record each.

A tip

OBSERVED Credit charged to the tipper and attributed to the creator, one record each.

Gross and play rate

DERIVED Plays plus tips less reversals, in credits; plays divided by views. The formula is named next to the number wherever it appears.

Two sources, reconciled

Attributions and the house's revenue records are written together. The clip's stats page compares them and reports a disagreement as a disagreement.

Charts

DERIVED Clips of the window ordered by counted views; the basis is printed under the chart. Nothing is boosted.

Plays and tips are paid in money as each sale settles, on one statement, on the same rail as every creator door on the estate. Operating cost and taxes come out first; the creator payout is ninety-five percent of what is left and the platform fee is the rest. The statement shows four lines that add up: Sale amount, Operating cost, Platform fee, Creator payout. A render in the Studio is a platform fee, charged by the second of clip and returned in full if the render fails. A paid play needs a creator who has completed the seller's steps; nothing is attributed to an account that has not.

A Studio clip carries a provenance record: the recipe (stages, transitions, bars, performers, the house sound on or off, the aspect), the digest of the track it was cut from, the hash of the engine that drew every frame, the beat grid, the frame count, the worker and the time. The clip's own digest is the bytes delivered. A clip uploaded from elsewhere is registered by its digest and carries no recipe, and the page says so.

The track stays on the creator's device; only its digest and the link they host are registered. The first account to register a digest owns the registration; a byte-identical copy by another account is recorded as evidence and cannot be sold.

Three more things hold a clip to its making. The record is signed by the service when it is written (an Ed25519 signature over the digest, the recipe hash, the making hash, the engine hash, the track digest and the time; the public key is published by the service), so a record that is altered afterwards no longer verifies, and anyone can check one without trusting this page. The file itself carries its making in its own metadata (the recipe hash, the making hash, the track digest, the engine hash and the door), so a copy names its origin wherever it travels. And a making is made once: the same scenes, seeds, window, sound and aspect on the same track is another creator's clip already, and the Studio refuses it before anything is charged; change one thing and it is yours.

Posts stay up; removal only for a legal reason. Nothing posted is edited or deleted by its author: a clip, an update, a comment. A correction is a new post or a comment. A post leaves the feed in two cases only: a recorded decision by the house (a hide, with its written reason, on the decisions log below), or the erasure of the account that made it, after which the record stays under a withdrawal marker so that nothing anyone else relies on is lost.

Legal duties come first. The operator can remove or hide content, and erase personal data, when the law or safety requires it: a court order, the TAKE IT DOWN Act's 48-hour removal of intimate imagery, a notice under the EU Digital Services Act, erasure of personal data under GDPR or CCPA, a copyright takedown, or a safety removal under the platform rules. That is the operator acting under a duty, recorded with its reason; it never gives an author an edit or a delete.

A hide, a restore and a stage challenge result are recorded with a written reason and published here, read live from the service. Each one is also a link in a hash chain: its record is hashed together with the hash of the record before it, so a decision cannot be altered, removed or inserted afterwards without breaking every link that follows, and the chain's verdict is printed under the log. Reports are evidence, not verdicts. A rights claim is shown to the creator with the claimant's contact; under the participant terms the creator deals with the claimant directly and bears the liability.

Paste a clip's digest (the sixty-four character SHA-256 the clip's page shows) to read its provenance from the service. To check a file you hold, choose it: it is hashed on your device, nothing is uploaded, and the two digests are compared. The record's signature is checked here too, on your device, against the key the service publishes.

It does not count what nobody earned: a demo clip shows no numbers, a guest spends nothing, a failed render is refunded. It does not rank by anything but counted views. It does not remove a post quietly. It does not pay anyone but the creator the play or the tip was attributed to. It does not place the engine that draws the clips on the public estate; signed-in members use it for their preview. It does not call a model to decide anything: the one recommendation it offers is drawn from the creator's own numbers, labeled, and never acted on by the service.

Every route the service answers is declared once, with who may call it, the rate it draws on, whether it spends credit or records a decision, and the shape of each input; the same declaration gates every request before a handler runs and is published by the service, so what you read here is what it enforces. A route not in this table does not exist.