Intake
Program, funder, restriction, deadline, owner, board question, and mission promise.
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.
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.
Program, funder, restriction, deadline, owner, board question, and mission promise.
CSV/PDF imports, manual entries, source confidence, missing fields, and lineage.
Runway, funding mix, donor durability, pay pressure, vacancy, program load, and compliance burden.
Executive, development, finance, program, frontline, board, and compliance views.
Donations, grants, expenses, pay investment, service units, staff strain, outcomes, and reporting.
Accept, adjust, or reject lessons before anything returns to the next decision.
Each mission lane has a different operating object. The shared loop stays the same; the calculators and evidence expectations change.
Restricted funds, unrestricted cash, recurring donors, donor retention, grant deadlines, payroll, and board policy.
Intake, animals in care, kennel/foster capacity, adoptions/placement, veterinary backlog, transfers, and volunteers.
Authorized hours, delivered hours, shift coverage, reimbursement limits, incidents, family support, respite, and wage pressure.
These public sources support why the system watches workforce, fundraising durability, shelter capacity, direct-support stability, reserves, and community-based services.
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.