The operational surface of the InkID protocol for music publishers, labels, and editorial organizations.
InkTrust is the publisher's terminal for the InkID protocol. Writer submissions arrive with their behavioral evidence already anchored. Decisions get recorded against a cryptographic audit trail. The whole pipeline — submission to pitch to release to catalogue — operates on a substrate of verifiable authorship.
Operations terminal · Multi-seat · Pilot cohort active
A publisher in 2026 faces three pressures the publisher in 2019 did not.
Some are written by writers. Some are not. The proportion is unknown and growing.
Sign, pass, pursue, drop — from writers, lawyers, and regulators. "Why did you do that?" is a question publishers now have to answer in writing.
AI-flagged work is one risk. Tortious interference, defamation, and class-action claims track exactly the opposite failure mode.
InkTrust is built around all three at once.
Writer submissions arrive through Direct Link — a per-publisher submission portal where writers attach their InkID. The behavioral evidence is already anchored, already independently timestamped, already verifiable. No "trust us" framing on either side. Just records.
For every submission, the protocol's evidence is visible at a glance: the dimensions captured, the timestamp authority, the writer's consent state, the catalogue context. The panel shows what InkID recorded. Decisions about what that means stay with the publisher.
Submissions move through your team's pipeline — pitched, pursued, signed, released, dropped — and every state change is captured in the audit trail. Pitches, sync briefs, A&R notes, team handoffs, all anchored.
Catalogue monitoring across streaming and release platforms. When a third-party track resembles a work in your catalogue, the radar flags it for review. The workflow is designed for action under DMCA §512 with contemporaneous human-review documentation that supports the publisher's safe-harbor posture.
A&R reviews, attorney reviews, label-head approvals, sync-team handoffs — each role's actions are scoped, logged, and accountable.
Every InkTrust seat opens behind a click-through agreement called the Publisher Compact. The Compact is short, specific, and versioned. It commits the publisher to three things — and binds those commitments cryptographically to the seat-holder's acceptance.
InkID data informs publisher judgment; it does not replace it. The publisher does not automate adverse decisions against writers from InkID signals alone. For any adverse decision substantially informed by InkID data, the publisher documents the non-InkID factors and the named senior reviewer.
Writers can see what the publisher reviewed and what factors informed an adverse decision, on request, within thirty days. The protocol is open in both directions.
If a writer makes a legal claim arising from an InkTrust-informed decision, InkID contributes toward the publisher's defense costs and cooperates in good faith on document preservation and joint defense.
Every consequential action in InkTrust — submission opened, pitch advanced, decision recorded, takedown initiated, team handoff — writes to the audit trail. The trail is independently anchored, append-only, and exportable. When a regulator, a writer's lawyer, or your own counsel asks "what did your team know, and when?", the answer is already in writing.
Writers anchor their InkIDs through InkWave, Folio, or another protocol surface. When they submit to a publisher through InkTrust, they choose what the publisher sees.
The publisher operates on what the writer chose to disclose. Not on what InkID could have shown.
A versioned DPA at inkid.io/legal/dpa is incorporated by reference into every Publisher Terms acceptance. Article 28 GDPR processor obligations, sub-processor enumeration, breach-notification timelines, audit rights, return-or-delete obligations — all in writing, all versioned, all under the published change history.
Tier 1 — raw behavioral signals — captured on-device, never transmitted off the writer's device. Tier 2 — aggregated dimension scores — processed for verification, retained as audit evidence. Tier 3 — document content — the writer's submitted work, stored under envelope encryption with InkID-managed keys.
Release Radar takedowns require named senior human review with contemporaneous documentation — the discipline §512(f) wrongful-takedown defense actually requires. Counter-notice flow is supported in the workflow.
Revoked consent triggers cryptographic erasure — not "we mark a flag and hope." The anchor token remains as a receipt of what existed; the underlying evidence is destroyed in a way the protocol can attest to.
InkTrust is operational infrastructure for a publisher's authorship workflow. It is not — and is precise about what it is not.
Boutique to major. Manage writers' InkIDs at catalogue scale; pipeline submissions; monitor release-day exposure with Radar.
Sign decisions defensibly. Pass decisions defensibly. The audit trail makes "we'll know" stop being aspirational.
Brief flow with attached authorship records. When a placement asks "did a person write this?" the answer is in the record, not in an email thread.
Songwriter associations, music charities, writers' guilds. The InkID protocol becomes organizational infrastructure for the writers you serve.
InkTrust pricing is tiered by organization size and use, billed per seat. Current ranges:
Pilot access is by introduction only. Independent, Professional, and Enterprise tiers open as the next cohort wave begins.
Request access →InkTrust is in active development and currently running a limited-cohort pilot. Access is by introduction only. Publishers interested in the next pilot wave can request access; we'll be in touch when the next cohort opens.