Start with Proof
Dashboards, screenshots, diagrams, and benchmarks that show outcomes.
Go to: /forge/proof/
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.
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.
Dashboards, screenshots, diagrams, and benchmarks that show outcomes.
Go to: /forge/proof/
Chronological work notes: decisions, tradeoffs, and next actions.
Go to: /forge/logs/
Checklists and recovery procedures that keep the build stable.
Go to: /forge/runbooks/
Everything here ties back to real builds inside Catalyst, Sentinel, and Atlas.
Build logs with clear structure: what changed, why, how it was verified, and what’s next.
Artifacts that show results: screenshots, diagrams, charts, benchmarks, and deployments.
Skills aren’t listed as claims. Each skill links to a log entry and proof artifact.
Step-by-step procedures that reduce chaos: setup, maintenance, and recovery.
Proof first. Then read the linked log entry for context and validation.
Forge documents the work. The modules are where the systems live.
Catalyst = health tracking. Sentinel = security workflows. Atlas = telemetry + geospatial layer.
Tip: As content grows, keep Forge navigable with tags and consistent log templates.