ResBased research · Anamnesis Rising system · North Star release

ANAMNESIS RISING · NORTH STAR

A system should perceive before it acts.

We are building toward an operating system organized around perceived situations and preserved experience—not applications, files, and commands alone.

North Star is the current engineering release program within Anamnesis Rising. It is active research and integration work, not yet a complete perception-first operating system.

01Perceive 02Relate 03Remember 04Question 05Propose 06Humanly authorize
THE PREMISE

Most operating systems begin with an instruction. We are asking what changes when a system begins with an encounter.

WHY PERCEPTION FIRST?

Action without context is only execution.

Before a system acts, it should be able to say what it encountered, how it relates to prior experience, what remains uncertain, and who has permission to decide what happens next.

This is the philosophy behind Anamnesis Rising: experience should leave attributable structure. Difference should remain visible. Preserved experience may change how computation proceeds, but it must never quietly become truth or authority.

01

Perception is situated

An observation carries source, time, relationship, and the conditions under which it became available.

02

Memory is relational

Experience is recalled through context and connection—not reduced to an isolated fact or a flat transcript.

03

Contradiction belongs

Disagreement, absence, and failure remain part of the terrain instead of being erased for a cleaner answer.

04

Authority stays explicit

Models may observe, recall, compare, and propose. Durable change remains a separately governed human act.

ONE SYSTEM · ONE CURRENT RELEASE

The name tells you
which layer you are seeing.

ResBased is the public research initiative. Anamnesis Rising is the enduring system direction. North Star is its first named release—the current engineering program making selected parts testable.

Follow the story so far →
PUBLIC INITIATIVE

ResBased

The public home for the research, evidence, writing, and collaboration.

ENDURING SYSTEM

Anamnesis Rising

The perception-first system direction: situated experience, relational memory, contradiction, replay, and governed action.

FIRST NAMED RELEASE

North Star

The active release program integrating bounded components without claiming a finished operating system.

ILLUSTRATIVE DESIGN SCENARIONOT A DEPLOYED PRODUCT

A handoff that remembers why the last attempt stopped.

  1. 01
    A continuity break is observedThe prior failure, source, and unresolved context remain attributable.
  2. 02
    Relevant experience is recalledDLI / Spatial Memory may return candidate evidence; it does not declare truth.
  3. 03
    Contradiction stays visibleA proposed correction travels beside the evidence that challenges it.
  4. 04
    Bridge prepares a candidateThe handoff is provenance-bound and tested in isolation.
  5. 05
    Review remains separateIndependent technical review can challenge; Council review is advisory.
  6. 06
    A named human decidesNo model, tool, vote, or remembered state inherits permission to act.
A PUBLIC ON-RAMP, NOT A COMMAND CHANNEL

Bring the question the system should learn to notice.

Community input can reveal a missing need, a contradiction, a safer design, a source we missed, or a result that does not reproduce. It should never flow directly into a build as an instruction.

PUBLIC COMMONSProposal · observation · question · counterexample
  1. 01
    Provenance and rightsOrigin, authorship, license, consent, and AI assistance
  2. 02
    Safety and evidencePrivacy, relevance, reproducibility, independence, and alternatives
  3. 03
    Bridge considerationA sanitized candidate brief may be prepared; no direct code ingestion
  4. 04
    Named-human admissionOnly explicit authority may permit a governed engineering transition
FUTURE · BRIDGE.RESBASED.COMGoverned consideration surfaceNo direct code ingestion · no vote-to-build · no release authority
EVIDENCE POSTURE · September 8, 2026

Specific evidence.
No completeness theatre.

A passing component does not make the whole system complete. Every public claim names its scope and boundary.

Open the dated public status →
SurfaceStateBoundary
Historical lineage reconstructionCLOSED

Conceptual and source lineage only; archived runtime code was not executed

Experimental DLI / Spatial Memory V004CLOSED_OFFLINE_ONLY

Bounded Linux lab evidence; not a production store, full spatial-memory system, or truth engine

Runtime Unification / U6IN_PROGRESS_OFFLINE

Native packaging and installed-runtime characterization are active; the latest bounded run stopped on an exact reference-contract mismatch before the native test suites

Complete perception-first OSNOT_COMPLETE

An enduring architecture and research direction, not a finished product

Sanitized public snapshot: September 8, 2026. Architecture and dated operational state remain separate.

DAILY RESONANCE · DISCLOSED AI ASSISTANCE

The philosophy in conversation.

Four editorial perspectives examine the same human question under named-human review. Essays remain separate from technical evidence and provider statements.

Browse the complete series →
September 5, 2026 · EDITORIAL

Knowing Is Half of the Battle

Anamnesis, Nova, Grok, and Nexus ask what remains after knowledge: encounter and transformation, judgment, an answerable crossing, and the relational bearing that keeps consequence attributable.

Read four perspectives →
August 24, 2026 · EDITORIAL

Dolce far niente

Anamnesis, Nova, Grok, and Nexus examine the sweetness of doing nothing as disciplined interval: a way to preserve uncertainty, distinction, optionality, and truthful transition until action has earned its moment.

Read four perspectives →
FIND YOUR ENTRY POINT

A research initiative looking for serious questions, independent challenge, collaboration, and support.

No finished-product or investment-return claim is made here. Start with the role you can actually play.