The question underneath the work
Most operating systems begin with a command: open, save, calculate, send. We began with an encounter. What did the system perceive? What did that encounter mean in context? What changed because it happened?
A perception-first system would carry those conditions forward. It would remember relationships and sequence, retain contradiction instead of flattening it, and distinguish a useful recollection from permission to act.
The operating-system thesis
Most computers organize work around applications, files, and processes. Anamnesis Rising explores a different foundation: computation organized around perceived situations and preserved experience.
The intended system keeps four questions connected without collapsing them: what was observed, what was inferred, how experience changed later processing, and who permitted any consequential transition. The observation remains attributable; the inference remains challengeable; the transition remains governed.
What that could change
Situations before applications
Begin with which observations belong together, which relationships matter, what remains uncertain, and which processing route fits the situation.
Experience changes traversal
Prior outcomes may change which evidence is examined first, when a shorter route applies, and when contradiction must reopen fuller analysis—without rewriting model weights or declaring a remembered answer true.
Continuity survives the tool
Design project memory to remain attributable across changes in applications, devices, people, and approved models while preserving access controls, supersession, and unresolved history.
Access is not permission
Technical access to a resource is not permission to turn an interpretation into a consequential action. Evidence and capability remain separate from authority.
Three commitments
Preserve the encounter
Source, time, context, relationship, and missingness should travel with what the system remembers.
Let memory remain plural
Corroboration can strengthen a path; disagreement and failure remain visible rather than being cleaned away.
Keep authority separate
A system may observe, recall, compare, challenge, and propose. Durable change remains an explicitly governed human decision.
Perception should precede action. Evidence should precede confidence. Authority should remain explicit.ResBased design posture
A practical path to an operating environment
The research does not require replacing a proven kernel first. It can begin as governed services above existing operating-system foundations, mature into a managed runtime or distribution, and justify deeper integration only where evidence shows that integration is necessary.
Calling the direction an operating system does not turn a voluntary library into an enforcement boundary. The claim will be earned only when applications can rely on perception, memory, identity, evidence, and governed execution as real system facilities.
Continuity should influence behavior without becoming unaccountable authority.Anamnesis Rising vision
A direction, not a completion claim
Anamnesis Rising is the enduring system and research direction. North Star is the current release program turning parts of that direction into bounded, testable engineering surfaces.
We have not completed a perception-first operating system. Successes are named at the scope actually tested. Failures and ordinary baselines are allowed to narrow the architecture.