C.32.ACS:4.3 - Row use classes

Use optimizationIndicator only when the row can responsibly guide architecture changes now. A project normally carries only three to five such rows.

Use monitoredGuardrail when the row protects against a loss caused by optimizing another row. Guardrails can have readings and eval results, but they do not define the cycle’s optimization direction.

Use contextOnly when the row helps interpretation but should not drive improvement, comparison, or selection in the current cycle.

Stop condition. Stop C.32.ACS when the criteria set names draft rows, use class, bearer or selected structure, scale form, proxy risk, protected counter-characteristics, receiving use, source-return condition, and any C.32.ACE or Q-Bundle reference that the current use actually needs.

Lowering condition. Lower an optimizationIndicator to monitoredGuardrail or contextOnly when it no longer guides the next architecture change or its proxy risk is not controlled. Lower a draft row to source vocabulary when bearer, scale form, use reason, receiving use, or protected counter-characteristics are missing. Use C.32.HCS when the holon-family starting point is wrong, C.25 when the row is really composite, and the named pattern for the next question when measurement, eval, comparison, publication, local choice, evidence, assurance, or decision work is current.