KCAE.Application:1.1 - The receiving work and source authority

CedarBench is a fictional data-export service. Its support collection contains 18,000 documents: manuals, localized copies, release notes, worked examples and private incident records. Public documentation changes several times a week; support receives repeated English and Spanish questions that rarely name the governing paragraph. These are constructed design conditions, not measured characteristics of an existing installation.

The intended result is a source-grounded explanation or conditional support proposal. The service does not autonomously change customer configurations. The product owner supplies the authority rule: the current approved English manual governs operational advice; an approved release note can override its named clause; a translation aids understanding but cannot override a newer governing condition. A local configuration report supplies case facts. An incident note reports what happened and does not amend the manual. Private row data may not be sent to external models. Those stipulated rules are inputs to this case; another organization must obtain its own.

One support episode says: “Nightly reports finish on time, but our senior analyst removes duplicates every morning. Can we buy faster workers?” A Spanish query might instead ask, “Cada manana quitamos filas duplicadas; el envio termina a tiempo.” The practical distinction is successful completion plus repeated compensation, not the word speed. The original episode remains available while queries explore both throughput and receipt reconciliation.