agent-desirecore/web/solver-report

Solver Report Web

Version-controlled source and build tooling for the public Solver Agent Team evidence report.

This directory owns the Web application, interaction behavior, build contract, validators, and deployment verification scripts. Scenario packs, runtime receipts, and original screenshots remain external build inputs so the core DesireCore Agent bootstrap does not grow by hundreds of megabytes.

Image viewer

The screenshot viewer supports:

• fit-to-window and 1:1 pixel modes;
• bounded zoom buttons and + / - / 0 / 1 keyboard shortcuts, including 1:1 source pixels on mobile;
• Ctrl/Command + wheel or trackpad pinch zoom around the pointer;
• double-click zoom and mouse/touch drag panning;
• two-pointer touch pinch zoom;
• an original-file download link and accessible live zoom status.

Each newly opened image starts in fit mode. Closing and reopening the viewer does not retain stale zoom or pan state.

Human + Agent scenario decision trees

Every scenario derives a structured decision tree from its Scenario Pack, accepted Run, and independent validation receipts. The tree shows:

• the business facts, hard rules, and objective priorities confirmed by a human;
• Agent clarification, modeling, and compatible-engine solve or diagnosis steps;
• independent recomputation of variable domains, constraints, objectives, and evidence;
• fail-closed branches for missing facts, incomplete rule mapping, or failed verification;
• the observed delivery, conflict diagnosis, rejection, or recovery outcome.

Tree data follows decision-tree.schema.json and binds the Scenario Pack, messages, session, governed tool receipts, result payload, OptimizationSpec, and validation-report hashes. The observed path comes only from settled summaries and receipts in the accepted Run; oracle data is used only to detect expectation drift. Optimization, validation-only, and recovery scenarios use different topologies, so the report never invents modeling or solve steps that did not occur. The page can switch between all branches and the observed path, and can download an SVG snapshot of the current scenario. UI code remains a generic renderer and contains no scenario-specific business tree.

Build

The build consumes an evidence directory with scenario-packs/, evidence/, and report-web/dist/ output. Rendering dependencies are resolved from a DesireCore application checkout.

Public builds also require evidence/public-release-attestation.json. The Draft-07 Schema binds the review to the content roots of every public message and all 174 screenshots, together with the review methods, evidence ownership, and public-release verdict. Any message or screenshot change invalidates the old attestation and fails the build.

The site consumes evidence/screenshots/public-screenshot-plan.json, a derivation plan whose sourceSha256 values bind every public image to the immutable raw evidence. Raw screenshots containing local paths must never be used as public originals.

export SOLVER_REPORT_INPUT_ROOT=/absolute/path/to/scenario-book
export DESIRECORE_APP_ROOT=/absolute/path/to/desirecore
node scripts/build-report-web.mjs
node scripts/validate-report-web.mjs

Optional environment variables:

• SOLVER_REPORT_OUTPUT_ROOT: override the generated directory. To make recursive cleanup safe, it must remain below <SOLVER_REPORT_INPUT_ROOT>/report-web/ and must not overlap the Agent source or DesireCore application checkout.
• LATEST_PLATFORM_REGRESSION_FILE: override the latest regression summary.
• SOLVER_REPORT_PUBLIC_RELEASE_ATTESTATION_FILE: override the public-release attestation path.
• SOLVER_REPORT_VALIDATION_FILE: override the validation report path.
• REPORT_BASE_URL: public URL used by validate-deployed-report.mjs.
• SOLVER_REPORT_DEPLOYMENT_VALIDATION_FILE: override deployment validation output.

Run the source contract tests with node --test tests/*.test.mjs.

Before signing a public-release attestation, review every original screenshot at readable resolution. Contact sheets are only a hash-labelled coverage index; they are not sufficient for reading small credentials. On macOS, run the original-resolution Apple Vision OCR gate as a second, independent check:

export SOLVER_REPORT_SCREENSHOT_OCR_FILE=/private/tmp/solver-report-ocr.json
export SOLVER_REPORT_SCREENSHOT_OCR_VALIDATION_FILE=/private/tmp/solver-report-ocr-validation.json
npm run privacy:ocr

The validator requires all 174 planned files in order, recomputes every source hash, and applies the same fail-closed sensitive-text policy to recognized text. OCR and full-resolution visual review are both required before updating the attestation. Review-only artifacts never enter the site output or Agent bootstrap.

Deployment boundary

The builder projects only allowlisted public provenance fields and rejects local paths, email addresses, private URLs, common key formats, and named credentials. Deployment validation also requires build.json#gates.publicReleasePrivacy=pass and an attestation digest matching the manifest.

Generate a new immutable release, verify every integrity.json entry before switching, and atomically update the server's current symlink. Never overwrite an existing release or relabel historical evidence as output from a newer platform commit.