Simulation Environment
Granullo

How Granullo Works

The authoritative visual model for understanding Granullo's governance flow.

v1.0 — Canonical Reference

Make sure money does what it's supposed to do.

What Granullo IS

  • ✓A governance layer • defines intent, constraints, and audit trails
  • ✓A system of record • for decisions, approvals, and coordination
  • ✓An explainability platform • AI explains governance, never decides
  • ✓Infrastructure for oversight • read-only visibility for authorized parties

What Granullo is NOT

  • ✗Not a bank • Granullo does not hold, move, or settle funds
  • ✗Not a wallet • no balances, no accounts, no custody
  • ✗Not a procurement portal • no purchasing, no vendor selection
  • ✗Not a decision-maker • AI explains, humans and banks execute

Granullo governs. External systems execute.

All settlement and fund movement happens through regulated partner banks.

The Governance Flow

Intent

Client defines why the program exists and what it should achieve.

Client

Rules

Eligibility criteria, spending constraints, and merchant rules are defined.

Client + Bank

Coordination

Multi-party alignment, approvals, and documentation across domains.

All Parties
GRANULLO STOPS HERE

Bank Execution

Settlement, fund movement, card issuance, and account operations.

Bank

Governance Record

Every decision, approval, and outcome is logged immutably.

Granullo

Responsibility Boundaries

Granullo Stops Here
  • Intent and rules recorded
  • Decisions logged
  • Coordination complete
Bank Responsibility Begins
  • Issue accounts/cards
  • Process transactions
  • Manage escrow
Settlement Occurs Here

Settlement occurs entirely outside Granullo. Banks move money, Granullo records the governance that allowed it.

What Granullo Will Never Do

Hold money

Funds never enter Granullo systems

Move funds

Settlement is executed by banks

Show balances

Balance data remains with banks

Replace bank systems

Banks retain full operational control

Act as a payment app

Granullo governs intent, not transactions

Digital Purpose Pass (DPP)

A Digital Purpose Pass is NOT money

It is a Right to Spend: a digitally verified eligibility unit that authorizes a specific purchase at an approved merchant within program constraints.

What DPP Does
  • • Determines IF a transaction is allowed
  • • Encodes program rules and constraints
  • • Validates merchant category (MCC)
  • • Checks beneficiary eligibility
Bank Executes Settlement
  • • Processes the actual transaction
  • • Moves funds from escrow
  • • Issues cards and accounts
  • • Reports settlement outcome
What DPP Does NOT Do
  • • DPP ≠ Money
  • • DPP ≠ Settlement
  • • DPP ≠ Balance
  • • DPP ≠ Payment instruction

Key Distinction: The DPP determines eligibility. The partner bank handles settlement. These are separate systems with a clear boundary.

Program Archetypes

All programs in Granullo follow one of four archetypes: governance templates with different defaults based on what the primary constraint is. Archetypes are NOT separate products or modules.

Purpose-Bound

Programs where the intent or purpose is the primary constraint. Funds must be used for a specific purpose.

CSR
ESG
Donations
Policy-Bound

Programs where rules and policies are the primary constraint. Complex rules determine eligibility.

Benefits
Allowances
Expenses
Vendor-Bound

Programs where vendor relationships are the primary constraint. Controls based on who receives funds.

Vendors
Partners
Procurement
Eligibility-Bound

Programs where who qualifies is the primary constraint. Eligibility criteria determine access.

Subsidies
Scholarships
Aid

All archetypes share the same governance boundaries: Granullo records, banks execute.

Governance Intelligence Layer (GIL)

AI explains. AI never decides.

The Governance Intelligence Layer (GIL) uses AI to generate plain-language explanations of governance history, design patterns, and audit context.

What GIL Does
  • • Generates briefings for regulators, banks, clients, auditors
  • • Summarizes governance timelines and decisions
  • • Checks program design against declared archetype
  • • Detects governance drift from original design
  • • Identifies areas an auditor might ask about
What GIL Does NOT Do
  • • No scoring or rating programs
  • • No approvals or denials
  • • No transaction execution
  • • No financial recommendations
  • • No balance or payment information

Explainability-only: All GIL outputs are stored as immutable governance artifacts. GIL explains governance history • it never makes decisions, approves transactions, or processes settlements.

Concrete Example: Employee Fuel Allowance

INTENT

Acme Corp provides ₹5,000/month fuel allowance to sales team

RULES

Only at approved fuel stations in Mumbai region

COORDINATION

Bank approves escrow, HR confirms employee list

BANK EXECUTION

Bank issues cards, processes purchases, debits escrow

RECORD

Granullo logs every decision for audit and compliance

Flagship Example: Universal Income Governance

Guaranteed Income Programs

How Granullo governs Universal Basic Income, Guaranteed Income pilots, and population-scale benefit programs • without selecting beneficiaries or disbursing funds.

Granullo Governs
  • ✓ Policy version history
  • ✓ Eligibility rule schemas
  • ✓ Decision reference logs
  • ✓ Public accountability reports
External Systems
  • → Identity verification
  • → Eligibility evaluation
  • → Enrollment decisions
  • → Social registries
Banks/Treasury
  • → Fund disbursement
  • → Payment execution
  • → Tax reporting
  • → Account management

Granullo does NOT: Select beneficiaries, store PII, disburse payments, or make eligibility decisions.

Settlement is executed by partner banks. Granullo records governance, rules, and outcomes.

v1.0 • This is the canonical reference. Do not duplicate elsewhere.

Drag me for clarity