Applet examples for local-first automation

Explore focused patterns for manifest-first applets, GUI Designer workflows, sealed premium plugins, and AI-assisted editor collaboration that remain inspectable on the user's machine.

Calculator applet

Beam Calculator

A production-style applet pattern: clear inputs, visible assumptions, result validation, exportable notes, and a reminder that engineering outputs require qualified review.

Open the Beam Calculator example page ->

applet.json
{
  "applet_id": "com.example.beam_calculator",
  "version": "0.1.0",
  "publisher_id": "pub.example",
  "language": "python",
  "entrypoint": "main.py",
  "capabilities": []
}

main.py
def hello():
    return True
AI companion pattern

Client Intake Review

The AI companion is being built to inspect applets and drive the Code, GUI, and PDF editors through app-owned controls. This example keeps the generated applet manifest-first and requires human review before it touches selected folders.

applet.json
{
  "applet_id": "com.example.client_intake",
  "version": "0.1.0",
  "publisher_id": "pub.example",
  "language": "lua",
  "entrypoint": "main.lua",
  "capabilities": []
}

main.lua
handlers = {}
function handlers.review()
  return true
end
GUI Designer applet

Client Portal Checklist

Build a guided checklist in the GUI Designer with widgets, bindings, preview, diagnostics, and a manifest-declared entrypoint. The applet should request only the capabilities it needs.

applet.json
{
  "applet_id": "com.example.client_portal",
  "version": "0.1.0",
  "publisher_id": "pub.example",
  "language": "python",
  "entrypoint": "main.py",
  "capabilities": []
}

main.py
def hello():
    return True
Premium plugin

Sealed Field Tools

A protected plugin pattern for specialized tools: the package is signed, encrypted, and locked to authorized users with the required entitlement before it can decrypt and run.

premium plugin package
- signed package metadata
- encrypted plugin payload
- required entitlement: com.example.field-tools
- unauthorized or tampered package: denied

What makes an applet production-ready?

  • Manifest first: include applet.json and the declared main.lua, main.py, or main.cs entrypoint.
  • Local data boundary: identify which folders, files, and optional network services the applet can touch.
  • Human review: show assumptions, generated explanations, and outputs before high-impact actions run.
  • Traceability: keep logs, versions, and validation evidence so users can audit what happened later.
  • Safe failure states: stop on missing inputs, ambiguous units, expired licenses, or failed checks instead of guessing.

Build from a known pattern

Start with the quickstart, choose the example closest to your workflow, then adapt it with applets, the GUI Designer, sealed plugins, and explicit capability requests.

Open the getting started guide ->