Pagan Homeland Collaboration Wayfinder

Wayfinder Build + Assets

Find Wayfinder build notes, page plans, code blocks, graphics, screenshots, style references, Signal Log Tracker, savepoint index, Muninn Drive Map, source-role records, active GIS build-lane notes, and handoff materials.

Use this page to locate the source materials behind PHC Wayfinder so future maintainers can update the system without recreating, mislabeling, or breaking the work.

Current Build Status

Phase 0 System Build

Current Use

PHC is currently in Phase 0: Administrative readiness / credibility.

Wayfinder Build + Assets preserves the build record, source files, visual references, maintenance trail, signal-tracking awareness, savepoint index, Muninn Drive Map, source-role routing, active GIS build-lane notes, and handoff materials for the Wayfinder hub.

Tested source-layer links are connected for Build Notes, Page Navigation Map, Code Blocks Folder, Graphics + UI Assets, the native Signal Log Tracker workbook, the Continuity + Savepoint Index, Muninn Drive Map, current source-role records, and active GIS planning context.

Pagan Homeland GIS / Map Layer is now tracked as an active build lane. The operational GIS system is not built yet. Current work is planning, research, language, source architecture, and future technical pathway definition.

Muninn is the current Drive Map / memory layer. Huginn gathers. Muninn remembers. Neither approves action.

Not Approved Here

This page does not approve public launch, access changes for restricted files, spending, fundraising, donor solicitation, grant submission, property control, formal partnerships, public statements, GIS publication, map-layer release, map-based site claims, geographic commitments, Drive sharing changes, source-anchor records as Board action, or binding action.

It protects the build record. It does not grant authority. Signal is not decision. Savepoints are continuity records, not approvals. Source anchors are orientation records, not authority. GIS planning is active, but it is not authority. Muninn is memory, not permission.

Build + Assets Routes

Live Routes + Tested Source Links + Signal Tracker + Drive Map
Submit Correction / Maintenance Open Tech Console Open Command Overview Open Input Console Open Archive Map Open Signal Log Open Site Radar Open Model Properties Open Signal Tracker Return to Internal Wayfinder Open Build Notes Open Page Navigation Map Open Code Blocks Folder Open Graphics + UI Assets Open Savepoint Index Open Drive Map

Source Continuity Note

Light Source-Role Reference
Framework

Business Plan Version 2.0

Board-facing / current framework source. Use it to understand current PHC structure, authority boundaries, planning framework, Board reporting logic, source priority, and lane safety.

Build records should label this as the current framework source when linked from Wayfinder pages.

Open Business Plan 2.0
Donor Story

Business Plan Version 1.0

Private donor-facing / donor narrative source. Use it for early case logic, original fundraising sequence, and donor-story context.

Build records should not label this as the current Board-facing governance framework.

Open Business Plan 1.0
Memory

Board Minutes Recovery

Raw institutional-memory / timeline source. Use it for source recovery, timeline support, and Board-history context.

Build records should treat this as internal recovery material unless later reviewed and converted into finished Board-safe or public-safe history.

Open Board Minutes Recovery
GIS Lane

Pagan Homeland GIS / Map Layer

Active planning and research lane. Use it for map-source architecture, geography, property radar patterns, site context, regional partner information, land-history notes, stewardship data, and due-diligence signals.

The operational GIS system is not built yet. GIS planning does not approve property control, acquisition, fundraising, public map release, or Board action.

Open Site Radar

Pagan Homeland GIS / Map Layer

Active Build Lane

Active GIS Build Lane

Pagan Homeland GIS / Map Layer is part of the active PHC planning process.

This build lane will help define how PHC may organize geography, property radar patterns, site context, regional partner information, land-history notes, stewardship data, due-diligence signals, and future map-based institutional memory.

Current work is planning, research, language, source architecture, page/source alignment, and future technical pathway definition. The operational GIS system is not built yet.

GIS Boundary

GIS planning does not approve property control, acquisition, negotiation, fundraising, grant submission, partner commitments, public launch, map publication, map-layer release, map-based site claims, geographic commitments, or site commitments.

GIS records, map drafts, property signals, and geographic patterns must stay tied to source records, due diligence, governance review, and Board action where authority is needed.

