Money. Identity. Technology.
Follow the money. Find the decision.
Local decision-maker translating reusable tools into platform action
The tool adopter or platform operator is the organisation that chooses and runs a safety tool in its own service. This abstract role separates the publisher of reusable software or policy guidance from the party configuring rules, connecting data and deciding what happens to users or content.
ROOST's integration guide describes choices about models, hosting, local policy and human review. Open licences permit modification subject to their terms, and published governance recognises forking as a check on upstream project control. These permissions do not supply platform credentials or restricted reference data. The Phoebe example likewise requires an operator's endpoints and repository configuration. Pathways support carries access and confidentiality conditions while expressly leaving implementation discretionary. A named deployment and its configuration would be needed to attribute a particular moderation action to this role.
CCF TVEC policy pack → Tool adopter / platform operator
Policy labels eight invalid categories, normally requires two indicators for credible-threat TVEC2 and describes law-enforcement escalation plus contextual EDSA/human review. This is proposed policy text in a reusable pack, not an operating legal duty or observed removal.
Tech Coalition Pathways → Tool adopter / platform operator
Current programme targets company employees handling user content/communications, excludes current member staff and vendors without that role, and reviews applicants. Coalition membership is neither required nor guaranteed. No registration or acceptance event observed.
ROOST Model Community (RMC) → Tool adopter / platform operator
Guide recommends detection/investigation/review/enforcement separation, comparison with existing policy and human review for uncertain cross-model results. Adopter chooses policy, model/hosting and integration; recommendation is not enforced architecture.
CCF TVEC policy pack → Tool adopter / platform operator
INCITE1 is referenced but undefined in inspected policy line 104; EDSA exclusion and otherwise-TVEC permission/evaluation language need reconciliation before treating this as an executable consistent specification. Not evidence of actual over-removal.
RMC CC BY 4.0 licence → Tool adopter / platform operator
Licence requires applicable attribution/notices and identification of changes, disclaims endorsement, and provides termination/cure terms. It does not require adopters to accept CCF updates or give CCF final authority over local content.
Pathways non-member terms → Tool adopter / platform operator
Terms address information/feedback requests and reasonable efforts to respond to information requests within three months. The duties do not grant an right to a platform user database or amount to blanket assignment of feedback IP.
Pathways non-member terms → Tool adopter / platform operator
Licence is personal, nonexclusive, nontransferable and internal/noncommercial within the stated site-material scope. It is not an assignment of participant inventions or universal permission to all linked third-party resources.
CCF TVEC policy pack → Tool adopter / platform operator
Annex 2 combines actor, content and behavior, discusses politicized/incomplete lists and uses selected incident context. Its examples are not legal designation findings or evidence that a named platform adopted those labels.
From model guidance to local rules: the Phoebe boundary ↗
Pathways: access conditions, advice and a separate consulting service ↗
ROOST — Robust Open Online Safety Tools Inc → describes forking as a check on upstream project control → Tool adopter / platform operator
Open-source model permits independent forks subject to the relevant licence. Published project rules do not compel downstream operators to deploy an upstream change.
RMC CC BY 4.0 licence → permits sharing and adaptation with attribution conditions → Tool adopter / platform operator
Licence requires applicable attribution/notices and identification of changes, disclaims endorsement, and provides termination/cure terms. It does not require adopters to accept CCF updates or give CCF final authority over local content.
CCF TVEC policy pack → offers removal and escalation language for voluntary adaptation → Tool adopter / platform operator
Policy labels eight invalid categories, normally requires two indicators for credible-threat TVEC2 and describes law-enforcement escalation plus contextual EDSA/human review. This is proposed policy text in a reusable pack, not an operating legal duty or observed removal.
CCF TVEC policy pack → supplies contextual actor guidance with explicit limitations → Tool adopter / platform operator
Annex 2 combines actor, content and behavior, discusses politicized/incomplete lists and uses selected incident context. Its examples are not legal designation findings or evidence that a named platform adopted those labels.
CCF TVEC policy pack → publishes a finite evaluation with mixed category results → Tool adopter / platform operator
2026-04-17 – 2026-04-17
Reported by the cited source
170 team-labelled items yield TP114/FN12/FP0/TN44 and reported 90.5% recall/100% precision. Recruitment 12/17 fails the stated 85% target; EDSA exact-category precision is distinct from binary valid/invalid errors; TVEC4 11/13 rounds to 85%. No general precision guarantee or observed deployed model.
CCF TVEC policy pack → retains an unresolved category reference and contextual tension → Tool adopter / platform operator
INCITE1 is referenced but undefined in inspected policy line 104; EDSA exclusion and otherwise-TVEC permission/evaluation language need reconciliation before treating this as an executable consistent specification. Not evidence of actual over-removal.
ROOST Model Community (RMC) → describes configurable model and human-review choices → Tool adopter / platform operator
Guide recommends detection/investigation/review/enforcement separation, comparison with existing policy and human review for uncertain cross-model results. Adopter chooses policy, model/hosting and integration; recommendation is not enforced architecture.
Tool adopter / platform operator → selects model, endpoint and repository configuration → Phoebe investigation prototype
2026-02-07 – 2026-02-07
Pinned defaults include a model setting and alternate backends; operator supplies service/repository settings. Adapter obtains action/feature/label/UDF metadata from the configured server, without a hardwired CCF taxonomy.
Phoebe investigation prototype → does not implement Ozone label application or removal in the inspected adapter → Tool adopter / platform operator
2026-02-07 – 2026-02-07
Both methods raise NotImplementedError and client remains TODO in this 18-line file. This prototype limit says nothing about all Ozone integrations or whether Bluesky can reverse a real action.
Phoebe investigation prototype → offers MIT software rights without service or data entitlement → Tool adopter / platform operator
2026-02-07 – 2026-02-07
Pinned MIT permission allows software reuse under notice/warranty conditions. It provides no server credentials, platform authority or licence to restricted data.
Tech Coalition Pathways → offers no-cost support after eligibility and registration review → Tool adopter / platform operator
Current programme targets company employees handling user content/communications, excludes current member staff and vendors without that role, and reviews applicants. Coalition membership is neither required nor guaranteed. No registration or acceptance event observed.
Pathways non-member terms → requires accurate registration and information cooperation → Tool adopter / platform operator
Terms address information/feedback requests and reasonable efforts to respond to information requests within three months. The duties do not grant an right to a platform user database or amount to blanket assignment of feedback IP.