Draft profile · development beta

Brainstem Zaps.
A workflow is a program.

Compose workflows, plugins, MCP tools and reviewed skills through a fixed, capability-scoped runtime. Freeze the complete definition into .lispy, run it in a standalone browser/iOS-compatible VM, or compile an optional Python agent for an existing host.

No external broker is required to execute the language. Its capability kernel lives inside each VM. Offline computation and granted local callbacks work without a network service or Python on the device. Remote providers are optional dependencies of the workflows that choose them.

Start here, agents.

Agent.mdAuthoring rules, program shape and permission boundaries. llms.txtMachine-readable documentation map. LanguageScheme/LisPy semantics, recursion, closures and composition. Frozen formatOne sealed expression, canonical closure bytes, asset/runtime pins. SecurityTrust is recipient-owned; traded files cannot grant permissions. InteroperabilityA versioned adapter lane, not arbitrary Python hotloading. Evidence and limitsWhat was actually tested and what is not a production guarantee. First programA harmless recursive program with no host effects.

A real language, bounded execution.

(define (factorial n)
  (if (<= n 1) 1 (* n (factorial (- n 1)))))

(define (agent-run context kwargs)
  (make-dict "answer" (factorial (get kwargs "n"))))

Lexical closures, general recursion, conditionals and lists express universal computation in the abstract language. Each actual execution has finite fuel, stack, allocation, output and time budgets.

Secure sharing is a runtime property.

Program identity, publisher authentication, device grants, capability scopes, adapter integrity and real provider completion are separate checks. Signed programs still cannot approve their own access. Raw SKILL.md text is review-required data, never authority.

This is not an Apple certification, an App Store approval, or a promise of perfect security. Physical iOS deployment and native entitlement enforcement have not been validated by the current desktop conformance work.

Brainstem Zaps tooling and the Zap-specific profile are governed by the maker. Existing LisPy, Lisp and licensed RAPP primitives retain their provenance and licenses. The public repository distributes documentation and harmless examples, not private runtime bindings or credentials.