This is the longest chapter because the method is the disclosure. A social responsibility report that does not explain how it decided what counts as true is asking to be believed on faith. We measure every claim on two independent axes, we admit projects by a fixed rule, we exclude by a fixed rule, and we publish our zeros. Each of those choices is described here.
Most reporting collapses "how far did the work get" and "how good is the evidence" into a single impression. We separate them, because the most dangerous error in a report like this is to write "the evidence is real" and let the reader hear "the impact has happened."
The delivery-stage axis has five values, each higher one implying the lower ones hold: STAGED (material on disk, not built), BUILT (builds and tests pass, no public surface), LIVE (publicly reachable, with a dated probe), USED (a real, non-team action was counted — and the count may be zero), and OUTCOME (a measurable change in someone's situation, with an attribution argument).
The evidence-grade axis has three values: VERIFIED (machine-traceable to a frozen snapshot field, a probe result, or a disk path plus commit), SELF-ATTESTED (an internal test, gate, or audit log, with no independent check), and UNAUDITABLE (no evidence path — stated together with the reason it cannot be audited).
A claim missing either label is dropped, not downgraded. UNAUDITABLE is not a failure label; it is an honesty label, and it always carries its reason.
Five combination rules hold across the report. A LIVE claim requires a dated probe, and a probe more than a few weeks old is downgraded rather than trusted. A USED claim must name a specific action metric, and a value of zero must be written out. A summary number inherits the weakest grade among its parts. Stages may not be skipped in narration — "we built X, therefore families now have Y" is not permitted; each step needs its own evidence. And the rule that governs the whole report:
This report contains zero claims at the OUTCOME · VERIFIED level. We have not established causal attribution for any change in any person's situation. Where we discuss outcomes at all, they are labeled UNAUDITABLE, and we state why.
The single OUTCOME-stage claim in the entire ledger — a tax platform's estimate that it cuts manual classification time by 90 percent or more — is labeled UNAUDITABLE precisely because no usage data or real users exist to support it. [[SVR-C5-m548-007]]
Projects entered this report through a fixed roster, not editorial choice. Of the candidate set drawn from the ecosystem's frozen snapshots, twenty-four were admitted. Two were held as conditional because they had no current snapshot entry to stand on and could not be verified in time. None was blocked outright. An earlier data cut had blocked the education chapter's intended core project and held back a longevity project for stale snapshots; a refresh at the freeze date cleared both, and they are admitted here. The admitted count is small on purpose; the alternative to a small honest roster is a large padded one.
Exclusion is fail-closed: a project on the exclusion list cannot appear in any form, including anonymized or aggregated counts. Seven categories were excluded, described here without naming the projects: skeleton or placeholder builds with no substance; work containing personal data that has not cleared a privacy review, including anything touching minors; identity-verification work whose human subjects have not approved publication; politically sensitive material; legal-stream work held behind a hard firewall; access-controlled internal systems; and one layered case admitted only at its public tier, with its private tier excluded.
A social responsibility report with no zero values and no unauditable items is not clean — it is unbelievable. The production pipeline that generated this report is built to halt if fewer than three zero-value usage claims or fewer than five unauditable claims appear, on the theory that a report which is too flattering is more likely to be fabricated than to be true. Concrete zeros in this edition include a hiring platform's zero applications [[SVR-C7-m647-002]], a curriculum platform's zero real external users [[SVR-C6-m552-002]], an expert atlas with readership at zero and an unwired analytics tag [[SVR-C3-m554-003]], and a completed book series with zero real readers [[SVR-C6-m800-006]].
Even the VERIFIED grade has boundaries we state openly. Several projects' snapshots contradict themselves — for example a navigator whose web-presence field reports a live 200 while its own verification flag reads false and its DNS bind is still pending — and we record the contradiction rather than pick the flattering side. [[SVR-C4-m518-003]]
We also test our own claims adversarially. An internal verification bridge (m620) runs negative controls against the ecosystem's cancer-evidence claims and caught three of three deliberately injected errors; its rule is that every verdict must embed the real negative-control output rather than a description of it [[SVR-C2-m620-001]][[SVR-C2-m620-002]]. That tool is honest about its own limits, too: it has produced verdicts on seven real cases but has zero downstream consumers and has been idle since May [[SVR-C2-m620-003]].
This report has not been independently audited. The word "verified" here means machine-traceable to our own frozen evidence, and nothing stronger.
Reporting entity. LIGHT HOPE LLC (微光集团), a for-profit Massachusetts company. This report covers the group's public-interest programs — its social-value work, carried out inside a commercial entity.
Period & boundary. The reporting period is 1 January – 30 June 2026, and every figure is frozen to a single evidence snapshot dated 11 August 2026. The boundary is the 24 admitted projects in the roster; projects on the exclusion list (sensitive-data or non-public surfaces) are deliberately out of scope and are named as excluded rather than dropped in silence.
Frameworks. This report does not follow, and does not claim to follow, the GRI Standards, ISO 26000, or SASB, and it has not been externally reviewed. It borrows a single idea from them — a clearly stated reporting boundary and basis of preparation — while remaining a self-reported document. Where such a framework would expect an outside-verified number, we instead show the evidence trail and label each claim's grade (verified / self-attested / unauditable).