Keep DOX usable before local memory initialization

[TerminallyLazy]

Clarify that the managed memory preflight applies when the generated local guidance exists. Clean checkouts without .tree-ring continue using the tracked DOX hierarchy and treat memory as inactive; initialization still requires an authorized setup task. The managed reference block remains byte-identical, preserving its activation fingerprint.

Validation: the root DOX contract remains complete without a local store; the marked block is unchanged; diff checks pass. No runtime behavior changes.

High-level PR Summary

This PR adds a clarifying note to the AGENTS.md documentation to explain that the memory preflight instructions only apply when generated local Tree Ring files exist in .tree-ring/. On clean checkouts without these generated files, the system should treat memory as inactive and use the tracked repository contract instead, ensuring the DOX hierarchy remains usable before local memory initialization.

⏱️ Estimated Review Time: 5-15 minutes

💡 Review Order Suggestion

Order	File Path
1	AGENTS.md

[coderabbitai]

Warning

Review limit reached

Next included review available in 46 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 4abf2230-d1ed-4eb8-b265-5ec66320650f

📥 Commits

Reviewing files that changed from the base of the PR and between db98ef2 and 307edf3.

📒 Files selected for processing (1)

• AGENTS.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can reply 'qodo' on any finding to push back, ask questions, or dig deeper

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

PR Summary by Qodo

Clarify DOX behavior before local memory initialization

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Clarifies memory preflight only applies when generated local guidance exists.
• Keeps clean-checkout work guided by tracked DOX while memory remains inactive.
• Requires explicit authorization before initializing missing local memory files.

Diagram

graph TD
  A["Repository work"] --> B{"Local guidance exists?"} -->|Yes| C["Memory preflight"] --> D["Substantive work"]
  B -->|No| E["Memory inactive"] --> F["Tracked DOX"] --> D
  E -->|Authorized setup| G["Initialize memory"]

Loading

High-Level Assessment

The chosen placement immediately after the managed reference block is optimal: it clarifies clean-checkout behavior without modifying the byte-sensitive activation fingerprint. Embedding the clarification inside the managed block was considered but would unnecessarily alter that fingerprint.

Files changed (1) +6 / -0

Documentation (1) +6 / -0

AGENTS.mdClarify clean-checkout DOX and memory behavior +6/-0

Clarify clean-checkout DOX and memory behavior

• Documents that the memory preflight applies only when generated '.tree-ring' guidance exists. Clean checkouts continue under the tracked DOX hierarchy with memory inactive, and initialization remains limited to authorized setup tasks.

AGENTS.md