A.E.G.I.S.
Setup, maintenance, and recovery procedures.

Forge Runbooks: written for future-you under pressure.

Runbooks turn systems into something you can rely on. These are step-by-step procedures for deploying, maintaining, and recovering A.E.G.I.S. components without guessing.

Back to Forge Browse runbooks
01
Repeatable
Steps work the same every time.
02
Concrete
Commands and actions, not theory.
03
Stress-proof
Readable at 2am when things break.
Runbook Console
OPS
RULE No memory required
FORMAT When → Steps → Verify → Notes
GOAL Stability
Logs
Proof
Skills

Runbooks

Each runbook defines when to use it, exact steps to follow, how to verify success, and notes for future improvement.

Deploy AEGIS site updates · AEGIS Core / Forge

Safely deploy updates to aegis.nathan-patterson.com without breaking navigation or shared assets.

When to use: After layout, content, or structural changes

Steps

  1. Pull latest changes locally and review diffs.
  2. Verify file paths and includes are correct (especially relative paths).
  3. Upload changed files to the correct subdirectories.
  4. Hard refresh and test key pages: /, /forge, /forge/logs, /forge/proof, /forge/skills, /forge/runbooks.
  5. Check mobile navigation and footer links.

Verify

  • No PHP errors displayed.
  • Navigation links resolve correctly.
  • Shared CSS and JS load once and apply consistently.

Notes

  • Keep landing pages stable. Living content belongs in Forge.
  • Avoid editing shared assets unless multiple sections benefit.

Permalink: /forge/runbooks/#rb-site-deploy

Create a new Forge log entry · Forge Logs

Document work using the standard Problem → Build → Verify → Next format.

When to use: After completing a meaningful build or change

Steps

  1. Define the real problem or trigger.
  2. List concrete build actions taken.
  3. Describe how the result was verified.
  4. Capture next actions while context is fresh.
  5. Assign consistent tags.

Verify

  • Log entry expands/collapses cleanly.
  • Tags align with existing taxonomy.
  • Permalink works and is shareable.

Notes

  • If there is no proof artifact yet, add one or mark it as pending.
  • Logs are chronological, not polished essays.

Permalink: /forge/runbooks/#rb-log-entry

Add a proof artifact · Forge Proof

Add screenshots, diagrams, or benchmarks and link them back to the originating log entry.

When to use: When a build produces a visible result

Steps

  1. Capture the artifact (screenshot, diagram, chart, etc).
  2. Place the file in /assets/img or a structured subfolder if needed.
  3. Add a new artifact entry in forge/proof/index.php.
  4. Link the artifact to the related log permalink.
  5. Confirm tags match the log entry.

Verify

  • Artifact opens correctly.
  • Log link resolves to the correct entry.
  • Summary accurately reflects the artifact.

Notes

  • Artifacts prove outcomes, not effort.
  • Prefer fewer, clearer artifacts over many noisy ones.

Permalink: /forge/runbooks/#rb-proof-artifact

Update the skills map · Forge Skills

Ensure skills are mapped to real evidence and remain current.

When to use: After adding new logs or proof that demonstrate a capability

Steps

  1. Identify the skill demonstrated by the work.
  2. Add or update the skill entry in forge/skills/index.php.
  3. Link at least one log and one proof artifact.
  4. Assign relevant tags.

Verify

  • Skill has no broken links.
  • Skill is not duplicated under multiple names.
  • Skill description matches actual usage.

Notes

  • Never list skills without receipts.
  • Refactor categories occasionally to keep them readable.

Permalink: /forge/runbooks/#rb-skill-update