Journals DNA
Your AI cannot skip your journal.
Journals DNA gives every project one markdown journal (<PROJECT>_JOURNAL.md) that your AI reads before it acts and
writes to while it works. The next session, or another AI, picks up exactly where the last one stopped, and you can
share your work with anyone by sending the journal.
It runs on your machine. Your journals stay where they are, in plain markdown.
New in 1.6.0
- A rules pack that is on by default, with no setup and no AI cost. It stops once (the same call again passes):
a secret written into a file or a commit, deletes that wipe a drive, your home or a whole project, losing unsaved
git work (
git reset --hard and the like, only when there is work to lose), DROP / TRUNCATE / DELETE
without WHERE, a force push to main, overwriting your .env or key files. It waits for a yes in your latest
message before publishing to production, spending money, or messaging customers and posting. Settings:
JOURNAL_DEFAULT_RULES=off, JOURNAL_DEFAULT_RULES_OFF=<rule,rule>, JOURNAL_MAIN_BRANCHES, and your own
~/.journal/yes_patterns.txt.
- Three questions make it yours. After the install your AI asks what costs you money, what must never go out
without your yes, and your production branch and deploy command, and writes the answers as exact patterns
(
starter_rules_interview.md).
- The journal brief on the first touch of any file in a project that has a journal, no Brain map needed: the
first folder above the file (up to your journal root) that holds 1 to 5
*_JOURNAL.md files is its project.
- A running service or timer is never taken as proof: the mod shows its newest incident or pause entry and says
to check its log first.
- BETA adapters for Codex, GitHub Copilot and Cursor (
mod-adapters/): the same journal brief through each app's
hooks. Codex tested live; GitHub Copilot and Cursor tested with recorded hook payloads. In these apps the journals
gate only delivers the brief; the other stops stay stops.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
