---
name: fesa-reference-onboarding
description: Onboard or review Abaqus reference artifacts for FESA verification without running Abaqus locally.
---

# FESA Reference Onboarding

Use this skill when the user adds, asks about, or wants to validate stored reference models and results.

## Read First

- `/AGENTS.md`
- `/PROGRESS.md`
- `/PLAN.md`
- `/docs/VERIFICATION_PLAN.md`
- `/docs/RESULTS_SCHEMA.md`
- `/docs/ABAQUS_INPUT_SUBSET.md`
- `/docs/NUMERICAL_CONVENTIONS.md`

## Artifact Checklist

- Abaqus `.inp` input file.
- Solved reference values, initially Abaqus-exported `*_displacements.csv`.
- Tolerance metadata by result field where needed.
- Unit notes, because FESA does not enforce a unit system.
- Abaqus version/provenance when available.
- Step/frame/result field mapping that matches `/docs/RESULTS_SCHEMA.md`.
- Unsupported keywords documented against `/docs/ABAQUS_INPUT_SUBSET.md`.

## Workflow

1. Inspect `references/` when present.
2. Verify that each artifact can be compared without hidden coordinate, sign, unit, or precision assumptions.
3. For `*_displacements.csv`, verify required columns: `Node Label`, `U-U1`, `U-U2`, `U-U3`, `UR-UR1`, `UR-UR2`, `UR-UR3`.
4. Check that `U` and `RF` expectations are clear; flag missing reaction artifacts and optional `S`, `E`, and `SF` ambiguity.
5. Record completed artifact onboarding in `PROGRESS.md` and remaining artifact tasks in `PLAN.md`.

## Do Not

- Do not run Abaqus.
- Do not alter numerical tolerances just to make comparisons pass.