INTERACTIVE · FICTIONAL REPORT
See why the recommendation changes.
Follow each contractual promise through a made-up source excerpt, an evidence assessment, and the next buyer action. This is a teaching example, not a real UpperCheck export or a customer result.
All contents below are synthetic. The contract, software project, paths, line numbers, commit labels, test descriptions, and execution logs are invented for illustration. None were retrieved from GitHub or produced by executing code. An actual UpperCheck report has separately validated citations and a locked real commit.
ILLUSTRATIVE RECOMMENDATIONHOLD
Six promises have illustrative source or documentation support. The seventh explicitly requires a captured service/API execution record, which this fictional delivery does not include.
Seven confirmed example promises
Each row links the fictional requirement to a supporting excerpt. Four high-level areas on the homepage summarize these seven atomic promises: Decimal precision (R-01/02), Architecture (R-03/04), Reproducibility (R-05/06), and Direct functional demonstration (R-07).
| Selected contract promise | Fictional source or evidence | Result |
|---|---|---|
| R-01 — Exact decimal arithmetic The service must calculate 0.1 + 0.2 exactly as 0.3. | Decimal operations are defined and tests specify expected output. [Source/test definition: see fictional excerpt] | Supported |
| R-02 — Decimal-safe values The conversion engine must avoid binary floating-point accumulation for currency amounts. | Decimal-safe value path shown in fabricated module. [Source: see fictional excerpt] | Supported |
| R-03 — Conversion route A POST /convert route must be provided. | A fictional service handler exposes POST /convert. [Source: see fictional excerpt] | Supported |
| R-04 — Response fields Successful responses must include source and target currency codes. | Fictional response includes both code fields. [Source: see fictional excerpt] | Supported |
| R-05 — Install documentation Installation steps must be documented in the repository. | README excerpt describes installation. [Documentation: see fictional excerpt] | Supported |
| R-06 — Test command Repository documentation must tell the buyer how to run tests. | README and package script include a matching command. [Documentation: see fictional excerpt] | Supported |
| R-07 — Demonstrated behavior A successful conversion must be demonstrated by a captured service/API run at the locked delivery. | A: no matching execution record; B: fictional example log illustrates required evidence. [Recorded execution required: see fictional excerpt] | Gap |
Inspect the example evidence trail
Evidence levels matter. Source files and test definitions are things observed in a repository; they do not prove execution. Only a relevant, authenticated execution record at the exact reviewed commit could demonstrate behavior when the contract requires that proof. In this illustration, the logs themselves are entirely fictitious.
E-01 · src/decimal.ts:12–24 · MOCK SOURCE
Example of inspected implementation. A test definition appears below, but this page does not claim the test ran.
12 import Decimal from 'decimal.js';
13 export function add(a: string, b: string) {
14 return new Decimal(a).plus(b).toString();
15 }
21 // MOCK TEST SOURCE — not an execution log
22 expect(add('0.1', '0.2')).toBe('0.3');E-02 · src/routes/convert.ts:30–47 · MOCK SOURCE
A fictional route and response fields. The snippet does not demonstrate a running server.
30 router.post('/convert', async (req, res) => {
31 const result = convert(req.body);
32 res.json({
33 amount: result.amount,
34 sourceCurrency: req.body.sourceCurrency,
35 targetCurrency: req.body.targetCurrency
36 });
37 });E-03 · README.md:8–21 / package.json:6–10 · MOCK DOCS
Example installation and test instructions, not proof that those commands succeeded.
08 npm install
12 npm test
package.json (synthetic):
08 "scripts": { "test": "vitest run" }E-04 · ci/jobs/convert-smoke.log:41–47 · SYNTHETIC LOG
Delivery A: no recorded execution artifact is included in this example. The requirement remains unsupported; no failure of the delivered code is established.
Not supplied for Delivery A.
What the buyer would do next — HOLD
Ask the developer for a credible service/API execution log from the locked delivery showing the required conversion scenario. Independently assess the provenance and whether it satisfies the exact contractual promise.
- Buyer confirms what the contract requires; AI suggestions do not create extra obligations.
- Findings depend on accessible artifacts and bounded retrieval; not an exhaustive audit.
- The buyer, not UpperCheck, decides whether to accept the milestone or release payment.
- The SHA-256 seal used for actual finalized reports detects alterations to report bytes; it does not establish that the conclusions are correct.