Enter the FieldParallax World Portal
Projects/Parallax Archive Core

Project Genome · ARCOR-001

Parallax Archive Core

The unified architecture for preserving projects, artifacts, histories, relationships, claim boundaries, and future migration paths.

draftCore canonTier 1
Parallax Archive Core project field card
Registry-bound visual · B4
RegionScriptorium
Status Exploring
MaturityGrowing
EvidenceOperational
Visibilitypublic candidate
RecordUpdated 2026-07-25
Guided appearances
UnderstandWander

01

Origin condition

Why it exists

A growing body of work can lose its own history when files, chats, versions, releases, and relationships are separated. Parallax Archive Core exists as one custody model beneath many interfaces, preserving projects, artifacts, relationships, trajectories, receipts, and the context needed to understand them later.

Can one archive remain coherent across decades of media and tools without reducing living work to a pile of files?

02

Working system

What it does

  • ▤
    Preserves six record domains

    Projects, artifacts, relationships, trajectories, receipts, and contextual interpretation share stable identity and lineage.

  • ⌁
    Supports many terminals

    Historical, personal, playful, gallery, original, and field interfaces can reveal the same core without duplicating custody.

  • ↺
    Keeps revision visible

    Supersession, migration, disagreement, missing context, and future repair remain part of the archive record.

03

System anatomy

Architecture

The Core uses stable identifiers, typed records, virtual-file locators, relationship edges, version and custody metadata, import review, and multiple terminal adapters.

01designed

Record domains

Project, artifact, relationship, trajectory, receipt, and context records.

02designed

Custody and lineage

Identity, source, versions, hashes, permissions, supersession, and retention.

03designed

Terminal adapters

IBM 5100 Discovery, SL1200 Origin, PAT Mk.1 Creation, Breadbox 64 Play, Gallery 128, and Field Luggable.

04forming

Portal projection

Read-only public rooms generated from approved archive records.

04

Present tense

Current state

Parallax Archive Core is recorded as Exploring at the Growing stage. The inventory currently marks 4 artifact lanes Ready, 2 Partial, and 2 Missing.

SeedSproutGrowingCanopyStewarded

B3 Tier 1 room draft · Core canon · Operational evidence · public candidate

05

Honest edges

Known limitations

  • The unified architecture is designed but not yet a complete migration-ready archive application.
  • Source files and connected-service records may have incompatible permissions, formats, and retention rules.
  • Hashes preserve byte identity, not meaning, accuracy, or permission to publish.
  • A single core increases the importance of backups, export formats, access control, and disaster recovery.

06

Claim boundary · v1.1.0

What we are—and are not—saying

Supported

A unified Archive Core architecture and roadmap define six record domains and a six-terminal foundation, and the B2 portal registry demonstrates a first structured projection.

Not claimed

The current record does not claim complete ingestion of Michael's archive, legal records management, permanent preservation, universal format support, or permission to publish every discovered artifact.

07

Development memory

Ledger

B3-ARCOR-001-01
Architecture

Unified Parallax Archive Core architecture and roadmap assembled.

✓ Documented
B3-ARCOR-001-02
Terminal foundation

Six terminal roles defined over one shared core.

✓ Documented
B3-ARCOR-001-03
Projection

B2 portal registry and relationships established as the first structured public projection model.

✓ Prototype

Curated project receipts · source-file binding and human review remain pending

08

Directional, revisable

Roadmap

01
Now

Freeze the record schemas

Approve stable IDs, virtual-file locators, permissions, versioning, and supersession for the six domains.

02
Next

Ingest one complete project lineage

Bring source files, decisions, artifacts, relationships, and receipts for one project through the full process.

03
Later

Connect the six terminals

Build interfaces only after all can read the same records without duplicating custody.

10

B10 evidence trail

Featured evidence

source bound

Direct source trail

At least one direct source, live route, publication, report, dataset, workbook, or source package is bound.

Parallax Archive Core evidence board
document · interface-map

Six-terminal foundation

Discovery, Origin, Creation, Play, Gallery, and Deployment interfaces.

Open bound artifact
visual · project-card

Parallax Archive Core — Project Field Card

B4-generated visual identity card built directly from the reviewed constellation registry.

Open bound artifact
data · genome-snapshot

Parallax Archive Core — Public Genome Snapshot

Public-safe JSON snapshot of the current project registry or expanded Project Genome.

Open bound artifact
Open the full evidence board

11

Publication intake

Artifacts & sources

Detail roomPartial
SummaryReady
Hero / posterPartial
SpecificationsReady
Demo / repositoryMissing
Public linkMissing
Claim boundaryReady
RelationshipsReady
architectureindexed

Parallax Archive Core unified architecture

Six record domains and custody model.

View archive recordarchive:intake/archive-core-architecture
interface-mapBound

Six-terminal foundation

Discovery, Origin, Creation, Play, Gallery, and Deployment interfaces.

Open bound artifact Live Archive index
receipt-setmissing

Complete reference-project ingest

Required proof of lineage, permissions, migration, and projection.

View archive recordarchive:intake/archive-core-reference-ingest

Source basis

Archive Core unified architecture and roadmaparchive:intake/parallax-archive-core/source-basisinternal-prototype
Enter the Field B3 Tier 1 room draftportal:project/parallax-archive-core@v0.4-b3planning-inventory

Review: Canon, claims, privacy, accessibility, and publication review · pending

12

Move with evidence

Next actions

primaryFollow the records into their interfaces

The Core is proven when multiple terminals reveal one lineage without copying or contradicting it.

reviewReview the artifact register

See which source packages, visuals, demonstrations, and public links are actually ready.

secondaryTrace related projects

Follow documented dependencies and neighboring systems without inventing connections.