A.E.G.I.S.
Documentation. Proof. Runbooks. Skills tied to real work.

Forge is where the receipts live.

This is the A.E.G.I.S. documentation hub. Every meaningful change gets captured here: what I built, why I built it, how I validated it, what broke, and how I fixed it. If it isn’t in Forge, it isn’t done.

01
Logs
Build notes, decisions, results, and next actions.
02
Proof
Screenshots, diagrams, benchmarks, dashboards.
03
Runbooks
Repeatable setup + recovery procedures.
Forge Console
TRUTH
RULE If it isn’t documented, it didn’t happen
FORMAT Problem → Build → Verify → Notes
EVIDENCE Screenshots + commands + configs
Logs
Chronological progress with tags and next steps.
/forge/logs/
Proof
Artifacts that show outcomes, not claims.
/forge/proof/
Skills
Skill map linked to logs + proof.
/forge/skills/
Runbooks
Setup + recovery procedures that reduce chaos.
/forge/runbooks/
Proxmox
Security
Dashboards
SQL
PHP
Automation

How to use Forge

If you’re browsing to understand what I can do, start with Proof, then jump into the linked log entries, then check the runbook if you want the repeatable process.

Start with Proof

Dashboards, screenshots, diagrams, and benchmarks that show outcomes.

Go to: /forge/proof/

Follow the Logs

Chronological work notes: decisions, tradeoffs, and next actions.

Go to: /forge/logs/

Steal the Runbooks

Checklists and recovery procedures that keep the build stable.

Go to: /forge/runbooks/

Forge sections

Everything here ties back to real builds inside Catalyst, Sentinel, and Atlas.

Logs

Build logs with clear structure: what changed, why, how it was verified, and what’s next.

  • Tags for fast browsing
  • Links to proof artifacts
  • Next actions included

Proof

Artifacts that show results: screenshots, diagrams, charts, benchmarks, and deployments.

  • Dashboards and charts
  • Network and architecture diagrams
  • Before/after comparisons

Skills map

Skills aren’t listed as claims. Each skill links to a log entry and proof artifact.

  • Tools and stacks used
  • Where it was applied
  • Evidence attached

Runbooks

Step-by-step procedures that reduce chaos: setup, maintenance, and recovery.

  • Disaster recovery basics
  • Standard operating procedures
  • Repeatable configurations

Want the fastest route to “what’s impressive”?

Proof first. Then read the linked log entry for context and validation.

View proof

Back to the modules

Forge documents the work. The modules are where the systems live.

Catalyst = health tracking. Sentinel = security workflows. Atlas = telemetry + geospatial layer.

Quick module links

Tip: As content grows, keep Forge navigable with tags and consistent log templates.