Aether Continuity Institute Supporting Paper  ·  No. 003
Year  2026
Version  1.0
Series  SP
Open Working Draft
ACI Supporting Paper No. 003 · Concept Paper · CC BY 4.0

The RAID-Battery: Segmented Energy Architecture, SEFI-R, and the Next Generation of Fault-Tolerant Electrochemical Storage Systems

Working Paper v1.0 — Pre-publication concept paper · Not a patent application

Cite as: Aether Continuity Institute (ACI), Supporting Paper No. 003, 2026.
Available at: https://aethercontinuity.org/papers/sp-003-raid-battery.html
License: Creative Commons CC BY 4.0
Related disclosure: SEFI-R v1.0, Open Technical Disclosure, 26 February 2026 (Zenodo, DOI: 10.5281/zenodo.14940723)
Energy Storage Architecture Fault Tolerance SEFI-R CC BY 4.0
Abstract

This working paper examines a potential paradigm shift in battery architecture — from the monolithic cell-chain to a distributed, segment-controlled energy system referred to here as the RAID-Battery. The concept does not primarily propose a new cell chemistry, but rather a fundamental change at the system level: the battery is no longer a passive energy reservoir, but a fault-tolerant, software-managed, situation-aware energy infrastructure.

The paper integrates five perspectives: physical architecture, control systems, testing methodology, use cases, and economic logic. The central argument is that the next major development step for batteries may not arise primarily from increased energy density, but from the transfer of reliability, safety, and performance from the individual cell to the system architecture as a whole.

In this context, SEFI-R (Segment-Event Fault Injection and Recovery) — published as an open technical disclosure in February 2026 (Zenodo DOI: 10.5281/zenodo.14940723) — emerges as a possible starting point for standardization: it provides a method for measuring a segmented energy system's ability to detect, isolate, and manage localized faults without destructive testing.

§ 01

Introduction

Current development of electric vehicles and large battery packs has been strongly cell-centric. Public discourse typically focuses on energy density, charging speed, cycle lifetime, and safety. Yet at the system level, present-day batteries remain surprisingly monolithic: even though a pack consists of modules and hundreds or thousands of cells, fault management is often crude protective switching rather than fine-grained fault tolerance.

This leads to several structural problems:

This paper proposes an alternative framing: the battery should be understood as a distributed energy system, more closely resembling an electrical grid, a data center, or a RAID disk array than a single chemical component.

Scope of novelty claim. This paper does not claim novelty for segmentation, bypass topology, or distributed battery management as such — these concepts have prior art dating to the 1990s. Its proposed contribution lies in the integration of segmented architecture, resilience-oriented orchestration, and the SEFI-R non-destructive recovery-testing methodology into a unified system framework.

§ 02

The RAID Analogy and Its Significance

RAID (Redundant Array of Independent Disks) emerged as a solution to a problem in information systems: a single disk failure caused the entire system to fail. The core insight of RAID was to transfer reliability from the individual component to the system architecture.

L1 — Vehicle Energy Management System (EMS)
driver demand · charging protocol · thermal
L2 — RAID-Battery Orchestrator (BMS 2.0)
Health Score · Load Allocation · SHN · State machine · Micro-SEFI diagnostics
L3 — Segment Controllers (Local MCU × N)
V · I · T sensing · local fault isolation · hard-limit enforcement (independent of L2)
L4 — Battery Segments (cells + switching + sensors)

Figure 1. RAID-Battery control stack. Reliability is an emergent property of the four-layer architecture. L2 (orchestrator) optimises; L3 (segment controllers) protect independently.

The same principle applied to batteries: an individual cell or segment is permitted to be imperfect; failure is accepted as a normal part of system behavior; the system detects, isolates, and compensates for localized faults; performance is maintained even in a partially degraded state.

2.1 Accepting Component Imperfection

Current battery packs are based on a series chain in which the weakest element determines the whole. RAID thinking starts from the premise that components are allowed to fail, provided the architecture is designed to tolerate this.

