Impact

The honest scoreboard.

Most platforms open with a large number. These start at zero, because TIMOMAX has not placed an animal yet — and a product that fabricates its own track record has no standing to ask anyone else for sourced data.

Placements and outcomes
Animals placed
0
A placement counts only when a person approved it and it completed.
Fosters matched
0
Rule-based matching; every score shows its own factor breakdown.
Transports completed
0
Requires a two-sided handoff in the chain of custody.
Contributions settled
$0
Settled money only. Payments in flight are never counted.
What is built

These are counted from the repository at build time. This build could not read it, so they are not stated.

Database tables
Data unavailable
Counted from supabase/migrations at build
Row-level security policies
Data unavailable
Counted from supabase/migrations at build
Behavioural checks written
Data unavailable
Counted from the suites in scripts/ at build
Fabricated statistics
0
Where a figure is missing, TIMOMAX prints Data unavailable

What TIMOMAX refuses to do

Every one of these is enforced in the database, not merely written in a policy — which is the difference between a promise and a control.

Place an animal without a person

A placement row is rejected unless a named human approved it, with a timestamp.

Publish a foster's address

Precise coordinates live in a separate table, released only after an approved placement.

Show money that has not arrived

A contribution raises a total only once Stripe confirms it over a signed webhook.

Call a donation tax deductible

Blocked unless an EIN has been checked against the IRS file, with a date.

Close a transport that did not happen

Requires a two-sided handoff: both the person releasing and the person receiving.

Invent a spending figure

Award, obligation and outlay stay three columns. Missing means Data unavailable.