---
id: add-spoke-reconnecting-state
name: Add Spoke 'reconnecting' Status or Document DB-Free Approach
status: completed
depends_on: []
scope: narrow
risk: low
impact: isolated
level: implementation
---

## Description

W06: The spoke status enum is only `connected`/`disconnected`. The spoke-runner.md describes a reconnection flow, but there's no `reconnecting` state. A spoke with a dropped WebSocket shows `disconnected`, indistinguishable from a permanently offline spoke.

Either add `reconnecting` to the spoke status enum, or document that reconnection is handled at the application layer (WebSocket reconnect timer) without a DB state change.

## Acceptance Criteria

- [ ] Either `reconnecting` added to `spokes.status` enum in `spokes.md` and `table-reference.md`, OR
- [ ] Document explicitly that reconnection is application-layer-only (no DB state change) with rationale
- [ ] `spoke-runner.md` reconnection flow section references the decision

## References

- docs/reviews/storage-architecture-review-2026-04-21.md#W06
- docs/architecture/storage/spokes.md:18
- docs/architecture/spoke-runner.md:130-136

## Notes

> To be filled by implementation agent

## Summary

> To be filled on completion