Abaqus Shared Naming Manifest Builder
Overview
Create a small, stable manifest that separates semantic roles from literal
Abaqus repository keys. A name change should occur once and be detected before
runtime if any consumer remains stale.
When to use
Use when identifiers cross files, stages, or post-processing scripts. Skip it
for a disposable single-file exploration with no reused output.
Inputs
- Inventory of declared models, parts, instances, regions, steps, jobs, and outputs
- Semantic purpose of every shared identifier
- Configuration format already used by the project
- Compatibility aliases that must remain temporarily readable
Outputs
Produce a human-readable manifest, a language-level access layer, and a report
of duplicate literals or unresolved aliases.
Workflow
- Group names by model, geometry, regions, analysis, jobs, and artifacts.
- Assign semantic keys such as
excavation_surface, not numbered placeholders.
- Preserve Abaqus spelling and case in manifest values.
- Replace consumers incrementally and run preflight after each group.
- Remove an alias only after searches and tests find no consumer.
Safety gates
- Do not rename live repository objects as a side effect of building the manifest.
- Do not merge two regions because their names look similar.
- Do not store machine-specific absolute paths in the manifest.
- Keep configuration values separate from engineering evidence.
Example prompts
Build a YAML-neutral naming manifest for the model, soil part, lining
instance, excavation sets, analysis steps, job, and ODB. Report duplicate
literals but do not edit the Abaqus model.
Common failures
- A manifest mirrors file structure instead of semantic ownership.
- Output scripts keep hidden string literals.
- Aliases have no removal criterion.
- Case changes silently break repository lookup.
Acceptance checklist
1---2name: abaqus-shared-naming-manifest-builder3description: Use when multiple Abaqus scripts or configurations repeat model, part, instance, set, surface, step, job, or result identifiers and require one authoritative naming contract.4---56# Abaqus Shared Naming Manifest Builder78## Overview910Create a small, stable manifest that separates semantic roles from literal11Abaqus repository keys. A name change should occur once and be detected before12runtime if any consumer remains stale.1314## When to use1516Use when identifiers cross files, stages, or post-processing scripts. Skip it17for a disposable single-file exploration with no reused output.1819## Inputs2021- Inventory of declared models, parts, instances, regions, steps, jobs, and outputs22- Semantic purpose of every shared identifier23- Configuration format already used by the project24- Compatibility aliases that must remain temporarily readable2526## Outputs2728Produce a human-readable manifest, a language-level access layer, and a report29of duplicate literals or unresolved aliases.3031## Workflow32331. Group names by model, geometry, regions, analysis, jobs, and artifacts.342. Assign semantic keys such as `excavation_surface`, not numbered placeholders.353. Preserve Abaqus spelling and case in manifest values.364. Replace consumers incrementally and run preflight after each group.375. Remove an alias only after searches and tests find no consumer.3839## Safety gates4041- Do not rename live repository objects as a side effect of building the manifest.42- Do not merge two regions because their names look similar.43- Do not store machine-specific absolute paths in the manifest.44- Keep configuration values separate from engineering evidence.4546## Example prompts4748> Build a YAML-neutral naming manifest for the model, soil part, lining49> instance, excavation sets, analysis steps, job, and ODB. Report duplicate50> literals but do not edit the Abaqus model.5152## Common failures5354- A manifest mirrors file structure instead of semantic ownership.55- Output scripts keep hidden string literals.56- Aliases have no removal criterion.57- Case changes silently break repository lookup.5859## Acceptance checklist6061- [ ] Each shared identifier has one semantic key and one owner.62- [ ] Literal values preserve required case.63- [ ] Consumers access the manifest rather than repeat strings.64- [ ] Compatibility aliases are documented and tested.65- [ ] No local machine path is part of the naming contract.
1348109517