Pagan Homeland Collaboration Wayfinder

Tech Console

Track Wayfinder code blocks, page builds, link repairs, screenshots, permissions notes, signal tracking, savepoint recovery, source roles, GIS planning, and maintenance tasks.

Use this page to understand the technical record, find code assets, record repairs, review active technical signals, locate continuity records, track active map-layer planning, and prevent future users from rebuilding or breaking work by accident.

Current Tech Status

Phase 0 System Build

Current Use

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

Tech Console helps maintain the Squarespace Wayfinder hub, Google Drive record layer, code block library, page plans, link maps, signal tracker, savepoint index, source-role notes, GIS planning lane, and repair notes.

Tested source-layer links are connected for Build Notes, Page Navigation Map, Code Blocks Folder, Graphics + UI Assets, the Continuity + Savepoint Index, Business Plan 2.0, Business Plan 1.0, and Board Minutes Recovery.

Pagan Homeland GIS / Map Layer is now tracked as an active planning and research lane. The operational GIS system is not built yet.

Muninn Drive Map is now connected as 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, savepoint records as Board action, Business Plan links as Board approval, Board Minutes Recovery as finished public history, Drive sharing changes, or binding action.

It supports technical continuity. It does not grant authority.

Current Source-Role Note

Do Not Blur These Records
Board Framework

Business Plan 2.0

Business Plan 2.0 is the Board-facing / current framework source.

Use it for committee structure, authority boundaries, current planning logic, and Board-governed framework context.

Open Business Plan 2.0
Donor Narrative

Business Plan 1.0

Business Plan 1.0 is the private donor-facing / donor narrative source.

Use it for early case logic, private donor cultivation, Phase 0 / Phase 1 development context, and donor-story framing.

Open Business Plan 1.0
Raw Memory

Board Minutes Recovery

Board Minutes Recovery is raw institutional-memory / timeline source material.

Use it for source recovery, timeline support, and institutional memory. Do not use it as finished public history or proof of Board action unless the minutes explicitly record that action.

Open Board Minutes Recovery

Source Boundary Reminder

Technical Continuity + Authority

Use Source Roles Clearly

  • Business Plan 2.0 supports Board-facing framework context
  • Business Plan 1.0 supports private donor narrative context
  • Board Minutes Recovery supports institutional memory and timeline recovery
  • Pagan Homeland GIS / Map Layer supports active planning, research, and map-source architecture
  • Higher-authority records control when sources conflict
  • Tech Console preserves source logic; it does not approve action

Do Not Treat As Approval

  • do not treat donor narrative as governance authority
  • do not treat raw institutional-memory extraction as finished public history
  • do not treat older source signals as Board approval unless formal minutes explicitly show Board action
  • do not treat GIS planning as property authority, acquisition readiness, or public map approval
  • do not treat a live link as permission to share restricted material
  • do not treat technical access as institutional authority

Pagan Homeland GIS / Map Layer

Active Technical Planning Lane

Active GIS Planning Lane

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

The GIS lane may help 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, 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, 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 Inputs

Potential Source Layers

  • 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 Uses

Technical Purpose

  • show patterns without implying commitment
  • support property-screening questions
  • preserve geographic context for future stewards
  • connect site records to due-diligence needs
  • 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

Tech Console Routes

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

Main Technical Routes

Build + Maintenance Records
Build Notes

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

Use for page build history, code file tracking, repair 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 Navigation Map
Code Library

06_Squarespace Code Blocks

Use for stored code block files for each Wayfinder page.

Open Code Blocks Folder
Assets

PHC Wayfinder – Graphics + UI Assets – 2026

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

Open Graphics + UI Assets
Continuity

PHC – Continuity + Savepoint Index – 2026

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

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

Open Savepoint Index
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
Board Framework

PHC 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.0
Donor Narrative

PHC Business Plan 1.0

Use as the private donor-facing / donor narrative source for early case logic, donor cultivation framing, and Phase 0 / Phase 1 context.

Open Business Plan 1.0
Raw Memory

Board Minutes Recovery

Use as raw institutional-memory / timeline source material. Not finished public history. Not proof of Board action unless formal minutes explicitly show it.

Open Board Minutes Recovery
Active GIS Lane

Pagan Homeland GIS / Map Layer

Use for tracking the active GIS planning lane. This supports research, source architecture, future map planning, and GIS boundary language.

The operational map layer is not built yet and does not approve property action.

Open Site Radar
Repair

Correction / Maintenance Request Form

Use for reporting broken links, wrong pages, typos, confusing routes, missing records, permission issues, or maintenance needs.

Submit Correction / Maintenance
Signals

Signal Log

Use for current technical signals, active maintenance alerts, recent repairs, and signal-routing context.

Open Signal Log
Signal Tracker

PHC – Signal Log Tracker – Stub Workbook – 2026

Use for All Signals, Build Signals, Reminder Signals, Resolved Signals, dashboard review, and follow-up tracking.

Open Signal Tracker
Build Hub

