cs/README.md

000 — READ ME FIRST

Primordial Compute Stack v0.1 — Integration Bundle

Created and Developed by Collin D. Weber Bundle assembled: April 30, 2026

---

What This Bundle Is

This is an integration bundle — not a reinterpretation, not a synthesis document, and not a promotion of any component to a status it has not yet earned. It collects the following independently-released artifacts into one addressable package with a unified manifest, integration specification, and boundary documentation.

It does not merge them. It does not flatten them. It does not re-narrate them. The components speak for themselves. This bundle provides the connective tissue.

---

What This Bundle Contains

Primordial_Compute_Stack_v0.1_Collin_D_Weber/
│
├── 000_READ_ME_FIRST.md           ← you are here
├── 001_STACK_OVERVIEW.md          ← what the stack is and what it is not
├── 002_INTEGRATION_SPEC.md        ← how the components connect
├── 003_CANONICAL_BOUNDARIES.md    ← what is canonical vs. provisional
├── 004_MANIFEST.md                ← complete file manifest with classifications
├── 005_SHA256_CHECKSUMS.sha256    ← checksums for all included files
│
├── source_packages/               ← original OSF-released zip archives (unmodified)
│   ├── Primordial_OS_HIR_Runtime_Prototype_v0_1_Collin_D_Weber_OSF.zip
│   ├── Primordial_OS_HIR_Runtime_Prototype_v0_1_Collin_D_Weber_zip.sha256
│   ├── Primordial_HIR_SPU_Architecture_v0_1_Collin_D_Weber.zip
│   ├── Primordial_HIR_SPU_Architecture_v0_1_Collin_D_Weber_zip.sha256
│   ├── Primordial_CyberSec_Suite_v0_1_Collin_D_Weber.zip
│   └── Primordial_CyberSec_Suite_v0_1_Collin_D_Weber_zip.sha256
│
├── docs_canonical/                ← OSF documentation set (extracted for direct access)
│   ├── README_OSF.md
│   ├── HIR_Architecture_Specification_v1.0_Collin_D_Weber.md
│   └── Primordial_OS_Baseline_Instruction_Set_v1.0_Collin_D_Weber.md
│
├── architecture_maps/             ← interactive HTML architecture diagrams (session-derived)
│   ├── Primordial_HIR_SPU_CPU_Map.html
│   ├── Primordial_HIR_SPU_GPU_Map.html
│   └── Primordial_RAM_Architecture_v0_1.html
│
└── osf_documents/                 ← OSF-format documents (session-derived)
    └── Primordial_RAM_Architecture_v0_1_Collin_D_Weber.docx

---

Reading Order

If you are new to this stack:

1. Read docs_canonical/README_OSF.md — the primary release statement for the OS runtime
2. Read 001_STACK_OVERVIEW.md — the layered picture of what has been built
3. Read 003_CANONICAL_BOUNDARIES.md — what is established vs. what is forward-looking
4. Read 002_INTEGRATION_SPEC.md — how the layers connect technically
5. Consult 004_MANIFEST.md for a per-file inventory

If you are verifying provenance:

1. Start with 005_SHA256_CHECKSUMS.sha256
2. Cross-reference against the .sha256 files inside source_packages/
3. The authoritative upstream hashes are those recorded in the original .sha256 files

---

Classification Key

Used throughout this bundle:

Tag	Meaning
[CANONICAL]	Upstream OSF-released specification or documentation
[RUNNABLE]	Executable Python prototype with passing test suite
[HARDWARE-SPEC]	Hardware architecture specification (RTL + docs, not fabricated)
[ARCH-MAP]	Interactive architecture diagram derived from source analysis
[PROVISIONAL]	Forward-looking specification, not yet prototyped or verified
[INTEGRATION]	Bundle-level documentation created for this integration package

---

Authorship

Primordial Calculus / HIR / Primordial OS / HIR-SPU / Primordial RAM Created and Developed by Collin D. Weber

All component artifacts carry their original authorship. This bundle does not modify, reattribute, or consolidate authorship. The integration documentation (000–005) is bundle-level scaffolding only.

---

What This Bundle Is Not

• It is not a reinterpretation of the source materials.
• It is not a synthesis that merges provisional layers into canonical ones.
• It is not a completed system. The components are at different maturity levels; see 003_CANONICAL_BOUNDARIES.md.
• It is not a replacement for reading the source packages directly.
• It is not a security-certified, production-ready, or formally verified system.

The limitations statements in each source package remain authoritative.