Team

MetaWeave Consulting LLP designs and runs enterprise AI offices for large organisations. We built LIFEOSAI — the substrate this entire site documents — and deploy it in production today across ship management, NGO operations, news editorial, and AI safety.

Delivery team

MetaWeave ID card — Prashant Kumar Singh, Founder & CEO — Marine Engineer · MBA IIM Calcutta · 13 years Chief Engineer at sea · founder of MetaWeave Consulting · co-founder of the Applied AI Foundation. Designs the systems, holds the relationships, runs the room.

MetaWeave ID card — Sriram A, Founding Director — Marine engineering background. Deep ship-management operational experience. Leads engagements where domain matters.

MetaWeave ID card — An Suhail A, Founding Engineer — Owns the LIFEOSAI codebase day-to-day. Built the platform overview + hub-and-spoke diagrams on this site. Ships the agents.

MetaWeave ID card — Prasanna, Founding AI Engineer — Builds and ships AI agents, integrations, and automations on LIFEOSAI — from office tooling to client-facing workflows. Turns the substrate into working offices.

Where we deploy

Ship management office

Multi-fleet ship-management deployment. Email processing, ERP integration, master + crew workflows. Production scale.

Maritime AI platform

Performance analytics, noon reports, emissions validators — domain agents on the same substrate.

Editorial workflows

Editorial agents reading source streams across multiple perspectives. Stories cluster, daily final story rebuilt.

AI Guardrail Lab (the showcase)

9 agents for AI incident analysis + guardrail design. Available as a starter office for any enterprise.

Our public artefacts

GitHub · LIFEOSAI The orchestration substrate, agents, skills. Read-access for engagement clients.

Workshop in Tokyo The 25–29 May 2026 NBS engagement — workshop materials live and post-workshop.

System architecture The two architecture papers (orchestration + memory) published in full.

How we work

Default	What it means
Substrate, not platform	Clients take the code, own the deployment, build their own offices. We help when they want help.
Async + written	We work in writing wherever possible — clear, dated, file-tracked.
Demos beat slides	Every concept lands as a running demo before it lands as a paragraph.
One office at a time	We deploy a first office in 5–8 weeks, then let the team build subsequent offices on the same substrate.