Export and restore multi-agent assistant setups as Markdown

GBDL (GrokBot Definition Language) is a community-proposed, v0.1 draft open format for saving a multi-agent desktop assistant setup - a dispatcher, specialist agents, routines, and account connectors - as a single portable Markdown file, then reinstating it later in a fixed order: connectors first, then onboarding, agents, memory, and routines. It is explicitly not an official Grok Bot product format, just a human-readable convention anyone can implement or extend. Canonical files use the .gbdl.md extension: a short Markdown introduction followed by exactly one yaml fence containing the bot persona, connectors, onboarding, user_context, and agents. A JSON Schema for the YAML object is published (schema/gbdl-0.1.schema.json), along with a SPEC.md defining semantics and validation rules, and three example files (a minimal definition, an ops-team fleet with dispatcher/email/workspace/Notion-style agents, and a fictional media-ops fleet). The problem it addresses: an assistant fleet - dispatcher plus specialists plus routines plus account links - usually lives trapped inside one product session; GBDL makes the definition itself portable enough to check into git, share as an example, or rebuild the same shape on a new machine without retyping every agent prompt by hand.

Hard rules for v0.1: no secrets (tokens, passwords, private keys) in the file - connectors declare which accounts to link, but credentials stay in the host; no real personal PII in shared examples (fictional names and example.com only); connectors must be prompted for before any agent that needs them is created; and the spec version is pinned in the file itself via gbdl: "0.1".

Use it to check a multi-agent assistant fleet's definition into version control, share a working example with someone else, or rebuild the same agent/connector/routine shape on a new machine. It is a draft convention, not a finished or officially adopted product format - it requires a GBDL-compatible loader to actually reinstate a definition automatically, or following the reinstantiation order from the spec by hand if no loader exists yet.

Input is a .gbdl.md file: Markdown text plus one YAML fence describing persona, connectors, onboarding, user_context, and agents. Output, via a compatible loader, is a reinstated assistant fleet - connectors linked first, then onboarding, agents, memory, and routines in that order.

Validated against a published JSON Schema (schema/gbdl-0.1.schema.json); intended for any GrokBot-style desktop assistant host that implements a GBDL-compatible loader.

People building or sharing multi-agent desktop assistant fleets who want the fleet's definition portable across machines and sessions, checked into git like any other config. MIT licensed.