Money. Identity. Technology.
Follow the money. Find the decision.
Shared publication and integration layer for policy and safety-model resources
ROOST Model Community is an open project collecting policy packs, integration guidance and resources for using safety models. The retained repository snapshot is commit 22b3bd4, dated 20 August 2026. Its materials include the Christchurch Call Foundation's terrorist-content policy pack and an investigation prototype example.
The inspected root licence is Creative Commons Attribution 4.0, allowing sharing and adaptation under its conditions. It is not a blanket licence to separately hosted models, service data or third-party content. The integration guide recommends separating detection, investigation, review and enforcement, comparing model outputs with local policy, and using human review for uncertain results. These are recommendations rather than enforced system properties. Repository history shows the Foundation pack present at the examined revision; that custody evidence does not establish a platform deployment or its policy version.
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 → ROOST Model Community (RMC)
2026-08-20 – 2026-08-20
May 27 relocation metadata says relocation without semantic changes; earlier-path query includes May 7. These are finite history results, not full authorship or adoption reconstruction.
ROOST — Robust Open Online Safety Tools Inc → ROOST Model Community (RMC)
2026-08-20 – 2026-08-20
Pinned README and current roadmap identify reusable resources. The 20 August 2026 inspected commit is a custody pin, not first release, adopter deployment or current runtime guarantee.
ROOST Model Community (RMC) → RMC CC BY 4.0 licence
2026-08-20 – 2026-08-20
Read root licence supports copying/adaptation subject to its terms. No separate platform contract or blanket licence to models, endpoint data or third-party content inferred.
ROOST Model Community (RMC) → Phoebe investigation prototype
Guide example supplies a discovery/architecture relation. It does not establish the same deployment, model, CCF policy or enforcement chain used by Discord or Bluesky.
ROOST project maintainers → ROOST Model Community (RMC)
General ROOST project roles assign releases, development and merge approval under branch protection. RMC is a hosted project; this does not identify each actual RMC approver or prove a specific policy merge decision.
From model guidance to local rules: the Phoebe boundary ↗
ROOST project maintainers → exercise project and merge authority under repository rules → ROOST Model Community (RMC)
Interpretation from the evidence
General ROOST project roles assign releases, development and merge approval under branch protection. RMC is a hosted project; this does not identify each actual RMC approver or prove a specific policy merge decision.
ROOST — Robust Open Online Safety Tools Inc → hosts an open model and policy integration project → ROOST Model Community (RMC)
2026-08-20 – 2026-08-20
Pinned README and current roadmap identify reusable resources. The 20 August 2026 inspected commit is a custody pin, not first release, adopter deployment or current runtime guarantee.
CCF TVEC policy pack → is present in the inspected repository → ROOST Model Community (RMC)
2026-08-20 – 2026-08-20
May 27 relocation metadata says relocation without semantic changes; earlier-path query includes May 7. These are finite history results, not full authorship or adoption reconstruction.
ROOST Model Community (RMC) → publishes CC BY 4.0 as its root content licence → RMC CC BY 4.0 licence
2026-08-20 – 2026-08-20
Read root licence supports copying/adaptation subject to its terms. No separate platform contract or blanket licence to models, endpoint data or third-party content inferred.
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.
ROOST Model Community (RMC) → links Phoebe as an investigation example → Phoebe investigation prototype
Guide example supplies a discovery/architecture relation. It does not establish the same deployment, model, CCF policy or enforcement chain used by Discord or Bluesky.