Supporting evidence
Absolute portfolio archive
The complete artifacts and detailed records behind the account. Current public references, original work and proposed designs retain their labels.
Detailed material
The problem
These materials provide background for selected product cases. They include company capability presentations, proposals and additional workstream notes with different dates and ownership records.
Browse by the question behind the source
The archive covers field-data collection, institutional information handoffs, commerce/distribution and credit proposals. Use the relevant source alongside its selected case; the index separates documented workstream, contribution and maturity.
Selected decision accounts
For delivered product accounts, return to commerce launch and operational readiness, trade payments and settlement, or agricultural information in lender appraisal. These background materials do not replace those accounts.
Artifact status
This archive does not consolidate a personal impact total. It records source and maturity per item.
How to use the archive
Each retained item has a source, status and related case. Company capability presentations and future plans are not personal delivery outcomes.
Workstream and source index
The following index lists each additional workstream once. Where the compilation does not establish individual ownership or a complete delivery record, the item remains team/company context.
Scroll across to see every column.
| Reader question / workstream | Source and maturity | Contribution and related account |
|---|---|---|
| Field-data collection · insurance survey app and web workflow | Additional compilation; multi-season team workstream. User-versus-survey units and revenue attribution unresolved. | Individual ownership not consistently established. Background to agricultural data and insurance. |
| Government and multilateral value chains | World Bank/Uttarakhand notes and JICA/Assam references, including fisheries monitoring. Institution-specific delivery status varies. | Use alongside the institutional material; no universal deployment of every advertised capability. |
| Commerce and distribution · Upaj centres | Additional phygital store, ARPU and expansion notes; separate stage/scope from the 200-store launch. | Related account: agri-input launch. Unresolved commercial totals excluded from personal impact. |
| Rural distribution · pipes and fittings | Digital roadmap for a distribution business. | Roadmap context; client turnover is not value created. Personal ownership detail is incomplete. |
| Investment due diligence | Product, technology and regulatory workstreams around a company raise. | Company financing context; a personal ownership breakdown is not supplied. |
| Enterprise trade pilot | Logistics, inspection, KYC and partner categories; lead and transacting-account notes. | Separate pilot from SilkRoute. Its scope is not consolidated into the flagship programme GMV. |
| Risk-SaaS and farmer-credit planning | Planning notes containing projected ARR and a financial-year credit target. | Plans, not delivered revenue or disbursement. Related account: assessment-to-lender product work. |
Source: additional Absolute compilation. Dates and personal contribution are not consistently supplied; this index does not upgrade company work, plans or targets to delivered personal results.
Historical institutional data-flow proposal
The proposal describes permissioned farmer/land information and analytical observations feeding institutional APIs. Its six layers are farmer entry; consent and registries; observations; analysis; institutional APIs; and commercial operation. Access and billing concepts remain proposed.
The source names Sentinel-1/2, Landsat, SRTM, MODIS, ERA, IMD and MOSDAC, plus proprietary IoT, soil samples and crop-recipe work. These are company data-stack descriptions, not personal authorship of every layer. The architecture is retained as historical proposal context.
| Layer | Information or function |
|---|---|
| Farmer entry | Mobile interaction, identity/KYC and access control |
| Registries and consent | Farmer and land records with permissioned access |
| Observation inputs | Satellite, weather, soil, IoT and crop information |
| Analysis | Farm health, yield/risk and recommended actions |
| Institutional APIs | Defined inputs, acceptance criteria and returned information |
| Commercial operation | Proposed central-wallet billing and payment handling |
Tamil Nadu institutional proposal
The historical proposal targets institutional access to farm information, advisory and monitoring. Its proposed pilot includes geofencing, KYC/transliteration, farm-health information, monitoring, loan/SOP alerts, insurance, bank-lien and input-loan information, and seven-day weather advisory.
API/wrapper and acceptance expectations are included with timing “as mutually agreed”. Potential users include banks, rural NBFCs, fintechs, government bodies, NGOs, farmers and insurers. The source does not establish acceptance, production deployment or NPA impact.
The deck’s footprint and R&D, country/state, staff/scientist, acreage, farmer-reach and advertised income/yield/input-cost claims are company context, not outcomes of this proposal or personal delivery.
Notes and sources
- Historical institutional presentations: Tamil Nadu slides 2–17 and 20–22; exact document dates are not supplied. These contain capability/proposal material, including work-in-progress and pilot labels.
- Additional Absolute compilation: team, business and planning notes. These records have different scopes and do not establish a consolidated personal impact total.
Historical Absolute / Upaj institutional presentations · Tamil Nadu presentation: slides 2–17 and 20–22 · Capability and proposed integration material; farmer-identifying examples excluded