Vetted knowledge only
Packs a curator has signed off on (Stage 05 in the vetting process). The safe default for production deployments, NGO field workers, and platform-moderation use.
Download vetted ZIP →GET /api/hub/knowledge/download?vetted=true
A pack is the unit of knowledge the harness cites against. Every pack is addressed by content hash, scoped to a corridor and jurisdiction, and frozen at a known date. Filter by kind, corridor, jurisdiction, or status; pin by version.
Every pack the hub serves -- vetted or unvetted -- is pre-anonymized before storage. Clients pick what fits their use:
Packs a curator has signed off on (Stage 05 in the vetting process). The safe default for production deployments, NGO field workers, and platform-moderation use.
Download vetted ZIP →GET /api/hub/knowledge/download?vetted=true
Includes proposed / community-submitted packs. Status flags clearly
distinguish vetted from proposed / needs_review.
Pre-anonymized but not curator-approved. For researchers, integration partners,
and pre-release audits.
GET /api/hub/knowledge/download?vetted=false
Anonymization is enforced at the schema boundary (Stage 03) on ingest; the hub never stores raw worker identifiers. The download bundle ships JSON envelopes per KnowledgeObject v1.0 with status, version, and content_hash on every entry.
Every published pack with its corridor, version, and review status. Click a result to open its JSON envelope and pull instructions.
The manifest is the only thing a client needs to verify and pin a pack. Pack bodies are large; manifests are tiny and hash-addressed.
pack_idstringCorridor slug, e.g. qa-np.versiondateCalendar version. Once published, never edited.hashsha256Content hash of the pack body. Used to address the body in the CDN.reviewercurator-keyCurator key id that approved this manifest.sourcesURL[]Public source URLs whose extracted facts are inside the pack.compatible_withsemver-rangeHarness versions that can consume this pack.privacy_statusenumAlways public-source-only; refused otherwise.A pack is never edited in place. Corrections ship as new versions; old versions stay verifiable so historical answers stay reproducible.
A curator, partner, or research-monitor crawler finds a public document worth indexing.
Facts and citations are extracted into a draft pack diff. The original URL and source hash are recorded.
The diff is checked: no PII, no private case content, no scraped private channels. Reject otherwise.
A human curator reviews the diff. Approve, request changes, or reject with reason.
The proposed version runs through the regression suite. Failing rules block publication.
Manifest is approved with the curator key and published. CDN serves the new body.
Local and partner deployments pull the new manifest, verify the signature, and switch on success.
Resolve manifest, download body, verify signature against the curator public key. Mirror locally and pin in your runtime config.
# 1. resolve latest manifest for a corridor curl https://api.duecare-ai.com/packs/qa-np/latest # 2. pull the pack body by content hash curl -O https://cdn.duecare-ai.com/packs/sha256:9ab3… # 3. verify the curator signature duecare verify pack.json --key curator-1.pub