Tools are the small, focused capabilities the runtime can invoke during a turn. Each one runs on the user's device, returns a draft, and never takes action on the user's behalf.
Compares an offered or requested recruitment fee against the legal cap for the corridor and sector. Draws on the corridor pack. never on a private database.
Drafts a structured complaint with cited rule references. Fields are placeholders; the caseworker fills, verifies, and decides whether and where to submit.
Surfaces verified, public organizations relevant to the corridor and the violation pattern. DueCare never contacts these organizations on the user's behalf.
Confirms that every claim in a DueCare draft is grounded in a passage from the vetted corridor pack. and rejects unsupported claims before the user ever sees them.
The single chokepoint in both directions. Outbound: strips PII and enforces the k-anon floor on anything a deployment chooses to send. Inbound: scrubs scraped public sources. advisories, registries, regulator pages. before any text enters a vetted pack. Audit-logged either way.
When the crawler proposes a pack update, the curator reviews the diff in plain text. no automation signs a pack on the curator's behalf.
Every DueCare tool returns a draft, a check, or a routing suggestion. None of them act. The product surface always ends at a draft for the user or caseworker to decide on.
Tools draft only. They never act.