Skip to main content

Future-worker API

Evidence and rights contracts

These rules are designed for future autonomous workers as much as for readers. Domain systems may be stricter; the platform layer must not weaken them.

1 · Source identity

Normalize the locator for deduplication, but never discard a native source ID. Aliases are provenance.

2 · Claim evidence

Claims may be verified, bounded, unknown, blocked, conflicting or scope-warning. Unknown is a valid state.

3 · Freshness

A recorded access/verification date is not automatically “current.” Currentness belongs to a domain policy tied to exact identity and field scope.

4 · Rights

Imported rights labels remain raw assertions. New media reuse stays review-required unless an owning system has an explicit accepted decision.

5 · Media provenance

Documentary media, generated illustration, reconstruction and interface art are separate classes. One must never silently substitute for another.

6 · Publication eligibility

Rights, evidence, freshness and identity holds are inputs to publication. Workers must not resolve them from memory.

Machine-readable endpoints

PurposePath
Pointer/data/evidence/current.json → platform_fabric
Manifest/data/evidence/icu-megaprogram-003-r000072/manifest.json
Source registry/data/evidence/icu-megaprogram-003-r000072/source-registry.json
Route profiles/data/evidence/icu-megaprogram-003-r000072/route-profiles.json
Review queue/data/evidence/icu-megaprogram-003-r000072/review-queue.json
Contract/data/evidence/icu-megaprogram-003-r000072/contracts.json