∞8
ARCH
Declarations v1.0
The professional standard for documenting how music gets made in the AI era.
Prove your process. Machine-readable declarations. Verifiable creative lineage. Free to use.
What ∞8 ARCH Does
Identity
Cryptographically verifiable artist identity. Collaborators with revenue splits. Contributors with roles.
Creative Stack
Document every tool in your workflow. DAWs, plugins, AI models, hardware. The full picture.
Production Intelligence
Quantified AI contribution by phase. Composition, arrangement, production, mixing, mastering. Methodology notes.
Provenance Chain
IPFS CID links to source material, samples, stems. Immutable revision history. Audio fingerprint verification.
Get Started in 3 Steps
Create or Import
Start from scratch or use our Suno/Udio bookmarklets to auto-fill track data. Takes 10 seconds.
Document Process
Add tools, AI percentages, collaborators, and methodology. Be as detailed or minimal as you want.
Save & Share
Get a unique URL for your declaration. Share it, embed it, or mint it on-chain later.
Platform Integrations
Created a track with Suno or Udio? Document it in 10 seconds with our one-click bookmarklets. Each bookmarklet extracts track metadata and pre-fills your declaration form.
Suno
Extracts title, prompt, model version, and artist from suno.com track pages.
Udio
Extracts title, prompt, tags, lyrics, model version, and creator from udio.com track pages.
One-Time Setup
Copy the bookmarklet code for your platform (Suno or Udio)
Right-click your bookmarks bar → “Add page” or “Add bookmark”
Name it (e.g. “∞8 + Suno” or “∞8 + Udio”) → Paste the code as the URL → Save
Daily Usage
Go to suno.com or udio.com and open a track page
Click the bookmarklet in your bookmarks bar
Declaration form opens pre-filled → Review details → Save
Suno: Extracts track title, prompt, model version (v3.5, v4), and artist name from any Suno track page.
Udio: Extracts track title, prompt, tags, lyrics, model version (v1, v1.5, v1.5 Allegro), and creator name from any Udio track page.
Declaration Structure
{
version: "1.0",
declaration_id: "∞8-Qm...",
identity: { primary_artist, collaborators, contributors },
creative_stack: { daws, plugins, ai_models, hardware },
production_intelligence: { ai_contribution, methodology },
provenance: { ipfs_cid, source_material, stems },
audio_fingerprint: { sha256, duration_ms, format }
}Frequently Asked Questions
Do I need a crypto wallet to use ∞8 ARCH?
No. You can create declarations anonymously during beta. Connecting a wallet enables on-chain minting, revenue splits via smart contracts, and permanent provenance records. But basic documentation works without one.
What happens to my data?
Declarations are stored in our database and can be viewed publicly in the gallery. Audio files are stored on IPFS (Pinata). Anonymous declarations can be deleted during beta. Wallet-connected and minted declarations become permanent for provenance integrity.
What do the labels mean (Human, AI-Assisted, AI-Native, Full AI)?
They're derived from your AI contribution across five production phases. Human = 0% AI. AI-Assisted = up to 25%. AI-Native = 25-75%. Full AI = 75%+. No judgment either way — it's a description, not a ranking.
Can I document non-AI music?
Absolutely. Set all AI contribution percentages to 0% and document your traditional workflow. The protocol works for any creative process—AI-native, hybrid, or fully human.
What does "minting" mean and why would I do it?
Minting creates an NFT of your declaration on the blockchain, making it permanently immutable. Benefits: cryptographic proof of creation date, integration with ISSUANCE platform for revenue streams, ability to track lineage and derivatives, and enforcing smart contract splits for collaborators.
Is this just for Suno and Udio? What about other AI music tools?
We have dedicated bookmarklets for Suno and Udio, but you can manually create declarations for any tool: Stable Audio, AIVA, or even traditional DAWs. The protocol is tool-agnostic.
Can I edit declarations after creating them?
Not yet. Once created, declarations are immutable by design to maintain provenance integrity. If you need to update information, create a new declaration with parentRelation set to "remix" or "derivative." Edit functionality may be added for pre-minted declarations.
What's the difference between collaborators and contributors?
Collaborators get revenue splits (on-chain enforcement via smart contracts). Contributors get credit but no direct splits (think: session musicians, studio engineers, co-writers). Both are recorded in the declaration for attribution.
Who This Is For
AI-native producers building tracks with Suno, Udio, or custom models — and want a professional record of how they work. Not because anyone asked. Because your process is the proof.
Producer-engineers running hybrid workflows — AI stems into Ableton, live vocals over generated arrangements, three collaborators across two continents. Traditional metadata can't capture what you're doing.
Anyone who sees transparency as a competitive advantage — not a liability. Your 73% AI composition paired with hand-crafted arrangement isn't something to hide. It's proof you understand your tools at a level most producers never reach.
EU AI Act Article 50 requires AI content labeling by August 2026. The infrastructure you'll need doesn't exist yet in the legacy music industry. It exists here.
Not for everyone. That's the point.
If documenting your creative stack feels like exposure rather than demonstration, that's fine — different stages, different needs. The protocol is here when you're ready.
Your process is your proof. Document it.
Create Your First DeclarationDisclaimer: ∞8 ARCH provides infrastructure for creative provenance documentation. Users are solely responsible for the accuracy of their declarations and compliance with applicable laws. We make no warranties regarding the legal enforceability of declarations or rights claimed therein. This service is provided "as-is" without guarantees of any kind.
AI model names (Suno, Udio, AIVA, etc.) are trademarks of their respective owners. Mention of these tools is for descriptive purposes only and does not imply endorsement or affiliation. Users should comply with the terms of service of any third-party tools they document in their declarations.