Likely Inputs

GIS Source Inputs

  • property radar records
  • model property notes
  • regional partner context
  • site history and land-use notes
  • zoning, floodplain, access, and infrastructure signals
  • institutional-memory timeline markers, when source-safe
Likely Uses

GIS Build Purpose

  • show patterns without implying commitment
  • support property-screening questions
  • preserve geographic context for future stewards
  • connect site records to due-diligence needs
  • help PHC explain why place, access, safety, and stewardship matter
Not A Shortcut

GIS Is Not Authority

  • GIS is not acquisition readiness
  • GIS is not Board approval
  • GIS is not a public campaign
  • GIS is not a promise to pursue any site
  • GIS is not a replacement for title, zoning, tax, inspection, legal, or Board review

Main Build Asset Routes

Source Layer
Build Notes

PHC Wayfinder – Code Block Index + Build Notes – 2026-05-08

Use for page build history, code file tracking, repair notes, route updates, source-role linking notes, and current build status.

Open Build Notes
Navigation

PHC Wayfinder – Page Navigation Map – 2026-05-08

Use for planned page routes, slugs, navigation structure, and future link testing.

Open Page Navigation Map
Code Library

06_Squarespace Code Blocks

Use for stored code block files for each Wayfinder page.

Open Code Blocks Folder
Visual Assets

PHC Wayfinder – Graphics + UI Assets – 2026

Use for graphics, screenshots, style references, visual assets, and UI materials.

Open Graphics + UI Assets
Signal Tracker

PHC – Signal Log Tracker – Stub Workbook – 2026

Use for All Signals, Build Signals, Reminder Signals, Resolved Signals, and current operational awareness.

Signal is not decision. Tracker entries preserve awareness; they do not create authority.

Open Signal Tracker
Page Plans

PHC Wayfinder – Page Navigation Map – 2026-05-08

Use for page-planning control, planned routes, page purpose, navigation structure, and future link testing.

Open Page Plans
Drive Map

PHC – Muninn Drive Map – 2026

Use for the current Drive Map / memory layer. Huginn gathers. Muninn remembers. Neither approves action.

Muninn helps users find Drive records. It does not change file access, approve public launch, or authorize any binding action.

Open Drive Map
GIS Build Lane

Pagan Homeland GIS / Map Layer

Use for tracking the active GIS build lane, map-source planning, GIS boundary language, and future map architecture.

The operational GIS system is not built yet and does not approve property action.

Open Site Radar
Repair

Correction / Maintenance Request Form

Use for broken links, page issues, outdated files, source mismatches, permission concerns, and maintenance needs.

Submit Correction / Maintenance
Continuity

PHC – Continuity + Savepoint Index – 2026

Use for savepoint recovery, folder-level continuity notes, handoff records, and project-state recovery if Quill is unavailable.

Savepoints are continuity infrastructure. They do not create Board action or binding authority.

Open Savepoints
Tech

Tech Console

Use for technical setup, page repairs, link checks, permissions notes, signal-tracker awareness, source continuity, GIS build-lane context, and maintenance coordination.

Open Tech Console

Built Page Source List

Live Page + Source Materials
Public

Public Wayfinder Front Page

Public-visible front page and entry point for the internal access gate.

Open Public Front Page
Dashboard

Command Overview

Main PHC dashboard for current status, quick links, report prep, active workstreams, and current source anchors.

Open Command Overview
Board

Board Briefing Station

Board reports, action items, proposal tracking, meeting records, manual Board dates, active GIS visibility, and Board review source notes.

Open Board Briefing
Property

Site Radar

Property leads, review stages, screening tools, and model dossiers. This is a likely source area for future GIS inputs.

Open Site Radar
Models

Model Properties

Model property examples used for process testing without implying acquisition approval. This may inform future GIS pattern work.

Open Model Properties
Protocol

Operations Protocols

Workflow, authority boundaries, status labels, sharing rules, and source priority.

Open Operations
Input

Input Console

Submissions, leads, corrections, process questions, and routing help.

Open Input Console
Archive

Archive Map

Folders, records, templates, dossiers, savepoints, source-role records, institutional-memory architecture, and build assets.

Open Archive Map
Funding

Resource Readiness

