Pagan Homeland Collaboration Wayfinder
Wayfinder Build + Assets π§°
The source bench: build notes, page plans, code files, graphics, screenshots, repair trails, and handoff records.
Use this page to find the materials behind the Wayfinder so future maintainers can update the system without recreating, mislabeling, or breaking the work.
Build + Assets Routes
Use these when you need source files, repair notes, visual assets, build records, or system recovery.
Main Build Asset Routes
These are the core places to check before changing Wayfinder pages.
Code Block Index + Build Notes
Use for page build history, code file tracking, repair notes, route updates, source-role linking notes, and current build status.
π οΈ Open Build NotesPage Navigation Map
Use for planned page routes, slugs, navigation structure, and future link testing.
π§ Open Page Navigation MapSquarespace Code Blocks
Use for stored code block files for each Wayfinder page.
β Open Code Blocks FolderGraphics + UI Assets
Use for graphics, screenshots, style references, visual assets, logo files, and UI materials.
β¦ Open Graphics + UI AssetsSignal Log Tracker
Use for All Signals, Build Signals, Reminder Signals, Resolved Signals, and current operational awareness.
π Open Signal TrackerMuninn Drive Map
Use for the current Drive Map / memory layer. It helps users find records. It does not change access or authorize action.
πΊοΈ Open Drive MapContinuity + Savepoint Index
Use for savepoint recovery, folder-level continuity notes, handoff records, and project-state recovery.
𧡠Open Savepoint IndexPagan Homeland GIS / Map Layer
Use for tracking the active GIS build lane, map-source planning, GIS boundary language, and future map architecture.
ποΈ Open Site RadarWanderer: WIS
Use for reviewed place, property, resource, and map-related signals. Internal planning layer only unless reviewed.
α± Open Wanderer: WISCorrection / Maintenance Request Form
Use for broken links, page issues, outdated files, source mismatches, permission concerns, and maintenance needs.
π οΈ Submit Correction / MaintenanceTech Console
Use for technical setup, page repairs, link checks, permissions notes, source continuity, GIS build-lane context, and maintenance coordination.
βοΈ Open Tech ConsoleBuilt Page Source List
Use this as a quick map of the current Wayfinder page set.
Public Wayfinder Front Page
Public-visible front page and entry point for the internal access gate.
Open Public Front PagePHC Wayfinder Internal
Main internal page-card navigation hub.
Open Internal WayfinderCommand Overview
Main PHC dashboard for current status, quick links, report prep, active workstreams, and current source anchors.
Open Command OverviewBoard Briefing Station
Board reports, action items, proposal tracking, meeting records, manual Board dates, and Board review source notes.
Open Board BriefingSite Radar
Property leads, review stages, screening tools, Wanderer: WIS context, and model dossiers. Likely source area for future GIS inputs.
Open Site RadarModel Properties
Model property examples used for process testing without implying acquisition approval.
Open Model PropertiesOperations Protocols
Workflow, authority boundaries, status labels, sharing rules, and source priority.
Open OperationsInput Console
Submissions, leads, corrections, process questions, and routing help.
Open Input ConsoleArchive Map
Folders, records, templates, dossiers, savepoints, source-role records, institutional-memory architecture, and build assets.
Open Archive MapResource Readiness
Donor-readiness, grant-readiness, restricted-fund, budget, and funding-prep materials.
Open Resource ReadinessExternal Relations
Partner leads, outreach lanes, SHEAVES support, PUN reference routing, collaboration boundaries, and relationship records.
Open External RelationsSignal Log
Recent updates, reminders, changes, active signals, and follow-up notes.
Open Signal LogSignal Log Tracker
Native workbook for All Signals, Build Signals, Reminder Signals, Resolved Signals, and dropdown lists.
Open Signal TrackerSavepoint Index
Central recovery map for savepoints, continuity records, folder-level notes, and handoff instructions.
Open Savepoint IndexTech Console
Technical setup, code blocks, screenshots, links, permissions, active GIS planning lane, maintenance notes, and repairs.
Open Tech ConsoleWayfinder 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 + AssetsWanderer: WIS
Reviewed place, property, resource, and spatial-intelligence layer for future map-informed PHC planning.
Open Wanderer: WISSource Role Notes
These records help orient the build. They do not all carry the same authority.
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.
π Open Business Plan 2.0Business Plan Version 1.0
Private donor-facing / donor narrative source. Use it for early case logic, original fundraising sequence, and donor-story context.
β§ Open Business Plan 1.0Board Minutes Recovery
Raw institutional-memory / timeline source. Use it for source recovery, timeline support, and Board-history context. Do not treat it as finished public history.
π Open Board Minutes RecoveryBoard Minutes Recovery Data Layer Plan
Active next-pass planning source: PHC β Board Minutes Recovery Data Layer Plan β Working β Internal β 2026-05-11.
Use after this page pass to review the planned data layer, reporting outputs, Wayfinder language mirrors, source categories, and board-safe institutional-memory next steps.
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.
ποΈ Open Site RadarWanderer: WIS
Wayfinder Information System for reviewed place, property, resource, and map-related signals. It reads from Mimisbrunnr and stays internal unless reviewed.
α± Open Wanderer: WISDrive Memory + Tooling Layer
The raven layer helps PHC gather and remember the system. It does not approve action.
Fresh Drive Inventory
Huginn gathers Drive structure, file names, locations, and routing clues through Apps Script / export work.
Huginn is a gatherer, not an approver.
Drive Map Memory Layer
Muninn remembers the current Drive Map layer so people can find records without rebuilding the system from ash, willpower, and one suspiciously durable spreadsheet.
Muninn is a map, not Board action.
πΊοΈ Open Drive MapApps Script / Automation Lane
Apps Script, exports, trackers, and automation tools can support records, reduce drift, and make repair easier.
Automation does not change authority, access, money, property, or Board process.
Raven rule: Huginn gathers. Muninn remembers. Nornir sort the thread. None of them approve action.
Pagan Homeland GIS / Map Layer
The map layer is active planning and research. It is not authority.
Active GIS Build Lane
Pagan Homeland GIS / Map Layer is part of the active PHC planning process.
This build lane may help define how PHC organizes 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, Wanderer: WIS routing, and future technical pathway definition.
α± Open Wanderer: WISGIS 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.
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
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
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
Asset Types
This page points to both current assets and future maintenance categories.
Build Asset Categories
- Page Plans
- Squarespace Code Blocks
- Graphics + UI Assets
- Screenshots
- Style References
- Link Maps
- Build Notes
- Repair Notes
- Signal Log Tracker
- Drive Map
- Source-Role Records
- Board Minutes Recovery Data Layer Plan
- GIS Planning Notes
- Wanderer: WIS Notes
- Map Source Architecture
- Apps Script / Tooling Notes
- 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
- Huginn / Muninn Run Notes
- GIS Build-Lane Notes
- Map-Layer Boundary Notes
- Previous / Next navigation checks
- Moon + Sky placement checks
Maintenance Reminder
A visible change should leave a source trail.
When Editing Wayfinder
- confirm whether live Squarespace or Drive-side code is the current master
- update the Squarespace code block
- preview the page
- check mobile view when needed
- test changed links
- update the Drive-side code file when that is part of the pass
- 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 Drive Map needs refresh notes
- confirm source-role labels stay accurate
- confirm Board Minutes Recovery data-layer references stay accurate when relevant
- confirm GIS and map-layer boundary language stays accurate when relevant
- confirm Previous / Next workflow navigation appears near top and near bottom
- keep Moon + Sky notes near the bottom unless a page-specific reason says otherwise
- 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.
Drive Map refresh note when needed.
Source-role label when needed.
Data-layer note when needed.
GIS boundary note when needed.
All of these should agree. Otherwise the record starts eating its own tail.
Known Build Rules
These rules keep the system understandable for the next person.
Current Wayfinder Build Rules
- Duplicate known-good pages instead of starting from blank pages.
- Store code blocks in the Drive code block folder.
- Create page plans before code files.
- Use the live Squarespace code as master when Drive source-code files are stale.
- Do not overwrite live Squarespace pages with stale Drive source docs.
- Use one full replacement code block unless a tiny patch is specifically requested.
- Place Previous / Next workflow navigation near the top and near the bottom of each page.
- Place Moon + Sky notes near the bottom unless there is a page-specific reason to do otherwise.
- 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 Signal Log Tracker workbook for signal tracking links.
- Use the Drive Map as the current Drive memory layer.
- Preserve meaningful runes in file names and code comments where they belong.
- Keep ritual-console language useful, not disruptive.
- 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 treat signal as decision.
- Do not treat savepoints as approval.
- Do not treat source anchors 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, Board Minutes Recovery data-layer workflow, GIS build lane, map-layer process, savepoint process, signal-tracking workflow, Drive Map workflow, or page-to-page navigation pattern, the Build Index should explain why.
Build Safety Note
Build records may point toward sensitive records. Keep the right information in the right lane.
Before Changing a Page
- confirm whether live Squarespace or Drive-side code is the current master
- confirm the source code file
- confirm the live Squarespace page
- check the Build Index
- check the controlled link inventory, if relevant
- check the Signal Log Tracker, if relevant
- check the Savepoint Index, if relevant
- check the Drive Map, if relevant
- confirm source-role labels stay accurate
- confirm Board Minutes Recovery data-layer references stay accurate when relevant
- confirm GIS boundary language stays accurate when relevant
- confirm Wanderer: WIS data is internal unless reviewed
- test changed links
- avoid exposing restricted files
Restricted Source Note
Build records may reference permissions, access layers, forms, sheets, Drive files, screenshots, internal pages, signal tracking, savepoints, source-role records, Board Minutes Recovery data-layer records, GIS planning records, map-source notes, property signals, Drive maps, or sensitive records.
Keep restricted build, access, signal, savepoint, source-role, institutional-memory, GIS, property, and Drive-map records in the correct controlled Drive location. Do not expose sensitive files directly on this page.
How Build Records Should Be Read β Nornir Build Logic
The Nornir layer keeps build work from pretending to be final, approved, or authoritative before the record supports it.
Checked Source Record
For completed page updates, tested links, confirmed source-code files, logged repairs, and finalized savepoint notes. A checked source record should help the next person trust what changed.
Active Build Work
For page passes, source-role revisions, code updates, GIS planning, Board Minutes Recovery data-layer planning, and style changes still being shaped. Active does not mean final. Visible does not mean approved.
Build Follow-Up
For missing files, outdated code blocks, broken links, pending build notes, Drive Map refreshes, and future repair passes. Skuld is the future wearing a clipboard. Annoying. Correct.
Build rule: visible page, source file, build note, savepoint, Drive Map, and repair trail should agree. Source fact first. Interpretation second. Authority boundary always.
Moon + Sky Note β Seasonal Awareness
For awareness only. Verify against a trusted local calendar before any ritual, public-facing, or Board-facing copy.
Current Moon
Current Planetary Positions
Planet signs and retrograde motion are the useful pieces here. For precise local charts, use a full astrology tool with your exact location.