Current Operations Status

Phase 0 Process Build

Current Use

PHC is currently building its internal operating system.

Operations Protocols are for process clarity, file routing, status discipline, source checking, correction routing, and Board-safe workflow.

The current protocol record links are connected for internal use: Workflow Summary, Status Labels, Source Priority Rule, Sharing Rules + Access Zones, and Business Plan 2.0.

Not Approved Here

No spending, acquisition, fundraising, property control, formal partnership, public statement, or institutional commitment is approved through this page.

This page explains process. It does not grant authority.

Current Framework Source

Board-Facing Reference

Business Plan 2.0

Business Plan 2.0 is the current Board-facing PHC framework source. Use it for committee structure, authority boundaries, current planning logic, and Board-governed framework context.

This source helps explain why the Wayfinder is built around documentation, source priority, Board reporting, property caution, donor trust, and institutional memory.

Open PHC Business Plan 2.0 – Board-Facing Framework

Source Boundary

Business Plan 2.0 does not replace the Deeply Rooted bylaws, formal Board minutes, adopted resolutions, Board-approved policies, or IRS records.

If there is a conflict, the higher-authority source controls.

Core Workflow Loop

How Work Moves

Step 1

Observe

Notice the property lead, funding question, partner opportunity, governance need, safety issue, or system gap.

Step 2

Document

Put the item somewhere real. Do not leave important work in memory, loose screenshots, or browser tabs breeding in the dark.

Step 3

Verify

Check whether the information is true, current, sourced, in PHC’s lane, and consistent with governing documents.

Step 4

Organize

Move the work into the correct folder, status label, access zone, and workstream.

Step 5

Build

Turn raw notes into usable material: a memo, tracker, proposal, checklist, case statement, dossier, or Board-facing brief.

Step 6

Recommend

Route it correctly. Keep it internal, move it to Board-facing review, make it share-safe, pause it, or close it.

Step 7

Board Action If Needed

If the matter requires authority, send it to the Board. Committee work is not organizational action by itself.

Step 8

Record Outcome

Update the Decision Log, Proposal Register, tracker, file status, or archive so future people can follow the record.

Workstream Routing

Where Things Go

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

Before It Moves

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

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

Protocol Routes

Live Routes + Protocol Records

Open Command Overview Open Input Console Open Site Radar Open Board Briefing Station Open Model Properties Return to Internal Wayfinder Report Protocol Issue Open PHC Business Plan 2.0 – Board-Facing Framework Open Workflow Summary Open Status Labels Open Source Priority Rule Open Sharing Rules + Access Zones

What This Does Not Approve

Using Operations Protocols does not approve:

spending
fundraising launch
property control or purchase
financing
formal partnerships
negotiation authority
public statements
binding commitments

Core Lane Phrase

PHC can build the work. The Board must approve binding action.

That means PHC may research, prepare, recommend, and report. Deeply Rooted must act formally where authority is required.

Current Use Note

This page now connects to current internal Wayfinder routes for Command Overview, Input Console, Site Radar, Board Briefing Station, Model Properties, and correction / maintenance reporting.

Workflow Summary, Status Labels, Source Priority Rule, Sharing Rules + Access Zones, and PHC Business Plan 2.0 are connected and ready for internal use.

Protocol Safety Note

Protocol pages explain process and routing. They do not approve action, override bylaws, replace Board review, or turn drafts into adopted policy.

When a protocol file conflicts with a higher-authority source, the higher-authority source wins.

Operations Protocols