Trust-artifact catalog

Most platforms publish an annual transparency report and call it done. We are trying to do something different: keep the receipts visible all the time, in one place, so a journalist on deadline, a county counsel reading our partner agreement, a donor doing due diligence, or a lived-experience advisor checking our work can find every surface that documents what we are doing and how. This page is the index. Each entry below names a public surface, says what it shows, and links straight to it. Nothing here is summary — the artifacts speak for themselves.

Operational visibility — what the platform is doing right now

• /today — live counters from the production database. Credits issued today, resources mapped in the Antelope Valley, partner organizations in field validation. Refreshes every 60 seconds. Returns "—" honestly when the database is unreachable rather than caching a stale number.
• /phase-0-ledger — Anadora-led field-interview ledger. Every conversation with a prospective partner organization is logged here, redacted at the individual level (names, direct quotes that could identify a person, internal politics) but explicit at the outcome level (joined, declined, willing to reconsider, signed LOI). This is the pre-launch evidence that the work is happening.
• /primary-sources — every numerical claim on the public site paired with its source. Each citation points at the underlying dataset, so a journalist, county counsel, or donor can verify any figure we publish against its primary source.

Commitments — what we promise and what governs us

• /ethics — non-waivable ethical commitments. What we will never do (controller of DV-survivor data, PHI without a BAA, peer attestation for trust progression, surveillance for law enforcement, undisclosed experiments). What we will do by default (the dignity floor). Abuse vectors with shipped mitigations and honest gaps. The kill-switch design principle — /ethics#kill-switch.
• /security — coordinated-disclosure policy. Safe harbor for good-faith research, scope, 90-day disclosure window, the carve-out for findings that touch DV-survivor paths, and the response SLA. Mirrored in SECURITY.md at the repository root.
• /privacy — California Privacy Rights Act rights, what data we collect, what we never collect, the hosting-infrastructure disclosure (Vercel edge logs, deliberate absence of behavioral analytics), safe-address use, and the press-and-analyst access point.

Who and where — the populations we serve and the people behind the work

• Six populations, sourced — homelessness, foster youth, reentry, behavioral-health discharge, domestic-violence survivors, veterans. Each number on the homepage population grid pairs with a primary source in /primary-sources.
• /anadora — Anadora Turner, MSW, USC. Clinical co-lead. Authority on the dignity floor and the trauma-informed register.
• /lived-experience — the lived-experience advisor program (Phase 1 commitment; honoraria documented in /ethics).

Financial sustainability — how we sustain this

• /how-we-sustain — the five revenue streams in activation order: 5% donation-processing fee (configured — activates with the donation rail), city licensing (Phase 1), business memberships (Phase 1), marketplace transaction fees (Phase 2), and data-and-analytics products (Phase 2). What is not a revenue stream is documented here too.
• /donate — the five donation funds (Meal, Transport, Gear, Laundry, Housing) with per-fund descriptions, illustrative credit costs, and 5% fee disclosure. Routes to Stripe checkout or the business-sponsor path depending on gift size.
• /sponsor — business and civic sponsorship tiers ($500 single-event, $2,000/month partner, $25,000+/year founding sponsor), sponsor wall, and lead-capture form.

Founding documents and outreach

• /letters — the published outreach bundle. Open letters, the partner-and-counsel correspondence we are willing to put on the record.
• /why-catalyst — why we started as a small grassroots project, why the founders chose to begin clean as a single nonprofit (no for-profit parent, no IP license), and the path to 501(c)(3) status as Guardians of the AV, Inc. Companion documents: docs/governance/founding_structure_clean_nonprofit.md and docs/legal/founding_charter.md.
• /why-catalyst — the 501(c)(3) filing timeline and the fiscal-sponsor interim posture.

Source code

The platform that runs this site — apps/web, the Supabase schema and row-level-security policies, the partner-data-processing agreement template, the ethics page, the security disclosure policy, the wizards — is tracked at github.com/aturner71/guardian-project.

Records requests

We are not a public agency, so the California Public Records Act (Cal. Gov. Code §§ 7920-7930) does not grant a statutory right to our records. What we will voluntarily provide as a courtesy (aggregate stats, governance documents, anonymized incident reports), what we will never voluntarily provide (user-identifying data, DV-survivor referral data, individual case notes, sponsor lists), and how we coordinate when a partner agency is served with a CPRA request that touches us — all of that is written down in docs/operations/public_records_request_runbook.md in the repository.

What is intentionally not on this page

Aspirational commitments that we have not yet shipped do not appear on this catalog. The ethics advisory board (Phase 1.5), the whistleblower channel (Phase 1.5), the published PGP key for security disclosures (Phase 1.5), and the annual third-party security audit (Phase 2) are all described honestly on /ethics and /security with their phase labels. They will be added to this catalog the day they ship, not before.

How this page changes

Material changes are recorded in git history at apps/web/app/transparency/page.tsx. A new public transparency surface should appear here within one business day of shipping. If you read this page and find a surface we forgot to link, that is itself a transparency failure — write to hello@guardiansofsolano.com and we will fix it.