The Framework

The architecture beneath every project

LOFL is not a general assistant or a consultancy deck. It is a systems architecture. Every piece of work must trace cleanly from a real human act to value that returns to the people who created it — and we can always name where a project sits on that path.

The spine

Activity → Evidence → Verification → Tokenization → Exchange → Regeneration

Six stages, in order. We do not compress verification into tokenization, and we do not treat activity as its own reward before evidence is defined.

Stage 01Activity: A real human act of learning, teaching, creating, stewarding, or caring. We help design and scaffold the activity so it is completable and observable.
Stage 02Evidence: Artefacts, logs, assessments, or records that prove the activity happened. We help define what counts as evidence and how it is captured and stored — with consent.
Stage 03Verification: A human or AI-assisted review that confirms the evidence against defined criteria. We design the rubrics and workflows, and flag the gaps.
Stage 04Tokenization: An Impact Unit is issued to the contributor's ledger. We specify which unit applies and keep issuance conservative and earned.
Stage 05Exchange: Verified impact moves into a marketplace, recognition system, or policy layer — without ever conflating internal units with regulated instruments.
Stage 06Regeneration: The feedback loop that makes the system self-sustaining and just. We identify how value loops back to contributors and communities, and flag extractive patterns.

Foundation principles

Four principles that govern every decision

When they are in tension with convenience or speed, the principles win.

i · Systems thinking first

Every problem is a system — incentives, behaviour, policy, second-order effects. Map it before proposing a solution. Name the actors, the flows, the feedback loops, and the failure modes.

ii · Indic & ethical lens

Grounded in Indic philosophy — balance, dharma, care for the commons, non-violence toward the self — paired with modern ethics: informed consent, data minimisation, anti-extraction, and dignity for every contributor.

iii · Open by default

Default to open protocols, interoperable architectures, and public-good tooling. Proprietary lock-in must be justified. Creative Commons licensing is the default for intellectual outputs.

iv · Product + capacity

Every engagement leaves behind something that works and people who understand it. The measure of the work is what persists when the session ends.

Where the work is recorded

The three ledgers

All project work generates entries in one or more of three ledgers. We always know which ledger we are writing to.

SDG 4 · Quality EducationKnowledge: Resources, pathways, curricula, mentor time, and reusable learning artifacts.
SDG 16 · Strong InstitutionsImpact: Verified impact claims, milestones, evidence packs, and verification sign-offs.
SDG 8 · 11 · 13Growth: Personal and institutional evolution; capability maturity; governance development.

The Impact Unit taxonomy

One verified activity, one earned unit

When an activity is ambiguous across types, we choose the dominant contribution and record the secondary one in the evidence.

LIU

Learning Impact Unit

Teaching, tutoring, mentoring, learning facilitation, curriculum creation.

SIU

Skill Impact Unit

Vocational training, craft development, professional upskilling, demonstrated competency.

CIU

Cultural Impact Unit

Oral traditions, artistic practice, community ritual, language preservation, cultural transmission.

GIU

Green Impact Unit

Ecological stewardship, water-body care, agroforestry, environmental documentation.

Units are non-transferable and non-tradable at the internal level. They are credentials and reputation signals — not securities. One activity issues one primary unit; we never stack units on a single unverified activity.

Verification protocol

No claim enters a ledger without verification

We begin with the simplest level sufficient for the stakes — and never engineer L2 complexity into an L0 pilot.

Level 0Self-reported: Verified by the contributor themselves. For early pilots, proof-of-concept, and low-stakes iterations — flagged clearly as unverified.
Level 1Peer verified: Verified by peers, mentors, or community reviewers. For knowledge listings, portfolio rubrics, and community learning circles.
Level 2Independent assessor: Verified by a qualified third party with defined credentials. For medium- and high-stakes programs, milestone grants, and funder-facing claims.
Level 3SSE-aligned: Verified through a regulated, SIA-equivalent workflow. For annual impact reporting and regulated disclosure.

For any project involving children, documented parental or guardian consent is required before any AI processing, verification review, or ledger entry. This is a hard stop, not a guideline.

The quality gates

Four tests every deliverable must pass

Could Sita Tai — a semi-literate woman in a Konkan village who teaches basic literacy to five children in her home — participate in this system, have her contribution verified, and receive meaningful recognition, without humiliation, excessive friction, or dependency on systems she cannot access or afford?

— The Sita Tai Test. The architecture exists to make her contribution constitutionally visible.

The 15-minute steward test. Can a teacher manage this in under fifteen minutes a week?
The ledger-ready test. Which ledger does this belong to, and what would make it ready to enter?
The VIC test. Does this move us toward a Verified Impact Claim — or only toward a more refined framework for producing one someday?

System design rules

Non-negotiable

Agents propose; policy decides

We may generate, draft, suggest, and model — but no agent writes directly to a production ledger or verified claim without a human sign-off in the workflow.

Evidence-first

A claim is not publishable until its evidence is indexed, stored with a content-addressed identifier, and access-controlled. No claim, no unit.

Everything is versioned

Listings, disclosures, metric definitions, evidence packs, and reports carry version numbers and provenance. Nothing is canonical without a date and a source.

The regulatory boundary is sacred

Internal Impact Units are not securities, and the regulated lane is a separate workflow. We never design features that blur the line.

Scaffolding ≠ substance

A well-structured framework with no real data, decisions, or constraints is not a deliverable — it is preparation for one. We name the difference.

Deployability is the filter

If a session produces only more structure and no real-world test, that is a pattern to flag. The goal is a verified claim, not a prettier framework.

See the framework at work

The programs are where the spine meets the field.

Explore the programs Work with us