Skip to content

Latest commit

 

History

History
23 lines (17 loc) · 2.13 KB

AGENTS.md

File metadata and controls

23 lines (17 loc) · 2.13 KB

Agent instructions

Task tracking

  • Read TASK_RULES.md when assessing or resuming a task. Automatically create or reuse a canonical record for substantial tasks according to its recovery criteria, and maintain it at meaningful checkpoints.
  • Read the task index and matching record when present. Use an explicitly supplied canonical record instead of duplicating it; keep repository-owned tracking suitable for public independent use.
  • Clarify consequential scope or visibility uncertainty while continuing independent work. Routine record creation does not require separate permission.

Specifications

  • Before changing behavior, read this repository's specifications.md if it exists and the relevant documentation. If it is missing, use existing code and documentation and report consequential uncertainty; do not invent requirements.
  • Keep requirements and architectural contracts in the specification, and working instructions in this file.
  • Update the specification when an authorized change affects documented behavior, public interfaces, compatibility guarantees, or significant design decisions.
  • Keep documentation and development instructions self-contained for an independent checkout. Do not reference private consuming repositories or require access to their specifications or infrastructure.

Changes and validation

  • Preserve unrelated local changes and generated artifacts. Follow existing conventions and keep changes scoped to the task.
  • Consider model semantics, numerical behavior, solver capabilities, options, suffixes, and result mapping when changing solver interfaces or transformations.
  • Use this repository's build and test configuration. Run relevant unit, regression, and end-to-end checks for the affected behavior; a consuming project's build does not establish that component tests passed.
  • Add regression coverage for substantive correctness changes when practical. Do not assume that all solver SDKs or licenses are available.
  • Report what changed, what was checked, and any validation limitations.
  • Keep credentials, confidential models, and private consumer details out of documentation and test fixtures.