Answer principles round 1: 1 🔴, 7 🟡 (0 misread); every effect is handed in as an argument, no test patches a global, and the traces principle scopes tools that run on their user's machine
CI / tests (pull_request) Successful in 3m43s

This commit is contained in:
2026-11-19 12:42:03 +01:00
parent 8ca612b7a4
commit cb3135bc8c
124 changed files with 1437 additions and 793 deletions
+1
View File
@@ -101,6 +101,7 @@
- Two spellings that can disagree are a correctness bug, whatever the reason for having both: derive one from the other, or reject the combination.
* All critical flows should have good traces, from where something was initiated until it completed.
- Use traceparent OTLP and standardized logging for this.
- A tool that runs only on its user's own machine keeps its trace on that machine, as an archive of each run, and doesn't send anything to a collector.
* Prefer the vendor-neutral option, and know what leaving would cost.
- A supplier is a component like any other, so compose-not-entangle's test is the whole test.
- Where two options do the job, the one that ties us to no supplier wins by default — dependency, protocol, format, service, provider and storage alike. Choosing neutral is usually free; it is the leaving that is expensive, so the test is what an exit costs and whether anyone has priced it.