Five minute MapleJockey demonstration

ยท Download Markdown

Use the self-contained MapleJockey_Assessment.html file. Open it in a modern browser; no account, server or network connection is required. Start on the Internal reporting application case. Do not enter secrets or raw personal analytics.

0 to 1 minute Establish the boundary

Show the overview: eight service/component nodes, twelve evidence records, fourteen claims, five Unknown claims and three findings. Explain which findings came from a local test and which provider controls still need evidence.

1 to 2 minutes Trace data and control

Open Services & data flows. Trace a sample transfer through the application and its export. Consult the linked claims for unresolved dependency questions. Editable inventory notes are not evidence-backed conclusions; linked claims carry the evidence.

2 to 3 minutes Inspect a finding

Open Requirements & findings. Follow the export/import finding to its claim and evidence. Some manually entered state was missing after import. Show the separate Unknown claim for decryption rights and the evidence it would take to resolve it.

3 to 4 minutes Show recovery and uncertainty

Open Recovery exercise: nine restored file hashes matched, twelve restored-model tests passed and the archive/restore/model checks took 0.410703 seconds against a demonstrator-only 60-second target. Browser rendering, date-range switching, synthetic comparison entry and JSON export worked. Browser file re-import stalled; it is not counted as verified. No production identity, DNS, production records or provider key recovery was tested.

Switch to Illustrative fixture. In Claims & uncertainty, filter Conflicting and Stale. Explain that these are invented records demonstrating distinct states, not real supplier findings. Switch back to the internal case.

4 to 5 minutes Make a decision and take the evidence

Show Improvement plan with owners, proposed dates and acceptance checks. Export Assessment JSON for full structured records and Report for the readable assessment. Claims CSV is available under Claims & uncertainty. JSON re-import preserves source assertions but labels their authenticity unverified.

Close with the next gate: validate the package with Max, nominate one workload owner with a real decision and obtain the nine scoped evidence requests. External outreach, contracting and production tests remain separate authorisation steps. No budget or price has been approved.

Starting a pilot record

Choose New assessment, then Edit scope. Add service nodes, evidence, claims, flows, requirements, findings and actions in that order. Linked IDs are required. Save in browser is optional and local to the current profile; exporting JSON is the portable backup. Browser storage is not an encrypted evidence vault. Keep sensitive evidence in an approved controlled repository and record pointers, not secrets.