A.E.G.I.S.
Homestead awareness. Local-first. Built in public.

Sentinel is my homestead monitoring and situational awareness layer.

This is the part of A.E.G.I.S. that watches what matters and ignores what doesn’t. Cameras, sensors, airspace awareness (ADS-B), weather monitoring, and eventually drones. The goal is simple: fewer surprises, less noise, and a setup I can trust.

See the systems Read the build logs
01
Signal over noise
Fewer false alerts. Better rules. Cleaner event history.
02
Local-first
Processing and storage stay on my hardware by default.
03
Documented build
Dashboards, screenshots, diagrams, configs, and notes as I go.
Sentinel Console
LOCAL
MISSION Awareness without chaos
INPUTS Video • Sensors • ADS-B • Weather
OUTPUT Alerts • Timeline • Dashboards
Surveillance
Zones, detections, event timeline.
/sentinel/surveillance/
Identity & Vehicles
LPR, known household, rules.
/sentinel/identity/
Airspace
ADS-B awareness and logging.
/sentinel/airspace/
Weather
Local node telemetry and trends.
/sentinel/weather/
Last update:
Event timeline
Rule-based alerts
Dashboards
Automation hooks

Sentinel systems

These are separate on purpose. Different data sources, different rules, different risk profiles. Keeping them modular makes the whole system easier to maintain and easier to improve.

Surveillance

Cameras, zones, detections, and an event timeline that’s actually usable. This is where “signal over noise” matters the most.

  • Motion and object detections
  • Zones and schedules
  • Event timeline and review

Identity & Vehicles

License plates and known household rules. The point is not to be weird. The point is to know if a known vehicle is home and to flag unknowns cleanly.

  • Known household list
  • Unknown vehicle events
  • Retention and cleanup rules

Airspace (ADS-B)

Aircraft awareness for situational context. I want a simple view of what’s overhead and the ability to log it if I need to.

  • ADS-B feed and map view
  • Basic logging and summaries
  • Optional alerts later

Weather monitoring

Local weather node data and trends. This is also one of the cleanest ways to show real telemetry work without turning the project into a debate.

  • Temperature, humidity, wind, rain
  • Charts and trend lines
  • Storm and lightning awareness later

Robotics layer

Drones and rovers are planned, but they stay phased and safety-locked. When that part starts, it gets its own section and runbooks.

Runbooks

How I’m building Sentinel

I’m doing this in phases so it stays real and manageable. Basic visibility first, then clean alerts, then automation, then robotics.

  1. Phase 1

    Visibility

    Get the feeds and data sources online. Build a basic timeline and dashboards that don’t lie.

  2. Phase 2

    Rules

    Zones, schedules, and sane alert rules. Reduce noise until it’s actually useful.

  3. Phase 3

    Automation

    Notifications, escalations, and workflow glue so I spend less time babysitting.

  4. Phase 4

    Robotics

    Aerial and ground systems for checks and patrols, with hard safety constraints and runbooks.

Want the good stuff?

The cool part is not the buzzwords. It’s the actual build. Logs, screenshots, diagrams, configs, and runbooks as this grows.

If you’re browsing Sentinel for capability, jump into the Forge and follow the chain from log → artifacts.

Quick links
Sentinel logs Artifacts Skills map Runbooks

Note: wording on the other pages will get tightened up later so everything matches this tone.