Donor-readiness, grant-readiness, restricted-fund, budget, and funding-prep materials.

Open Resource Readiness
Relations

External Relations

Partner leads, outreach lanes, SHEAVES support, collaboration boundaries, and relationship records. This may inform future regional GIS context.

Open External Relations
Signals

Signal Log

Recent updates, reminders, changes, active signals, and follow-up notes.

Open Signal Log
Tracker

Signal Log Tracker

Native workbook for All Signals, Build Signals, Reminder Signals, Resolved Signals, and dropdown lists.

Open Signal Tracker
Continuity

Savepoint Index

Central recovery map for savepoints, continuity records, folder-level notes, and handoff instructions.

Open Savepoint Index
Tech

Tech Console

Technical setup, code blocks, screenshots, links, permissions, active GIS planning lane, maintenance notes, and repairs.

Open Tech Console
Build

Wayfinder Build + Assets

Build notes, asset folders, style references, screenshots, GIS build-lane notes, signal-tracker awareness, source-continuity notes, and code block records.

Open Build + Assets

Asset Types

What Lives Here

Build Asset Categories

  • Page Plans
  • Squarespace Code Blocks
  • Graphics + UI Assets
  • Screenshots
  • Style References
  • Link Maps
  • Build Notes
  • Repair Notes
  • Signal Log Tracker
  • Muninn Drive Map
  • Source-Role Records
  • GIS Planning Notes
  • Map Source Architecture
  • Continuity Savepoints
  • Continuity + Savepoint Index

Current / Future Asset Categories

  • Live Form Links
  • Permission / Access Notes
  • Repair Screenshots
  • Live Squarespace Page URLs
  • Maintenance Notes
  • Final Drive Links
  • Signal Tracking Records
  • Source Record Checks
  • Source-Role Link Checks
  • Route Update Logs
  • Savepoint Index Updates
  • Drive Map Refresh Notes
  • GIS Build-Lane Notes
  • Map-Layer Boundary Notes

Maintenance Reminder

Visible + Source Layer

When Editing Wayfinder

  • update the Drive code file
  • update the Squarespace code block
  • preview the page
  • check mobile view when needed
  • test changed links
  • update the Build Index
  • update the Savepoint Index when a major recovery record changes
  • check whether the Signal Log Tracker needs a follow-up entry
  • check whether the Muninn Drive Map needs refresh notes
  • confirm source-role labels stay accurate
  • confirm GIS and map-layer boundary language stays accurate when relevant
  • note repairs or visual changes
  • check access and link safety
  • avoid exposing restricted files
  • keep the Correction / Maintenance route available

Short Reminder

Visible page.

Source file.

Build note.

Savepoint index when needed.

Signal tracker when needed.

Muninn refresh note when needed.

Source-role label when needed.

GIS boundary note when needed.

All eight should agree. Otherwise the record starts eating its own tail.

Known Build Rules

Do Not Casually Break These

Current Wayfinder Build Rules

  • Duplicate known-good pages instead of starting from blank pages.
  • Use the established Project Moana command-console visual shell.
  • Store code blocks in the Drive code block folder.
  • Create page plans before code files.
  • Update the Build Index after major steps.
  • Use the Savepoint Index for continuity and recovery mapping.
  • Batch-link Internal Wayfinder page cards where practical.
  • Test Internal Wayfinder card links after linked pages exist.
  • Keep Quick Actions as placeholders until real Forms, Sheets, or Drive links exist.
  • Use the native Signal Log Tracker workbook for signal tracking links.
  • Use Muninn as the current Drive Map / memory layer.
  • Treat Pagan Homeland GIS / Map Layer as an active planning and research lane.
  • Do not treat GIS planning, map drafts, property signals, or geographic patterns as Board approval.
  • Do not publish maps or map-based site claims without proper review and authority.
  • Do not call Muninn “Drive Live Export” as the primary button label.
  • Do not treat signal as decision.
  • Do not treat savepoints as approval.
  • Do not treat source anchors as authority.
  • Do not treat Muninn as authority.
  • Do not imply Board approval through page text or links.
  • Keep restricted materials out of public-facing or broad-share pages.

Change Carefully

Build speed is useful. Untracked edits are not.

