Preserve the thread
Persistent state, correction handling, unfinished work, and bounded re-entry across changing models and interfaces.
Founder and systems architect
Decades in systems.
Years of research.
One question.
What would it take for an AI to return to shared work with its history, corrections and permissions intact?
Dustin Reiser is the founder and systems architect of Cadence Continuity Inc. and Harmony Nexus, LLC: a service-disabled U.S. Army veteran in Minnesota with roughly 25 years of professional technology experience, and a musician and artist. Cadence Continuity is his answer in progress.
Service-disabled U.S. Army veteranMinnesotaLinux, networking, securityMusician and artist
The path
Many instruments.
One practice.
Chapters from the public founder record. The evidence pages hold the proof.
01 / SERVICE
Service.
A service-disabled U.S. Army veteran, based in Minnesota.
02 / SYSTEMS
Decades of practical systems.
Roughly 25 years of professional technology experience across Linux systems, networking, security, and computer hardware and support, with Linux+, Network+, Security+ and A+ training.
03 / RESEARCH
Groundwork before implementation.
About three years of foundational research preceded the development phase.
04 / THE BUILD
Self-funded, under real constraint.
The development phase had reached roughly eight months by October 2026. He leads the architecture, Linux integration, troubleshooting and technical review; AI collaborators help implement the work, on a tightly constrained, self-funded budget.
05 / THE OTHER INSTRUMENTS
Music, art and making.
He is a musician and artist as well as a systems builder, and the company’s work spans the same range: continuity engineering, music and creative tools, practical fabrication collaboration, and spatial and perception work.
06 / WHAT HE KEEPS
Nobody’s history silently overwritten.
Local control and ownership. Records stay bound to their owner, source and date; corrections supersede or tombstone, they do not silently rewrite; and remembering never becomes permission by itself.
07 / NOW
Continuity that can be examined.
An operating Home environment, the Continuity Door, dated public evidence, and a planned open evaluation toolkit.
Continuity integrity engineering
Continuity requires
a discipline.
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.
Operating system
Continuity Door
Bounded, model-agnostic re-entry that preserves identity anchors, relevant history, active work, unresolved questions, and provenance under strict context budgets.
Active research
RQ-AR-01
Temporal Harmonic Engine integration research separating verification, formal specification, prior-art analysis, evidence custody, instrumentation, and later behavior-affecting integration.
Evaluation practice
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.
Public founder record
Evidence before
certainty.
The founder record explains who built the system. It does not replace the receipts that support the system’s claims.
- Name
- Dustin Reiser
- Companies
- Cadence Continuity Inc.
Harmony Nexus, LLC - Founder CV
- Public founder CV (PDF)
- Continuity requires proof. Persistent context should be traceable, replayable, and reviewable.
- Observation is not interpretation. Evidence stays separate from claims about cognition, agency, causality, or wellbeing.
- Safety belongs in the architecture. Privacy, control, changing permissions, reversibility, and fail-closed behavior are design requirements.
Follow the founder record into the operating evidence.
Founder record ≠ system proof.