CQCQ Nonprofit LoopMethod & Evidence Open workspace
Transparent enough to trust

Show the operating logic, protect the engine.

The public method explains what the system considers: funding durability, unrestricted runway, staff protection, program capacity, compliance evidence, actuals, feedback, and approved memory. Production weights and conflict rules should remain protected.

Closed-loop method

The same spine runs every page.

The product is not a fundraiser, HR tracker, grant calendar, or program dashboard by itself. It is a decision loop connecting those systems before and after commitments.

01

Intake

Program, funder, restriction, deadline, owner, board question, and mission promise.

02

Evidence

CSV/PDF imports, manual entries, source confidence, missing fields, and lineage.

03

Operating model

Runway, funding mix, donor durability, pay pressure, vacancy, program load, and compliance burden.

04

Role packets

Executive, development, finance, program, frontline, board, and compliance views.

05

Actuals

Donations, grants, expenses, pay investment, service units, staff strain, outcomes, and reporting.

06

Governed memory

Accept, adjust, or reject lessons before anything returns to the next decision.

Industry-specific factors

Why the nonprofit pages are split.

Each mission lane has a different operating object. The shared loop stays the same; the calculators and evidence expectations change.

General nonprofit

Funding mix and operating reserves.

Restricted funds, unrestricted cash, recurring donors, donor retention, grant deadlines, payroll, and board policy.

Animal welfare

Capacity and care flow.

Intake, animals in care, kennel/foster capacity, adoptions/placement, veterinary backlog, transfers, and volunteers.

Disability services

Direct-support stability.

Authorized hours, delivered hours, shift coverage, reimbursement limits, incidents, family support, respite, and wage pressure.

Evidence anchors

Research-informed without copying anyone’s model.

These public sources support why the system watches workforce, fundraising durability, shelter capacity, direct-support stability, reserves, and community-based services.

Protected boundary

What should not be exposed in production.

Public pages can explain what the product does. Production should protect formulas, scoring thresholds, source-conflict logic, access keys, private records, and client-specific data.

Keep scoring weights and thresholds server-side.
Keep account access, role permissions, and protected records behind authentication.
Do not expose private staff, donor, family, client, or participant records in public HTML.