If a future maintainer changes the visual shell, link structure, access model, source record process, source-role labels, GIS build lane, map-layer process, savepoint process, signal-tracking workflow, or Drive Map workflow, the Build Index should explain why.

Internal Routes
Submit Correction / Maintenance Open Tech Console Open Command Overview Open Operations Protocols Open Input Console Open Archive Map Open Site Radar Open Model Properties Open Signal Log Open Signal Tracker Open Savepoint Index Open Drive Map Return to Internal Wayfinder

What This Does Not Approve

Using Wayfinder Build + Assets does not approve:

  • public launch
  • access changes for restricted files
  • spending
  • fundraising launch
  • donor solicitation
  • grant submission
  • property control or purchase
  • formal partnerships
  • public statements
  • GIS publication or public map release
  • map-layer release
  • map-based site claims or geographic commitments
  • GIS records as Board action
  • binding commitments
  • Board action through Signal Log Tracker entries
  • Board action through savepoint records
  • Board action through source-anchor records
  • Drive sharing changes through Muninn

Current Use Note

This page now connects to the live Correction + Maintenance Request Form, current internal Wayfinder routes, the public front page, built page routes, tested source-layer links, the native Signal Log Tracker workbook, the Continuity + Savepoint Index, Muninn Drive Map, active GIS build-lane notes, and current source-role records.

Build Notes, Page Navigation Map, Code Blocks Folder, Graphics + UI Assets, Signal Log Tracker, Savepoint Index, Muninn Drive Map, Business Plan 2.0, Business Plan 1.0, Board Minutes Recovery, and Pagan Homeland GIS / Map Layer are connected.

  • Code Block Index
  • Page Navigation Map
  • 06_Squarespace Code Blocks folder
  • Graphics + UI Assets folder
  • Signal Log Tracker workbook
  • Continuity + Savepoint Index
  • Muninn Drive Map
  • Business Plan 2.0 source-role reference
  • Business Plan 1.0 source-role reference
  • Board Minutes Recovery source-role reference
  • Pagan Homeland GIS / Map Layer active build-lane reference
  • Site Radar and Model Properties as likely GIS source-context routes
  • screenshots and style references remain controlled source-layer records
  • folder-level savepoints remain near the work they describe
  • permission and access notes remain controlled source-layer records
  • Huginn gathers; Muninn remembers; neither approves action

Build Safety Note

Wayfinder Build + Assets helps PHC preserve source continuity. It does not authorize public launch, file access changes, restricted-record sharing, spending, GIS publication, map-layer release, map-based site claims, or institutional commitments.

Before changing a page, confirm the source code file, live Squarespace page, Build Index, Controlled Drive Link Inventory, Signal Log Tracker, Savepoint Index, Muninn Drive Map, source-role labels, GIS boundary language, and relevant test notes all stay aligned.

Signal tracking supports current operational awareness and follow-up. It does not replace the Decision Log, Proposal Register, Board reports, formal minutes, or Board action.

Savepoint tracking supports continuity and recovery. Source-role labels support orientation and routing. GIS planning supports map-layer research and source architecture. Muninn supports Drive memory and navigation. None of these replace governing documents, formal minutes, adopted resolutions, Board-approved policies, or Board action.

Restricted Source Note

Build records may reference permissions, access layers, forms, sheets, Drive files, screenshots, internal pages, signal tracking, savepoints, source-role records, GIS planning records, map-source notes, property signals, Drive maps, or sensitive records.

Keep restricted build, access, signal, savepoint, source-role, GIS, property, and Drive-map records in the correct controlled Drive location. Do not expose sensitive files directly on this page.

Governance note: Pagan Homeland Collaboration may research, prepare, recommend, and report. Finding, building, repairing, updating, or tracking build materials through this hub does not approve spending, acquisition, fundraising, partnership, property control, public statements, access changes for restricted files, GIS publication, map-layer release, map-based site claims, Signal Log Tracker entries, savepoint records, source-anchor records, Drive-map records, GIS records, or any binding commitment. Signal is not decision. Savepoints are not approval. Source anchors are not authority. GIS planning is not authority. Huginn gathers. Muninn remembers. Neither approves action. Board action is required where authority is needed.