This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Preservation Status Dashboard

Last reviewed: 2026-07-16 · Owner: Ryuu · Review cadence: monthly and after every verified baseline

This dashboard reports evidence, not aspiration. A green cell means the named evidence exists and was checked; it does not make unrelated cells green.

System	Source mirror	Client/release artifact	Compatibility evidence	Runnable baseline	Offline recovery	Owner / next action
LandSandBoat	🟢 Forgejo/local mirror at 34a92a55…; verified bundle	🔴 No cataloged client snapshot	🔴 #9	🔴 #7	🟢 Bundle 330bb351… verified	Ryuu · complete client intake
Project Meteor	🟢 Mirror 01f76bce…; verified bundle	🔴 1.23b client metadata/assets missing	🟠 Requirement known; #10	🔴 #3	🟢 Bundle 9d186358… verified	Ryuu · preserve legacy dependency set
Sapphire	🟢 Mirror eac3c982…; verified bundle	🔴 Versioned SqPack snapshot missing	🟠 Safe-start rule known; #11	🔴 #4	🟢 Bundle 4be9757f… verified	Ryuu · map revision to data version
TrinityCore 3.3.5	🟢 Forgejo full-history mirror contains d1ebb092…	🔴 Authorized build-12340 snapshot missing	🟠 Requirement known; no runtime proof	🔴 #13	🟠 Full local bundle not yet captured	Ryuu · restricted client intake and Linux test host
TrinityCore master	🟢 Forgejo full-history mirror contains fd9c4868…	🔴 No pinned retail snapshot	🔴 #8	🔴 #8	🟠 Full local bundle not yet captured	Ryuu · retain first exact known-good pair
Aura Kingdom	🟢 Mirror 6d36aabf…; verified bundle	🟠 Release-link inventory exists; files have gaps	🔴 #12	🔴 #12	🟢 Bundle bc93db2b… verified	Ryuu · resolve each release profile in #5
X-Legend legacy collection	🟢 Eight primary server archives SHA-256/CRC verified and read-only	🟠 Paired clients exist for some supplemental profiles; several clients/auth sets missing	🟠 All primary layouts and available base schemas smoke-tested; exact gaps inventoried	🔴 No matched-client baseline promoted	🟠 Immutable originals and manifests on Pi; independent offline copy not yet recorded	Ryuu · recover clients/auth data listed in the compatibility ledger

Legend

• 🟢 Verified: evidence exists, has an integrity check, and is linked or inventoried.
• 🟠 Partial: capture or documentation exists, but an explicit verification or dependent artifact is missing.
• 🔴 Missing/blocked: the required artifact or test is not available. Follow the linked issue.

Program status

Control	State	Evidence / action
Forgejo labels and milestones	🟢 Complete	15 labels; Preservation foundation, TrinityCore 3.3.5 P3 baseline, and 2026 Q3 restore drill milestones.
Preservation gap tracking	🟢 Complete	Issues #1–#13 created and assigned.
Mirror inventory	🟢 Live	Mirror Inventory records source, Forgejo mirror, refs, and offline checkpoints.
Machine-readable catalog	🟢 Implemented	Stored under preservation/catalog/ in the main repository and checked in CI.
Wiki quality automation	🟢 Implemented	Broken links, placeholders, profile fields, duplicate IDs, review dates, YAML schemas, and checksums are validated.
Scheduled wiki bundle	🟢 Implemented	Workflow creates and verifies a dated wiki Git bundle; same-instance artifacts are not an independent backup.
Independent restore drill	🔴 Not completed	Tracked by #6.

Update this page only from evidence. Closing an issue without linking a manifest, test, or recovery record does not change a red or amber cell.