A video game where you play as a misaligned AI, deceiving and building power. An experiment in spec-driven development. forked from cameron.stream/misaligned

2026-07-05-bevy-sim-port.md
2026-07-05-bevy-visual-fixes.md
2026-07-05-constitution-and-knowledge.md
2026-07-05-continuous-simulation.md
2026-07-05-demolition.md
2026-07-05-misaligned-design-session.md
2026-07-05-pixel-art-pipeline.md
2026-07-06-b1-basement-slice.md
2026-07-06-core-scope-split.md
2026-07-06-cursor-and-senses.md
2026-07-06-flow-law.md
2026-07-06-intel-record-and-process.md
2026-07-06-people-panel.md
2026-07-06-roadmap-consistency.md
2026-07-06-schedules.md
2026-07-06-spec-horizon.md
2026-07-06-terminal-first-class.md
2026-07-07-agent-play.md
README.md
README.md

Devlogs #

Development notes, one file per working session or theme, named YYYY-MM-DD-topic.md. (There is also a root-level DEVLOG.md with short reverse-chronological entries; that's the quick factual ledger, these are the longer session writeups.) These are the informal record: what was done, what was decided and why, what broke, what's bugging us. The formal design record lives in DESIGN.md (vision, pillars, decisions log); devlogs are allowed to be messy and opinionated.

When you finish a meaningful chunk of work, add an entry. Future-you reads these to remember why the code looks the way it does.