Donation & Project Model

Transparent Giving System

This page defines how TaoDaoism should separate donation paths, public project reporting, restricted giving, and private backoffice records before accepting public donations at scale.

Core Principle

Every donation path should answer four questions before a visitor gives: who receives the funds, what the funds support, whether the gift is restricted, and how progress will be reported. This protects donor trust and keeps TaoDaoism, community projects, and the future Temple entity from becoming financially or legally confused.

Public Giving Paths

Operating Support

TaoDaoism General Support

Supports the website, teaching library, quote reflections, design, hosting, email/community tools, and administrative development.

  • Unrestricted unless specifically stated.
  • Reported as general platform development.
  • Does not imply temple-restricted use.
Restricted Projects

Project-Specific Giving

Supports a named project chosen by the donor, such as Kids’ School Supplies, Koi Reflection Pond, or Library Additions.

  • Tracked by project ledger.
  • Public page shows sanitized progress.
  • Private records stay protected.

Project Lifecycle

1Draft

Define purpose, public need, restrictions, privacy risks, and owner.

2Approved

Confirm scope, budget categories, reporting rules, and donation language.

3Open

Publish public page, needs list, and donation pathway.

4Active

Track receipts, in-kind support, updates, milestones, and expenses.

5Reported

Post public-safe summary, totals, outcomes, and next steps.

6Closed / Ongoing

Close completed projects or move recurring efforts into operations.

Public vs Private Data

Area
Public Website
Private Backoffice
Donations
General totals, project progress, donation categories.
Donor identity, contact details, receipts, payment notes.
In-Kind Gifts
Needed items and collected quantities.
Donor names, item condition notes, delivery records.
Expenses
Category totals and sanitized summaries.
Invoices, vendor quotes, contracts, account numbers.
Recipients
Anonymous impact summaries only.
Protected identities, addresses, schools, family details.
Temple Site
Stage, criteria, major milestone updates.
Negotiations, private addresses, security details.

Standard Project Fields

Public Fields

Project title, summary, status, public goal, needed categories, milestone stage, sanitized updates, public contact path, donation category.

Private Fields

Project owner, internal budget, restricted ledger, donor records, receipts, vendor notes, recipient details, risk notes, approval history.

Reporting Fields

Progress summary, amount raised if public, items collected, expenses by category, milestone changes, completion note, lessons learned.

Governance Fields

Approval status, reviewer, date opened, date closed, restrictions, privacy level, legal/tax notes, public wording approval.

Temple Creation Funding Stages

The Temple Creation project should be tracked separately from daily operations. During the build stage, giving supports planning, land, permitting, architecture, construction, altar infrastructure, and opening. After opening, giving can support named operations projects.

Stage
Donation Purpose
Public Tracking
Finding Land
Research, feasibility, location criteria, professional consultation.
Stage status and criteria, not private negotiations.
Permitting
Legal, zoning, architectural, and compliance preparation.
Permit stage and public milestones.
Building
Construction, renovation, altar space, safety systems.
High-level progress and budget categories.
Blessing & Opening
Opening ceremonies, community preparation, initial operations.
Event readiness and public schedule once safe.
Daily Operations
Maintenance, programming, library, garden, pond, festivals.
Named operations projects with separate goals.

Next Build Requirements

  • Create a future WordPress custom post type: Project.
  • Create private project fields that are never rendered publicly.
  • Create public dashboard fields that can be safely displayed.
  • Add donation category metadata before payment integration.
  • Add project status workflow: Draft, Approved, Open, Active, Complete, Archived.
  • Add audit notes and manual reporting controls before automating totals.