Story How it works Tests Insights Whitepaper What's next Download Author Contact
← Back to Download

Update EIDARA: v1.0 → v2.0

~5 minutes · Low risk · Your VAULT data is untouched

Let your AI handle the upgrade

Download this file, give it to your AI (Claude, GPT, DeepSeek…) and it will migrate you to v2.0 automatically. Your data stays safe.

Download UPDATE-V1-TO-V2.md ↓

Or follow the manual steps below.

What's new in v2.0

Six defense-in-depth improvements that turn DARA from "good if you actively maintain it" to "self-correcting if you ignore it for weeks."

1. Librarian self-trigger. Every read of BRAIN.md now shows the Librarian status in the header. Alert threshold tightened from 7 days to 3. The post-compile status report (W6) must include Librarian status and prompt you if overdue.

2. Missing-summary auto-push. When compile detects neurons >1500 chars without a →brain: summary, it auto-writes a feedback file to INBOX. The header shows a to-do count. W6 also reports and prompts.

3. Session-closing summaries capped. W9 closing recaps must be ≤500 words per neuron. Longer recaps go to a dedicated session neuron. Compile emits a WARNING when any single neuron grows ≥50% in one pass.

4. Sandbox/FUSE stale-view caveat. W12 now includes: when working in sandboxed environments, files can appear truncated due to stale caches. Cross-verify before any restore.

5. W3(b) integrity check. New compile step tracks sizes of 5 protected files. Any size drop ≥50 bytes without justification fires a CRITICAL alert with a rollback pointer.

6. Cowork environment detection. compile.py detects Cowork/sandboxed runs and skips the git auto-commit step cleanly instead of erroring.

7. Anti-tampering. If .librarian-last-run says "today" but no [Librarian] entry exists in today's changelog, compile flags it as suspicious.

8. Librarian MISSION section. The Librarian protocol now opens with an explicit mission: format checking is necessary but not sufficient.

9. Arrow auto-fix extended. validators.py now auto-converts ->brain: and ->detail: to Unicode arrows.

What's NOT changed

Your data. None of your VAULT content is touched. The upgrade only replaces 5 system files:

  • DARA.md (the constitution)
  • SYSTEM/compile.py + SYSTEM/validators.py
  • VAULT/ENABLERS/agent-librarian.md
  • SYSTEM/config.json (version bump only)

Your NEURONS, changelog, BRAIN.md, BACKUP, and all other ENABLERS are preserved as-is.

How to upgrade

1

Backup your current DARA

Open PowerShell (Windows) or Terminal (Mac/Linux):

cd C:\Users\YourName\Desktop
Copy-Item -Recurse -Path DARA -Destination "DARA_v1_backup_$(Get-Date -Format yyyy-MM-dd)"

Mac/Linux: cp -r ~/Desktop/DARA ~/Desktop/DARA_v1_backup_$(date +%Y-%m-%d)

2

Download the v2.0 package

Download EIDARA v2.0 from GitHub.

3

Replace the 5 system files

From the v2.0 package, copy these into your existing DARA folder, overwriting the v1 versions:

  • DARA.md
  • SYSTEM/compile.py
  • SYSTEM/validators.py
  • SYSTEM/config.json
  • VAULT/ENABLERS/agent-librarian.md
Do NOT touch anything else. Your NEURONS, your changelog, your BRAIN.md — all stay.
4

Verify

Run python SYSTEM/compile.py once. You should see:

  • BRAIN.md compiled! at the end
  • Compiler version: 3.2 in the COMPILATION STATS
  • The BRAIN header now showing a Librarian: line

Open LIBRARY/BRAIN.md and check the header has the new Librarian line. You're on v2.0.

First-time observations

Librarian: never run in the header is expected on first compile. If you've been running the Librarian, update VAULT/.librarian-last-run with today's date and add a [Librarian] entry to today's changelog.

.w3b_sizes.json is created automatically, capturing baseline sizes of the 5 protected files.

ASCII arrow auto-fix: if you had ->brain: instead of the Unicode arrow, the validator will fix it on the next compile.

Missing-summary push: if you have neurons >1500 chars without a summary, the next compile will show them in the header and auto-write a feedback file to INBOX.

Troubleshooting

Q: "librarian timestamp SUSPICIOUS" — what does it mean?

The compile noticed .librarian-last-run is set to today but there's no [Librarian] entry in today's changelog. Either add one or investigate what touched the file.

Q: CRITICAL alert about W3(b) integrity failure.

One of the 5 protected files dropped in size unexpectedly. Most likely an Edit-tool truncation. Roll back from VAULT/BACKUP/SYSTEM/.

Q: How do I rollback to v1?

Replace the 5 upgraded files with their v1 versions from your backup. Delete SYSTEM/.w3b_sizes.json. Recompile.

Q: Will v2 break my existing scripts/agents/MCPs?

No. The reading interface (BRAIN.md, INDEX, summaries) is backward-compatible. New lines are additive.


Go to Download page →