Question
For a named capability or stated need: what is each representation, where does it exist, which realization state applies, how do the representations relate, and what intervention - if any - is minimally sufficient?
CSR
Capability Surface Reconciliation establishes where a named capability or stated need exists, in which realization state, how its representations relate, what covers which part of the need, and the smallest sufficient intervention before something new is built or installed.
Core model
named capability / need -> identity + surface inventory -> realization state -> representation relationships -> coverage map -> smallest sufficient intervention
Boundaries
documented != runtime available
implemented != installed
installed != authorized
surface != capability identity
reconciliation != orchestration
Composition
CSR composes with SORR for semantic resolution, ORBIT for orientation, Capability-Gap Reconnaissance for absence discipline, GDSA for relevance and activation, and CARD/POINTER for durable representation and routing.
Capability model
CSR treats capability as something that may be represented across source, implementation, installation, runtime and projection surfaces. It reconciles those representations without assuming that presence on one surface proves presence on another, and without replacing the authority of the systems it composes.