Skip to content
← All modules

06

Who Signs

What happens when a human has to sign for what a machine proposed?

The applied case. Where the first five modules meet a domain that already has a written specification for what a valid signature requires.

6 lessons · 9 checks · 58 min

Why it sits here

Last because it needs all of it. The harness proposes, the workflow makes the wait durable, the compiled rule is what the agent invokes, the audit trail is what the signature emits. And it is the only module where the evidence will actively argue with your design instincts.

Lessons

  1. The contradiction at the centreThe industry has an answer to the signing problem. The best evidence says the answer makes reviewers worse.10m
  2. You are probably building the wrong layerThe only RCT in this space decomposes where the benefit comes from, and the split is not close.10m
  3. Your users are not the users in the literatureOne finding inverts a design assumption everything else rests on.8m
  4. What makes a review a controlAccounting already wrote the specification. Apply it and every shipped surface fails.10m
  5. The baseline runs backwardsWhat actually happens today when a human posts a wrong entry. The comparison everyone skips.8m
  6. The build orderEvidence-led rather than taste-led. Two of the five obvious design laws are contradicted.12m

Pre-reading

14 sources · ~7h if you read all of it

Ranked, not exhaustive. The lessons stand on their own, so treat the first tier as the genuinely load-bearing sources and the rest as depth when a lesson makes you want it.

Read properly