Pagan Homeland Collaboration Wayfinder
Archive Map
Find PHC folders, records, templates, dossiers, savepoints, Drive maps, source anchors, and build assets.
Use this page when you need to locate a file, understand the Drive structure, find a template, check the archive, or avoid rebuilding work that already exists.
Current Archive Status
Phase 0 System BuildCurrent Use
PHC is currently in Phase 0: Administrative readiness / credibility.
Archive Map is part of the internal system build. Its purpose is to help people navigate the PHC Drive structure and preserve institutional memory.
Tested source-layer links are now connected for the PHC Root Folder, all main PHC Drive folders, key governance tracking records, the Continuity + Savepoint Index, the Signal Log Tracker workbook, Muninn Drive Map, Build Notes, Page Navigation Map, Code Blocks Folder, Graphics + UI Assets, Command Overview, Board Briefing Station, current Board Report, Board Report Item Form, Board Status Report Template, 08_MEETINGS + RECORDS, Input Console live form routes, operations protocol records, property-stage folders, property review tools, property dossier records, resource / funding records, external relations records, partner support records, SHEAVES Records stub, PUN Notes stub, SHEAVES Portal, PUN Site, Business Plan 2.0, Business Plan 1.0, Board Minutes Recovery, and STEP 129 Board Minutes Recovery architecture records.
Muninn is the current Drive Map / memory layer. Huginn gathers. Muninn remembers. Neither approves action.
Not Approved Here
Finding a file through Archive Map does not approve spending, acquisition, fundraising, property control, formal partnership, public statement, savepoint records as Board action, Drive sharing changes, timeline claims, public history, or binding action.
This page helps locate records. It does not make a record controlling.
Archive Routes
Live Routes + Source Links + Protocol + Property + Funding + ExternalCore Source Anchors
Framework + Donor Narrative + Institutional MemoryPHC Business Plan 2.0
Board-facing / current framework source. Use for committee structure, authority boundaries, current planning logic, and Board-governed framework context.
Higher-authority records still control: bylaws, formal Board minutes, adopted resolutions, Board-approved policies, and IRS records.
Open PHC Business Plan 2.0 – Board-Facing FrameworkPHC Business Plan 1.0
Private donor-facing / donor narrative source. Use for early case logic, private donor cultivation, Phase 0 / Phase 1 development context, and donor-story framing.
Do not use this as the current Board-facing governance framework or as proof of Board approval.
Open PHC Business Plan 1.0 – Private Donor Narrative SourceBoard Minutes Recovery
Raw institutional-memory / timeline source material drawn from Deeply Rooted Board minutes and related source review.
Use for timeline support, source grounding, and institutional memory. Do not use as finished public history or proof of Board action unless the minutes explicitly record that action.
Open Board Minutes Recovery – Raw Institutional Memory SourceInstitutional Memory Note
Truth Without InflationWhat Board Minutes Recovery Is For
Board Minutes Recovery is an institutional memory project. Its purpose is not to force a single narrative or inflate the history of Pagan Homeland Collaboration.
Its purpose is to recover the factual record of Deeply Rooted’s long-term evolution: financial pressures, land-care needs, expansion discussions, leadership labor, property concerns, and recurring themes that later became clearer through Pagan Homeland work.
Boundary
Older references to land expansion, property review, church acquisition, financial endurance, organizational persistence, and long-term Deeply Rooted stewardship may be relevant source signals.
They should be preserved and labeled carefully, not inflated into formal PHC action unless the minutes explicitly show Board action.
Institutional Memory + Board Minutes Recovery
Source Architecture + Timeline GuardrailsWhat This Layer Does
Board Minutes Recovery is an internal institutional-memory source layer for PHC.
It helps track reviewed Deeply Rooted Board records, confirmed PHC / Pagan Homeland references, pre-PHC patterns, quiet-year markers, source authority, relevance categories, verification gaps, and Wade feedback notes.
This section makes the new STEP 129 source architecture findable. It does not add timeline claims or public history.
What This Layer Does Not Do
It does not turn older discussion into PHC approval.
Approved minutes matter. Drafts need labels. Raw recovery is not final history. Pattern is not approval. Wade can point. Records must prove. Board must approve.
Find The Source Architecture
- check source authority before relying on a record
- separate approved minutes from drafts and raw extraction
- categorize confirmed PHC references and pre-PHC patterns
- prepare internal timeline entries with caution language
- capture Wade feedback as oral context, not Board action
- keep public history and donor narrative parked until reviewed
Avoid Overclaiming
- claim PHC existed before the sources support it
- treat draft notes as approved minutes
- turn raw recovery into final public history
- treat Wade feedback as Board action
- claim fundraising, property, acquisition, or partnership authority
- publish timeline claims before source and sensitivity review
Main Folder Routes
Drive Structure00_START HERE
Orientation, naming rules, sharing rules, workflow, source priority, and access rules.
Open 00_START HERE01_GOVERNANCE
Committee scope, authority boundaries, Board reporting rhythm, roles, annual review, and governing references.
Open 01_GOVERNANCE02_VALUES + SAFETY
Values and safety MOU, conduct standards, safety tiers, incident notes, accessibility baseline, and steward standards.
Open 02_VALUES + SAFETY03_PARTNERS + ONBOARDING
Partner intake, readiness review, contact tracking, collaboration boundaries, and partner files.
Open 03_PARTNERS04_PROPERTIES + SITE DOSSIERS
Property radar, active leads, due diligence, approved targets, closed leads, site dossiers, and screening tools.
Open 04_PROPERTIES05_GRANTS + FUNDING
Donor language, restricted-fund tracking, grant readiness, budget templates, funder research, and funding records.
Open 05_FUNDING06_PROJECTS + BUILDOUTS
Site activation concepts, early-use models, stewardship, operations, accessibility, compliance, and capital projects.
Open 06_BUILDOUTS07_COMMS + MEDIA
Share-safe one-pagers, public copy, graphics, approved photos, press items, Wayfinder assets, and code blocks.
Open 07_COMMS08_MEETINGS + RECORDS
Agendas, notes, proposals, votes, resolutions, status reports, decision log, proposal register, action items, signal tracking, and Board Minutes Recovery.
Open 08_RECORDS09_TEMPLATES + TOOLKIT
Reusable templates, dossier shells, intake forms, Board memo templates, build notes, and Wayfinder planning files.
Open 09_TOOLKIT99_ARCHIVE
Superseded drafts, retired assets, closed files, deprecated templates, old comms materials, and historical LLM savepoints.
Open 99_ARCHIVEPHC Root Drive Folder
Top-level folder for the full Pagan Homeland Collaboration Drive structure.
Open PHC Root FolderCommand Overview File Routes
Dashboard + High-Level RoutesDashboard Safety Reminder
Dashboard routes help users find current work. They do not approve action, replace Board review, or turn a linked record into adopted policy.
Manual dashboard fields remain manual until a later controlled pass connects a live source.
Use Dashboard Routes To Find
- current status pages
- Board report preparation routes
- source-layer navigation
- signal tracking and Drive map records
- property, funding, external relations, and build routes
Board Briefing + Governance Review Routes
Board Reports + Governance RecordsBoard Route Safety Reminder
Board briefing routes help users find report materials and governance records. They do not place items on an agenda, approve documents, replace minutes, or create Board action.
Board-facing materials still need review, context, and the proper Deeply Rooted process before being treated as approved.
Use Board Routes To Find
- current Board report materials
- Board report item intake
- action item tracking
- proposal and decision records
- 08_MEETINGS + RECORDS
- signal tracking and Drive map records
Input Console + Live Form Routes
Submission Forms + Review IntakeInput Safety Reminder
Input Console forms create records for review. They do not approve action, place items on an agenda, authorize spending, launch fundraising, control property, approve partnerships, or create Board action.
Signal is not decision. Muninn is memory, not permission.
Use Input Routes To Submit
- Board report items
- property leads
- partner leads
- funding leads
- corrections and maintenance needs
- process questions and continuity notes
Operations Protocol File Routes
Workflow + Source Priority + Access RulesProtocol Safety Reminder
Protocol pages explain process and routing. They do not approve action, override bylaws, replace Board review, or turn drafts into adopted policy.
Business Plan 2.0 is a Board-facing framework source, not a replacement for higher-authority records.
Use Protocol Records To Check
- where work belongs
- what status label applies
- which source has higher authority
- which access zone is appropriate
- whether Board action is needed before moving forward
Resource + Funding File Routes
Funding Folders + High-Use RecordsExternal Relations File Routes
Partner Records + Network ReferencesProperty File Routes
Site Review Records + Review ToolsHigh-Use Records
Governance + Continuity + Signal Backbone + Drive MapPHC Business Plan 2.0
Use as the Board-facing / current framework source for committee structure, authority boundaries, and current planning logic.
Open Business Plan 2.0PHC Business Plan 1.0
Use as private donor-facing narrative source material for early case logic and donor cultivation framing.
Open Business Plan 1.0Board Minutes Recovery
Use as raw institutional-memory / timeline source material. Not finished public history. Not proof of Board action unless the minutes explicitly show it.
Open Board Minutes RecoveryBoard Minutes Source Authority Key
Use to label approved minutes, drafts, raw extraction, recovery summaries, oral context, quiet-year markers, and unclear source status.
Open Source Authority KeyBoard Minutes Relevance Category Framework
Use to separate confirmed PHC references, Board action, pre-PHC patterns, quiet-year markers, sensitive context, and verification gaps.
Open Category FrameworkInstitutional Memory Timeline Framework
Use before drafting timeline entries. Timeline may show evolution. Timeline does not create authority.
Open Timeline FrameworkPHC – Decision Log – 2026
Use for recorded decisions and outcomes.
Open Decision LogPHC – Proposal Register – 2026
Use for proposal tracking from draft to approved, closed, or archived.
Open Proposal RegisterPHC – Action Items Tracker – 2026
Use for current task tracking and follow-up work.
Open Action ItemsPHC – Continuity + Savepoint Index – 2026
Use for savepoint recovery, continuity records, folder-level notes, and handoff instructions.
Open Savepoint IndexPHC – Signal Log Tracker – Stub Workbook – 2026
Use for All Signals, Build Signals, Reminder Signals, Resolved Signals, dashboard review, and follow-up tracking.
Open Signal TrackerPHC Wayfinder – Code Block Index + Build Notes – 2026-05-08
Use for Wayfinder page build history, code file tracking, and repair notes.
Open Build NotesPHC Wayfinder – Page Navigation Map – 2026-05-08
Use for page structure and planned internal routes.
Open Navigation Map06_Squarespace Code Blocks
Use for stored source code files for Wayfinder pages.
Open Code Blocks FolderPHC Wayfinder – Graphics + UI Assets – 2026
Use for graphics, screenshots, style references, visual assets, and UI materials.
Open Graphics + UI AssetsPHC – Muninn Drive Map – 2026
Use for the current Drive Map / memory layer. Huginn gathers. Muninn remembers. Neither approves action.
Open Drive MapRelated Wayfinder Pages
Internal RoutesWhat This Does Not Approve
Using Archive Map does not approve:
- spending
- fundraising launch
- donor solicitation
- grant submission
- restricted-fund changes
- property control or purchase
- financing
- formal partnerships
- sponsorship
- fundraising alignment
- shared branding
- public endorsement
- program adoption
- public launch
- Business Plan links as Board approval
- Board Minutes Recovery as finished public history
- timeline framework as approved history
- Wade feedback as Board action
- oral context as approved minutes
- institutional-memory files as authority
- institutional-memory signals as Board action
- protocol records as Board action
- dashboard route links as Board action
- external reference links as Board action
- stub records as Board action
- negotiation authority
- public statements
- file access changes
- Drive sharing changes
- savepoint records as Board action
- Signal Log Tracker entries as Board action
- Muninn records as Board action
- binding commitments
Current Use Note
This page now connects to current internal Wayfinder routes, correction / maintenance reporting, Command Overview, Board Briefing Station, current Board Report, Board Report Item Form, Board Status Report Template, 08_MEETINGS + RECORDS, Input Console live form routes, PHC Root Folder, all main PHC Drive folders, key governance tracking records, the Continuity + Savepoint Index, the Signal Log Tracker workbook, Muninn Drive Map, protocol records, property records, resource / funding records, external relations records, partner support records, SHEAVES / PUN stub records, Business Plans 1.0 and 2.0, Board Minutes Recovery, STEP 129 institutional-memory architecture records, and tested source-layer links.
Archive Map now surfaces the main Drive structure plus the current command overview, Board briefing, input console, operations protocol, property, resource / funding, external relations, core source anchor, and institutional-memory layers. These links help staff locate records. They do not authorize public use, restricted sharing, fundraising launch, donor solicitation, grant submission, partnership, program adoption, public launch, property control, public history claims, timeline claims, oral context as proof, or Board action.
- Command Overview is connected
- Board Briefing Station is connected
- Current Board Report is connected
- Board Report Item Form is connected
- Board Status Report Template is connected
- 08_MEETINGS + RECORDS is connected
- Input Console is connected
- Property Lead Form is connected
- Partner Lead Form is connected
- Funding Lead Form is connected
- Correction / Maintenance Form is connected
- General PHC Question + Process Help Form is connected
- Operations Protocols is connected
- Workflow Summary is connected
- Status Labels is connected
- Source Priority Rule is connected
- Sharing Rules + Access Zones is connected
- Business Plan 2.0 is connected as Board-facing framework source
- Business Plan 1.0 is connected as private donor narrative source
- Board Minutes Recovery is connected as raw institutional-memory source
- Source Authority Key is connected as the Board Minutes Recovery source-label rule layer
- Relevance Category Framework is connected as the Board Minutes Recovery category rule layer
- Drive-Side File Structure Plan is connected as the Board Minutes Recovery structure note
- Extraction Register is connected as the future structured entry layer
- Institutional Memory Timeline Framework is connected as the timeline guardrail layer
- Wayfinder Integration Notes are connected as the future display-planning layer
- Wade Feedback Notes are connected as oral-context capture, not Board action
- PHC root Drive folder is connected
- main PHC Drive folders 00–09 and 99_ARCHIVE are connected
- Decision Log, Proposal Register, and Action Items Tracker are connected
- Continuity + Savepoint Index and Signal Log Tracker workbook are connected
- Muninn Drive Map is connected as the current Drive Map / memory layer
- Huginn gathers; Muninn remembers; neither approves action
- property route layer is connected
- resource / funding route layer is connected
- external relations route layer is connected
- SHEAVES Portal and Pagan Underground Network Site are connected as public reference routes
Archive Safety Note
Archive Map helps people find records. It does not decide which record is authoritative.
Before using a file, check its date, status, source priority, access level, and whether a newer or higher-authority version exists.
Muninn supports Drive memory and navigation. It does not replace governing documents, formal minutes, adopted resolutions, Board reports, protocol rules, or Board action.
Restricted Record Note
Some PHC records may involve donor, Board, legal, finance, personnel, property, negotiation, title, safety-sensitive, signal-tracking, continuity, institutional-memory, oral-context, source-recovery, or Drive-map information.
Keep restricted records in the correct controlled Drive location. Do not expose sensitive files directly on this page.