Wayfinder Build + Assets

Use for build-source navigation, page plans, source code records, screenshots, style references, and handoff materials.

Open Build + Assets

Built Page Tracker

Current Wayfinder Pages
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, and active workstreams.

Open Command Overview
Board

Board Briefing Station

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

Open Board Briefing
Property

Site Radar

Property leads, review stages, screening tools, and model dossiers. This is one 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, source anchors, savepoints, Board Minutes Recovery 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
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, source roles, 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, and code block records.

Open Build + Assets

Technical Status Labels

Build States

Suggested Labels

  • Planned
  • Active Planning Lane
  • Research In Progress
  • Page Plan Created
  • Code File Created
  • Code Pasted
  • Squarespace Page Created
  • Preview Tested
  • Works
  • Needs Repair
  • Repaired
  • Needs Link Update
  • Links Pending
  • Links Tested
  • Archived / Replaced

Completion Rule

A page or active build lane is not complete until the code source, Squarespace page, preview test, build notes, and relevant savepoint index records agree.

One good preview at 1:00 a.m. is not a durable maintenance plan. Make the records agree before calling a page complete.

Before Complete

Before Marking Complete

  • page title is correct
  • URL slug is correct
  • page is enabled
  • page is Not Linked
  • password or internal access is correct
  • correct code block is pasted
  • preview is tested
  • mobile preview is reviewed when needed
  • related links do not expose restricted files
  • source roles are labeled clearly where relevant
  • GIS, map, property, or source-layer claims are clearly bounded where relevant
  • correction and maintenance route is available
  • Signal Log Tracker is updated when a signal needs follow-up
  • Savepoint Index is updated when a major recovery record changes
  • Build Index is updated

Batch-Link Workflow

Internal Wayfinder page cards may be batch-linked to planned page slugs.

Full link testing should happen after the destination pages exist, rather than testing each future card before its page is built.

Repair Log Reminder

When Something Looks Off

If A Page Needs Repair, Record

  • what looked wrong
  • which source page or code shell was used
  • what changed
  • whether the Drive code file was updated
  • whether the Squarespace page was updated
  • whether preview now works
  • whether links were tested
  • whether source-role notes need updating
  • whether GIS or map-layer notes need updating
  • whether the Signal Log Tracker needs a signal entry
  • whether the Savepoint Index needs a continuity update
  • whether Build Index was updated

Known Repair Example

Operations Protocols originally used a mismatched visual shell.

It was repaired using the Site Radar visual shell so it matched the Project Moana command-console style.

Internal Routes
Submit Correction / Maintenance Open Build + Assets 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 Return to Internal Wayfinder

What This Does Not Approve

Using Tech Console 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
  • Business Plan links as Board approval
  • Board Minutes Recovery as finished public history
  • institutional-memory signals as Board action
  • GIS records as Board action
  • savepoint records as Board action
  • Drive sharing changes
  • binding commitments

Current Use Note

This page now connects to the live Correction + Maintenance Request Form, current internal Wayfinder routes, tested source-layer links, build-source navigation, Signal Log, the native Signal Log Tracker workbook, the Continuity + Savepoint Index, Muninn Drive Map, Business Plan 2.0, Business Plan 1.0, Board Minutes Recovery, and the active Pagan Homeland GIS planning lane.

Build Notes, Page Navigation Map, Code Blocks Folder, Graphics + UI Assets, Signal Log Tracker, Savepoint Index, Muninn Drive Map, Business Plans 1.0 and 2.0, Board Minutes Recovery, Site Radar, Model Properties, and active GIS planning context are connected.

  • Code Block Index is connected
  • Page Navigation Map is connected
  • 06_Squarespace Code Blocks folder is connected
  • Graphics + UI Assets folder is connected
  • Signal Log page is connected
  • Signal Log Tracker workbook is connected
  • Continuity + Savepoint Index 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
  • Pagan Homeland GIS / Map Layer is tracked as an active planning and research lane
  • Site Radar and Model Properties are connected as likely GIS source-context routes
  • Muninn Drive Map is connected as the current Drive Map / memory layer
  • Huginn gathers; Muninn remembers; neither approves action
  • screenshots and style references remain controlled source-layer records
  • access and permissions notes remain controlled source-layer records

Tech Safety Note

Tech Console helps PHC preserve technical continuity. It does not authorize public launch, file access changes, restricted-record sharing, spending, GIS publication, map-layer release, property claims, or institutional commitments.

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

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

Restricted Access Note

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

Keep restricted technical, 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.

Governance note: Pagan Homeland Collaboration may research, prepare, recommend, and report. Finding, building, repairing, updating, or tracking technical 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, Business Plan links as Board approval, Board Minutes Recovery as finished public history, institutional-memory signals as Board action, GIS records as Board action, Signal Log Tracker entries, savepoint records, Drive-map records, or any binding commitment. Signal is not decision. Savepoints are not approval. GIS planning is not authority. Huginn gathers. Muninn remembers. Neither approves action. Board action is required where authority is needed.