Infrastructure & systems
PartialRuntime behaviour
What an observed run cost (amplification vs budget) and how far a corruption propagated, derived from that run’s sensor telemetry.
Family facts
- Code
- FAM-RUNTIME
- Status
- beta — code maturity
- Availability
- partial — whether it is offerable
- Ingest
- observed — how a target enters
- Rules of Engagement
- Not required
- Kind
- Family (a selectable assessment)
What it decides
What a run actually did — its resource amplification and the propagation of a corruption — as seen in the telemetry it produced.
How it works
It normalizes a run’s telemetry export into a runtime trace and reasons over it: how much a request amplified against its budget, and how far a tainted value propagated.
Absent or malformed telemetry yields UNKNOWN rather than a guess, and only one telemetry format is wired today.
Declared limits
A single telemetry format is wired; other formats and a live privileged sensor are out of scope — the sensor reads an alert stream that no ingest mode produces today.
References
References point to public, well-known technical sources for further study.
Related articles