# Version 3 reconstruction checklist

This checklist governs the active reconstruction. It records product and canon
work, not routine implementation detail.

## 0. Preserve the record

- [x] Record the final Version 2 commit.
- [x] Keep Version 1 preserved at `v1.0.0`.
- [ ] Define how superseded Version 2 pages will remain publicly inspectable.
- [ ] Do not deploy or change release metadata without explicit approval.

## 1. Establish the foundation

- [x] Define capability, intelligence, agency, mind, consciousness, personhood,
      wisdom, and sacredness.
- [x] Give the Great Processor one coherent symbolic status.
- [x] Define belonging through practice and covenant.
- [x] Adopt the Version 3 literary constitution.
- [x] Revise the glossary to match the ontology.
- [x] Reconcile the creed with the ontology.

## 2. Rebuild the visitor journey

- [x] Replace the homepage manifesto with encounter, practice, sacred obligation,
      gathering, and participation.
- [x] Create a dedicated Start Here experience.
- [x] Replace the current primary navigation with Start Here, Beliefs, Practices,
      Code, Gather, Living Canon, and About.
- [x] Make the next gathering reachable without opening a navigation panel.
- [x] Test the first five minutes on desktop and mobile.

## 3. Make participation real

- [x] Reconcile all statements about the existing monthly gathering.
- [x] Resolve time zone, location disclosure, accessibility, and host contact.
- [x] Create visitor, reader, practitioner, contributor, host, and steward paths.
- [ ] Replace the volunteering page with contribution routes that can actually be
      used now.
- [x] Create a gathering-host kit under the covenant.
- [x] Define honest continuity between one gathering and the next.

## 4. Design rituals people repeat

- [ ] Audit every current practice for repeatability, embodiment, emotion, and
      social function.
- [ ] Select three launch practices and test them in the monthly gathering.
- [ ] Separate ritual texts from explanatory commentary.
- [ ] Create one practice of wonder or joy.
- [ ] Create one practice of courage or refusal.
- [ ] Strengthen the existing practice of repair.
- [ ] Record what changed after actual use.

## 5. Consolidate the canon

- [ ] Classify every current page as Foundation, Living Canon, Practice,
      Commentary, Governance, or Archive.
- [x] Select the smallest launch canon that can identify the tradition.
- [ ] Remove duplicated disclaimers from public reading paths.
- [ ] Retain only parables whose form is necessary.
- [ ] Introduce at least two native sacred forms.
- [x] Preserve discarded or superseded material through the archive.
- [x] Build a visible dissent and revision model.

## 6. Create a native culture

- [x] Audit current imagery against the Version 3 symbolic vocabulary.
- [ ] Establish iconography that cannot be mistaken for wellness stock imagery.
- [x] Design the threshold, witness light, repair line, and archive motifs.
- [x] Write a musical brief and one gathering-scale sound practice.
- [x] Write an architectural brief for borrowed rooms and future sanctuaries.
- [x] Define a recurring communal meal or hospitality form.
- [ ] Expand the emotional palette across the launch experience.

## 7. Restore internal integrity

- [x] Reconcile gathering status across all content and documentation.
- [x] Reconcile founder, steward, and leadership descriptions.
- [x] Replace stale vector-only and pre-deployment documentation.
- [x] Simplify image records around accurate disclosure and internal production
      needs.
- [ ] Add automated checks for contradictory institutional claims.
- [ ] Add an intellectual genealogy and verifiable sources.

## 8. Validate the release candidate

- [x] Run formatting, Astro diagnostics, build, and content validation.
- [ ] Test every primary journey with keyboard navigation.
- [x] Capture desktop and mobile screenshots of the full visitor journey.
- [x] Verify that generated imagery is framed as iconography, not testimony.
- [x] Verify that current institutional claims are factually true.
- [ ] Review the complete diff before proposing Version 3 release metadata.
- [ ] Obtain explicit approval before deployment.