Organization modern slavery service

Versions

• v1 # Changelog ## v6 - Renamed from `supplier-modern-slavery-service` to `organisation-modern-slavery-service` (and its two nested skills, `supplier-modern-slavery-enumerate` and `supplier-modern-slavery-report`, to `organisation-modern-slavery-enumerate` and `organisation-modern-slavery-report`), to match the generic-to-organisations naming now used for the per-record blueprints this skill pair is paired with. **Identity rename only** — this blueprint's own prose is unchanged, because it is correct: this is the estate-wide sweep over `/organization/local/suppliers` and nothing else, it has no `action` block, and it is not mappable to a resource type, so it is never offered on a Customer record. `SUPPLIERS_ROOT`, the `lib/suppliers.py` module filename, `enumerate_suppliers`, `classify_supplier`, `_wait_for_supplier_tree`, `_resource_hint`, the manifest field names, and the workspace artefact filenames (`supplier-modern-slavery-manifest.json`, `supplier-modern-slavery-report.pdf`/`.md`) are all unchanged on purpose — they describe the real supplier collection and real on-disk names, not this blueprint's identity. - The three dispatcher literals in `skills/organisation-modern-slavery-enumerate/lib/dispatch.py` (`BATCH_KIND`, `SHARD_SKILL_REF`, `REDUCE_SKILL_REF`) move from `supplier-modern-slavery`/`supplier-modern-slavery-collect`/`supplier-modern-slavery-report` to `organisation-modern-slavery`/`organisation-modern-slavery-collect`/`organisation-modern-slavery-report`. Any modern-slavery batch dispatched before this deploy and still in flight across it references a shard ref, a reduce ref and a batch kind that no longer resolve after the rename — the same in-flight-batch hazard already called out for the ISO batch, and it applies here identically. - Dangling references to Task 1's already-renamed skills, left behind because this blueprint's own files were outside that task's scope, are corrected: the prompt's `@[skill:supplier-resolve-identity|...]` token and plain-prose "Supplier Resolve Identity" / "Supplier Modern Slavery Collect" mentions now read `organisation-resolve-identity` / "Organisation Resolve Identity" and `organisation-modern-slavery-collect` / "Organisation Modern Slavery Collect". - No behaviour change: the cortex collection path (`/organization/local/suppliers/{id}/`) is unchanged. ## v5 - Supplier Modern Slavery Collect moves out of this bundle to a shared top-level skill (`qonstrue/skills/supplier-modern-slavery-collect`), as Supplier ISO Collect already is. Nothing here references it by path — the `referencedSkills` URI, `dispatch.py`'s `shardSkillRef` and the prompt all name it by skill id — so the enumerate → dispatch → shard → report flow is unchanged. The move is what lets a second blueprint reference the same collector, which is how the per-record modern-slavery risk action gets one without a second copy of the scoring logic. ## v4 - List the Ploutonion `organization-compliance` agent in `referencedA2aAgents`. Supplier Modern Slavery Collect v1.2 discovers statements (`modern-slavery-statements.discover`) and adverse media (`adverse-media.discover`) over A2A instead of the broker's removed Talos helpers, and the broker refuses agents the blueprint does not list (`a2a_agent_not_allowed`). - Identity resolution is documented as the Ploutonion `organization-identity` agent (`organizations.resolve`, then `organizations.identify`), matching Supplier Resolve Identity v1.4. Descriptions, listing and the refresh use case no longer say Talos. ## v3 - Add Archify showcase workflow diagram under `docs/` and `documentation` manifest. ## v1 - Initial release: resolve identity → enumerate → dispatch (generic batch fan-out) → collect (background shards) → reconcile → report modern-slavery risk across workspace suppliers. - Resolve missing `identity.json` from `resource.json` via Talos before enumerate/collect. - Collect combines deterministic geographic/industry inherent risk with LLM-scored governance/operational mitigation, escalated one risk band on adverse-media matches ≥ 2. 11/3/2026