A.E.G.I.S.

A.E.G.I.S.

Asset Enhancement & Geospatial Information Systems

A.E.G.I.S. is a personal system and technical portfolio. It’s where I build and document the tools I use to track health, monitor my environment, and visualize what’s going on over time.

Overview

  • Scope: health + performance (Catalyst), homestead awareness (Sentinel), visualization (Atlas)
  • Documentation: build logs, artifacts, and runbooks in Forge
  • Default approach: local-first, modular, and documented as it evolves
Systems Latest updates

Systems

A.E.G.I.S. is split into modules so each part can be built, tested, and improved without turning into one big mess.

Catalyst

Health and performance tracking: training, nutrition, biometrics, habits, and reviews.

  • Inputs: workouts, intake, sleep, steps
  • Outputs: trend views and weekly adjustments

Sentinel

Homestead awareness: surveillance, identity/vehicles, airspace (ADS-B), weather, and future robotics.

  • Inputs: video, sensors, ADS-B, telemetry
  • Outputs: timeline, summaries, rule-based alerts

Atlas

Visualization and context: maps, timelines, overlays, and correlations across systems.

  • Where and when
  • Trends over time

Forge

Documentation: logs, artifacts, skills mapping, and runbooks. If it isn’t documented here, it’s not real.

  • Logs: what changed and why
  • Runbooks: repeatable procedures

Start here

If you want substance over summaries, go straight to the logs and follow the chain from change → artifacts → next steps.

Forge logs

Roadmap

Built in phases so the system stays usable at every step. Tracking and visibility first, then cleanup, then automation.

  1. Phase 1

    Visibility

    Get the core inputs online and reliably logged. No fancy layers until the data is consistent.

  2. Phase 2

    Rules

    Reduce noise with clear thresholds, schedules, zones, and retention policies.

  3. Phase 3

    Visualization

    Build views that make trends obvious: maps, timelines, and summaries that answer “what changed?”

  4. Phase 4

    Automation

    Add lightweight automation where it removes friction, not where it adds complexity.

Updates and documentation

Updates are the change history. Documentation is how the system stays maintainable.

Updates

Chronological logs of what changed, why it changed, and what happened next.

  • Build notes
  • Decisions and tradeoffs
  • Verification and next steps

Docs

Runbooks and notes designed to be followed when something breaks or when rebuilding from scratch.

  • Setup procedures
  • Maintenance routines
  • Recovery steps
Open Forge Back to top