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_SURFACE was 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
1---2name: abaqus-dependency-preflight-validator3description: Use when an Abaqus scripting project spans multiple files and model, part, instance, region, step, job, output, or ODB identifiers may have drifted before execution.4---56# Abaqus Dependency Preflight Validator78## Overview910Perform a static, read-only audit of cross-file contracts before Abaqus is11started. Report mismatches with source locations and downstream consumers.1213## When to use1415Use after a rename, configuration change, script split, output-path change, or16failed lookup that may cross module boundaries.1718## Inputs1920- Project root and intended entry point21- Configuration files and naming manifest22- Build-stage order and supported execution mode23- Expected job, input, and result artifacts2425## Outputs2627Return a dependency table with producer, identifier, consumer, source location,28status, severity, and a smallest-fix recommendation. Separate definite errors29from warnings that require runtime evidence.3031## Workflow32331. Inventory configuration, Python, input, and manifest files.342. Extract declared and consumed identifiers without executing project code.353. Compare repository names, paths, step order, and job/output relationships.364. Flag risky patterns such as positional repository assumptions, implicit37 working directories, and CPU/domain disagreement.385. Stop before edits and present the dependency chain.3940## Safety gates4142- Do not import project modules when import has side effects.43- Do not open or alter model/result databases during static preflight.44- Do not guess that similar spellings identify the same region.45- Do not advance from warning to confirmed defect without evidence.4647## Example prompts4849> Preflight this multi-file project after `LINING_SURFACE` was renamed. Show50> every producer and consumer, including output extraction. Diagnose only.5152## Common failures5354- Searching only Python while the authoritative value lives in configuration.55- Treating dictionary order as a stable repository contract.56- Checking job names without checking their expected result paths.57- Reporting matches without line-level provenance.5859## Acceptance checklist6061- [ ] Every high-risk identifier has one identified producer.62- [ ] Every consumer resolves to the intended declaration.63- [ ] Step and artifact dependencies are ordered.64- [ ] Findings include file and line evidence.65- [ ] No project code or solver job ran during preflight.66
1348109517