delaunay AGENTS.md

AGENTS.md

Essential guidance for AI assistants working in this repository.

This file is the entry point for all coding agents. It should stay short enough to load and remember. Detailed operational rules are indexed in docs/dev/README.md; focused architecture references are indexed from docs/code_organization.md.

---

Contents

• Required Reading
• Non-Negotiable Rules
• Project Context
• Design Priority
• Scientific Invariants
  • Numerical Correctness
  • Topological Correctness
  • Validation Layers
  • Symbolic Perturbation
• Design Principles
• Where Detailed Rules Live
• Agent Expectations

---

Required Reading

Before modifying repository files, agents MUST read:

• AGENTS.md (this file)
• docs/dev/README.md - development guidance index; read each focused document whose ownership row matches the files or workflows the task touches
• docs/code_organization.md - short architecture hub; follow its focused links when touching module layout, public namespace, preludes, or file organization

docs/dev/README.md explains which focused document owns each development workflow. Agents must read the task-relevant focused documents completely before making changes and load additional owners if the task expands. Cross-cutting changes must follow every applicable owner; unrelated development histories and workflow references do not need to be loaded preemptively.

Non-Negotiable Rules

• Do not mutate version-control state unless the maintainer explicitly asks. Never run git commit, git push, git tag, or ref/index-mutating Git commands by default. Use git --no-pager for read-only Git commands. Detailed Git/GitHub rules live in docs/dev/git.md.
• Use patch editing for manual edits. Never use sed, awk, perl, or Python to modify code. Shell text tools are fine for read-only analysis.
• Do not revert user changes. The worktree may be dirty; preserve unrelated changes and work with any overlapping edits.
• Unsafe Rust is forbidden. The crate enforces #![forbid(unsafe_code)].
• Validate with the right command. Core Rust changes require final just ci. Documentation, configuration, Python, notebook, Rust unit-test-only, doctest-only, integration-test-only, benchmark-only, and example-only changes use the matching focused validators from docs/dev/commands.md; compose those validators once each when multiple focused surfaces changed.
• Find local MacTeX tools before declaring them missing. On macOS, prepend /Library/TeX/texbin to PATH when commands such as chktex are not visible to a non-interactive shell; see docs/dev/commands.md.
• Do not edit generated changelogs manually. Changelog and documentation maintenance rules live in docs/dev/docs.md.
• Treat paper prose as author-owned. Agents must not add substantive publication prose to papers/; local paper maintenance rules live in docs/dev/docs.md.
• Keep notebook execution deliberate. just notebook-check is lint-only. The canonical macOS leg of just ci may execute the validation notebook only to compare regenerated figures with tracked artifacts; it must not publish them. Execute other notebooks only when the task requires it, and refresh tracked notebook artifacts only through named recipes when the task includes that refresh. Every cell must have a unique, stable, descriptive lowercase kebab-case ID. Detailed policy lives in docs/dev/notebooks.md.
• Keep README and citation prose mirrored. The first paragraph under README.md's Introduction is mirrored by the abstract field in CITATION.cff; update both together. The invariant is checked by scripts/tests/test_readme_citation_mirror.py.