claim candidate goes to: this-edition V villager
Security experience is what lets you ship with known gaps: list them, match them to the reader, say what would change the call
A design with no server has gaps, and the honest thing is to write them down: a reader can edit a balance, start again in a private window, credit themselves; every one changes a number only the cheater sees. Closing them would bring back accounts, a database, a server and a sign-up wall. Security judgement is asking who you are protecting against, accepting what does not match the threat, and naming the condition that would make the gaps unacceptable.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Note. The synthetic readers found no security problem but found the cost of the gaps in the words on the page ('below zero' read as a debt).
Where it comes from
- No server, by design Security as a business tool (newsroom)
- Who are you protecting against? Draw the security line where the attacker is, not above it the question (newsroom)
What it answers in the 2018 book
- Threat Modeling answered outline, Security
- Security creates better developers answered outline, Security
Where it goes
Chapter Controlling your agent: RiskMandate, part Build it without a server (drafting); topic Security for the agent era: least code, supply chain, secrets, learning to hack.
Other ideas proposed for the same chapter: Mandate, reach and the gap: hope versus enforcement, Code is a liability; the future is the smallest code that does the job, Learning to hack is still how you learn how things work: draw the line where the attacker is, The secret goes from the drop into the tool, never into the chat.
Node idea:security-as-a-business-tool in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.