Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-20 17:39:03 UTC · snapshot created 2026-11-20 17:39:53 UTC · last check 2026-11-20 19:55:51 UTC

SIE.9:3 - Forces

ForceTension
MinimalityA small interface is easier to use and maintain, while hiding source, loss, or failure makes it unsafe.
Receiving the resultThe receiver needs to interpret the result and be able to return a disputed premise for review. A programmatic interface needs a stable schema, stable branch codes and a return path the caller can follow. A human-readable interface needs to explain the branch and show where to raise the question.
AbstractionReceiver-friendly names reduce burden, while source identifiers and meanings must remain recoverable.
PerformanceRich provenance and alternative claims cost bandwidth and attention, while omitted trace defeats challenge and validation.
SecurityThe receiver needs enough source information to rely, while disclosure can violate provider, privacy, or protection conditions.
EvolutionStable interface promises aid use, while source or mapping changes must not be hidden behind unchanged field names.