2.2 Fault State Management

A RAID system does not merely detect a fault — it continues operating afterward. Analogously, the RAID-Battery does not aim solely for safe shutdown, but for sustained degraded-mode operation.

2.3 Quantifying Recovery

In information systems, rebuild time is a key metric. The battery system equivalent is the quantification of recovery: the system is not simply intact or broken, but its ability to recover from a fault event can be measured. This is precisely what the SEFI-R Recovery Ratio (Recov(Z)) enables.

§ 03

Segmented Battery Architecture

3.1 The Segment as an Energy Node

A single segment may contain its own cell group, voltage/current/temperature sensing, optional impedance measurement, local switching and bypass capability, and a local microcontroller. The segment is therefore not merely a mechanical subdivision, but an active energy node.

3.2 Illustrative Example: 80 kWh EV Pack

ParameterValue
Total capacity80 kWh
Number of segments16
Capacity per segment~5 kWh
Shared busHigh-voltage DC bus
ControlCentralised pack orchestrator
Impact of one segment loss~6.25% capacity reduction only

3.3 Architecture Variants

Multiple architectural approaches are possible, ranging from simple series segments with bypass paths, through multiple independently controlled segment buses, to a fully modular DC/DC-based energy-node architecture. Early commercial implementations are likely to use simpler bypass-path solutions, while longer-term evolution may lead to genuinely distributed HV energy nodes.

§ 04

Pack Orchestrator: BMS 2.0

A conventional BMS primarily performs measurement, balancing, and protective switching. In a segmented battery, this is no longer sufficient. A new control tier is required — the pack orchestrator.

4.0 Two-Layer Control Architecture: Reflexes and Intelligence

A practical implementation separates two structurally distinct roles across two layers. The Guardian layer is implemented in deterministic hardware (microcontroller or RTOS-based embedded system). It holds hard limits, runs the protection loop, and maintains a fallback current-limit profile that can operate without any input from the orchestrator. The Orchestrator layer is implemented on a more capable compute platform and handles all optimisation, learning, and diagnostics functions. It is permitted to fail and restart without causing a safety event, provided the Guardian layer continues to operate correctly.

The orchestrator–guardian interface must be minimal, explicit, and unidirectionally safe. Three elements are sufficient: a liveness signal (monotonically advancing sequence counter with timestamp); a current-limit broadcast with a defined time-to-live; and a re-enable gate in the guardian requiring N consecutive valid signals before returning control authority after a recovery event.

4.1 The Health Score and Resilience Algorithm

HS = w₁ × cap_ratio + w₂ × dcir_factor + w₃ × Recov(Z) + w₄ × thermal_factor
(default weights: 0.35 · 0.25 · 0.25 · 0.15)

The orchestrator no longer simply asks whether a segment is usable, but how much it should be loaded relative to other segments at any given moment. This is a critical departure from conventional BMS thinking.

4.2 B-Grade and B+ Cell Management

The practical value of HS logic is particularly apparent when the system contains non-prime cell material. A segment that is weaker in capacity or resistance can be kept safely in operation if the orchestrator assigns it a reduced discharge and charge current, prioritises cooling, transfers it to light-duty mode as needed, and isolates it before a critical fault if recovery capacity is declining. This transforms weakness into a managed property rather than an immediate cause for rejection.

4.3 Micro-SEFI as a Software Maintenance Tool

SEFI-R in this model is not only a laboratory test, but can be conceived as a software-based maintenance tool. The system may perform controlled micro-SEFI-type tests during servicing, diagnostics, or charging cycles. Recov(Z) becomes an updating resilience parameter continuously feeding orchestrator decision-making.

4.4–4.6 Load Distribution, Orchestrator Redundancy, Two Time Scales

Discharge and charging power is distributed in proportion to segment health scores. Orchestrator redundancy (hot standby, safe fallback mode) is a long-term requirement. Control requires at least two loops: a fast protection loop at the millisecond level, and a slower optimisation and diagnostics loop at the second-to-minute level.

