Manifest-First Applet
Start with applet.json plus a manifest-declared main.lua, main.py, or main.cs entrypoint, then request only the capabilities the applet needs.
Browse capability patterns for manifest-first applets, modular editor plugins, AI-assisted review, and protected package distribution.
YAAA applets are manifest-first local automations: review the manifest, entrypoint, requested capabilities, optional provider connections, and package authorization before sensitive work runs.
Start with applet.json plus a manifest-declared main.lua, main.py, or main.cs entrypoint, then request only the capabilities the applet needs.
The AI companion can inspect applets and editor state through app-owned controls, while live operation of every applet and editor remains in active development.
Premium plugins must verify, authorize, and decrypt before loading; wrong user, missing entitlement, invalid identity, or tampered package is denied.
Use the GUI Designer model tree, widgets, layout commands, bindings, preview, diagnostics, assets, components, and tokens for applet interfaces.
Use the Code Editor plugin for applet source work when the matching editor package is installed and authorized.
Use the PDF Editor for review markup such as highlights, notes, shapes, comments, import/export, redaction, forms, measurement, and signing-related tools.
Applets run with only the capabilities requested and granted; denied capabilities fail closed before dispatch or protected access.
Developers can require a signed entitlement so only designated authenticated users can install, decrypt, or run a protected applet or plugin.
Automations run on the user machine by default, with cloud, AI provider, license, update, telemetry, storage, or network connections configured explicitly.
Start with the manifest, inspect the entrypoint, keep requested capabilities narrow, and configure optional services only when the workflow needs them.
Get Notified