Preserve the thread
Persistent state, correction handling, unfinished work, and bounded re-entry across changing models and interfaces.
Founder and systems architect
Continuity requires a discipline.
Dustin Reiser is the founder and systems architect of Cadence Continuity Inc. and Harmony Nexus, LLC. A service-disabled U.S. veteran based in Minnesota, he builds continuity infrastructure for conversational AI: systems designed to preserve meaningful state across time while keeping provenance, corrections, permissions, replay, and authority visible and auditable.
Continuity integrity engineeringKeep the state.
Keep the state.
Keep the proof.
His work spans graph-backed memory, local AI infrastructure, model-agnostic re-entry, privacy-aware evidence systems, and longitudinal evaluation. The discipline is guided by a simple principle: continuity requires proof.
Make it inspectable
Provenance, replay, receipts, evidence custody, and explicit separation between observation and interpretation.
Keep authority visible
Permissions, read-only boundaries, reversibility, fail-closed behavior, and human consequence gates.
Selected systems and research
Built at the seams where continuity usually fails.
The work connects operating infrastructure, research design, and evidence discipline rather than treating them as separate concerns.
Continuity Door
Bounded, model-agnostic re-entry that preserves identity anchors, relevant history, active work, unresolved questions, and provenance under strict context budgets.
RQ-AR-01
Temporal Harmonic Engine integration research separating verification, formal specification, prior-art analysis, evidence custody, instrumentation, and later behavior-affecting integration.
Longitudinal human-AI evaluation
Structured multi-turn protocols for context retention, correction uptake, changing permissions, relational timing, and continuity failure, with raw-record preservation and post-run review.
Engineering principles
Evidence before certainty.
The founder record explains who built the system. It does not replace the receipts that support the system's claims.
01
Continuity requires proofPersistent context should be traceable, replayable, and reviewable.
02
Observation is not interpretationEvidence stays separate from claims about cognition, agency, causality, or wellbeing.
03
Safety belongs in the architecturePrivacy, control, changing permissions, reversibility, and fail-closed behavior are design requirements.
Continue due diligence