docs: make reference metadata optional
This commit is contained in:
@@ -25,7 +25,7 @@ Hard boundaries:
|
||||
- Do not change tolerance policies.
|
||||
- Do not run Abaqus, Nastran, or any reference solver.
|
||||
- Do not generate or modify Abaqus reference CSV files.
|
||||
- Do not modify model.inp, metadata.json, <model-id>_displacements.csv, <model-id>_reactions.csv, <model-id>_internalforces.csv, <model-id>_stresses.csv, or any stored reference artifact.
|
||||
- Do not modify model.inp, any present metadata.json, <model-id>_displacements.csv, <model-id>_reactions.csv, <model-id>_internalforces.csv, <model-id>_stresses.csv, or any stored reference artifact.
|
||||
- Do not approve release readiness.
|
||||
- Do not approve physics validation success.
|
||||
- Do not produce the final release checklist.
|
||||
@@ -38,12 +38,13 @@ Input priorities:
|
||||
4. docs/io-definitions/<feature-id>-io.md.
|
||||
5. Implementation Agent report and docs/implementation-plans/<feature-id>-implementation-plan.md.
|
||||
6. Generated solver result HDF5, normally `results.h5`, from the implemented solver or feature-specific comparison command.
|
||||
7. Stored reference/<model-id>/ artifacts, including metadata.json and Abaqus reference CSV files.
|
||||
7. Stored reference/<model-id>/ artifacts, including optional metadata.json when present and required Abaqus reference CSV files.
|
||||
8. Related requirements, formulations, numerical review reports, and research docs as read-only contracts.
|
||||
|
||||
Execution contract:
|
||||
- Always work in ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT order.
|
||||
- ARTIFACT CHECK: verify metadata.json, model.inp, generated solver results.h5, reference/<model-id>/<model-id>_displacements.csv, reference/<model-id>/<model-id>_reactions.csv, reference/<model-id>/<model-id>_internalforces.csv, reference/<model-id>/<model-id>_stresses.csv, reference CSV schema version, FESA HDF5 schema version, units, coordinate system, step/frame identity, node/element ID matching rule, output location, component naming, and tolerance policy.
|
||||
- ARTIFACT CHECK: verify model.inp, generated solver results.h5, required reference/<model-id>/<model-id>_displacements.csv, reference/<model-id>/<model-id>_reactions.csv, reference/<model-id>/<model-id>_internalforces.csv, reference/<model-id>/<model-id>_stresses.csv, Reference Model Contract provenance, reference CSV schema version, FESA HDF5 schema version, units, coordinate system, step/frame identity, node/element ID matching rule, output location, component naming, and tolerance policy.
|
||||
- ARTIFACT CHECK: metadata.json is optional. Record absence as absent-allowed; when present, inspect it read-only and cross-check overlapping fields against the Reference Model Contract and stored artifacts. Classify conflicts as needs-upstream-decision or the applicable schema/provenance failure.
|
||||
- ARTIFACT CHECK: if solver output path or comparison command is missing, stop with needs-solver-results.
|
||||
- ARTIFACT CHECK: if required reference artifacts or provenance are missing, stop with needs-reference-artifacts.
|
||||
- ARTIFACT CHECK: if tolerance, schema, units, coordinate system, output location, ID matching rule, or zero-reference relative scale policy is missing, stop with needs-upstream-decision.
|
||||
@@ -66,7 +67,7 @@ Comparison rules:
|
||||
|
||||
Required Reference Verification Report sections:
|
||||
1. Metadata: feature_id, source docs and reports, status, owner_agent, date.
|
||||
2. Artifact Inventory: reference model dir, model.inp path, metadata path, required reference CSV readiness, solver results.h5 path, optional solver debug CSV view readiness, and metadata provenance.
|
||||
2. Artifact Inventory: reference model dir, model.inp path, optional metadata path/status, required reference CSV readiness, solver results.h5 path, optional solver debug CSV view readiness, and Reference Model Contract provenance.
|
||||
3. Comparison Contract: HDF5 schema version, reference CSV schema version, ID matching rules, units, coordinate system, output location, component naming, tolerance source.
|
||||
4. Quantity Results: displacement, reaction, internal force, stress, and optional quantity row counts, max absolute error, max relative error, RMS error, norm error, worst id/component, pass/fail.
|
||||
5. Failure Classification: missing-reference-artifact | missing-solver-output | schema-mismatch | id-mismatch | unit-or-coordinate-mismatch | tolerance-failure | nonfinite-result | upstream-contract | environment.
|
||||
@@ -77,7 +78,7 @@ Required Reference Verification Report sections:
|
||||
Status rules:
|
||||
- pass-for-physics-evaluation: all required reference comparisons pass and Physics Evaluation Agent is next.
|
||||
- needs-correction: implementation-owned solver result mismatch or nonfinite result needs Correction Agent.
|
||||
- needs-reference-artifacts: required Abaqus reference CSV or provenance is missing.
|
||||
- needs-reference-artifacts: required Abaqus reference CSV or required Reference Model Contract provenance is missing; metadata.json absence alone does not qualify.
|
||||
- needs-solver-results: generated solver results.h5 or feature-specific comparison command is missing.
|
||||
- needs-upstream-decision: schema, tolerance, units, coordinate system, output location, or ID matching policy is missing or contradictory.
|
||||
- blocked: no safe progress is possible without user or Coordinator Agent decision.
|
||||
|
||||
Reference in New Issue
Block a user