§ 05

SEFI-R as a Testing Methodology and Standardisation Basis

The central insight of SEFI-R is that a battery need not be physically damaged in order to measure its fault tolerance. Instead, a controlled electrical fault path is introduced into the system, after which the response, isolation, and recovery are measured.

Table — SEFI-R Method Structure
PhaseNameDescription
AFault InjectionA known electrical leakage condition is introduced temporarily via an externally controlled impedance element. No physical damage.
BResponse MeasurementDetection latency and isolation response time are recorded during and immediately after the event.
CRecovery QuantificationA normalised recovery metric is computed after a defined recovery period. Repeated events permit trend evaluation.

5.2 The Recovery Ratio

Recov(Z) = Z(recovery) / Z(baseline)
SHN = P10(Recov(Z) across all active segments)

A value of 1.0 indicates complete functional recovery. Values below 1.0 indicate residual degradation. SHN provides a pack-level resilience indicator robust to localised outliers in large cell assemblies.

5.3 Relationship to Existing Standards

StandardScopeGap addressed by SEFI-R
IEC 62133Safety; abuse testingNo non-destructive fault injection or recovery metric
IEC 62660Performance; cycle lifeNo resilience or recovery characterisation
ISO 12405EV traction battery testingNo segment-level fault injection or isolation validation
IEEE 1679Electrochemical energy storage evaluationNo fault proxy or recovery ratio defined
UN 38.3Transport safety; destructive abuse testsDestructive only; not applicable to resilience measurement

5.4 Recov(Z) vs DCIR

DCIR measures instantaneous electrical condition; Recov(Z) measures the system's ability to return to stable operation after a controlled perturbation. Two cells may exhibit similar DCIR values while having very different recovery characteristics. Recov(Z) may function as an earlier indicator of resilience loss before any corresponding rise in DCIR becomes measurable. This hypothesis requires experimental validation (identified as open question OQ-1).

5.5 Standardisation Pathway

Submission of SEFI-R as a new work item to IEC TC 21 or ISO TC 69 is proposed in §13. Without a shared testing method, certification frameworks, cross-manufacturer comparison, and insurance/warranty risk management frameworks cannot develop for segmented architectures.

§ 06

Fault Tolerance and Fail-Operational Design

PropertyFail-Safe (Conventional)Fail-Operational (RAID-Battery)
Fault detectionYesYes
Fault responseSystem shutdownSegment isolation + load rebalancing
Post-fault operationNoneDegraded mode with remaining segments
Performance after faultZeroProportionally reduced
Mission continuationNot possiblePossible (critical applications)

6A Physical and Electrical Resilience Architecture

6A.1 Electrical Isolation Layer (Guardian). The Guardian layer enforces hard limits on voltage, current, and temperature independently of the pack orchestrator, responding to boundary violations within defined time bounds: short-circuit isolation under 100 µs, overvoltage/undervoltage under 10 ms, over-temperature under 100 ms. Predictive isolation is triggered by thermal rise rate exceeding 2°C/s.

Three structural properties: determinism (all safety responses bounded in time by hardware constraints); independence (correct operation when the orchestrator is absent, crashed, or sending invalid commands); authority (no orchestrator command can override an active envelope violation).

6A.2 Thermal Containment Layer. Thermal runaway in a lithium-ion cell generates heat, flammable gases, and potentially sustained combustion at temperatures between 500°C and over 1000°C. Electrical isolation alone does not extinguish the exothermic reaction. The barrier system uses a hybrid material approach: aerogel (primary thermal insulation, 0.015–0.020 W/mK) combined with mica plate (mechanical support, 900–1000°C rated) and intumescent edge seals. Directed venting channels route evolved gases away from adjacent segments into a common manifold.

