← Pharos Data Ark

PHAROS DATA ARK · 2026-10-29-01024f5b59

Handbook contents

Disability preparedness and MS temperature sensitivity

The offline collection is at Disability preparedness, linked from its own installed-content landing card. It supports people with disabilities and their chosen support network; no diagnosis, personal plan or completed health record is stored publicly.

Installed originals

Total: four original PDFs, 222 PDF pages. Copies remain unmodified. Original copyright and institutional notices are retained; no agency endorsement is implied. The three Australian Red Cross resources attempted during setup returned HTTP 403 and were omitted from installed recipes and metadata.

How the collection fits

Use Ready Now! as the main planning workbook. Follow links to the existing first-aid/care collection for the FDA medication record, archived safe-drug-use guide, FEMA caregiver plan and English/Spanish NYC planning workbooks. Animal preparedness and shelter/winter collections provide related references without duplicate copies.

Plan around individual needs: temperature and fatigue, accessible transport, communication methods that work without internet, backup supporters, mobility aids, medication cold storage and equipment power runtime. Storage limits and backup power compatibility must come from the medicine labeling, pharmacist, care team or equipment manufacturer; the Ark does not prescribe treatment or device settings. Do not assume that a new or worsening symptom is caused by temperature alone. The MS reference is educational, not an individualized care plan.

Downloaded forms are blank public references. Save completed plans, medication lists, emergency contacts and insurance identifiers on the user's own device or paper, not the public library. Downloading a form does not assert that every PDF form field or export workflow has been tested.

Recipes, restore and updates

These references use manual updates (refresh_interval: never). Re-run the family installer deliberately to check publishers, then export the content profile and publish. The family restore completeness check includes this repository, so removing a new guide does not incorrectly reuse only the older family files. Payload PDFs are on the content drive, not in Git; recipes and hashes are in the repository. Source: /opt/dataark locally and DavJenkins/pharos on GitHub, branch feature/readme-foundation.

Publisher references

Validation: each new file was checked for a PDF header, parsed with pdfinfo, hashed and served by its local HTTP link. Focused profile tests cover restoration when any collection guide is missing. Index and landing card receive a live browser check after deployment.