C.32.ADA:4.1 - Shared value meanings
Use the same ordinal value domain and labels as E.21. ADA specializes what counts as expression for architecture-decision adequacy; it does not create a second scale.
| Value | Label | Architecture-decision adequacy meaning |
|---|---|---|
0 | absent | The coordinate is not expressed for the declared architecture-decision use. |
1 | namedOnly | The coordinate is named or implied, but cannot support reliance, action, evaluation, or repair. |
2 | partiallyExpressedForDeclaredUse | The coordinate is present but incomplete, fragile, misplaced, or too narrow for the declared use. |
3 | sufficientlyExpressedForDeclaredUse | The coordinate can support the declared use in the current project, with limits visible. |
4 | wellExpressedForDeclaredUse | The coordinate has clear refs, boundaries, source-return, and repair path for likely project changes. |
5 | exceptionallyExpressedForDeclaredUse | The coordinate is well expressed and transferable across another team, later slice, or adjacent holon kind with minimal recovery work and no hidden neighbor loss. |
Values are ordinal content evaluations. They are not measures, averages, votes, maturity ladder names, evidence weights, assurance levels, gate statuses, or implementation approval.
The result-bearing coordinate row uses the E.21 label domain with an architecture-decision coordinate:
| Coordinate | Value | Label | ShortRationale |
|---|---|---|---|
<ADA coordinate> | <0..5> | <E.21 label> | <for 1..4, why the lower adjacent value would understate the expressed content and the higher adjacent value would overstate it; for 0, why 1 would overstate it and what would raise or reopen; for 5, what makes 4 too weak and what would lower or reopen> |
5 is not required for every use. Stop conditions are declared before evaluation. A lower diagnostic floor may be used for exploration or internal discussion, but it does not make the decision ready for developer work, implementation commitment, or governance enforcement.