Direct reset verification and resource reuse.

Question and rationale

Can direct reset-register observations resolve the preceding cleanup stop and allow local resource use to continue? In that return, the SET alias read zero and its expected-one comparison stopped execution before direct confirmation. The earlier CLR alias had also read zero while the direct register confirmed the requested action. The SET write's effect remained unobserved.

This comparison tests responsibility for restoration and further local work after acquisition. Control of connected resources and their reuse supports the wider objective of sovereignty over the cluster and a physical foundation for Hyphos, SeigrOS and Seigsit.

Method and controlled change

Preparation 55810A9141BA uses the same AArch64, Cortex-M3 and PIO SEIGRASM instructions as 83841979437C. The sole executable descriptor change is tag 134's comparison mask, from one to zero. Its SET-alias readings remain in the record. The following direct-register check at tag 135 remains mandatory before disabling the ADC clock.

The 141-access sequence retains the same eight source cases, 24 commanded conversions, eight untriggered readings, 10,000-tick waits and two PIO timing references. It records operation outcomes separately from interval validity. Cleanup verifies the candidate reset field, clock stop, whole reset bank, divider and selector. A further six-case PIO trial tests local usability and powered retention of the acquisition journal.

The source conditions are disabled-to-disabled, disabled-to-enabled, enabled-to-enabled and enabled-to-disabled, followed in reverse order. Labels 0 and 1 describe this source control. They do not define Seigsit states. Raw ADC codes and timer counts are reported in decimal unless prefixed; neither is an independently calibrated physical unit.

Declared criteria

Require all scheduled accesses, valid local timing, both PIO references, reset-bank and clock restoration, timer-control restoration, and unchanged acquisition contents through the subsequent PIO trial. Its new activity marker and valid final report are required: matching stored contents alone cannot qualify retention through activity.

Retain alias observations independently of direct confirmation, all first readings and ADC error indications. A failed direct reset confirmation stops before clock disable. The frozen protocol defines these criteria, timing bounds and failure paths before the run.

Preparation and recovery

The preparation preserves 41 source inputs and 33 passing preparation checks. Installation verified 4,096 transfers and two complete image readbacks before ejection. The powered allowance was 25 minutes. The recovered coordinator interval is 1,219.243269 seconds (20 minutes 19.243 seconds) at the reported 54 MHz, excluding boot-loader time and the final record write/readback. Total powered duration and physical boot count were not independently measured.

All 29,498 journal sectors, 7,378 outer operations and 7,362 boot-bus transfers were recovered. Local entry, upload/readback, initial PIO controls and final route restoration passed. No transport failure or missing journal record was found.

Reset confirmation and restoration

The declared sequence criteria are met in this return. All 141 local accesses completed with status zero and valid timing. The terminal phase is 2, with primary and cleanup status zero. The alias still reads zero, while the direct register confirms the requested reset field and subsequent whole-bank restoration.

These observations establish that the SET request acted on the candidate field in this run despite zero alias readback. They resolve the comparison assumption that stopped the preceding run; the preceding SET action itself cannot be reconstructed retroactively. The candidate's ADC association remains supported by register defaults and source responses, without establishing all effects of the field.

Source responses and acquisition history

All eight untriggered readings retain their reference. Enabling the source changes probe codes by +115 to +116; disabling changes them by −114 to −116. The initial disabled-source reference of 770 precedes two probes of 747, a −23 departure. The preceding return recorded 772 followed by 748, a −24 departure. This first-use pattern recurs, while the last disabled-to-disabled case differs by at most one count in both returns. Its cause is unresolved; source-disabled potential is unspecified.

All 32 ADC-ready polls succeeded on their first read. No ADC error indication was retained. Command completion and source-correlated changes do not independently establish the freshness or analog accuracy of every conversion.

Timing and retained observations

All 141 recorded access intervals are valid, spanning 151 to 10,090 local ticks. Every one of the 16 requested waits has a recorded endpoint interval of 10,090 ticks. There is no recorded wrap or invalid timer-control indication. Saved SysTick CTRL and LOAD were both zero and returned to zero.

Both PIO references record 14,344 decrements, an inner bracket of 86,023 ticks and an outer bracket of 86,095 ticks, identical to the preceding return. The conditional relative-rate bounds are 14343/86096 and 14345/86022. Divider normalization gives 0.999558632 to 1.000557997, including one. PIO configuration is restored after both references. Shared clock ancestry and absolute frequency remain unqualified.

The later six-case PIO trial completed. The acquisition marker changed from zero to two; all other report contents were retained. The early header also matches the first full report. This establishes powered retention through that local activity. It does not establish retention across power loss or repeated ADC reacquisition.

Interpretation and next investigation

Local SEIGRASM now completes acquisition, verifies the candidate reset and clock restoration, and continues using PIO with its observations retained. This adds an observed resource-management capability inside another component. The comparison demonstrates why action must be verified at a meaningful observation point: alias readback alone failed to describe the reset field.

The next discriminating comparison is first conversion after reset and reacquisition versus continued acquisition without reset, with matched source selection and timing. Retain every first reading and compare local sequences within the same boot. Reappearance of the elevated initial source-off reading after reset, and its absence in continued acquisition, would support an initialization-related explanation. Other outcomes would direct attention toward source-selection history or conversion history. These remain hypotheses, not identified causes.

Physical Seigsit transport, six-state operation through this local path, independent conversion freshness, complete firmware replacement and control of every cluster component remain open. SoC boot firmware, RP1 ROM entry, inherited clocks/pads and the present recording/return transports remain dependencies. The results concern one tested apparatus and do not establish cross-cluster reliability.

Evidence and provenance

Two read-only 64 MiB captures agree at SHA-256 0697eeaa27a8101d909c8577435e0d03c6762b1dc245bc399e16cbe83762157e. All 50 preparation artifacts verify. The 3,206 unused journal sectors retain their prepared reservations. Partition geometry, boot configuration and executable are unchanged; FAT copies agree. Seven sectors outside the journal changed, including directory metadata; writer and timing are not established.

Twenty-four return-assessment checks passed, covering both acquisition returns, timing and local execution, altered-record controls and unchanged target instruction provenance. The prepared protocol and sources remain frozen; the current assessment reconstructs both revisions without changing their declared outcomes.

Preceding cleanup observations · SEIGRASM recording contract · Local timing observations.