Methodology

1. Intake. Complainant submits narrative, company, issue type, incident date, amount disputed, and up to 10 evidence files via /complaints/submit.
2. Triage. Backend stores submission with status pending. Rate limits apply per IP.
3. Moderation. Reviewer checks evidence, classifies issue, redacts PII, and confirms the company match.
4. Publication. Anonymised summary appears on the company profile feed and the witness wall (if applicable).
5. Cohort aggregation. Once 5+ complaints share company and issue type, a coordinated filing draft is generated.
6. Regulator filing. Coordinated draft is reviewed and filed with BSP / SEC / DTI / small-claims court.
7. Resolution log. Outcomes recorded against the original complaint with primary-source receipts.

• Every public-record entry requires at least 1 primary-source URL or 2 independent news cites.
• Primary sources rank above secondary news: court PDFs, regulator orders, NPC resolutions, BIR notices, SEC filings.
• The date field is the date of the event, not the news coverage.
• Source URLs are re-checked at entry time; broken links are flagged and replaced.
• When a regulator has not acted, the absence is documented with noEnforcement: true and the search method is recorded in the summary.

• Names, phone numbers, email addresses, and exact home addresses are redacted before publication.
• Government IDs, account numbers, and birth dates are stripped from any uploaded evidence shown publicly.
• Faces in screenshots are blurred unless the subject is a public-record figure named in a primary source.
• Original files are retained server-side; the public version always uses the redacted copy.

• Every claim links to the source document. Quotes are reproduced verbatim where reproduction is fair-use scoped.
• Court decisions link to lawphil.net or the Supreme Court e-library.
• Regulator orders link to the agency's official PDF (NPC, BSP, SEC, DTI, BIR, FDA, IC).
• News cites prefer outlets with corrections records (Inquirer, Rappler, Philstar, Manila Bulletin, BusinessWorld, Bilyonaryo).

• ≥3 complaints sharing company + issue: visible cohort counter on the company page.
• ≥5: a coordinated-filing draft is generated for review.
• ≥10: filing pack is escalated to the on-call moderator for outbound submission.
• Issue-type taxonomy is fixed: kill-switch lockout, undisclosed fee, data-privacy breach, illegal collection practice, refund non-payment, service interruption, other.

Cite-to-public-record only. Codified at the data layer in frontend/src/lib/publicRecord.ts.

• Title and summary must be factual; no adjectives, no characterisation.
• Every entry must have ≥1 primary source URL or ≥2 independent news cites.
• outcome is derived from the source document, not editorialised.
• noEnforcement: true is allowed only when the absence is itself documented.
• No editorial commentary; quote the source directly where possible.
• Disambiguate look-alike companies (M Lhuillier ≠ Cebuana / PJ Lhuillier Inc.).
• Person pages cite-to-public-record only. No home addresses, personal phones, family info, or rank-and-file employees.

• The platform documents accounts including a first-surfaced consumer report of a sub-litigation charge paired with an MCCS kill-switch shutdown. This pattern — small disputed amounts below the cost of legal redress, enforced by remote-disable leverage — is the documented origin of LabanPH and the editorial spine of its early reporting.
• LabanPH is operated as an editorial collective. Individual operator identity is not disclosed for safety reasons given the regulatory-target nature of this work.
• Affiliate revenue from rate-comparison links is disclosed on each rates page. Affiliate status does not influence whether a company is listed as a bad actor.
• No advertising. No paid placements. No sponsored content.
• If a moderator has a personal connection to a company under review, that moderator recuses from the file.

• Complaint files: retained until the complainant requests deletion or 7 years after final resolution, whichever is shorter.
• Server logs: rotated every 30 days.
• Whistleblower claim codes: stored as SHA-256 hashes; the original code is never persisted.
• IPFS-pinned evidence (opt-in only): permanent and not removable. The opt-in flow shows a permanence warning before submission.
• Backup snapshots: encrypted and rotated every 90 days.

Errors are logged at /corrections with date, what was wrong, how it was fixed, and the source that prompted the correction.