Skip to content

Latest commit

 

History

History
34 lines (27 loc) · 1.54 KB

AGENTS.md

File metadata and controls

34 lines (27 loc) · 1.54 KB

Aethermor Agent Guide

Mission: build a fast, physics-grounded reduced-order thermal and inverse-design tool for architecture-stage chip/package decisions.

Canonical path: physical power map -> FourierThermalTransport.solve_steady() -> typed SteadyStateResult -> package/inverse design/CLI/demo. Do not create a second flagship equation.

Commands:

python -m pytest -q
aethermor validate --json
aethermor demo --samples 30
python -m scripts.generate_validation_report
ruff check aethermor/physics/thermal.py aethermor/physics/cooling.py aethermor/physics/chip_floorplan.py aethermor/analysis/inverse_design.py aethermor/analysis/uncertainty.py aethermor/validation/engineering.py aethermor/demo.py aethermor/cli.py tests/verification examples/architecture_tradeoff.py

Scientific invariants:

  • never preserve a result at the expense of physics;
  • never call repository-authored validation independent;
  • all cross-material comparisons require shared device constraints;
  • all numerical results must be mesh-independent within a stated tolerance;
  • integrated input power must equal reported solved power;
  • unconverged results must never look successful;
  • package coupling must not double-count die resistance or cool impossible faces.

Use SI units and unit-bearing names at public boundaries. Every engineering datum needs source, condition, orientation/grade where relevant, uncertainty, and an honest provenance status. Public claims must map to docs/CLAIM_EVIDENCE_MATRIX.md; stale numerical claims are removed, not protected as compatibility behavior.