AIAPS-002 — Implementation Guide

Active Standard

Implementation Guide

This document describes how to protect a recording under AIAPS v1.0. A compliant protection workflow must generate a fingerprint, embed a watermark, register the recording in an AIAPS-compatible registry, and support verification.

The official AIAPS plugin is the reference implementation. It operates locally within standard DAW environments. No audio content is transmitted externally.

Document Info
StatusActive
Spec ReferenceSections 7, 10, 14
InputWAV / FLAC / AIFF
ScopeFinished Recordings

Section 01 — Protection Workflow

Protection Steps

A compliant AIAPS protection workflow performs the following steps in sequence.

Protection Flow
InputFinished audio recording (WAV / FLAC / AIFF)
AnalyzeSpectral and temporal structure analysis to derive a perceptual fingerprint
EmbedWatermark encoded into psychoacoustically masked regions of the audio signal
RegisterFingerprint, AIAPS ID, timestamp, and NO_AI_TRAINING policy written to the registry
MetadataAIAPS-PROTECTED notice written to file metadata where the format permits
OutputAIAPS-protected recording with assigned AIAPS ID

Section 02 — Protection Components

What a Protected Recording Receives

Upon successful processing, the following components are generated and associated with the recording.

Required components (Spec Section 7)

01Registry record with AIAPS ID

02Audio fingerprint (spectral + temporal)

03Embedded AIAPS watermark (inaudible)

Associated identifiers (Spec Section 8)

01Spectral fingerprint for registry lookup

02Watermark payload (version, policy, ID, timestamp, integrity)

03Registry record (ID, fingerprint, artist, title, timestamp, policy)

Section 03 — Standard Mark

AIAPS Standard Mark

Recordings protected through a compliant AIAPS workflow may display the AIAPS Standard Mark.

AIAPS-PROTECTED

Unauthorized AI training prohibited.

The standard mark may appear in

01Distribution pages

02Album liner notes

03Website descriptions

04Promotional materials

05Metadata fields where available

Section 04 — Requirements

Implementation Requirements

4.1

The recording SHALL be in WAV, FLAC, or AIFF format at the time of processing.

4.2

The recording SHALL be a finished music recording or exported stereo master. AIAPS v1.0 does not define stem-level or source-session protection.

4.3

The rights holder or authorized representative SHALL initiate the protection process.

4.4

The implementation SHALL run locally. No audio content is transmitted externally during analysis or watermark embedding.

4.5

The implementation SHALL register the recording in an AIAPS-compatible registry and assign a unique AIAPS ID in the format AIAPS-YYYY-NNNNNN.

4.6

The implementation SHALL embed an AIAPS-compliant watermark that remains inaudible under normal listening conditions while remaining detectable by compliant verification tools.

4.7

The registry record SHALL contain at minimum: AIAPS ID, fingerprint, artist name, track title, registration timestamp, policy code, and account linkage.

The AIAPS plugin is currently in development.

Join the Waiting ListRead the Specification