Library / Semantic Integration Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:40:20 UTC

SIE.9:3 - Forces

ForceTension
MinimalityA small interface is easier to use and maintain, while hiding source, loss, or failure makes it unsafe.
Human and machine useMachines need stable schemas and branch codes; people need interpretations and challenge paths.
AbstractionReceiver-friendly names reduce burden, while source identifiers and exact 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.