Reference · compiler products
Artifacts and manifests
Presolve’s generated files are a matching, versioned publication. They are evidence and execution inputs—not authoring surfaces. Never edit one or combine products from different builds.
Route and document products
ArtifactMeaning
file-routes.manifest.jsonCanonical route paths, entry components, and published document inventory.routes/**/index.htmlComplete static documents generated from the strict application template.route-metadata.jsonSchema-v1 title and optional description sidecars joined to canonical route identity.route-loaders.plan.jsonSchema-v2 loader identity, package coordinate, result codecs, parameter mapping, cache facts, and Resource bootstrap target; contains no server source.route-server-actions.plan.jsonSchema-v2 Form/action identity, package coordinate, compiler-issued request path, input, response, cancellation, and typed-failure facts.Browser and resume products
runtime.<sha256>.jsContent-addressed browser execution for the exact document;
runtime.js remains a compatibility coordinate.app.<sha256>.cssContent-addressed global CSS linked from document head;
app.css remains a compatibility coordinate.Resume recordsComponent, state, binding, structural, form, resource, and effect restore membership for one build.
Capability registriesOnly exact authority-proven validator, client submission, and terminal package exports selected by the compiler.
package-invocations.runtime.jsonBeta.17 terminal package calls joined to their owning Action, exact import coordinate, registry key, and event-restore policy.
environment.browser.jsonOnly manifest-admitted public values actually read by source.
public assetsCaller-owned files copied to root paths and included in the deployment inventory.
Production evidence
ArtifactMeaning
production.runtime.jsonFrozen runtime tables for the selected resume build.optimization-report.jsonCompiler-owned optimization decisions and invariant evidence.runtime-cost-report.jsonStatic runtime counts and production byte accounting.production-audit.jsonSchema-v1 audit joining those reports; the only success status is passed.Audit failures use PSV2A001 through PSV2A005 for schema, build identity, validation, count, and byte invariants. Vite verifies and transports the audit; it does not recreate policy.
Node deployment products
ArtifactMeaning
.presolve/node/deployment.plan.jsonSchema-v3 static/dynamic route inventory plus registry paths and SHA-256 digests..presolve/node/server.mjsGenerated host that consumes only compiler-issued routes, request coordinates, codecs, cache policy, and bootstrap targets.presolve.route-loaders.mjsVite-built frozen registry containing only admitted loader named exports.presolve.server-actions.mjsVite-built frozen registry containing only admitted server-action named exports.Integrity rules
- All schemas, compiler contracts, build identities, and digests must match.
- Artifact paths are publication-relative and cannot escape the output root.
- Unknown fields, missing records, duplicate routes, non-callable package exports, and checksum drift fail closed.
- Returning browsers use content-addressed runtime and stylesheet coordinates to avoid stale pairings.
- Provider adapters may filter or copy only as their contract permits; they cannot repair malformed products.
Inspect safely
pnpm buildpnpm exec presolve explain app/routes/index.tsx --format jsonpnpm exec presolve inspect # see presolve help for the installed formGenerated means immutable
If an artifact is wrong, fix authored source, package contracts, or the compiler. Patching dist/ makes the inventory untrustworthy and can break resume or deployment integrity.