The .ini format is so simple, so archaic, that it feels like carving runes into a stone tablet. That is exactly the point. Your reasoning should be permanent. Your logic should be legacy.
[oracles] ; The prophecies spoken by the linter we chose to ignore. #101 = "Disabled rule @typescript-eslint/no-explicit-any because the vendor API is a lie." #204 = "Sleep(500) added here. Do not remove. The upstream webhook needs to breathe."
The compiler doesn't care about your soul. But codex.ini does. Did you actually create a codex.ini ? Tag me in your repo. Let’s start a movement of documented memory over clever code. codex.ini
; codex.ini ; The Book of Truth for Project Phoenix ; Last Ritual: 2024-05-21 [genesis] author = "Alex Chen" date = "2023-11-01" license = "MIT" mission = "To reduce report generation time from 45 seconds to under 2."
Philosophically? It is the most important file you will ever write. Your logic should be legacy
You can’t put that in a README . It belongs in the codex.ini . Technically? It doesn’t exist. There is no official codex.ini specification from Microsoft, Linux, or any RFC.
So go ahead. Open your project root. Write [genesis] . Write down why you started. Do not remove
[sacrifices] ; We chose SQLite over Postgres for deployment simplicity. ; We know this breaks at 10k concurrent users. We accept this fate. timestamp_accuracy = "Lost 10ms precision for 40% speed gain" ui_framework = "Vanilla JS. No React. We choose pain."