Repository navigation
Conversation
Root AGENTS.md, the governance document, and the Copilot/CodeRabbit review configuration now recognize an optional AGENTS.md inside each source/source_xxx/ module directory. Module-level files refine the root baseline and never override it. Add source/source_esolver/AGENTS.md as the first such file: it states the esolver cockpit-dashboard constraint and two checkable rules -- orchestrate the algorithm flow only, and reuse the shared cross-solver naming. .coderabbit.yaml loads nested AGENTS.md through a new "**/AGENTS.md" knowledge-base pattern.
mohanchen
added
Machine Learning & AI
|
@ABACUS-PR-BOT please review the PR |
ABACUS-PR-BOT
left a comment
ABACUS-PR-BOT
left a comment
There was a problem hiding this comment.
Static review of b7af2921: no blocking issues found in this docs/config-only change. git diff --check passed; the governance checker pinned at e9d04303 reported one metadata warning and no errors. No builds or runtime tests were run; CI status was unavailable through the required connector.
Non-blocking: Please fill the verification section with the static commands/results actually run and a docs/config-only reason for skipping runtime tests, add the issue or no-issue rationale, and replace the remaining template placeholders. The opening prose already describes the change.
Address the review note on PR deepmodeling#8148: the owning-module examples now use the directory names registered in source/CMakeLists.txt (source_estate, source_hamilt) instead of the legacy module_elecstate/module_hamilt names, so the guidance is directly searchable. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
| 1. `esolver` functions only orchestrate the algorithm flow (e.g., SCF | ||
| iteration, relaxation steps). Any computation of a concrete physical |
There was a problem hiding this comment.
Should "relaxation steps" be listed as an ESolver responsibility here? The outer relaxation loop currently lives in Relax_Driver::relax_driver(), which calls ESolver's runner() through esolve() for each ionic step🤔
This branch has not been deployed
3 participants
Root AGENTS.md, the governance document, and the Copilot/CodeRabbit review configuration now recognize an optional AGENTS.md inside each source/source_xxx/ module directory. Module-level files refine the root baseline and never override it.
Add source/source_esolver/AGENTS.md as the first such file: it states the esolver cockpit-dashboard constraint and two checkable rules -- orchestrate the algorithm flow only, and reuse the shared cross-solver naming.
.coderabbit.yaml loads nested AGENTS.md through a new "**/AGENTS.md" knowledge-base pattern.
Reminder
AGENTS.mdanddocs/developers_guide/agent_governance.md.source/changes.Linked Issue
Fix #
Unit Tests and/or Case Tests for my changes
What's changed?
Governance Notes