Create is the authoring side of Burton: knowledge, structured records, and the workflows that run later. Markdown and YAML stay files you can diff. The Agent can draft them; you finalize.

Wiki

The knowledge store is a git repository of markdown per team. That is the moat: clone, review, restore.

• Create files and folders. Nest or hoist with drag-and-drop.
• Link with [[Wiki links]] or ordinary Markdown.
• Every save, move, rename, and folder change is a git commit.
• Connect a remote and branch, then Sync or Clone.

The built-in engine is llm-wiki (Karpathy-style). Generated trees are written by rabun-wiki; the UI shows them as read-only. Detail: Wiki.

Source: src/plugins/wiki

Automations

Agent-designed automations are how Burton compounds. The Automations plugin is a vertical journey of triggers, waits, branches, and messages. Save a draft, finalize a live version Rabun can run. Import and export burton.workflow/v1 YAML.

If a step depends on a disabled plugin, Rabun skips it instead of failing the run. Burton authors; Rabun executes (rabun-automations planned).

Source: src/plugins/automations

Forms and schemas

Forms are custom YAML forms with field types, validation, and draft/finalize. Public sites POST captures to rabun-forms; Burton never stores the form token.

Schemas is a YAML library with Open Knowledge Format, schema.org search, downloads, and finalize. Reuse a schema from a form or a site.

Source: forms · schemas

Images

Generate images from a description through an MCP endpoint (the Agent / Images plugin is a client). Export SVG, PNG, WebP, or JPEG.

Source: src/plugins/images

Documents

YAML documents you draft, then publish or attach:

Source: resumes · jobs · events