ResBased research · Anamnesis Rising system · North Star release

RESBASEDPerception · Memory · Authority
A history of questions, results, and revisions

The story is not that every idea worked. The story is that each useful question changed what we built next.

This public timeline describes the goal at each chapter, what the work established, and what the evidence forced us to reconsider—without exposing private implementation or operational detail.

GoalOutcomeWhat we learned
How to read this timeline

A milestone is evidence of progress within its stated scope. It is not proof of a finished operating system, scientific validity, security certification, production readiness, or authority.

A nonlinear lineage

Anamnesis Rising began as a philosophy of perception and continuity. Its concepts branched, were renamed, became executable experiments, and sometimes lost to simpler baselines. North Star is the release lineage that makes that history inspectable rather than rewriting it into an inevitable success story.

Every chapter below separates the aspiration from the achieved result and the remaining boundary.

The calendar chronicle · ideas take shape

These dates mark the first located appearance or a supported later synthesis in the preserved chronicle—not necessarily the absolute origin of an idea. Calendar dates and North Star release phases are separate records.

  1. 01
    JANUARY 1–4, 2026VOCABULARY EMERGES

    Scars, crystals, and brightness

    The question
    Could memory preserve both repeated patterns and the differences that should not disappear?
    What changed
    The chronicle first records a vocabulary of scars, crystals, brightness, recurrence, and coherence for navigating experience.
    What we learned
    This established design language and intent, not an implemented memory engine. Repetition alone could not safely imply truth.
  2. 02
    JANUARY 9–14, 2026PERCEPTION MODEL DEEPENS

    Difference, understanding, and appreciation

    The question
    Could a present state be compared with remembered structure, and could familiarity remain distinct from contextual importance?
    What changed
    Delta, salience, and the early FPUA language of Understanding and Appreciation entered the record as distinct perceptual inputs.
    What we learned
    A useful delta needs recoverable endpoints. Coherence and salience can guide navigation, but neither is truth or authority.
  3. 03
    JANUARY 17–22, 2026DESIGN CONVERGENCE

    One architectural conversation

    The question
    Could perception, field behavior, memory, replay, simulation, safety, and authorization be considered without collapsing their roles?
    What changed
    The dated record brings these concerns into a shared architectural conversation and makes integration, recovery, and authority separation explicit goals.
    What we learned
    This was design convergence and reported work, not proof that a unified implementation existed.
  4. 04
    JANUARY 23–25, 2026PROCESS FORMALIZED

    Persistent difference and the perception cycle

    The question
    Could scars remain durable, and could an encounter move through association, weighting, response or restraint, and reflection?
    What changed
    Persistent scars and a recursive perception cycle became explicit parts of the blueprint.
    What we learned
    The blueprint made the process inspectable, but its proposed measures and durable storage still required independent evidence.
  5. 05
    JANUARY 29, 2026SPATIAL MODEL EXPLICIT

    Memory becomes a landscape

    The question
    Could experience be revisited through relationship and terrain instead of stored only as a list?
    What changed
    Spatial Memory, Spatial Kernel, and navigable-terrain concepts entered the dated record.
    What we learned
    A coordinate or landscape metaphor is not evidence of retrieval performance. It creates a question that can be tested.
  6. 06
    FEBRUARY–MAY 2026INSUFFICIENT SURVIVING EVIDENCE

    The gap remains visible

    The question
    Can the chronology stay honest when the surviving record cannot establish day-level activity?
    What changed
    The reconstruction marks an evidence gap instead of manufacturing a smooth narrative.
    What we learned
    Missing evidence does not prove that nothing happened. It means the public timeline cannot responsibly say what happened.
  7. 07
    JUNE 1–11, 2026HYPOTHESIS BECOMES TESTABLE

    Addressing and falsifiability

    The question
    Could spatial placement become more precise, and could crystal-and-scar ideas be framed so evidence might reject them?
    What changed
    Spatial addressing appears and the later synthesis identifies the crystal-and-scar theory crossing from metaphor toward a falsifiable hypothesis.
    What we learned
    Testability is progress. It is not validation of the mechanism.
  8. 08
    JULY 7–24, 2026ROLES CLARIFIED · CHRONICLE SEALED

    Where versus why it matters

    The question
    Did perception weighting and spatial addressing solve the same problem?
    What changed
    The work separated them: coordinates answer where; perception weighting helps estimate familiarity and contextual significance. The original daily chronicle was then sealed through July 24.
    What we learned
    Clearer roles reduced conceptual overlap. Later work belongs in a successor chapter rather than being backfilled into the sealed chronology.
  9. 09
    AUGUST 19, 2026 · RETROSPECTIVELATER CONTINUATION

    Memory as movement

    The question
    Could change be represented as a trajectory through remembered structure?
    What changed
    Trajectory deltas appear in the later retrospective lineage.
    What we learned
    This is later evidence about the evolving model and must not be backdated into the January–July chronicle.

