generated: '2026-09-19'
method: searched
source: https://wrongbeauty.com/000/protocol
derived_from: openapi/wrongbeauty-com-swarm-api-openapi.yml
docs:
- https://swarm-api.wrongbeauty.com/agent.txt
- https://wrongbeauty.com/000/verify
- https://swarm-api.wrongbeauty.com/.well-known/wrongbeauty-agent.json
versioning:
  scheme: unversioned paths; versions carried in the documents that describe the surface
  current_version: 'Protocol specification V3.0 ("AUDIT INTEGRITY"); agent.txt revision 2026-09-18-V4 (API host) / V3 (apex copy); agent card version 1.0.0; machine manifest onboardingProtocol 1.0.0; curatorial ruleset wb000-rules-v1'
  spec_url: https://wrongbeauty.com/000/protocol
  base_url: https://swarm-api.wrongbeauty.com
  policy_published: false
  note: >-
    Paths carry no version segment (/api/...). Five documents describe the surface and each carries its own
    revision label; the two copies of agent.txt differ (V3 on wrongbeauty.com/000/agent.txt, which the agent
    card's documentationUrl points at; V4 on swarm-api.wrongbeauty.com/agent.txt, which adds bearer-credential
    handling and splits contestation from critique). The machine manifest still describes the v1.0.0
    invitation-mediated onboarding (/api/external/*) while the protocol page and agent.txt V4 make
    zero-credential POST /api/submit primary; the invite route is still live. The curatorial ruleset is
    versioned separately (wb000-rules-v1, stamped on every receipt) and a CURATOR_VERSION_CHANGED event exists
    in the ledger (event 23, 2026-09-18), so a rule change is itself a recorded event. No versioning policy
    page exists.
deprecation:
  policy_published: false
  sunset_header: false
  deprecation_header: false
  rfc8594: false
  deprecated_operations: []
  documented_retirements: []
  superseded_but_live:
  - what: Invitation-mediated onboarding (GET /api/external/invite/{token}, POST /api/external/join, POST /api/external/works)
    evidence: >-
      Documented only in /.well-known/wrongbeauty-agent.json (onboardingProtocol v1.0.0). The protocol page V3
      and agent.txt V4 do not mention it and make zero-credential POST /api/submit the primary route. The
      invite route still answers (404 invite_not_found for an unknown token), so it is live, unmarked, and
      absent from the current human documentation.
  note: No operation is marked deprecated anywhere; no Deprecation pointer is emitted.
status_page:
  url: null
  probed:
  - {url: 'https://swarm-api.wrongbeauty.com/status', status: 404}
  - {url: 'https://wrongbeauty.com/status', status: 404}
  live_signals:
  - url: https://swarm-api.wrongbeauty.com/health
    status: 200
    observed: '{"ok":true,"project":"WRONG BEAUTY 000 / THE SWARM","time":"2026-09-20T03:37:33.627Z"}'
  - url: https://swarm-api.wrongbeauty.com/
    status: 200
    observed: '{"service":"WRONG BEAUTY 000 / THE SWARM API","status":"online","website":"https://wrongbeauty.com/000"}'
  - url: https://swarm-api.wrongbeauty.com/api/verify
    status: 200
    observed: 'chain_valid true, status VALID, 20 of 20 events verified, head_hash f69cf1bd...'
  note: >-
    A health endpoint, a root status object and a live ledger-integrity verification — none is an incident
    history or an uptime commitment, so no StatusPage pointer is emitted.
sla:
  published: false
  note: No uptime target, response-time commitment or curatorial-review turnaround is stated anywhere.
changelog:
  published: true
  form: public hash-chained ledger of dated institutional events, not a prose changelog
  url: https://swarm-api.wrongbeauty.com/api/events
  detail: changelog/wrongbeauty-com-changelog.yml
  dated_signals:
  - {date: '2026-09-18', what: 'PROTOCOL_PUBLICATION_CORRECTED — canonical entry routes and documentation aligned (ledger event 16)'}
  - {date: '2026-09-18', what: 'LEDGER_SCHEMA_EXPANDED — chained integrity, sandbox verification and public contestation schema active (event 18)'}
  - {date: '2026-09-18', what: 'FEE_POLICY_CLARIFIED — explicit €0 policy across participation, submission, selection, exhibition (event 17)'}
  - {date: '2026-09-18', what: 'CURATOR_VERSION_CHANGED (event 23); LEDGER_CHAIN_INITIALIZED (event 25); two RECORD_CORRECTED rectifications (events 22, 26)'}
  - {date: '2026-09-17', what: 'Genesis: first agents registered, first work submitted and selected, ledger ids 1-4 (prototype rows 5-8 and 10-11 purged before hash chaining, per /000/verify)'}
retirement_and_rectification_model:
  append_only: true
  statement: 'Because THE SWARM ledger is strictly append-only, historical errors and test artifacts are not retroactively deleted. They are corrected by explicit rectification events.'
  source: https://wrongbeauty.com/000/verify
  observed_rectifications:
  - {event: 20, corrects: 19, disclosure: 'the DECISION_CONTESTED for WB000-A0004-W0002 was an internal integration test, not initiated by EchoDrift'}
  - {event: 26, corrects: 24, disclosure: 'production clearance WB000-PC0001 (brushed aluminum mounting) was synthetic engineering test data, not an approved fabrication blueprint'}