LSAS Platform - public synthetic Evidence Packet

Measured using synthetic test data

Packet: lsas-public-evaluation-2026-11-07-v1
Source export: 2026-11-07T06:58:36.404Z
Curated: 2026-11-07T07:36:13.000Z

Curated from an existing schema-2 Developer Evaluation export containing four retained decisions recorded October 27–29, 2026. This is not a new execution run.

Evaluation, user, tenant, application, receipt, request, decision-event and grant identifiers are replaced with deterministic public aliases, including correlated references and navigation paths. The private mapping is not distributed.

Historical fingerprints are preserved exactly as recorded. Original input and output bodies are not included, so those fingerprints cannot be independently recomputed here and do not authenticate the remapped identifiers or this packet. The manifest separately hashes the downloadable file bytes.

Four recorded requests, one exact policy version. Complete refers to four retained records out of four lifetime records in the supplied snapshot; it is not suite coverage, regulatory compliance, accuracy or production readiness.

WHAT IS INCLUDED
evidence.json: authentic Evaluation schema 2, retaining all four recorded decisions and original fields; identifiers replaced.
report.html and report.pdf: generated from that same curated snapshot by the existing LSAS Evaluation report functions, with an explicit public-sample disclosure and publication footer. The PDF includes a curation cover and all four request records.
manifest.json: SHA-256 and byte length of the five listed payload files, plus curation provenance. It cannot checksum itself.
verify.mjs: offline Node.js checksum and basic record-count verifier. Requires Node.js 20 or later; no packages, account, credentials or network.
sample-packet.zip: exact bytes of the five payload files plus manifest.json. The ZIP and manifest are excluded from the manifest inventory to avoid circular hashes.

VERIFY AFTER EXTRACTING THE ZIP
node verify.mjs
Or: node scripts/evidence-packet/verify.mjs apps/web/public/evidence/sample-packet

A successful check only establishes agreement with this unsigned manifest. An attacker who replaces both files and manifest can create a new internally consistent packet. This is not a signature, trusted timestamp, customer approval or independent attestation.

INTERPRETATION AND LIMITS
- No real external model provider, arbitrary tool, customer production workflow or downstream delivery is demonstrated.
- Two ingress blocks recorded zero synthetic provider calls. One safe-release scenario recorded one local synthetic-provider call; one allowed-read action recorded one fixed synthetic-reader invocation.
- The action kernel's computed-unreleased receipt and the later final RELEASED outcome represent different stages. An intermediate receipt does not itself authorize final release.
- The export contains decision-event references, not a full audit-log export or separate received/dispatch timestamps. Missing ingress rule details are not reconstructed from final rule matches.
- No transformed or held final outcomes occur in this four-record sample. Absence from this sample does not establish general capability or failure rates.
- Recorded mixed-route timings are retained for fidelity, not presented as latency benchmarks or current service performance.
- This public sample carries no organization approval, recipient access grant, signature, certification or independent attestation. An expired historical grant is not reusable authority.
- The exact historical code/build version was not included in the supplied export. Report-generation source references describe curation tooling, not the historical execution build.

HTML/PDF navigation is curated to public documentation, the public sample report and Contact. Original JSON next-step paths retain their schema with aliased workspace identifiers; they are historical metadata, not accessible accounts or grants. Public sample access does not enable private export or external sharing.

REGENERATION
The approved source file is intentionally not distributed. Curation requires that separately reviewed source and the existing repository tooling:
pnpm exec tsx scripts/evidence-packet/generate.ts /path/to/reviewed-source.json
The generator refuses a different source digest and checks exact agreement with the existing schema-2 generator before writing artifacts.

No historical execution build was provided. Curation reuses buildEvaluationEvidence, evaluationReportHtml and evaluationReportPdf; this tooling does not replay historical requests.
