A regulated agricultural financial infrastructure platform for the Philippines, using Stellar strictly as a settlement and tokenization rail.
This repository contains the complete documentation suite for a Philippines-first, regulator-aligned platform for agricultural subsidy distribution, controlled-value vouchers, merchant payments, and microfinance.
The platform operates as a Program Administrator & Orchestration Layer. It does not act as the anchor, custodian, or primary credit risk taker unless explicitly licensed. All operations align with BSP, AMLC, SEC, DPA, and PhilSys regulatory frameworks.
| # | Document | Description |
|---|---|---|
| 1 | 00_ARCHITECTURE_BACKGROUND.md |
Platform positioning, architectural principles, boundary mapping (Stellar vs. off-chain), regulatory philosophy, compliance-by-design framework, auditability model, scope boundaries (MVP → Scale → Regional), failure domain philosophy, and five core architectural patterns (Dual-Ledger, Anchor Abstraction, Policy Decision Point, Reconciliation Control Tower, Assisted Agent Channel) |
| 2 | 01_BSP_AMLC_COMPLIANCE_MATRIX.md |
Complete regulatory compliance mapping: BSP licensing (Circulars 1098, 946, 808, 1097, 1126, 972), AMLC obligations (CTR/STR/SAR, CDD/KYC tiers, PEP/sanctions screening, 8 transaction monitoring rules, 5+ year retention), SEC pathways (Lending Company vs. API referral model), DPA compliance (Controller/Processor roles, DSR handling, purpose limitation), application timelines, partner delegation models, regulator engagement checklists, and audit readiness matrix |
| 3 | 02_ANCHOR_PARTNERSHIP_SLA_TEMPLATE.md |
Formal SLA template for BSP-licensed anchor partners (EMI/Bank/Trust): fiat custody, reserve segregation, SEP-10/12/24/31/38 integration specifications, liquidity guarantees, T+0/T+1 settlement commitments, failover routing logic, dynamic FX quoting, penalty clauses, audit rights, dispute resolution, and full technical API contract for the Anchor Orchestrator (endpoints, idempotency, webhook delivery guarantees, error codes) |
| 4 | 03_TREASURY_RESERVE_ATTESTATION_PLAYBOOK.md |
1:1 PHP float backing model, segregated trust account structure with legal segregation language, daily NAV reconciliation workflow (three-way match: bank float ↔ on-chain supply ↔ program ledger), variance thresholds (>0.01% triggers halt), investigation queues, maker-checker compensation approvals, 8 stress testing scenarios, circuit breakers (70/85/95%), exposure limits per anchor (max 40%), third-party auditor reporting template, and monthly/quarterly/annual attestation processes |
| 5 | 04_PHILSYS_KYC_INTEGRATION_SPEC.md |
PhilSys (PSA/DICT) API integration flow with explicit consent capture and data minimization, four-tier identity model (Tier 0 Assisted → Tier 1 Gov ID → Tier 2 PhilSys-Linked → Tier 3 Credit/Coop/SEC) with exact capability limits per tier, AMLC/CFT screening integration (PEP, sanctions, adverse media, device/IP profiling), fallback onboarding paths for rural areas (offline queue, agent-mediated verification, deferred sync), data retention schedules, consent revocation workflows, DSR handling, and cross-border transfer restrictions |
| 6 | 05_VOUCHER_POLICY_ENGINE_CONFIG.md |
Off-chain policy engine architecture with on-chain Stellar enforcement mapping, MCC-like agri-vendor category tagging schema (10 eligible + 7 blocked categories), whitelist management, spend limits (daily/weekly/seasonal), program-window expiry and auto-burn logic, Stellar ClaimableBalance usage for conditional disbursements, asset flag configuration (AUTH_REQUIRED, AUTH_REVOCABLE, AUTH_CLAWBACK_ENABLED) with compliance triggers and operator approval workflows, and policy change governance (versioning, testing sandbox, maker-checker deployment, rollback procedures) |
| 7 | 06_DPA_GOVERNMENT_ACCESS_BLUEPRINT.md |
Data ownership model (Government = Controller, Platform = Processor under RA 10173), DPA compliance framework (purpose limitation, AES-256/TLS 1.3 encryption, retention schedules, deletion workflows), governed API access structure for government audit/BI dashboards (read-only, role-scoped, rate-limited, consent-tagged), immutable audit log design (event-sourced financial activity, signed API payloads, CSV/JSON/PDF export formats), and incident response (72h breach notification SLA, forensic logging, third-party data sharing controls, independent audit hooks) |
- Compliance-by-Design — Every flow embeds BSP/AMLC/DPA controls natively
- Reconciliation-First — Dual-ledger architecture is the foundation, not an afterthought
- Minimal On-Chain Exposure — Only settlement hashes and token movements on Stellar; all compliance logic off-chain
- Bounded Failure Domains — Component isolation, circuit breakers, graceful degradation
- Assisted Access Model — Agent-mediated onboarding for rural and low-connectivity users
| Body | Key Regulations |
|---|---|
| BSP | Circulars 1098, 946, 808, 1097, 1126, 972 |
| AMLC | RA 9160 (AMLA) as amended by RA 10365 |
| SEC | RA 9474 (Lending Company Regulation Act) |
| DPA / NPC | RA 10173 (Data Privacy Act) |
| PhilSys | RA 11055 (Philippine Identification System Act) |
| Stellar | SEP-10, SEP-12, SEP-24, SEP-31, SEP-38 |
- Bull Run Consulting
- Starting Block Ventures
Proprietary — All rights reserved.
© 2026 Bull Run Consulting / Starting Block Ventures. This documentation and all associated materials are the proprietary intellectual property of Bull Run Consulting and Starting Block Ventures. Unauthorized reproduction, distribution, or use is strictly prohibited.
See LICENSE.md for full license terms.