6A.3 Combined Protection. The Guardian's dT/dt trigger is the primary link: if the barrier begins to lose effectiveness, the Guardian triggers predictive isolation before the adjacent segment reaches its absolute limit. The barrier buys time; the Guardian uses that time. RAID-Battery achieves fail-operational behaviour only when electrical isolation and thermal containment are jointly satisfied.

§ 07

Ultra-Fast Charging in a Segmented Battery

1–2 MW charging in an 800 V system implies very large currents. In a monolithic pack, the constraints are: the weakest element limits the whole; large I²R thermal loads; uneven stress distribution. When an 80 kWh pack is divided into 16 segments, total power is distributed across segments — approximately 75 kW per segment on average for 1.2 MW charging. Power is distributed intelligently: healthy segments accept more; warm segments accept less; degraded segments receive only a small fraction.

A segmented battery in this context resembles a small internal electrical grid: energy node states are monitored in real time; load is routed safely; thermal stress and aging are balanced across segments; fault conditions do not collapse the entire charging session.

§ 08

Economic Logic: Yield, Grading, and the B-Grade Market

In a conventional series-based battery, the weakest cell constrains the whole — leading to aggressive cell grading, underpriced use of B- and C-grade cells, high testing requirements, and significant material waste. The battery industry's yield problem is a major structural cost driver.

When the system is fault-tolerant, slightly weaker but still functional cells can be used — increasing manufacturing yield, reducing sorting and grading costs, lowering warranty costs, and opening a new market for B+ grade cells currently difficult to place in premium applications.

RAID did for the disk industry what segmentation may do for batteries: the requirement for individual component perfection decreased; reliability emerged from the architecture; and the cost structure changed permanently.

§ 09

Barriers to Adoption

This suggests that the transition is likely to originate in niche applications — drones, eVTOL, specialised ground vehicles — before moving to premium EVs and eventually the mass market.

§ 10

System Resilience Assessment: Key Resilience Indicators

Component level
Strong — active node design
Risk: measurement/switch redundancy needed
System level
Strong — orchestrator logic
Risk: single orchestrator failure point
Temporal degradation
Uncertain — mixed-quality aging
Risk: segment-level aging tracking required
Scalability
Good — hierarchical potential
Risk: control architecture complexity
Market / regulatory
Weak — institutional barriers
Risk: certification and standards gap — the primary bottleneck
§ 11

Technology Adoption Roadmap

Near Term (1–3 Years)

Research prototypes of segmented pack architectures. Drone and eVTOL first deployments. SEFI-R-type validation tests on segmented demonstrators. Early publications establishing prior art and concept.

Medium Term (3–7 Years)

Premium EV and specialty vehicle applications. Segment-level fault management in commercial systems. First steps toward standardisation (IEC TC 21, ISO TC 69). Measurable improvements in serviceability and cycle lifetime.

Long Term (7–15 Years)

Broader adoption in the EV market. B-grade and B+ grade cells integrated within fault-tolerant architecture. Controlled segment-level implementation of 1–2 MW charging. Batteries evolving into programmable, upgradeable energy infrastructure.

Use Case Positioning

Immediately strong: Unmanned aerial systems and eVTOL (fault tolerance over peak energy density); heavy-duty industrial vehicles (serviceability over long asset life); stationary energy storage systems (mixed-grade and second-life cell populations).

Promising but requiring further evidence: Commercial electric fleets; premium electric vehicles; defence and critical infrastructure.

Not the right tool: High-volume consumer EVs optimising for maximum structural integration and minimum unit cost per kWh.

RAID-Battery is not the best battery — it is the best system when the battery is not permitted to fail.

§ 12

Conclusions

  1. Battery reliability can shift from the individual cell to the system architecture
  2. SEFI-R provides a promising foundation for testing and potential standardisation of segmented architectures
  3. Ultra-fast charging in a segmented battery is primarily a control and load distribution challenge, not solely a materials problem
  4. Production yield and total cost of ownership can improve significantly if the system tolerates weaker but still functional segments
  5. The future of the battery may more closely resemble an electrical grid or data center than a traditional chemical component
