From concept to evidence
- SEIGRASM and Hyphos define concepts, execution contracts and the reasons for development decisions.
- Experiments state a question, apparatus, method and criterion before assessing a returned record.
- Evidence & provenance connects each result to preserved bytes, source snapshots and reproducible analysis.
Chapter links identify the particular result supporting a claim. Experiment links lead back to the concepts being tested. A protocol with pending results is a planned test of a claim.
Evidence categories
| Category | What it establishes | Where to read it |
|---|---|---|
| Definition or design objective | The intended meaning or required capability; it requires implementation and validation. | Concepts & relations |
| Software validation | Behavior under the stated execution model and supplied inputs. | SEIGRASM checks |
| Physical observation | Measurements and execution records recovered from the identified apparatus. | Returned records |
| Interpretation or hypothesis | A bounded explanation or prediction, with remaining alternatives identified. | Stability interpretation; repeatability question |
Acquisition counts do not establish independent conversions. Agreement between repeated register reads does not demonstrate conversion freshness. Raw ADC codes are retained without claiming absolute voltage accuracy.
Criteria and assessment
Assess the installed procedure against its declared criteria. Retain wrong, unresolved and unavailable classifications, rejected calibration and unattempted steps. Report successful operations alongside unmet criteria; a successful substep does not qualify the whole experiment.
Separate fitted training bands from held-out observations. Changes motivated by returned results belong to a subsequent procedure; they cannot retroactively qualify the returned run. Acquisition logs describe recorded checkpoints and observations, with continuous behavior between them left unmeasured.
Apparatus and execution boundary
The current apparatus is one Raspberry Pi 5 executing AArch64 SEIGRASM from SD. Native instructions perform GPIO selection, PMIC register transactions, ADC acquisition, supervision and reserved-sector recording. The existing ROM/EEPROM path supplies initial loading.
Silicon access distinguishes direct register control from firmware replacement. Bootstrap integration identifies the remaining Hyphos qualification boundary. Experiments on this apparatus do not establish behavior on every ISA.
SD acquisition procedure
The Pi remains powered off throughout returned-data analysis and preparation of the next image; this interval is normally at least 30 minutes. The prepared card is inserted with power off, followed by one uninterrupted 30-minute powered session. Power is removed before the card returns to the PC for read-only acquisition.
This is the shared external procedure for subsequent runs unless a chapter states a change. Run records identify deviations when reported; the prescribed power window and customary off interval are not measured target durations. Recorded processor counters supply the acquisition and recording intervals.
Evidence preservation
Preserve returned bytes before analysis. Record the installed candidate, source hashes, acquisition metadata and independent assessment. Preparation archives and returned captures remain identifiable when the live notebook grows.