Qentrix Labs, Inc. · Phase 0
iUGNAY · Product & Architecture Foundation v0.1

Product Baseline & Scope

IUG-P0-001v0.1 · Draft / Not ApprovedReview: IUG-P0-G126 October 2026
Controlled draft — not implementation authority The complete 24-page iUGNAY Proposal & Functional Masterplan v1.0 (26 October 2026) is now received, checksum-verified and source-reconciled. Sponsor approval, pilot agreement, implementation authorization, official integrations and public partnership claims remain pending.

iUGNAY is envisioned as a resident-centered public-service platform, beginning with barangay operations and extending only through authorized municipal, city and future agency relationships.

Product Starting Point — Verified v1.0 Proposal

The 24-page final proposal v1.0 (26 October 2026) has been source-checked, including its six pillars on pages 4 and 6–11 and the **P0/P1/P2 scope matrix in Appendix A (page 23)**. These are source-confirmed proposal contents, but still await G1 approval and locally agreed pilot scope.

IDCandidate pillarIllustrative scope
IUG-CAP-01Resident ServicesHouseholds, resident registry, clearances, QR verification, reports, announcements
IUG-CAP-02Peace, Safety & JusticeBlotter, barangay mediation, tanod, disaster/relief, restricted VAWC/child cases
IUG-CAP-03Health, Social & EnvironmentHealth-worker tasks, program aid, youth and social services, waste operations
IUG-CAP-04Governance, Finance & CouncilMinutes, resolutions, committees, collections, assets, disclosure and reporting
IUG-CAP-05Livelihood & Economic UpliftmentJobs and training, small businesses, farm/fisherfolk matching, marketplace
IUG-CAP-06Proactive Personal AI CompanionOpt-in multilingual assistance, relevant alerts, maps and controlled family concepts

Stakeholders

Residents and households; Punong Barangay, Kagawad and committees; Secretary and Treasurer; tanod, disaster and environmental teams; health and social workers; city/municipal LGUs; approved agencies; platform operators. Job titles never imply unrestricted access.

Indicative Delivery Stages (proposal v1.0, page 17)

StageDraft working focusOpen dependency
Weeks 1–2Discovery, process mapping, legal/data analysisNamed LGU/pilot approval
Weeks 3–4Foundation: roles, initial lawful data and dashboardsLGU readiness, access review
Weeks 5–8Pilot: requests, certificate tracking, incidents and staff trainingAuthorized service workflows
Weeks 9–12Pilot operations, feedback, support, quality reviewMeasurable acceptance
Conditional later rolloutLivelihood/marketplace, optional AI, notifications, LGU expansionApprovals and vendor contracts

Source-Reconciled Pilot and Expansion Scope

P0 / minimum pilot: resident/household data coordination, request and certificate processing, incident/blotter intake, office roles/assignments, Kapitan dashboard and staff training. P1 / later barangay rollout: QR verification, concerns, tanod/justice/disaster, council and inventory, selected social/health (gated), livelihoods and first AI guidance. P2 / advanced or external: city/agency integrations, producer marketplace, safety mapping, opt-in family circles and native mobile — none implicitly included in P0.

Candidate Requirement Clusters

IUG-FR-001–004: resident records, certificate lifecycle, assigned case processing, scoped reporting. IUG-FR-005–007: council, restricted social/health and disaster operations. IUG-FR-008–010: optional livelihood, marketplace/payment and guarded AI assistance. IUG-FR-011–012: authorized data exchange and assisted non-smartphone service. Full wording and dependencies are in the Markdown source.

Product Safeguards and Nonfunctional Intent

  • Privacy, case confidentiality, separation of duties, provenance and audit before feature expansion.
  • Accessible, low-bandwidth, multilingual and assisted resident journeys.
  • No automatic public-benefit decisions, diagnosis, law enforcement determinations, national ID merge or cross-LGU disclosure through AI.
  • No approved operational SLOs, price figures, certified government integrations or signed agency partnerships.

G1 Review and Source Reconciliation

See IUG-G1-TRC-001 for source-page and P0/P1/P2 requirements and IUG-G1-RVW-001 for G1-D01–D06 sponsor review. An earlier conceptual v0.1 component list is a historical comparison, not a v1.0 PDF-native list. This draft is not software implementation authorization.

G1 Exit Checklist

PDF received and checksum recorded; review source reconciliation and confirm pilot in/out; assign LGU reviewers and legal roles; bound outcomes and metrics; retain open decisions with owners. Review open decisions.


Authoritative Markdown: IUG-P0-001 source on private GitHub. Human-readable summary; refer to source for normative detail.