ProtectedPortable

Connect Your Platforms

When you post to Pixiv, GitHub, or Booth, Accord automatically records your authorship. Install once — protect forever.

1
Sign in to Accord
2
Install userscript
3
Verify connection
Log in with your account to auto-set your ID
Logging in ensures the same author ID is used across all devices.
Log in →
ACR Setup — Install & Provider Configuration — userscript issuerId health fail-closed

Step 1 — issuerId Setup

Your issuerId is your Supabase user.id — the stable identifier that links your canonical world, all artifacts, revenue, and community membership. It is automatically set when you sign in to Accord. No manual entry required.

Sign in to set your issuerId automatically
issuerId = your Supabase user.id — automatically bound on sign-in.
Sign In →

The userscript reads your issuerId via the Accord session API at /api/canonical/issuer/me. No localStorage is used.

Step 2 — Pixiv Userscript v2.2.0 Install

The pixiv userscript intercepts upload/edit form submissions on pixiv.net. It calls the ACR resolve endpoint, writes the continuity reference into the work caption, and only allows the submit to proceed after a successful writeback. Fail-closed: if ACR fails or the DOM writeback returns false, submit is blocked.

Installation via Tampermonkey / Violentmonkey
  1. Install Tampermonkey or Violentmonkey browser extension
  2. Create a new userscript and paste the source below
  3. Set accord-base-url meta content to your Accord instance URL
  4. Sign in to Accord — your issuerId is bound automatically from your Supabase account
  5. Visit pixiv.net/upload — the userscript activates on submit
Userscript header (// ==UserScript== block)
// ==UserScript==
// @name         Accord ACR — pixiv
// @version      2.2.0
// @description  Accord Action Completion Runtime for pixiv. Fail-closed.
// @match        https://www.pixiv.net/*
// @grant        none
// ==/UserScript==
Source file
⬇ Download userscriptACR endpoint →
Fail-closed guarantee
writebackToPixivDOM() returns boolean
• if return value is false → submit blocked + error banner shown
• if ACR resolve fails (network error, 4xx, 5xx) → submit blocked
• if no issuerId set → submit blocked immediately
• submit is called only after confirmed successful writeback

Step 3 — Provider Health Check

Run an observe (read-only) call to verify the ACR endpoint is reachable and the provider adapter is responding correctly. No mutation is made.

Step 4 — Test Action (pixiv resolve)

Run a full resolve (real mutation) for pixiv/work_post. This creates a canonical record and returns dom_writeback completionOutput. Verify thatcaptionAppend contains the continuity reference.

Provider Completion Matrix

ProviderActioncompletionOutput kindTarget
pixivwork_postdom_writebackcaption textarea
pixivwork_editdom_writebackcaption textarea
githubcode_pushfile_generateACCORD.md + ACCORD_LICENSE
githubrepo_createfile_generateACCORD.md + ACCORD_LICENSE
xtweetmetadata_injecttweet content
discordmessage_postmetadata_injectmessage content
boothproduct_listmetadata_injectproduct description
youtubevideo_uploadmetadata_injectvideo description
notearticle_postmetadata_injectarticle body
Canonical Recovery
World ControlObject RegistryACR RuntimeExportVerifyRebuild