@@ -592,3 +592,23 @@ When adding or changing diagnostic fields after 0.5.3:
|
||||
AL/mortar consistent tangent rewrite is explicitly scheduled.
|
||||
- Do not mark compact contact benchmarks as proof of complete industrial
|
||||
contact coverage.
|
||||
|
||||
## 20. 0.6.0 Lifecycle Developer Notes
|
||||
|
||||
When adding a new nonlinear owner state after 0.6.0:
|
||||
|
||||
- Record lifecycle events through `fem_nonlinear_lifecycle` instead of creating
|
||||
a second event vocabulary.
|
||||
- Use existing event names and add new ids only when a test or output consumer
|
||||
needs a distinct state.
|
||||
- Pair every trial-state mutation with an observable commit or rollback audit.
|
||||
- Extend `nonlinear_lifecycle`, the relevant owner test and one report/output
|
||||
checker when adding lifecycle fields.
|
||||
- Keep `continuation_path.csv` append-only for new lifecycle/report columns.
|
||||
- Add restart state only as an optional block unless a deliberately versioned
|
||||
format break is approved.
|
||||
|
||||
0.6.0 lifecycle hooks are diagnostics and audit infrastructure. Do not use
|
||||
them to claim delivery of complete AL/mortar consistent tangents,
|
||||
mixed-control continuation, cohesive contact mainline, harmonic cyclic
|
||||
nonzero-wave solving, DEM subcycling or production roll-forming workflows.
|
||||
|
||||
Reference in New Issue
Block a user