A synthetic range and intake handoff

A range follows an explicit rule

Estimate accepts finite positive area and two declared synthetic rules. It returns lower and upper values, rule version and synthetic units, keeping quotation confirmation false. No installation price, saving or contractual quote is imported.

A real integration needs approved coefficients, applicability bounds and a site-confirmation process. Successful arithmetic is not market validation. The numeric bound belongs to this independent experiment rather than an industry standard.

Keep context and receiver disclosure together

Handoff reconstructs the calculation, checks consistency and adds recipient information separately. Neither operator nor listed mode claims completed direct partner delivery. Listed mode requires confirming the recipient before submission. No identity is collected and submission remains false.

Disclosure alone cannot verify a delivery route. The code performs no network call or intake operation. Actual submission needs separate authentication, information handling and failure checks. Prepared context and an arrived message are different outcomes.

Preserve a note before replacing it

Prefill takes a note and local revision, returning conflict if a different sentence already exists. Explicit replacement inserts the new context; stale revisions fail. This independent version exposes an edit-preservation policy rather than silently copying the source’s automatic wording.

The live screen calculates, edits synthetic text, prefills conservatively and replaces explicitly. Invalid recalculation clears old context. Its inline core matches the public file, but it implements neither persistent server storage nor multi-user editing.

export function estimate(area,kind){if(typeof area!=='number'||!Number.isFinite(area)||area<=0||area>1000)throw Error('Area must be positive and bounded');const rules={basic:[2,3],extended:[3,5]};if(!Object.hasOwn(rules,kind))throw Error('Unknown synthetic rule');const [low,high]=rules[kind];return{area,kind,low:area*low,high:area*high,unit:'synthetic units',quoteConfirmed:false,ruleVersion:'demo-v1'};}
export function recipient(mode){if(mode==='own')return{mode,receivingParty:'This demonstration operator',directPartnerDelivery:false};if(mode==='listed')return{mode,receivingParty:'Listed party must be confirmed before submission',directPartnerDelivery:false};throw Error('Unknown recipient');}
export function handoff(result,mode){const expected=estimate(result.area,result.kind);if(JSON.stringify(result)!==JSON.stringify(expected))throw Error('Changed calculation context');return{context:expected,recipient:recipient(mode),personalDataIncluded:false,submitted:false};}
export function prefill(current,incoming,expectedRevision,replace=false){if(!Number.isSafeInteger(current.revision)||current.revision<0||expectedRevision!==current.revision)throw Error('Stale local revision');if(typeof current.note!=='string'||current.note.length>400||typeof incoming!=='string'||incoming.length>400)throw Error('Bounded note required');if(current.note&&current.note!==incoming&&!replace)return{...current,conflict:true};return{note:incoming,revision:current.revision+1,conflict:false};}

Inspect values after a replacement conflict

After editing a synthetic note, conservative prefill reports conflict and retains it. Explicit replacement advances the revision and inserts context. Invalid recalculation then prevents reusing that context. Verification covers the order that prevents stale values from following an apparently successful input.

The counterexample is inspectable through tests and saved execution records. Adoption requires checking input meaning and failure policy before changing labels. A small independent function does not replace an operational application.

Published code and ZIP use the same reviewed files. The central decision can be inspected without importing company records or running another system. Any added integration needs separate observed results; the existing package does not pre-certify its behavior.

Actual execution evidence and its boundary

The source folder and a fresh ZIP extraction each passed 17 tests. Actual example results are saved in records.json, and the published core can be compared with the download. Historical project completion messages and test totals were not reused as evidence of this execution.

The live screen changes synthetic state through its actual inline code, with handlers also executed against DOM stubs. These checks do not establish rendered-browser or physical-device behavior. An integrated service needs its own observed verification rather than inheriting a broader claim from these small tests.

Before adapting the download

The ZIP contains core implementation, tests, runner, saved results and guidance; live examples also include bilingual HTML. This is new synthetic code with permission to modify and reuse, without original customer images, operational records or credentials. It contains no instruction to execute the source business program or transmit its material.

Begin adoption by defining units, input provenance and failure messages for the actual workflow. Passing tests cannot certify all supplied facts or grant operational authority. Authentication, persistence, transmission and rendered-interface review remain outside the small contract. I share both a reusable implementation and the decisions an adopter still needs to make.