KCAE.Application:1.2 - The small source slice that decides this episode
The relevant constructed sources are:
| Source and address | Decision-bearing content | Role |
|---|---|---|
English manual rev. 7, exports/resend | Automated resend requires a stable batch identity, destination receipts and protocol v2 deduplication. Select missing export IDs by comparing intended IDs with accepted receipt IDs. | Governing procedure under the stipulated rule. |
English manual rev. 7, exports/manual-reconcile | For protocol v1, compare the export ledger with the destination report and prepare a supervised reconciliation proposal; do not use the automated resend procedure. | Alternative when the automated condition fails. |
Compatibility table rev. 7, row v1 | Deduplication: no. Receipt count available; an identity-bearing report must be obtained separately. | Conditions and missing-input distinction. |
Compatibility table rev. 7, row v2, footnote 2 | Deduplication: yes, within one stable batch identity; accepted-ID receipts are available. | Scope of the affirmative table cell. |
Spanish localization rev. 5, reenvio | A general resend explanation that does not state the later protocol distinction. | Discovery and language aid, incomplete for today’s advice. |
| Local configuration report, not initially obtained | Destination protocol, batch-identity setting and report endpoint. | Authorized case facts. |
Capacity note rev. 3, export-cache | Each active export reserves 2 GB until completion; the shared cache is 5 GB. | Whole-schedule constraint. |
Prepare the table as addressable rows with column meaning and footnote links. A flat extraction “v1 v2 no yes” cannot support the decision. Check the extracted values against the original table and preserve the visual return. Mark the localization’s edition and role so that a high lexical rank cannot make it governing.
The proposed exact reader accepts source identity, edition and unit address, and returns the requested unit with its context links and completion status. Its corpus enumerator can list original units independent of the topic index. A retrieval hit retains both the retrieval-unit address and the reading-unit address. Therefore the table footnote remains obtainable even when the initial hit is only its affirmative cell.