Pagan Homeland Collaboration Wayfinder
Tech Console βοΈ
The repair bench: links, code records, source maps, build notes, tools, scripts, and system fixes.
Use this page when something is broken, outdated, missing, mislabeled, hard to find, technically confusing, or drifting away from the record. The Tech Console keeps the working system repairable without turning every repair into a decision.
Tech Console Routes
Use these when you need to repair the system, find the source code, check the build notes, or report something broken.
How to Use the Scripts Together
This is the plain route. Most users should open records. Only assigned technical people should run scripts.
Check Muninn First
Open Muninn Drive Map first to find the current file, folder, code block, or source record. This prevents duplicate work.
Open Muninn Drive MapRun Huginn Only When Needed
Huginn refreshes the Drive inventory. Use Save β Run exportPHCDriveMap when the Drive map needs a fresh scan.
Open Huginn ScriptCheck UrΓ°r
UrΓ°r holds checked-past/source-archive records and the Mimir_Source_Fact_Queue. Use it when source facts are ready to move forward.
Open UrΓ°r WorkbookUse VerΓ°andi for Active Review
VerΓ°andi handles active extraction and staging. Use it when records are being shaped, cleaned, and prepared.
Open VerΓ°andi ScriptRoute Obligations to Skuld
Skuld holds what still needs to be checked: source gaps, Board questions, review tasks, and follow-up work.
Open Skuld FolderRun Mimir Import Bridge
Mimir receives reviewed source-fact rows from UrΓ°r. Run the setup/test first, then import only when source facts are ready.
Open Mimir WorkbookRun Mimisbrunnr Output Bridge
Mimisbrunnr turns reviewed Mimir source facts into report-ready output views, including Wanderer_WIS_Output_View.
Open Mimisbrunnr WorkbookRun Wanderer: WIS Import
Wanderer: WIS reads reviewed place, property, resource, and infrastructure signals from Mimisbrunnr. Keep it internal unless reviewed.
Open Wanderer: WISUpdate Wayfinder Last
Wayfinder gets updated after source records are stable, links are checked, and the page scope is clear. Do not push raw data into public-facing pages.
Return to Internal WayfinderPlain route: Muninn first. Huginn only when the Drive map needs refresh. UrΓ°r / VerΓ°andi / Skuld sort the record. Mimir imports reviewed facts. Mimisbrunnr prepares outputs. Wanderer: WIS reads reviewed place data. Wayfinder shows only what belongs on the human page.
Core Source + Build Records
These records keep the Wayfinder build from becoming oral tradition with buttons.
Code Block Index + Build Notes
Use for page build history, replacement code tracking, page repairs, build status, and source notes.
π οΈ Open Build NotesPage Navigation Map
Use for current page structure, route planning, and internal navigation checks.
π§ Open Navigation MapSquarespace Code Blocks
Use for stored source-code files, page-code records, replacement blocks, archived code, and current source alignment.
β Open Code Blocks FolderGraphics + UI Assets
Use for screenshots, style references, visual assets, Northwoods imagery, icons, logo files, and UI materials.
β¦ Open Graphics + UI AssetsWayfinder Build + Assets
Human-facing route for source-code files, UI assets, logo files, page build records, and controlled build-material handling.
π§° Open Build + AssetsContinuity + Savepoint Index
Use for savepoint recovery, handoff records, continuity notes, and next-chat restart context.
𧡠Open Savepoint IndexSignal Log Tracker
Use for build signals, reminder signals, resolved signals, and follow-up tracking.
π Open Signal TrackerMuninn Drive Map
Use for current Drive Map and memory layer. It helps locate records. It does not approve action.
πΊοΈ Open Drive MapCorrection Responses
Use after someone submits a broken link, page issue, outdated text, or route confusion.
Open Correction ResponsesProcess Help Responses
Use when someone submits a route question, tool question, or process-help request.
Open Process Help ResponsesDrive 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.
Use Save β Run exportPHCDriveMap only when the Drive map needs a fresh scan.
Open Huginn ScriptDrive Map Memory Layer
Muninn remembers the current Drive Map layer so people can find records without rebuilding the system from ash and caffeine.
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.
Source-Fact Workflow Tools
These tools help turn source records into reviewed data. They are useful. They are not authority.
UrΓ°r Workbook
Holds source archive / checked-past material and the Mimir source-fact queue. Do not use it for unverified claims.
Open UrΓ°r WorkbookVerΓ°andi Script
Supports active extraction and staging. Use for working review, not final claims.
Open VerΓ°andi ScriptSkuld Folder
Holds follow-up needs, verification tasks, Board-clarification needs, and review burdens.
Open Skuld FolderMimir Workbook
Receives structured source facts from UrΓ°r and holds Mimir_Source_Facts for reviewed source intelligence.
Open Mimir WorkbookMimisbrunnr Workbook
Pulls reviewed Mimir source facts into report-ready views, including timeline, funding, property, language, and Wanderer views.
Open Mimisbrunnr WorkbookWanderer: WIS
Wayfinder Information System for reviewed place, property, resource, and map-related signals. It reads from Mimisbrunnr.
Open Wanderer: WISWeb of Wyrd route: UrΓ°r β VerΓ°andi β Mimir β Skuld β Mimisbrunnr β Wanderer: WIS β Wayfinder. Huginn and Muninn support Drive memory alongside the route.
Business Plans + Institutional Memory
These records help explain the project. They do not all carry the same authority.
Business Plan 2.0
Current Board-facing framework source for PHC structure, authority boundaries, committee scope, Board reporting logic, property caution, funding sequence, and planning framework.
π Open Business Plan 2.0Business Plan 1.0
Private donor-facing narrative source for early case logic, donor cultivation, Phase 0 / Phase 1 context, and donor-story framing.
β§ Open Business Plan 1.0Board Minutes Recovery
Raw institutional-memory and timeline source. Useful for source grounding. Not finished public history or proof of Board action unless the minutes explicitly show that action.
π Open Board Minutes RecoveryWanderer: WIS + Pagan Homeland GIS / Map Layer
The map layer is active planning and research. It is not authority.
What This Lane May Hold
Wanderer: WIS means Wayfinder Information System. It is a GIS-style tool for reading reviewed place, property, resource, infrastructure, and stewardship signals from the source-fact layer.
A GIS is a map-based information system. In plain terms: it helps people connect records to places.
- property radar geography
- model property context
- regional partner context
- zoning, floodplain, access, and infrastructure signals
- source-safe timeline markers
- stewardship and public-benefit layers
- future open-source learning tools for other Pagan communities
Map Boundary
GIS records, map drafts, geographic patterns, and property signals do not approve acquisition, site control, fundraising, grant submission, public map release, or Board action.
A map can show patterns. It cannot make a promise.
Place matters. So does proof.
Common Tech Console Work
Not every repair is the same. Name the kind of work so it can be routed cleanly.
Broken or Wrong Content
Wrong links, old language, typos, missing buttons, confusing labels, outdated notes, or stale route language.
Code Block Records
Stored page code, replacement code blocks, archived code, and live-vs-Drive code alignment.
Page Route Problems
Broken internal pages, missing routes, unclear navigation, duplicate pages, or route-name confusion.
Graphics + UI Materials
Images, badges, screenshots, icons, visual references, Northwoods assets, logo files, and style notes.
Signal Tracking
Build signals, reminder signals, repair signals, resolved signals, and current work visibility.
Map Layer Planning
Map logic, geography fields, future GIS structure, property context, and source-safe map planning.
Tooling + Console Scripts
Apps Script, trackers, exports, ritual-console traces, execution logs, and tool behavior notes.
Permissions + Sharing
Access questions, Drive sharing questions, restricted files, domain visibility, and page privacy concerns.
Old Versions + Retired Files
Superseded code, old screenshots, retired assets, deprecated drafts, and savepoint history.
How to Handle a Tech Issue
A repair should leave a better trail than the problem did.
Repair Steps
- notice the issue
- submit a correction or maintenance request if needed
- check the relevant source record
- confirm whether live Squarespace or Drive-side code is the current master
- check Build + Assets for source-code and visual-asset routing
- make the repair in the proper lane
- test the link, page, widget, sheet, or code block
- update the Drive-side source file when that is part of the pass
- rename or date-align records if needed
- log the work in Build Notes or Signal Tracker
- update Muninn Drive Map if the file route changed
Do Not Fix by Fog
Do not quietly repair something and leave no record.
Do not overwrite historical code blocks if the current plan is to archive old versions and create new files going forward.
Do not let "I fixed it" become another mystery for the next person to untangle.
Live vs. Drive Master Rule
The code trail matters. So does knowing which copy is current.
When Editing a Wayfinder Page
- use the live Squarespace code as master when Drive-side source-code files are stale
- do not overwrite a live page with an old Drive source file
- use one full replacement code block unless a tiny patch is specifically requested
- after live testing, update the matching Drive-side source-code file when practical
- rename or date-align the source-code file after the pass
- log the completed work in Build Notes
- route asset issues through Build + Assets
Safe Short Version
Live page first when live is current.
Drive source second after testing.
Build Notes last so the next person can see what happened.
The archive is allowed to keep old code. The live page should not inherit old ghosts.
Tech Safety Note
Technical records may point toward sensitive records. Keep the right information in the right lane.
Before Acting on a Tech Record
- check whether the record is current, archived, draft, or superseded
- check whether live Squarespace or Drive-side code is the master for the current pass
- check whether Build + Assets has the needed source-code or visual-asset route
- check whether the change affects only one page or the whole system
- check whether the change should be logged in Build Notes
- check whether a Signal Tracker entry is needed
- check whether the Drive Map should be updated
- check whether access or sharing would change
- check whether Apps Script/tooling changes need testing
- check whether Board attention is needed
- check whether a script result should route to Skuld for follow-up
- check whether Wanderer: WIS data is internal only
Restricted Tech Note
Some tech records may involve Board, donor, property, legal, finance, access, Drive mapping, code, continuity, Apps Script, institutional-memory, source-recovery, or GIS / spatial-intelligence information.
Keep restricted technical records in the correct controlled Drive location. Do not expose sensitive records directly on this page.
The quiet work matters. The signpost only helps if someone can read it later.
How Technical Records Should Be Read β Nornir Tech Logic
The Nornir layer keeps build work from pretending to be final, approved, or authoritative before the record supports it.
Checked Build Record
For confirmed code replacements, tested links, logged repairs, completed source updates, and known working records. A checked repair should leave proof, not folklore.
Active Build Work
For pages under revision, code being tested, route passes, active tool work, and repairs still in progress. Active does not mean stable. Working does not mean approved.
Technical Follow-Up
For broken links, stale files, missing source records, map-layer questions, tool errors, access issues, and future repairs. Skuld is the sticky note that refuses to become a haunting. Helpful little menace.
Tech rule: fix the trail, mark the repair, leave the next person a record. 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.