Supplier Modern Slavery Collect

Versions

• v4 # Changelog ## v1.3 - Run statement and adverse-media discovery concurrently (two threads) instead of back to back, so one supplier's discovery costs ~485s rather than ~970s against the 600s sandbox exec that runs a shard. - Print a failed discovery to stderr (exception type and message). `a2a_agent_not_allowed` is re-raised, so a blueprint missing `organization-compliance` from `referencedA2aAgents` fails the supplier instead of scoring it as "nothing found". - Treat a whitespace-only website as missing: statement discovery is skipped, and the manifest row's website is used when identity's is blank. - SKILL.md: the tool timeout advice is the 600s maximum (it said 900–1800s, which the sandbox tools reject); multi-supplier runs go through the batch path. ## v1.2 - Statement and adverse-media discovery move from the broker's Talos helpers (`talos_modern_slavery_discover`, `talos_news_discover`, now removed) to the Ploutonion `organization-compliance` A2A agent via `qb.a2a_call_skill` — `modern-slavery-statements.discover` and `adverse-media.discover`. Request fields keep their names (`organizationName`, `jurisdictionCode`, `websiteUrls`); response fields are unchanged. - Pass `timeout_sec=480` on both calls: discovery runs up to 420s and the broker's default A2A timeout is 180s. - Skip statement discovery for a supplier without a website instead of sending an empty `websiteUrls` — the skill rejects it (Talos returned 400 for it too), so the outcome is the same without the wasted call. `jurisdictionCode` is omitted rather than sent as null when unknown. - `allowed-tools`: `a2a_call_skill` replaces the two Talos helpers. The consuming blueprint must list `organization-compliance` in `referencedA2aAgents`. ## v1.1 - Report each shard item to the agent-control-plane via `qb.batch_item_done` instead of writing a `shard-<i>.json` file ledger. Dropped `_write_shard_progress` / `SHARD_LEDGER_ROOT` — no local shard-ledger file. `collect_shard` now returns the reported items list instead of a path. - SKILL.md: updated the shard-mode section to describe the `qb.batch_item_done` reporting path. ## v1 - Initial release: deterministic geographic/industry inherent scoring (`ms_risk`), Talos statement discovery + LLM governance scoring, LLM operational mitigation scoring (with conservative fallback defaults), Talos adverse-news discovery + escalation, hybrid combine into a single final risk score/level/grade, written to per-supplier `modern-slavery-risk-assessment.json`. - Shard mode: `collect_shard`/`main_shard` for the generic batch fan-out mechanism, contract-conformant with `batch-reconcile/CONTRACT.md` (byte-for-byte shard doc shape shared with `supplier-iso-collect`). 10/13/2026
• v3 # Changelog ## v1.1 - Report each shard item to the agent-control-plane via `qb.batch_item_done` instead of writing a `shard-<i>.json` file ledger. Dropped `_write_shard_progress` / `SHARD_LEDGER_ROOT` — no local shard-ledger file. `collect_shard` now returns the reported items list instead of a path. - SKILL.md: updated the shard-mode section to describe the `qb.batch_item_done` reporting path. ## v1 - Initial release: deterministic geographic/industry inherent scoring (`ms_risk`), Talos statement discovery + LLM governance scoring, LLM operational mitigation scoring (with conservative fallback defaults), Talos adverse-news discovery + escalation, hybrid combine into a single final risk score/level/grade, written to per-supplier `modern-slavery-risk-assessment.json`. - Shard mode: `collect_shard`/`main_shard` for the generic batch fan-out mechanism, contract-conformant with `batch-reconcile/CONTRACT.md` (byte-for-byte shard doc shape shared with `supplier-iso-collect`). 7/31/2026
• v2 # Changelog ## v1.1 - Report each shard item to the agent-control-plane via `qb.batch_item_done` instead of writing a `shard-<i>.json` file ledger. Dropped `_write_shard_progress` / `SHARD_LEDGER_ROOT` — no local shard-ledger file. `collect_shard` now returns the reported items list instead of a path. - SKILL.md: updated the shard-mode section to describe the `qb.batch_item_done` reporting path. ## v1 - Initial release: deterministic geographic/industry inherent scoring (`ms_risk`), Talos statement discovery + LLM governance scoring, LLM operational mitigation scoring (with conservative fallback defaults), Talos adverse-news discovery + escalation, hybrid combine into a single final risk score/level/grade, written to per-supplier `modern-slavery-risk-assessment.json`. - Shard mode: `collect_shard`/`main_shard` for the generic batch fan-out mechanism, contract-conformant with `batch-reconcile/CONTRACT.md` (byte-for-byte shard doc shape shared with `supplier-iso-collect`). 7/30/2026
• v1 # Changelog ## v1 - Initial release: deterministic geographic/industry inherent scoring (`ms_risk`), Talos statement discovery + LLM governance scoring, LLM operational mitigation scoring (with conservative fallback defaults), Talos adverse-news discovery + escalation, hybrid combine into a single final risk score/level/grade, written to per-supplier `modern-slavery-risk-assessment.json`. - Shard mode: `collect_shard`/`main_shard` for the generic batch fan-out mechanism, contract-conformant with `batch-reconcile/CONTRACT.md` (byte-for-byte shard doc shape shared with `supplier-iso-collect`). 7/22/2026