Abaqus Dependency Preflight Validator
Overview
Perform a static, read-only audit of cross-file contracts before Abaqus is started. Report mismatches with source locations and downstream consumers.
When to use
Use after a rename, configuration change, script split, output-path change, or failed lookup that may cross module boundaries.
Inputs
- Project root and intended entry point
- Configuration files and naming manifest
- Build-stage order and supported execution mode
- Expected job, input, and result artifacts
Outputs
Return a dependency table with producer, identifier, consumer, source location, status, severity, and a smallest-fix recommendation. Separate definite errors from warnings that require runtime evidence.
Workflow
- Inventory configuration, Python, input, and manifest files.
- Extract declared and consumed identifiers without executing project code.
- Compare repository names, paths, step order, and job/output relationships.
- Flag risky patterns such as positional repository assumptions, implicit working directories, and CPU/domain disagreement.
- Stop before edits and present the dependency chain.
Safety gates
- Do not import project modules when import has side effects.
- Do not open or alter model/result databases during static preflight.
- Do not guess that similar spellings identify the same region.
- Do not advance from warning to confirmed defect without evidence.
Example prompts
Preflight this multi-file project after
LINING_SURFACEwas renamed. Show every producer and consumer, including output extraction. Diagnose only.
Common failures
- Searching only Python while the authoritative value lives in configuration.
- Treating dictionary order as a stable repository contract.
- Checking job names without checking their expected result paths.
- Reporting matches without line-level provenance.
Acceptance checklist
- Every high-risk identifier has one identified producer.
- Every consumer resolves to the intended declaration.
- Step and artifact dependencies are ordered.
- Findings include file and line evidence.
- No project code or solver job ran during preflight.