DAY 188 / 210

Safety Properties in Distributed Systems

This day launches the distsys-safety phase by establishing why safety guarantees matter for production AI tooling like StartupTribunal. It equips Maku to recognize and avoid violation patterns before implementing fault-tolerant services. The focus on definitions and misconceptions creates a shared vocabulary for the remaining week.

⏱ 45 min target📝 3 quiz Qs

Resources

readingraft.github.io
Raft Consensus Algorithm
Sections 1-3
30 min

Deliverable

Create a new journal entry file at journal/day-188-safety-properties.md with three concrete safety properties relevant to the maku brief pipeline.

Quiz · 3 questions

1. Which statement best distinguishes safety from liveness?

Safety properties can be violated temporarily while liveness cannotSafety properties assert that nothing bad ever happens; liveness asserts that something good eventually happensSafety is only relevant in synchronous networksLiveness properties are easier to prove formally than safety

2. Give one real-world example of a safety violation that could occur in a rate-limited API endpoint.

3. How might the current rate-limiter implementation in lib/rate-limiter.ts fail a safety property under concurrent access?

Journal

Time spent (minutes)

Blockers

Commit / PR links (one per line)