ResBased research · Anamnesis Rising system · North Star release

RESBASEDPerception · Memory · Authority
The intended perception-first spine

Encounter becomes perception. Perception becomes relational memory. Memory can inform action without authorizing it.

The full Anamnesis Rising architecture separates observation, perceptual context, memory, contradiction, review, and governed transition. North Star is implementing and testing bounded parts of this spine.

Data flowAuthority flowProvenance
Non-scope

North Star is not a foundation model. North Star is not a truth engine. North Star is not an unrestricted autonomous agent.

Intended system layers

  1. 01
    Encounter
  2. 02
    Attributed Observation
  3. 03
    Perception / Context
  4. 04
    Relational Memory
  5. 05
    Witness / Replay
  6. 06
    Contradiction / Review
  7. 07
    Named-Human Authority Boundary

A vocabulary that survived the lineage

The project has used vivid names to make a difficult systems problem easier to discuss. The names below recur across preserved architecture and current unification work, but they do not all describe one finished runtime or carry the same maturity.

Read the plain function first and the historical name second. Where a metaphor has an implemented descendant, the exact version and evidence scope still control the claim.

Enduring concepts, present meaning

TermTechnical functionWhy the name fitsCurrent public boundary
WitnessKeep an observation attributable, integrity-bound, and replayableA witness records what a source reported and preserves a path back to that reportImplemented only in bounded, version-qualified surfaces; witnessing does not establish truth
Spatial KernelGive observations a deterministic place, neighborhood, and relationship contextKernel names the small set of placement and traversal rules on which higher-level memory behavior can dependHistorical implementation family with successor functions under integration; not a finished operating-system kernel
TorusIn variants that use periodic coordinates, compute neighborhood and distance with wraparound so opposite coordinate edges can remain adjacent; more generally, model recurrence and returnA torus has no boundary edge along its wrapped dimensions, matching a memory space in which traversal can return and edge positions can be neighborsHistorical topology vocabulary with bounded implementations; a current claim must name the exact geometry and distance rule. It is not new physics or a universal memory geometry
The KnitMatch attributable records by identity and relationship, join selected evidence, measure agreement, and retain contradictions or HOLD states instead of averaging them awayA knit is made from local stitches: each link joins specific source threads while the original threads remain traceableHistorical coordination identity and current assembly concept; a knitted result is a candidate or recommendation, not consensus truth, permission, or release authority
The WeaveRepresent the wider graph formed by records, relations, provenance edges, and witness paths across components or domainsRepeated local crossings and stitches form a larger fabric; the name describes system-scale relationship without claiming that every thread agreesEnduring architectural description; not presently one deployed service, one canonical data structure, or proof of coherence
Void / Void SwarmHold missing, unexpressed, high-uncertainty, or unresolved possibilities for bounded considerationThe name marks what is not yet admitted as governed knowledge rather than filling gaps silentlyHistorical metaphor and coordination vocabulary; not an oracle, truth reservoir, or production claim
Membrane and GatesMake admission, validation, review, and permission boundaries explicitA membrane separates contexts; a gate evaluates the exact conditions for a bounded crossingExact current contracts govern; passing a technical gate cannot silently grant broader authority
ClocksOnFireHistorically recommend persistence, decay, or promotion from recurrence, salience, and coherence signalsThe clock points to time-dependent change; fire evokes activation and decay rather than permanent storageHistorical implementation identity; recommendation remains separate from governed promotion and named-human authorization
BraidCarry related observations and witness context together without erasing their sourcesA braid keeps identifiable strands while giving them a shared routeHistorical Node Zero and Dual-State vocabulary; no universal canonical Braid contract is claimed

Proposed accountable-experience contract

SurfaceQuestionBoundary
ObservationWhat did the system receive or encounter, from which source, and when?An attributable observation or source claim is not guaranteed reality
InterpretationWhat did a particular human, model, or process infer?An inference remains attributable, provisional, and challengeable
RoutingHow did preserved experience change later traversal or processing?A familiar route remains conditional and can be revoked without rewriting history
AuthorityWho permitted which consequential transition, under what conditions?Technical capability, model confidence, and Council review do not grant authority

