The Paper chapters
Today, Timeline, Next meal, Insights, and Library share one composer and command palette. Evidence and operational tools have separate homes.
A reader's guide · September 2026
Follow the context.
Inspect the evidence.
ParkinSUM's Paper workspace connects local records with deterministic explanations and a synthetic research workbench. This guide shows where to start, how the layers fit together, and where the evidence stops.
Educational production-architecture prototype. Synthetic public demos only. Not medical advice or a medical device; no clinical validation is claimed.
I. Architecture
A visible path from context to explanation.
Local state & provenance
Owner-entered records, catalog metadata, explicit units, and missingness remain distinct. Public demonstrations use fresh synthetic state.
Deterministic rules
Supported context passes through applicability and provenance gates. Rules own classifications, scores, safety gates, and evidence.
Educational traces
Mechanistic sensitivity views stay trace-only. They do not select meal times, reorder recommendations, or establish patient-specific predictions.
A bounded post-rule role
Explicit consent permits only rule-screened, non-BLOCK whitelist reranking or copy polish. Rule-owned results cannot be overridden.
Observatory & replay
Production-derived traces, static contracts, synthetic rule cases, and replay artifacts have separate evidence labels and limitations.
II. Demo route
Begin with a synthetic notebook.
Run the app with its local backend and a fresh synthetic profile. Keep personal records, real identifiers, credentials, and exports out of public demonstrations.
- 01
Today → Library → Timeline
Show the entry composer, source-aware catalog, and a synthetic record. An empty fresh state is valid; unsupported context should remain explicit.
- 02
Next meal → explanations
Supply a user-defined time window and inspect candidate rationale, missingness, and limitations. A withheld interpretation can be the correct bounded result.
- 03
Algorithm Observatory
Open it from the evidence group or command palette. Compare fixed non-personal fixtures and inspect explanation trees. Static registry contracts are not live trace observations.
- 04
Synthetic rule test workbench
Inspect authored expectations and actual assertions in a disposable workspace. Passing a case does not install a rule or establish clinical correctness.
- 05
Verification & open boundaries
Read the capability matrix and dated timeline. Distinguish a documented check from a recorded successful run and a proposal from an implemented feature.
III. Evidence limits
What the demonstration establishes.
A browser capture shows visible rendering at a recorded source state. A passing synthetic case establishes its scoped assertion. Neither establishes clinical validity, complete standards conformance, production readiness, or physical-device and accessibility acceptance.
The model is not clinically calibrated. ParkinSUM is not for diagnosis, treatment, medication timing, dose or diet guidance, patient care, or emergencies. Owner-entered records may contain sensitive information.
Keep reading
A reviewable project, one change at a time.
Documentation index ↗
Records, algorithms, standards experiments, sources, and releases.
Capability matrix ↗
Implemented features, synthetic evidence, reports, and future work.
Verification guide ↗
Commands, expected results, prerequisites, and failure scope.
Contribute ↗
Improve provenance, reproducibility, accessibility, and explanation clarity.