AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
Git-native MDX docs. I built this for people who already write MDX in git. No second editor. Hosted is $0. MIT if I disappear.
Developer toolsTypeScript · MDXGitHub @mblodeOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Blode.md: git-native docs, published on merge
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Knowledge docs for agents. Git-native MDX. Publish on merge.
Your site is live on its own blode.md subdomain, taking its name, navigation, and theme from the docs.json that edda new writes.
Install the slash command for Claude Code or any skills.sh-compatible agent:
Then scaffold and deploy in plain language:
Every command exits with one of these, so a CI gate can branch on the number:Read the full README ↗Knowledge docs for agents. Git-native MDX. Publish on merge.
npm install -g edda-docs
# Sign in with GitHub in your browser, once
edda login
# Scaffold a docs site into ./docs
edda new docs --template starter
# Preview it at localhost:3030, reloading as you edit
edda dev
# Deploy
edda push docs
Your site is live on its own blode.md subdomain, taking its name, navigation, and theme from the docs.json that edda new writes.
| Command | Description |
|---|---|
edda login | Authenticate with GitHub in your browser, no API key to manage |
edda new [dir] | Scaffold a docs site, --template minimal or starter |
edda dev | Serve the docs locally and reload on save |
edda validate | Check docs.json before you deploy |
edda push [dir] | Deploy a docs directory to its project |
edda projects | List the projects on your account |
edda analytics | Manage PostHog: get, set posthog <key>, unset posthog |
Install the slash command for Claude Code or any skills.sh-compatible agent:
npx skills add mblode/edda -g --all -y
Then scaffold and deploy in plain language:
/edda new my-project --template starter
/edda push docs/ --project my-project
| Variable | Purpose |
|---|---|
EDDA_API_KEY / BLODEMD_API_KEY | API key. Used ahead of a stored login session, so CI needs no edda login. |
EDDA_PROJECT / BLODEMD_PROJECT | Default value for --project. |
EDDA_API_URL / BLODEMD_API_URL | API origin. Defaults to the hosted API. |
Every command exits with one of these, so a CI gate can branch on the number:
| Code | Meaning |
|---|---|
0 | Success |
1 | Error |
2 | Cancelled, including a declined prompt |
3 | Invalid input or config |
4 | Authentication required |
5 | Network failure |
With --json, a failure is data too: the command writes one line to stdout shaped {"error":true,"code":"AUTH_REQUIRED","message":"...","hint":"..."}. Branch on code, which is stable, rather than on message, which is written for a human.
push, validate, and projects take --json, and push reads EDDA_PROJECT / BLODEMD_PROJECT, EDDA_API_KEY / BLODEMD_API_KEY, and EDDA_BRANCH / BLODEMD_BRANCH from the environment, so CI can deploy without an interactive login.MIT
Crafted by Matthew Blode