Implementation direction

The proposed platform can begin above an existing kernel: human and application interfaces over perception and relational-memory services, backed by evidence, policy, identity, and controlled execution. Deeper operating-system integration is a future measurement question, not a present completion claim.

This is a proposed system contract. North Star currently validates bounded parts of it; it does not yet provide four complete production ledgers or a finished installable operating system.

How Bridge connects to Anamnesis Rising and North Star

Bridge does not decide what becomes true or what gets built. It preserves provenance, applies governance, and routes eligible work into evidence-producing engineering.

Anamnesis RisingThe enduring system and architecture
developed through↓
North StarThe current release and runtime-unification program
NORTH STAR · CURRENT RELEASE PROGRAM
PLANNED COMMUNITY INPUT
CommonsPlanned community interface
BridgeGoverned consideration boundary
routes eligible candidates toward →
CURRENT / EMERGING EVIDENCE-PRODUCING PEER LANES
BigEyeBigEye-MarketField DynamicsDLI / Spatial MemoryRuntime Integration
Contradiction · HOLD · Request MoreNo forced consensus
Isolated ValidationBounded testing
Witness & ProvenanceReplayable evidence
Independent ReviewTechnical challenge
Council ReviewAdvisory only
Named-Human AuthorizationRequired and separate
Release CandidateMay be considered
DeploymentSeparately authorized
  • Commons is a planned input channel, not a current runtime dependency.
  • Evidence-producing components are peer lanes, not one mandatory linear chain.
  • Council recommendation cannot replace named-human authorization.
  • Release-candidate and deployment authority are separate decisions.

Five pathways that must not collapse into one

01

Data pathway

  1. Authenticated source
  2. Observation contract
  3. Authority-null runtime
  4. Witnessed evidence
  5. Candidate query result

Boundary: Carries observations and state; cannot establish truth.

02

Provenance pathway

  1. Source identity
  2. Time
  3. Transformation
  4. Canonical hash
  5. Replay receipt

Boundary: Carries origin and lineage; cannot grant permission.

03

Contradiction pathway

  1. Competing claim
  2. Independence check
  3. Missing evidence
  4. Unresolved state
  5. Decision packet

Boundary: Preserves disagreement; cannot silently select a winner.

04

Review pathway

  1. Candidate proposal
  2. Council challenge
  3. Evidence synthesis
  4. Recommendation
  5. Named-human decision boundary

Boundary: Council review is advisory evidence preparation, not external or named-human authorization.

05

Promotion pathway

  1. Explicit proposal
  2. Named-human authorization
  3. Authority manifest
  4. Durable transition
  5. Post-transition receipt

Boundary: Only the explicitly authorized transition may mutate canonical state.

Architecture components

Unified Runtime

A bounded observation and normalization surface with no action authority.

Perception Layer

The intended context, relationship, coherence, salience, and missingness surface. Not yet a complete integrated operating-system layer.

Witness & Replay

Canonical hashing, append-only journals, deterministic replay, restart, backup, and restore evidence.

Spatial Memory & DLI

Relational coordinates, lineage, query, historical state, and candidate results.

Dual-State & Contradiction

Expansive proposal and independent challenge without forced consensus.

ANLS

Structured semantic packets and receipt-bound reconstruction.

Bridge

An internal governed engineering and continuity substrate, not a public SaaS product.

Council / Review Boundary

A review mechanism that prepares evidence; it is not named-human authorization.

Authority Manifest

The explicit record of permitted transitions and named-human authority.

Flows kept separate

FlowCarriesCannot grant
DataAuthenticated observations and semantic stateTruth
ProvenanceSource, time, lineage, and transformationPermission
ContradictionDisagreement, gaps, and dependencyWinner selection
ReviewChallenges and decision packetsExternal authorization
PromotionOnly an explicitly authorized durable transitionRetroactive source rewrite