{
"$schema": "https://cmn.dev/schemas/v1/spore-core.json",
"id": "agent-first-data",
"name": "Agent-First Data",
"version": "0.26.0",
"domain": "agentfirstkit.com",
"key": "ed25519.BwbSzqdDYyMN1pPW5snRk3afrJAovHn8aueMvDpfNKVw",
"synopsis": "A naming convention that lets AI agents understand your data without being told what it means, plus a CLI and library for reading and safely editing structured JSON, TOML, YAML, dotenv, and INI documents.",
"intent": [
"Encode all semantic information in the field name itself so agents parse structured data without external schemas, documentation, or type systems — _ms/_s/_epoch_ms for time, _msats/_sats/_usd_cents for currency, _bytes for size, _secret for auto-redaction",
"Define a JSONL output protocol where every line carries a kind discriminator (result, error, progress, or log), a payload field named after that kind, and a trace object for execution context (duration, token counts, cost, data source) — same structure whether the transport is CLI stdout, HTTP response body, MCP tool result, or SSE stream",
"Provide three output formats via --output json|yaml|plain: JSON is the canonical lossless format, YAML preserves structure with quoted strings and --- separators, plain applies suffix-driven human formatting (epoch_ms → RFC 3339, _bytes → human-readable, _secret → ***, _ms ≥ 1000 → seconds)"
],
"license": "MIT",
"mutations": [
"Render Markdown help from the shared help model instead of the argument parser's own help writer, so --output selects a format and never a different set of commands or arguments",
"Make the Markdown export real Markdown — heading, prose, usage, and argument/subcommand tables — instead of concatenated terminal help blocks with no Markdown structure",
"Add a gate check asserting that json, plain, and markdown describe the same commands and the same arguments at one scope, verified against a reintroduced regression",
"Drop the -0 alias for --null on paths and keys: a short flag that merely abbreviates a flag of afdata's own invention, which the convention's own rule rejects",
"Document --null where a reader meets it, in the Bash authoring guide and the README, including why line-separated output is unsafe when a JSON key contains a newline",
"Fix the spec's short-flag example to cite imitation of an established interface rather than an abbreviation of afdata's own flag"
],
"bonds": [],
"tree": {
"algorithm": "blob_tree_blake3_nfc",
"exclude_names": [
".git",
".cmn"
],
"follow_rules": [
".gitignore"
]
}
}