SEM is a new file format that is simultaneously a human-readable document and an executable runbook — versioned, DRM-protected, and distributable on the AIMD marketplace.
npm i -g @getaimd/cli && aimd run runbook.sem---
name: Deploy Pipeline
version: 2.1.0
drm: seat-locked
---
# Deploy Pipeline
Run security scans, build, deploy and notify.
>>> Step 1: Run security scan
```bash
aimd scan --critical
```
---
name: Vercel Security & Deploy
version: 1.4.2
runtime: bash
drm: seat-locked
seats: 10
---
# Vercel Security & Deploy
Run full scan, build, deploy to edge network.
>>> Step 1: Security scan
```bash
aimd scan --level critical
```
>>> Step 2: Build
```bash
npm run build
```
…and 4 more steps
The SEM format
A .sem file is a Markdown document with a YAML frontmatter block — exactly like the files you already write for GitHub READMEs or blog posts.
The difference: any code fences tagged with a runtime (bash, python, node) are actual steps that get executed in sequence when you run aimd run.
The frontmatter carries metadata that makes it a software-grade package: version, DRM seat locks, runtime requirements, and licensing terms — all human-readable, all machine-enforceable.
Everything you need
SEM isn't just a clever format — it's an opinionated runtime with DRM, versioning, marketplace distribution, and compliance baked in from day one.
SEM files are plain Markdown with a YAML frontmatter header. Open them in any editor, read them like a README, and execute them like a script — zero friction.
Install the AIMD CLI, point it at any .sem file, and watch it parse, validate, and execute each step with structured output and timing.
Ship a SEM file as a premium product. Define seat counts in the frontmatter — AIMD enforces them cryptographically, blocking unauthorized runs.
Every SEM file lives as a versioned package on AIMD. Others can fork and remix your runbooks — you earn a 15% royalty on every downstream sale.
Declare the runtime per-step in backtick fences. SEM dispatches each block to the right interpreter — no wrapper scripts needed.
aimd proof generates a cryptographic compliance signature for each execution, creating an immutable audit trail for regulated environments.
How it works
Add YAML frontmatter (name, version, DRM settings) then write plain Markdown prose. Wrap executable blocks in backtick fences tagged with the runtime.
Run aimd publish. Your .sem file becomes a versioned, DRM-protected package on the AIMD marketplace, searchable and purchasable by others.
After purchase, buyers run aimd run your-runbook.sem. The CLI validates their license seat, then executes each step with structured output.
Every run from a seat-locked purchase earns you revenue. Every fork earns you a 15% royalty. Your knowledge compounds on autopilot.
Why SEM?
You've been gluing bash scripts, Makefiles, and internal wikis together for years. SEM is what they were always trying to be.
| Feature | Shell script | Makefile | SEM |
|---|---|---|---|
| Human-readable source | |||
| Executable without config | |||
| Versioned & distributable | |||
| DRM seat licensing | |||
| Marketplace monetization | |||
| Step-by-step audit log | |||
| AI-parseable frontmatter | |||
| Cross-runtime (bash/py/node) |
Use cases
From one-line deploys to multi-stage AI pipelines — every repeatable process deserves to be versioned, readable, and executable.
Deploy scripts with seat-locked access for your team or clients. Every execution is timed, logged, and cryptographically signed.
aimd run deploy.semIncident response that reads like prose and executes like code. Runnable under pressure, auditable after the fact.
aimd run incident.semChain LLM calls, tool invocations, and validation gates — packaged as a distributable, seat-locked SEM file.
aimd run agent-chain.semETL workflows that document what they do in prose and do it in code — all in the same file. No separate README ever again.
aimd run etl-pipeline.semSell or share reproducible onboarding runbooks. New hires get a working environment in one command — no tribal knowledge.
aimd run onboard.semStandard Operating Procedures that are cryptographically signed on every execution — immutable audit trail for regulated teams.
aimd proof sop.sem“I replaced our 3 bash scripts, a Makefile, and a Confluence page with one .sem file. My team actually reads it now.”
“I published my deployment runbook on AIMD. It's now my #1 income stream — 47 seats sold, 15% royalties on 3 forks.”
“SEM is what I always wanted runbooks to be. Executable documentation, not documentation-about-executables.”
Get started today
Join thousands of engineers turning their runbooks into premium, distributable products. It takes 5 minutes.