Pagan Homeland Collaboration Wayfinder
Operations Protocols 🛠️
The working rules that keep PHC from becoming a pile of good ideas.
Use this page when a lead, draft, question, correction, or task needs to move from raw idea into documented work. Put the work somewhere real, name what stage it is in, check the source, keep the record findable, and keep authority in the right lane.
Core Protocol Files
These files explain the rules behind the work. Open the file that matches the question in front of you.
Workflow Summary
The basic PHC workflow from idea to record to review to recommendation. Use this when someone asks: what happens next?
Open Workflow SummaryStatus Labels
Defines labels like draft, working, reviewed, Board-facing, approved, closed, and archived. Use this so records do not pretend to be more final than they are.
Open Status LabelsSource Priority Rule
Shows which source wins when records conflict. Use this before relying on drafts, memory, summaries, or older notes.
Open Source Priority RuleSharing Rules + Access Zones
Explains what can be public, internal, Board-facing, restricted, or private. Use this before sharing links or moving records.
Open Sharing RulesBusiness Plan 2.0
Current Board-facing PHC framework source. Use this for committee scope, authority limits, planning phases, and Phase 0-first logic.
Open Business Plan 2.0Business Plan 1.0
Private donor-facing narrative source. Use this for donor-story context, not for governance authority when Business Plan 2.0 or higher sources control.
Open Business Plan 1.0Muninn Drive Map
Finds current Drive files, folders, IDs, and links. Use this when someone asks: where does that file live?
Open Muninn Drive MapSignal Tracker
Tracks recent changes, route notes, and system updates. Use this before editing so you know what changed.
Open Signal TrackerBuild Notes
Records Wayfinder page changes, code passes, source alignment, failures, repairs, and build decisions.
Open Build NotesCore Workflow Loop
The basic path from "someone noticed something" to "the record can be used by the next person."
Observe
Notice the property lead, funding question, partner opportunity, governance need, safety issue, or system gap.
Document
Put the item somewhere real. Do not leave important work in memory, loose screenshots, texts, or browser tabs breeding in the dark.
Verify
Check whether the information is true, current, sourced, in PHC's lane, and consistent with governing records.
Organize
Move the work into the correct folder, status label, access zone, and workstream.
Build
Turn raw notes into usable material: a memo, tracker, proposal, checklist, case statement, dossier, or Board-facing brief.
Recommend
Route it correctly. Keep it internal, move it to Board-facing review, make it share-safe, pause it, or close it.
Board Action If Needed
If the matter requires authority, send it to the Board. Committee work is not organizational action by itself.
Record Outcome
Update the decision log, proposal register, tracker, file status, or archive so future people can follow the record.
Workstream Routing
The folder structure is not decoration. It is how the next person knows where the work lives.
Governance
Use 01_GOVERNANCE for committee scope, authority boundaries, Board reporting rhythm, annual review, roles, and governing references.
Values + Safety
Use 02_VALUES + SAFETY for conduct, consent, safety tiers, incident notes, accessibility baseline, and steward standards.
Partners
Use 03_PARTNERS + ONBOARDING for intake, readiness review, contacts, collaboration boundaries, and partner files.
Properties
Use 04_PROPERTIES + SITE DOSSIERS for Site Radar, active leads, due diligence, approved targets, closed leads, and property dossiers.
Funding
Use 05_GRANTS + FUNDING for donor language, restricted-funds tracking, budget templates, funder research, and grant readiness.
Buildouts
Use 06_PROJECTS + BUILDOUTS for activation concepts, early-use models, stewardship, compliance planning, and capital projects.
Comms + Media
Use 07_COMMS + MEDIA for share-safe language, one-pagers, approved public copy, graphics, photos, and code assets.
Meetings + Records
Use 08_MEETINGS + RECORDS for agendas, notes, proposals, votes, resolutions, status reports, decision logs, and action items.
Templates + Toolkit
Use 09_TEMPLATES + TOOLKIT for reusable templates, dossier structures, intake forms, memo shells, and standard build notes.
File Safety Checks
These checks keep speed from dressing itself up as readiness.
Move Forward When
- the item is documented in the correct place
- the facts are verified enough for the next stage
- the status label is honest
- the access level is clear
- the wording stays inside PHC's authority
- the file does not imply Board approval where none exists
- someone can pick it up without needing the whole backstory retold
Stop When
- authority is unclear
- facts are unverified
- the file sounds approved while still draft
- property excitement outruns due diligence
- funding language outruns Treasurer and Board oversight
- sharing the file would create confusion or risk
- the work depends on one person remembering everything
Current Framework Source
Use the right source for the right kind of question. Not every document carries the same weight.
Business Plan 2.0
The current Board-facing PHC framework source. Use it for committee structure, authority boundaries, current planning logic, Board-governed framework context, and the Phase 0-first approach.
This source helps explain why Wayfinder is built around documentation, source priority, Board reporting, property caution, donor trust, and institutional memory.
Open PHC Business Plan 2.0Source Boundary
Business Plan 2.0 does not replace Deeply Rooted bylaws, formal Board minutes, adopted resolutions, Board-approved policies, or IRS records.
If there is a conflict, the higher-authority source controls. A newer draft does not outrank a governing record just because it is easier to find.
Keep the Record Honest
Some language explains the record. Some language interprets the pattern. Both can be useful. They are not the same thing.
Source Fact
Source fact is what the record directly supports.
- bylaw text
- Board minutes
- adopted resolutions
- IRS records
- formal dossiers
- verified title, tax, zoning, or permit records
Interpretive Language
Interpretive language helps name a pattern. It must stay clearly marked unless adopted formally.
- lineage framing
- Generative Chaos
- quiet-year meaning
- network vs. brand framing
- lessons drawn from conflict or growth
- working language not yet adopted by Board
Clean wording: "The record shows…" for source facts. "A working interpretation is…" for pattern language. This keeps the story useful without making the record lie.
Open-Source Mindset
Some PHC tools may someday help other Pagan groups start without starting from scratch. That does not make private records public.
What Can Become Reusable
- workflow loops
- status label patterns
- property screening questions
- partner intake structure
- Board-safe memo formats
- share-safe language examples
- source-priority teaching tools
What Stays Controlled
Reusable process is different from restricted records.
- donor notes
- private financial material
- property negotiation details
- restricted Board records
- sensitive source extracts
- private contacts or personnel details
How the Workflow Tools Fit Together — Data Route
These names are mythic. The work is practical: gather, remember, check, shape, track, summarize, and route.
Gather + Find
Huginn gathers Drive records. Muninn remembers the Drive Map. Most users should open Muninn rather than run scripts.
Open Muninn Drive MapCheck + Shape
Urðr, Verðandi, and Skuld help separate checked records, active review, and follow-up tasks.
Open Nornir FolderSummarize + Route
Mímir, Mímisbrunnr, and Wanderer: WIS turn reviewed records into useful views. Wayfinder shows where the work belongs.
Script run instructions belong in Tech Console. Build history belongs in Wayfinder Build + Assets.
Plain rule: If you are not assigned to run scripts, do not run scripts. Use the files, forms, and Wayfinder routes. If something looks broken, submit a correction.
How Institutional Memory Moves — Nornir Operating Logic
The Nornir system helps PHC remember carefully. It separates checked records, working review, and future follow-up.
Checked Records
For records after they have been checked. Holds source-supported history, preserved decisions, and reviewed lessons. If it is not checked, do not let it harden into institutional memory.
Working Review
For records while they are being sorted, tested, corrected, compared, and prepared. This is where a rough idea becomes useful work without pretending to be final.
Follow-Up Work
Tracks what still needs review: source checks, Board asks, Treasurer questions, property diligence, route repairs, and missing records. The next obligation named before it becomes a problem with teeth.
Nornir rule: No discussion becomes approval unless the minutes say so. Source fact first. Interpretation second. Authority boundary always.
Protocol Records + Reporting
Open the key records here. If something is wrong, report the issue instead of working around the broken route.
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.