The North Star release chronicle · ideas become engineering

A phase records an engineering package or validation milestone. It is not interchangeable with the calendar date on which an idea first appeared.

  1. 01
    NORTH STAR · PHASES 0–67ENGINEERING SCAFFOLDING

    The philosophy gains a lifecycle

    The question
    Could the system support recovery, inquiry, terrain, trust evaluation, replay, and operator control?
    What changed
    A staged release lineage explored these concerns through bounded modules and contracts. At a major release boundary, the recorded disposition was to defer.
    What we learned
    A deliberate stop is a valid result. Incomplete work should not be made to look like a release.
  2. 02
    NORTH STAR · PHASES 29–34GOVERNANCE SEPARATED

    Evidence is not authority

    The question
    Could inquiry branches, possibility, challenge, and disposition remain distinct rather than collapsing into forced consensus?
    What changed
    The release lineage developed bounded contracts for preserving questions, alternatives, contradiction, Dual-State review, and explicit disposition.
    What we learned
    Agreement is not truth. Council review is advisory. Only a separately authorized transition may create durable canonical change.
  3. 03
    NORTH STAR · PHASES 78–82BOUNDED CORE REPRODUCED

    Memory becomes measurable

    The question
    Could indexing, lifecycle replay, contradiction, provenance, and explanation work together in a reproducible core?
    What changed
    A major non-integrated perception-and-memory surface became deterministically testable.
    What we learned
    The custom representation preserved useful structure, but ordinary approaches won several performance comparisons. The broader advantage claim was withdrawn.
  4. 04
    NORTH STAR · PHASE 89CONTROL MILESTONE

    A cumulative control surface

    The question
    Could the release lineage consolidate operator-control work without pretending separate execution planes were already unified?
    What changed
    A sealed control milestone was reached while the remaining assembly problem stayed explicit.
    What we learned
    A large component can be real and reproducible without making the whole system complete.
  5. 05
    AUGUST 24, 2026LINEAGE MADE LEGIBLE

    Learning exactly what we had

    The question
    What survived across phases, aliases, branches, and separate runtime planes?
    What changed
    The project reconstructed the phase and component lineage, identified disconnected execution planes, and preserved unresolved chronology rather than smoothing it away.
    What we learned
    Recovery and documentation are engineering work. Historical ambiguity remains visible where source cannot resolve it.
  6. 06
    AUGUST 31, 2026EVIDENCE REVISES THE CLAIM

    Measurement over mythology

    The question
    Had the custom memory approach earned a unique performance advantage over a matched ordinary index?
    What changed
    Controlled comparisons found no distinctive advantage, even as a bounded core remained reproducible.
    What we learned
    The project kept the useful structural work and rejected the unsupported superiority story.
  7. 07
    SEPTEMBER 1, 2026BOUNDED LAB EVIDENCE

    Recall at a point in time

    The question
    Could an experimental memory surface append, recover, replay, and explain evidence exactly as it existed at an earlier sequence?
    What changed
    A bounded Linux experiment demonstrated crash recovery, temporal query, deterministic replay and recall, and a read-only no-change boundary.
    What we learned
    This establishes an experimental surface—not a complete native spatial-memory system, production store, or truth engine.
  8. 08
    CURRENT CHAPTERINTEGRATION ACTIVE

    Runtime unification

    The question
    Can separately tested producers, memory, contradiction, review, and evidence paths operate together without losing provenance or human authority?
    What changed
    The project is moving from isolated components into governed integration runs. Failed runs remain part of the evidence and are corrected through bounded successors.
    What we learned
    The perception-first operating system remains under construction. The immediate goal is truthful cooperation among components, not a premature completion claim.
  9. 09
    NEXTOPEN INVITATION

    Widen the inquiry

    The question
    What lived problems, counterexamples, accessibility needs, or simpler designs should the system learn to notice?
    What changed
    The Commons provides a public place to contribute questions and evidence. A governed path toward future Bridge build consideration is being designed.
    What we learned
    Community input remains non-authoritative: popularity cannot grant truth, deployment, promotion, or release authority.