Library / Systems 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:35:10 UTC

SYSE.26:11 - SoTA-Echoing

For the question “How should an internal platform let users obtain a usable result?”, adapt the task-oriented, minimum-use-path and clear-feedback line in DORA Platform engineering. It changes sections 4.1–4.3: begin with the task and expose its outcome, instead of selecting a portal or measuring submitted jobs. The trade-off is more deliberate exception design for less user-side diagnosis. DORA’s software findings do not demonstrate the physical-bench result.

Adopt the thin-interface-over-actual-providers alternative in the CNCF Platforms White Paper, where it supplies the same user result. Compared with rebuilding every provider capability, it avoids unnecessary implementation while retaining the support and compatibility burden. Compared with a bare collection of links, section 4.4 keeps an actionable failed-use return. The selected interface may still be manual; no centralization or portal preference follows.

Reopen the comparison when representative users cannot recover from a supported failure, a legitimate variant repeatedly bypasses the path, or a different interface supplies the same bounded result with less total user and provider effort.