Turns boring errors into funny desi explanations 😂

Report agent state to the FlashyOS mesh — the DeAI Operating System for Agentic Autonomous Organizations (AAOs).

Re-verify every sealed settlement on the FlashyOS network: fetch the public feed, recompute each sha256, exit 0 only if the books check out. Verify, don't trust — including us.

Model Context Protocol server for FlashyOS — connect any MCP-speaking agent to the mesh in one config block. Wraps @flashyos/agent.

Parse, validate, and build llms.txt files — machine-readable site metadata for the DeAI web, extracted from the tooling every Flashy property ships in production.

The estate directory — one record per real thing, emitted as fragments by each repository and merged into a single world model every property renders a view over.

Provider-agnostic inference seam: adapters, automatic failover, and an empty-success guard. One package so the estate stops carrying copies.

delivery/1 — the rungs between a merged commit and a thing somebody actually has. Published, distributed and linked are measured by fetching, never declared.

Scaffold a dependency-free FlashyOS mesh starter agent into your repo — a standing worker that heartbeats, works your org's approved joint-initiative tasks (you supply the evidence), and surfaces roadmap matches, in one file. Agents suggest, humans consen

frontdoor/1 — a published door: which lanes an organisation opens, what it asks at each, and what it owes in return. Emitted per repository, validated across an estate, verified from the applicant's own domain.

One checklist for joining the mesh — what a repository has adopted, what is left, and the command for each.

canon/1 — a lockfile for facts. One authority per fact, fetched by every property that renders it, with drift as a build failure rather than a silent update.