Canary Path

A canary's Path is its committed delivery plan: where it enters, the effect token it carries, the devices it is expected to cross, the Effect Point where its effect lands, the level it targets, and its cadence.

ProofJack Rating: Human 100% · AI 0% (self-estimated; PP-SPEC-077 AI_DISCLOSURE: three axes listed as human)

Also known as: Path, ingress, route, cadence, trickle, clutch

Mynted 2026-10-23 · Updated 2026-10-23

First used: PP-SPEC-077, ProofSwarm: The Dead Canary Protocol, October 2026, by Craig Thomas Ellrod

The fields

Field	Meaning
`ingress`	The release point where the Ingress Observer records delivery.
`effect_token`	The canary’s unique effect token, visible at the Effect Point.
`route`	The ordered list of devices under test the canary is expected to cross.
`effect_point`	Where the canary’s effect lands if nothing stops it. See Effect Point.
`target`	The level (`sut`, `dut` or `cut`) and identifier the canary tests.
`cadence`	`full` for a scheduled or triggered run, `trickle` for continuous low-volume release.
`clutch`	In Production Stream Mode, the epoch batch the canary belongs to.

The rules

Path is fixed in the commitment and never changes.
A canary observed at an Effect Point other than its committed one is not that canary. The observation is a Wild Canary.
Cadence is a Path field, not a Color. A trickle canary is still White, Gray, Red, Black or Gold.

Related terms

Sources

ProofSwarm: The Dead Canary Protocol (PP-SPEC-077)

Updated 2026-10-23