VinylStack Legal Document Standards

Document ID: VS-LGL-003
Version: 1.0
Status: Working Draft
Effective Date: Not applicable
Last Updated: 18 August 2026
Document Owner: VinylStack
Publication Classification: Public governance draft
Cross References: VS-LGL-000 v1.0, VS-LGL-001 v1.0, VS-LGL-004 v1.0, VS-LGL-005 v1.0

Purpose

This document defines how VinylStack creates, reviews, publishes, accepts, supersedes and preserves legal, commercial and governance documents.

Documents should be consistent, readable, version-controlled, technically accurate, legally reviewable, commercially transparent and accessible to their intended audience.

Required header

Every controlled document must identify:

• Document Title;
• Document ID;
• Version;
• Status;
• Effective Date, or “Not applicable” for a non-operative document;
• Last Updated date;
• Document Owner;
• Publication Classification; and
• exact-version Cross References where relevant.

Binding documents must additionally identify the VinylStack contracting entity, governing law or applicable territory where required, intended accepting party and language of record.

Required footer

Every controlled document should conclude with:

• revision history;
• copyright notice; and
• any applicable Schedules, approval information or solicitor-review notes.

Canonical statuses

Working Draft

In development. Not approved and not operative.

Draft for Solicitor Review

Commercially prepared for professional legal review. Not operative.

Approved for Publication

Approved by VinylStack after the required professional and internal reviews. Eligible for controlled publication, but not operative until every required product activation or acceptance condition is satisfied.

Superseded

Replaced by a later version. Preserved with its publication and acceptance evidence.

Withdrawn

Unavailable for new reliance. Preserved with its publication and acceptance evidence.

Document IDs and versions

Each document receives a permanent ID. An ID never changes when the document is revised.

Working drafts may use normal editorial revisions. Once a document has been published for acceptance, every change to its bytes requires:

1. a new version;
2. an updated revision history;
3. a new immutable publication artifact;
4. a new SHA-256 Document Digest;
5. a new publication record; and
6. fresh acceptance wherever acceptance is required.

There is no exception for typographical, formatting or “clarification-only” changes to an accepted artifact. The Document Digest is the authority: if it changes, the accepted document changed.

Cross references and incorporation

A binding document must not incorporate a changing document merely by title or URL. It must identify an exact Document ID and version and state whether that document is incorporated as a binding term or supplied only for information.

The Agreement and its Schedules should contain the definitions essential to interpretation. If VS-LGL-001 is incorporated, its exact version must be pinned. Later Glossary edits never alter an existing agreement.

The order of precedence in VS-LGL-005 applies unless an Accepted Agreement expressly establishes a different order for itself.

Review blocks

Unresolved questions should use a consistent block:

SOLICITOR REVIEW REQUIRED
Topic
Current Product Behaviour
VinylStack Commercial Position
Legal Questions
Required Outcome

Commercial choices should use:

MANAGEMENT APPROVAL REQUIRED
Topic
Current Product Behaviour
Recommendation
Decision Owner
Decision State

Tax, accounting, privacy, platform-policy and technical reviews should be identified separately. A solicitor advises on law; VinylStack management owns the commercial choice.

Technical claims

Where wording depends on platform behaviour, the document must identify the dependency and the evidence required before publication. Documentation must not promise a capability merely because it is designed, partly implemented, configurable or expected from a provider.

Claims such as encrypted playback, capture response, individual traceability, revocation, permanent availability, payout or piracy prevention remain unavailable until their documented production gates pass. No document may claim that copying is impossible.

Publication formats

• Working source: Markdown in docs/legal.
• Public reading copy: accessible server-rendered HTML may present the controlled source and its draft status.
• Accepted commercial artifact: immutable, downloadable and accessible PDF or another approved durable format.

The public reading surface must not relabel a Working Draft as approved. A binding acceptance control must open the exact accepted artifact, not a summary or a separately rendered Markdown page.

Publication record

For every approved immutable artifact, retain:

• Document ID, title and version;
• status and effective date;
• public URL;
• Document Digest;
• file size and publication timestamp;
• approver and scope of approval;
• source commit or controlled source reference; and
• superseding document, if any.

Published artifacts are never overwritten or deleted through normal document maintenance.

Acceptance records

The current Artist Release acceptance implementation records:

• accepting User ID;
• Artist ID and Release ID;
• document version, title, URL and effective date;
• Document Digest;
• acceptance timestamp; and
• bounded app version, platform and environment context.

Acceptance scope follows the document. The master Artist Release Agreement is Artist-account scoped, affirmative and idempotent, so its exact current version and digest persist across Releases. The Artist Release Schedule and final rights declaration are Release-scoped. Listener and Record Token Terms are Listener-account and document-version scoped. A changed version or digest invalidates the corresponding current authority for submission, approval, collection or purchase.

The standards do not claim that VinylStack records a raw IP address, full device identity or rejected acceptance. Any additional personal identifier requires an approved purpose, lawful basis, privacy notice, retention period and access control before collection.

Per-release evidence

VS-LGL-010 is intended to define the master Artist relationship. VS-LGL-011 should bind it to the exact Release submitted by recording the Artist, authorised manager, Release ID, track programme, Rights Holder declarations, contributors, samples, territories, restrictions and relevant Release Manifest version or digest.

Commercial configuration changes must invalidate or refresh the corresponding submission and acceptance evidence. Purchase history and earlier accepted artifacts remain immutable.

Approval register

An Approved for Publication entry must identify:

• VinylStack management approver;
• solicitor reviewer and scope of legal review;
• accountant, privacy, security or platform-policy reviewer where applicable;
• jurisdictions and product version reviewed;
• unresolved conditions;
• exact Document Digest; and
• date approved, next review date and status.

Confidentiality and publication classification

Working material is not automatically confidential and public material is not automatically operative. Each document must carry an explicit publication classification. Sensitive internal operational, security, evidence or commercial information must remain outside public artifacts.

Language and accessibility

Documents should use plain language, defined technical concepts, navigable headings, meaningful link text and accessible output. Legal precision must not be hidden behind unnecessary jargon.

Preservation

Superseded and Withdrawn documents, publication records and acceptance evidence remain preserved under the approved retention policy. They must not be rewritten to reflect later product behaviour.

Revision history

© 2026 VinylStack. All rights reserved.