SP-003 — Core thesis

The battery is not, in the future, a single component — but a distributed, programmable, and fault-tolerant energy infrastructure.

§ 13

Proposed Further Development

§ 14

Strategic Conclusion

The RAID-Battery does not appear in this paper merely as a new battery product, but as a potential reference architecture for energy systems. Its significance is threefold: it transfers reliability from the individual cell to the system; it opens the possibility of using more aggressive cell chemistries and less perfect cell production; and it transforms the battery's role from a passive component to a software-managed, serviceable, and fault-tolerant infrastructure.

The question is not only about a continuation of battery technology, but about a possible new development trajectory in which electrochemistry, power electronics, embedded software, standardisation, and production economics converge into a single system-level innovation.

Ref

References

Appendix A

Simulation Results: Concept Validation

All simulations in this appendix are conceptual model results. They do not incorporate full electrochemical or thermal physics models. Results should be interpreted as indicative of system-level behaviour, not as validated performance metrics or certified design data.

A1. Fault Injection Behaviour

The simulation runs a 16-segment pack (12 A-grade, 4 B-grade) over 800 cycles under four fault injection profiles: no faults, one segment isolated at cycle 200, two faults at cycles 200 and 400, and three faults at cycles 200, 400, and 600. In all cases the orchestrator continues degraded-mode operation, redistributing load across remaining active segments. Each fault removes approximately 6.25% of total pack capacity. No full system shutdown occurs in any scenario.

Key result: The fail-operational envelope holds across all tested fault counts. This provides quantitative support for the working paper's central claim that system reliability can be transferred from the individual segment to the architecture.

A2. Fast-Charge Thermal Stress

The simulation compares four operating profiles under both default Health Score weights and a thermal-heavy weighting (w₄ = 0.45). The thermal factor routes load away from hot segments in real time, without any hardware change.

Key result: The same physical hardware exhibits meaningfully different thermal behaviour depending on orchestrator weight configuration. This supports the concept of the RAID-Battery as a software-defined energy system in which operational profile is a software parameter, not a hardware constraint.

A3. Economic Monte Carlo Analysis (3,000 runs)

A Monte Carlo simulation compares the total manufacturing and warranty cost of a conventional all-prime-cell pack against a RAID-Battery pack accepting B-grade cells in 2–4 of 16 segments.

Table A3 — Key Assumptions
ParameterValue
A-grade cell cost80 €/kWh
B-grade cell cost52 €/kWh (35% discount)
Pack assembly18 €/kWh
Sorting cost — conventional4 €/kWh
Sorting cost — RAID1 €/kWh
Control electronics overhead~480 € per pack
Warranty event cost — conventional600 € (full pack)
Warranty event cost — RAID150 € (segment-level)
Table A3b — Results Summary (3,000 Monte Carlo runs)
MetricConventionalRAID-BatteryDelta
Median pack cost113.3 €/kWh104.8 €/kWh−8.5 €/kWh
90% CI on saving[2.1, 14.9] €/kWh
RAID lower cost98% of scenarios
Manufacturing yield improvement+6.0 pp median

Key result: The cost case is driven primarily by B-grade cell acceptance and reduced warranty exposure, and holds robustly across the simulated parameter range even with added electronics cost.

Appendix B

Indicative Case Study: Electric Forestry Machine, Kuopio Region

All values in this appendix are indicative estimates based on publicly available industry data and operational experience from Finnish forestry operations. They are not based on measured data from a specific vehicle or operator. Purpose: order-of-magnitude illustration only — not a business case or investment recommendation.

B1. Application Context

Finnish forestry machines — harvesters and forwarders — represent a demanding application environment that aligns well with RAID-Battery properties. Machines operate in two-shift patterns (up to 16 hours/day) across a Nordic climate ranging from approximately −16°C in January to +24°C in July in the Kuopio region. Downtime is expensive: a productive harvester generates estimated revenue of 150–220 €/h, and a single pack-level failure can result in three or more days of lost productivity. Asset lives of 10–15 years are normal.

