Synthetic content completeness note 024: revision-aware acceptance

Synthetic note 024, observation 1: this controlled content completeness example records a decision, its inputs, and its verification boundary. The collection belongs to a local engineering experiment and contains no client measurements. A route can exist while its substantive text belongs to an older revision. A successful build is only one event in the release decision; expected content, discovery links, and source revisions are checked independently. Synthetic note 024, observation 2: this controlled content completeness example records a decision, its inputs, and its verification boundary. The collection belongs to a local engineering experiment and contains no client measurements. A route can exist while its substantive text belongs to an older revision. A successful build is only one event in the release decision; expected content, discovery links, and source revisions are checked independently. Synthetic note 024, observation 3: this controlled content completeness example records a decision, its inputs, and its verification boundary. The collection belongs to a local engineering experiment and contains no client measurements. A route can exist while its substantive text belongs to an older revision. A successful build is only one event in the release decision; expected content, discovery links, and source revisions are checked independently. Synthetic note 024, observation 4: this controlled content completeness example records a decision, its inputs, and its verification boundary. The collection belongs to a local engineering experiment and contains no client measurements. A route can exist while its substantive text belongs to an older revision. A successful build is only one event in the release decision; expected content, discovery links, and source revisions are checked independently. Synthetic note 024, observation 5: this controlled content completeness example records a decision, its inputs, and its verification boundary. The collection belongs to a local engineering experiment and contains no client measurements. A route can exist while its substantive text belongs to an older revision. A successful build is only one event in the release decision; expected content, discovery links, and source revisions are checked independently. Synthetic note 024, observation 6: this controlled content completeness example records a decision, its inputs, and its verification boundary. The collection belongs to a local engineering experiment and contains no client measurements. A route can exist while its substantive text belongs to an older revision. A successful build is only one event in the release decision; expected content, discovery links, and source revisions are checked independently. Synthetic note 024, observation 7: this controlled content completeness example records a decision, its inputs, and its verification boundary. The collection belongs to a local engineering experiment and contains no client measurements. A route can exist while its substantive text belongs to an older revision. A successful build is only one event in the release decision; expected content, discovery links, and source revisions are checked independently. Synthetic note 024, observation 8: this controlled content completeness example records a decision, its inputs, and its verification boundary. The collection belongs to a local engineering experiment and contains no client measurements. A route can exist while its substantive text belongs to an older revision. A successful build is only one event in the release decision; expected content, discovery links, and source revisions are checked independently. Revision R2 adds an explicit rule: retain availability only while reporting that the recovered content is stale; do not promote fallback as the latest source.