Pagan Homeland Collaboration Wayfinder
Signal Log π‘
The current-awareness table: updates, reminders, repairs, and follow-up signals.
Use this page to see what changed recently, what needs attention, and what should be routed into records, reports, proposals, or action items. A signal is useful because it points. It does not decide.
Signal Log Routes
Use these when a signal needs intake, correction, a tracker, a source record, or a place to live.
Core Signal Files
These are the records most likely to receive a signal once it becomes work.
Signal Log Tracker
Main workbook for All Signals, Build Signals, Reminder Signals, Resolved Signals, dashboard review, and follow-up tracking.
Open Signal TrackerBoard Report Responses
Holds submitted Board report items. Use this before shaping items for Board Briefing Station.
Open ResponsesCorrection Responses
Holds reported broken links, outdated text, confusing routes, page issues, and maintenance needs.
Open ResponsesAction Items Tracker
Use for current task tracking and follow-up work that has moved beyond a loose signal.
Open Action ItemsDecision Log
Use only when a real decision or outcome has been recorded. A signal alone is not a decision.
Open Decision LogProposal Register
Use for proposal tracking from draft to reviewed, approved, closed, or archived.
Open Proposal RegisterMuninn Drive Map
Finds current Drive files, folders, IDs, and links. It helps locate records. It does not approve action.
Open Drive MapCode Block Index + Build Notes
Use for Wayfinder build history, code files, page repairs, source alignment, and page-status notes.
Open Build NotesPage Navigation Map
Use for page structure, planned internal routes, page scope, and route repair.
Open Navigation MapWayfinder Build + Assets
Use for source-code files, UI assets, logos, page build records, graphics routes, and controlled Wayfinder asset checks.
Open Build + AssetsTech Console
Use for technical maintenance, source alignment, tested links, code repair notes, and page-level troubleshooting.
Open Tech ConsoleArchive Map
Use when the signal points toward a folder route, old file, source layer, savepoint, template, or record location.
Open Archive MapMain Signal Categories
Name the kind of signal so the next person knows where to look and what to do with it.
Build Updates
Recent Wayfinder pages, code block changes, repairs, navigation changes, source-code files, build assets, and page-build progress.
Open Build SignalsBoard Report Signals
Items that may need to appear in the next PHC Board status report.
Submit Board Report ItemProperty Signals
Property leads, watchlist changes, dossier updates, Site Radar notes, Wanderer: WIS signals, and diligence reminders.
Open Site RadarFunding Signals
Donor-readiness, grant-readiness, restricted-fund, budget, or funding-prep updates.
Open Resource ReadinessPartner Signals
Outreach, SHEAVES activity, partner leads, contact updates, and relationship follow-up.
Open External RelationsCorrection / Broken Link Signals
Wrong links, broken pages, outdated files, missing records, typos, confusing navigation, or asset mismatch.
Submit CorrectionReminder Signals
Upcoming tasks, report-prep windows, Board meeting reminders, and recurring work.
Open Reminder SignalsSource / Drive Signals
Drive locations, source-layer questions, missing files, stale source links, Muninn updates, and map checks.
Open Drive MapClosed / Resolved Signals
Signals that were handled and no longer need active attention.
Open Resolved SignalsSignal Routing Reminder
A signal should not sit forever. Route it when it becomes work.
Route Signals When Needed
- build issue β Tech Console / Build Notes / Build + Assets / Signal Tracker
- broken link β Correction Form / Tech Console / Signal Tracker
- source-code or graphics issue β Build + Assets / Code Blocks Folder / Graphics + UI Assets
- Board report item β Board Status Report Form / Board Report Responses / 08_MEETINGS + RECORDS
- property lead β Site Radar / Wanderer: WIS / property dossier
- funding lead β Resource Readiness / 05_GRANTS + FUNDING
- partner lead β External Relations / 03_PARTNERS + ONBOARDING
- actual decision β Decision Log
- formal proposal β Proposal Register
- assigned task β Action Items Tracker
- working signal β Signal Log Tracker
- source or Drive location check β Muninn Drive Map
- institutional memory issue β Archive Map / source record
Short Reminder
Signals point.
Records hold.
Board action decides.
The spreadsheet may whisper. It does not govern.
Signal Entry Standard
A good signal entry gives enough shape that someone else can carry the next step.
A Good Signal Entry Includes
- date
- topic
- short summary
- source or related file, if known
- current status
- next step
- owner or follow-up person, if known
- whether Board attention may be needed
- whether the signal contains restricted or sensitive material
Suggested Status Labels
- New Signal
- Active
- Needs Review
- Needs Routing
- Board Report Candidate
- Build / Asset Check Needed
- Waiting
- Resolved
- Closed
Clean signal language: "Signal received," "Needs routing," "Board report candidate," "Build / asset check needed," "Tracker updated," "Resolved," or "Closed." Avoid wording that makes a signal sound like approval.
Signal Safety Note
Some signals may point toward sensitive records. Keep the right information in the right lane.
Before Acting on a Signal
- check whether it belongs in a form
- check whether it needs a tracker entry
- check whether it belongs in a Board report
- check whether it needs a decision log entry
- check whether it needs a proposal register entry
- check whether it belongs in a Drive record
- check whether Build + Assets should be checked
- check whether the Drive Map should be updated
- check whether restricted access is needed
- check whether the signal is source fact, interpretation, or reminder
Restricted Signal Note
Some signals may involve donor, Board, property, legal, finance, personnel, partner, safety, source-recovery, institutional-memory, source-code, build-asset, or negotiation-sensitive information.
Keep restricted signals in the correct controlled Drive location. Do not expose sensitive records directly on this page.
A clean signal is not a small thing. It is how the next person knows where to put their hands.
How Signals Should Be Read β Nornir Signal Logic
The Nornir layer keeps signals from pretending to be more final, more formal, or more approved than they are.
Resolved or Checked Signal
For signals that have been checked, resolved, routed, recorded, or tied to a confirmed source. A resolved signal should leave a trail, not a rumor.
Active Working Signal
For active build notes, reminders, questions, broken links, routing needs, or items still being shaped. Active does not mean approved. Visible does not mean complete.
Follow-Up Signal
For Board report candidates, future tasks, missing records, Drive map updates, page repairs, source-code checks, asset checks, and review needs. Skuld is where "we should remember this" becomes "someone can actually find this."
Signal rule: signals point; records hold; Board action decides. 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.