This case study models a 120 kWh electric harvester with a 20-segment RAID-Battery pack (16 A-grade, 4 B-grade) operating 240 working days per year over a 12-year asset life. A conventional all-prime-cell pack of identical nominal capacity is the comparison baseline.

B2. Cold-Weather Capacity Management

Battery capacity derates approximately 1.2 percentage points per °C below 15°C. At the January average of approximately −12°C, this implies derating to ~68% for a conventionally managed pack. A RAID-Battery orchestrator can selectively pre-warm only segments scheduled for immediate high-load operation. Conservative recovery estimate: +4 percentage points → approximately 72% usable capacity in January conditions.

B3–B4. Lifecycle Cost Model and Indicative Results

Table B3 — 12-Year Lifecycle Cost Comparison (Indicative)
Cost categoryConventionalRAID-Battery
Initial pack cost~12.8 k€~12.5 k€
Scheduled replacements (×2)~84.0 k€ (years 5 + 10)Segment swaps only
Unscheduled downtimeSignificant (3+ days/event)Reduced (0.25 days/segment event)
Total 12-year cost (indicative)~156.7 k€~52.5 k€
Indicative 12-year saving~104 k€ (~66% of conventional cost)

The saving is driven primarily by elimination of full-pack replacement events and reduction in unscheduled downtime — not by the initial cost difference.

B5. Limitations

Results are sensitive to assumed downtime cost rate, failure interval, and pack replacement cost. The cold-weather recovery of 4 percentage points has not been validated against a physical system. Segment swap cost of ~2,800 € assumes field-replaceable modules — an architectural assumption not yet proven in a production design.

Appendix E

Methodology and Assumptions

E1. Nature of This Work

This is a concept-level system architecture paper. It describes a proposed approach to battery pack design and control, supported by logical argument, simulation modelling, and comparison with analogous systems in other engineering domains. It does not present measured data from a physical prototype. All quantitative results in Appendix A (simulation) and Appendix B (lifecycle cost) are model outputs, not measurements.

E2. Simulation Methodology

Simulations are implemented in Python using a population-based segment model (16–20 segments with realistic spreads for capacity, internal resistance, recovery metric, and temperature). Health Score formula and load allocation logic are direct implementations of §4 definitions. Aging dynamics are load-proportional with grade-specific multipliers. These are structural models — they capture system-level behaviour but do not model lithium-ion chemistry, thermal physics, or degradation mechanisms at the electrode level. The economic Monte Carlo (3,000 runs) uses assumed parameter distributions; not based on audited cost data.

E3. Claims and Their Basis

ClaimBasisConfidence
Fail-operational behaviour under multiple segment faultsSimulation (Appendix A)High at system logic level; not validated with real electrochemistry
Thermal containment prevents propagationEngineering analysis (Appendix B material properties)Moderate; requires physical TR test to confirm
Recov(Z) provides earlier degradation signal than DCIRHypothesis (electrochemical reasoning §5.5)Low; requires experimental validation (OQ-1)
8.5 €/kWh median cost savingMonte Carlo model with assumed parametersOrder-of-magnitude plausible; sensitive to segment swap cost assumption
SEFI-R addresses gap in existing standardsComparison with IEC/ISO/IEEE/UN standards (§5.3)High; no identified standard covers non-destructive fault injection + recovery quantification

E4. What This Paper Does Not Claim

Appendix F

Terminology and Definitions

