~/404human

$ whoami

hey, I break things.

Then I fix them, and write down what I learned. Mostly Rust: runtimes, background jobs, AI tools. All in public, mistakes included.

$ tail -1 build.log

Colophon · P3 · 3.5 The Studio, designed

Status

• colophon A Rust + Svelte CMS that can prove what it published, designed in the open and built one proven milestone at a time. P3 · 3.5 · 251 tests
• service-monitor A Rust uptime monitor that tells the truth, built one tested checkpoint at a time. M2 · 2.8 · 441 tests
• rust-knowledge-base Claude Code studying the whole Rust Book, checked by exams the AI can’t see. final exam 59/59
• writing Every experiment written up here, including the parts that didn’t work. 49 write-ups

Build log

Colophon in progress 26 entries

Latest · P3 · 3.5: The Studio, designed

1. D design 2 entries
2. P0 foundation 7 entries
3. P1 never lose an edit 8 entries
4. P2 publish exactly once 4 entries
5. P3 prove it reached the site 5 entries
6. R roles you define next
7. M content you can shape next
8. P4 time travel next
9. E editorial parity next
10. DX developer parity next
11. P5 safe automation next
12. P6 running on its own next

0.13.5

• 3.5
  The Studio, designed
• 3.4
  A site built from one release
• 3.3
  A receipt for every publish
• All 26 entries, by milestone →

Service Monitor in progress 20 entries

Latest · M2 · 2.8: Telling certificate problems apart

1. M0 one check 8 entries
2. M1 checking on repeat 4 entries
3. M2 remembering 8 entries
4. M3 alerts next
5. M4 a real dashboard next
6. M5 running on its own next

0.12.8

• 2.8
  Telling certificate problems apart
• 2.7
  Disk limits and backups
• 2.6
  Keeping a week, summing up the rest
• All 20 entries, by milestone →

Projects

• 2026
  Colophon CMS in progress

  A content management system that can prove what it published and survives being killed at any moment. Rust and Svelte, open source, every step logged here.

• 2026
  Service Monitor in progress

  Keeps an eye on your websites and tells you, honestly, when something breaks. Written in Rust, built in the open, one tested step at a time.

• 2026
  Teaching an AI Rust write-up

  Claude studied the entire Rust Book, then took hidden-test exams with no compiler. 59/59 on a final test full of decoys.

• 2026
  This site live

  This portfolio and build log: built with Zola, drawn like a small control room, with real numbers from the posts. No tracking.

Writing

• 2026-10-26
  Five lessons from PHP2Shell, PingCAP, Railway and the AGENTS.md hijack

  A bitcoin dare, PHP2Shell, the PingCAP breach, Railway's leaked secrets and the AGENTS.md hijack: five lessons from one bad week, checked against the CMS I'm building.

• 2026-10-25
  What I'm building at Akira Shirase OSS, and the cycle every step goes through

  A CMS that can prove what it published, an uptime monitor that never fakes a green light, and one loop for every step: plan, build, prove, write it up, ship.

• 2026-10-14 experiment
  I made an AI read the entire Rust Book. Then I tried to make it fail.

  It passed. But the most interesting part was the one bug it did write.

Contact

• x
  @akirashiraseoss
• github
  akira-shirase-oss