LAB NOTEBOOK / 01CHAPTER 01 / CONCEPTS & RELATIONS

CHAPTER 01

Concepts & relations.

Definitions used in this notebook, linked to their implementation, experimental method and evidence.

Supporting experiments and qualification ↓

How the pieces connect

SEIGRASM supplies native execution for Hyphos; Hyphos is the basis for SeigrOS. Capability discovery and verified implementations connect this foundation to available silicon.

Physical evidence feeds back into those implementations. The Seigsit is a carrier within this development; the electrical experiment examines one candidate physical relation.

SEIGRASM

The project’s custom assembly language, expressed as explicit native instruction encodings. It supplies the execution foundation for controlling silicon and bootstrapping Hyphos. AArch64, x86-64 and RV64IM with Zifencei have distinct instruction streams implementing a common seed contract.

Implementations and native images →

Hyphos

The language being developed as the native basis of SeigrOS. The unfinished core code provides capability and semantic references. Elementary behavior is implemented and physically tested through SEIGRASM as that language is consolidated. The present electrical payload does not establish Hyphos-made Seigsit creation.

Bootstrap integration →

SeigrOS

The operating system to be built using Hyphos. The minimal physical apparatus is a testing ground for its foundation. A returned electrical record qualifies only the operations it observes; it does not establish a complete SeigrOS installation.

Silicon access and dependencies →

Agnosticism

A common Hyphos capability is realized using the resources available on a silicon cluster, within their technical limits. Discovery and verified implementations connect that capability to particular instruction sets and component interfaces. A common contract does not require identical physical opcodes.

Replacement mechanisms →

Senary

Base six is the default numerical notation in SEIGRASM. Unprefixed digits use 0 through 5; explicit prefixes select other bases. Notation, in-memory transport and physical electrical state count are separate properties to specify and test.

Senary execution contract →

Electrical state

In the six/sixteen-state comparison, a requested control setting paired with an observed raw ADC response. Six or sixteen such states are proposed over the same control interval. Recognition depends on the observed response and frozen training bands. Physical state count does not determine the CPU’s instruction representation.

Six/sixteen-state method →

Seigsit

The layered carrier to be created and used by Hyphos. Creation precedes the availability of all content; its layers can subsequently carry different kinds of information, including Hyphos when required. The electrical experiments do not define its complete layout or equate its number of layers with a voltage cardinality.

Relation to bootstrap →

Firmware

Executable software that initializes or controls a processor or component. Replacement requires an established execution and loading interface. Direct register control can replace a firmware-mediated operation without replacing the component’s or board’s boot code. Fixed ROM, writable executable storage and control registers require different investigations.

Firmware replacement →

Calibration & recognition

The current procedure builds each state’s closed band from its training minimum and maximum plus a declared two-count guard. Bands must be disjoint before validation begins. Recognition receives the raw observation and frozen bands, independently of the requested state. This procedure is not an absolute voltage calibration.

Training intervals and recognition results →

Native journal

SGDATA01 is the current reserved-sector recording format. Native SEIGRASM encodes numeric fields as senary digits, adds run identity and integrity checks, writes the SD sector and reads it back. A PC reader verifies preserved copies. The raw journal requires no target filesystem.

Returned journal and integrity →

Evidence & qualification

Raw returned bytes are retained separately from interpretation. Supplied-input execution tests establish bounded software behavior; physical records establish the observations they contain. A failure, unresolved classification or unattempted step remains part of the result.

Verification and provenance →

Experimental evidence for these concepts

Definitions describe the intended relations. Physical qualification is limited to the operations observed in the linked records.