TermDefinition
DCIRDC Internal Resistance. Standard proxy for cell health and power delivery capability. Does not capture dynamic recovery behaviour after a disturbance.
Degraded modeSystem operating state in which one or more segments have been isolated but remaining active segments continue to deliver power at reduced total capacity. Synonymous with "fail-operational" in this context.
Envelope ProtectionThe Guardian layer's continuous enforcement of hard limits on segment voltage, current, and temperature. Active in all states. Cannot be overridden by the Orchestrator.
Fail-operationalSystem property by which the system continues to deliver useful output after a fault event, at potentially reduced performance. Distinguished from fail-safe (system stops).
Freshness counter8-bit monotonically incrementing counter in every CMD frame. Guardian rejects frames not strictly greater than last accepted value, preventing replay attacks.
Guardian layerDeterministic firmware layer at the segment controller (SCU) bare-metal level. Implements Envelope Protection, state machine, and L-MAC validation.
Health Score (HS)Real-time normalised composite indicator (0–1) for each segment. Weighted sum of capacity ratio, DCIR factor, Recov(Z), and thermal factor. Used by Load Allocation Engine.
L-MACLightweight Message Authentication Code. Per-message authentication mechanism for Guardian–Orchestrator communication. Based on AES-CMAC or HMAC-SHA256 with 32-bit truncated tag.
Micro-SEFISoftware-based scheduled SEFI-R-type perturbation during low-demand windows. Provides updating Recov(Z) value as a continuous maintenance parameter.
OrchestratorUpper software layer running on Linux-based SBC or equivalent. Responsible for Health Score computation, load allocation, micro-SEFI scheduling, system-level diagnostics. Permitted to fail and restart.
Recov(Z)SEFI-R Recovery Ratio: Z(recovery) / Z(baseline). Value of 1.0 = complete functional recovery. Values below 1.0 = residual degradation. Primary resilience input to Health Score engine.
SEFI-RSegment-Event Fault Injection and Recovery. Non-destructive test methodology. Zenodo DOI: 10.5281/zenodo.14940723.
SegmentElectrically and control-logically independent subdivision of the battery pack. Contains its own cell group, sensing, local switching, and a segment controller (SCU/Guardian). Basic unit of fault isolation.
SHNSystem Health Number. 10th percentile of Recov(Z) values across all active segments. Pack-level resilience indicator robust to localised outliers.
Thermal barrierPhysical inter-segment separation interrupting thermal runaway propagation. Composed of aerogel insulation, mica plate, and intumescent edge seals.
TTLTime-to-Live. Field in CMD frame specifying validity period (1–500 ms). Guardian reverts to fallback profile when TTL expires without renewal.
Appendix G

Development Methodology and AI Contribution Statement

G1. Development Process

This work was developed through an iterative process of human-led system design, analysis, and decision-making, with AI-assisted structuring, writing, simulation implementation, and document production. The conceptual contributions — the RAID analogy applied to battery architecture, the SEFI-R methodology, the two-layer Guardian–Orchestrator control architecture, and the use case positioning — originated from and were directed by the human author throughout.

G2. AI Tool Contribution

Claude (Anthropic, claude-sonnet-4 series) was used as an AI assistant throughout the development process for: document structuring and drafting from human-provided outlines; simulation code generation in Python; Word document generation; prior art search assistance; cross-referencing consistency checks; and technical writing in English.

The AI did not originate the core technical concepts, did not make independent architectural decisions, and did not determine the scope or direction of the work. All substantive technical choices were made by the human author.

G3. Attribution Statement

Developed through human-led system design and AI-assisted validation, structuring, and document production. The intellectual contribution, conceptual direction, and all technical decisions are those of the human author. AI tools were used as productivity instruments, not as independent contributors.

Suggested citation acknowledgement for derivative works:
"Developed through human-led system design with AI-assisted documentation and simulation structuring (Anthropic Claude, March 2026)."

G4. Reproducibility

Python simulation source code is available in the Zenodo repository alongside the SEFI-R disclosure (DOI: 10.5281/zenodo.14940723). All simulation parameters are documented in the code. Results are reproducible by running the provided scripts with Python 3.11+, numpy, matplotlib, scipy. Results are deterministic (fixed random seed).

License: Creative Commons CC BY 4.0 — Released for open discussion. Not a patent application.
Related disclosure: SEFI-R v1.0, Zenodo DOI: 10.5281/zenodo.14940723
Competing interests: None declared.