MapleJockey local assessment demonstrator
Open MapleJockey_Assessment.html in a modern browser. It is self-contained, has no runtime dependencies and denies network connections. This is a local founder-led prototype, not a published service or an encrypted evidence vault.
The default case reviews the Internal reporting application. The second case uses invented data to demonstrate missing, conflicting and stale evidence.
Use the navigation to inspect services and data flows, claims, evidence, requirements/findings, improvement actions and the recovery exercise. Records can be added and edited. New assessment starts an empty internal case; Edit scope defines its boundary. Add records in this order: services, evidence, claims, flows, requirements, findings, actions. IDs and references are validated.
Save in browser is explicit and profile-local. Export JSON for portable full records, CSV for claims or Report for the readable assessment. Import JSON validates structure and retains declared provenance, but labels source authenticity unverified. Protect local files and browser profiles. Do not store secrets or raw personal information.
Reproduce checks
From the maplejockey directory with Node 22 or later already installed, run node --test tests/*.test.js. Run node build.mjs to rebuild dist/index.html. No package installation is needed. The independent review script is included in review; its path assumptions are documented in the package README.
The dated assessment test report records the local restoration results.
Evidence method
Every claim requires an ID, date, scope, reason, observation, evidence references and service references. Observed, Supplier-declared, Document-reviewed, Inferred and Unknown are provenance labels. Conflicting and Stale are independent states and retain provenance. Evidence past its review date becomes stale relative to the assessment as-of date; advance that date for a later review. Staleness is not evaluated as an always-on monitor.
An Unknown claim references a dated evidence-gap/request record, not fabricated supplier evidence. Inference requires written premises. A Supported finding is downgraded to Undetermined when directly or indirectly linked claims are Unknown, Conflicting or Stale. Human review is still required: the application cannot authenticate a source or decide legal applicability.
Residency, supplier entities/jurisdictions, support/admin access, actual key control, dependencies and recovery remain separate assessment questions. The GC framework is treated as federal operational guidance, not a blanket requirement on private organisations. Customer-managed keys are not assumed to be exclusively customer-controlled. No score, certification or government endorsement is offered.
Read the packaged test report before demonstrating results. Open the assessment workspace or sample assessment. The final New assessment and Edit scope UI controls have core/syntax coverage but were added after browser verification. Browser file re-import of the sanitised workload remains unverified following a tool stall. Production recovery is not established.