# SafeRouter Home

A local router project that connects an owner interface with controlled network-policy changes and recovery after interrupted updates.

- Role: Product requirements, network-policy workflow and AI-assisted engineering.
- Status: Engineering alpha
- Status code: engineering-alpha
- Case page: https://oleksii.almalvs.online/work/saferouter-home
- Reviewed: 2026-09-06

## Problem

Home network controls need to explain what changed, preserve owner access and recover when an update is interrupted.

## Constraints

- Keep core operation local
- Apply configuration changes as controlled transactions
- Distinguish service health from verified network protection

## Architecture

- Owner request
- Policy validation
- Apply and confirm
- Recovery if interrupted

## Decisions

- Keep configuration changes reviewable
- Record interrupted transactions for recovery
- Expose the limits of each reported status

## Evidence

- OpenWrt router stack and owner interface
  - Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.
  - Sources: None published.
- Policy transaction and recovery contracts
  - Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.
  - Sources: None published.
- Browser and network-contract test suites
  - Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.
  - Sources: None published.

## Safety and boundaries

- Engineering alpha, not a certified security product
- Device identity and owner-access recovery remain areas for further work
- Installed packages do not prove filtering or VPN enforcement; hardware and traffic checks are required

## Stack

- OpenWrt
- Linux
- nftables
- UCI
- Local web UI
- Transaction recovery

## Media

![SafeRouter alpha owner interface with household modes and device assignment controls.](https://oleksii.almalvs.online/images/evidence/saferouter-runtime.png)

Archived alpha UI test screenshot with sample state. The green protection message is an identified UI limitation, not evidence of verified household protection.

## Credits

- None published.

## Public sources

- None published.

## Related projects

- [ecogen-controller](https://oleksii.almalvs.online/work/ecogen-controller)
- [mac-bid-research](https://oleksii.almalvs.online/work/mac-bid-research)

## Engineering baseline

Canonical case section: [https://oleksii.almalvs.online/work/saferouter-home#result](https://oleksii.almalvs.online/work/saferouter-home#result)

SafeRouter combines a local owner interface with a router stack for controlled policy changes. The implementation includes transaction guards, persistent records of interrupted changes and boot recovery hooks.

Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.

Sources:
- None published.

## Changing a network safely

Canonical case section: [https://oleksii.almalvs.online/work/saferouter-home#workflow](https://oleksii.almalvs.online/work/saferouter-home#workflow)

A requested change passes through validation, application and confirmation. Recovery is part of that process, so an interrupted configuration update has a defined path back. Core operation does not depend on a cloud service.

Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.

Sources:
- None published.

## Alpha boundaries

Canonical case section: [https://oleksii.almalvs.online/work/saferouter-home#boundary](https://oleksii.almalvs.online/work/saferouter-home#boundary)

The project still needs work on owner-access recovery, device identity and accurate status reporting. Service health alone cannot establish that a household is protected. Filtering, routing and recovery need verification on the actual hardware and traffic path before a broader pilot.

Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.

Sources:
- None published.