Build

The Build section is for developers who extend FlowLakes in code: packaging a whole application as a blueprint, and writing the script bodies that run inside rules and workflows. Everything you configure in the admin UI has a programmatic shape underneath, and these pages show you how to author it directly.

In this section

• Blueprint authoring: package tables, rules, workflows, approvals, dashboards, and seed data as one installable JSON file, then validate and install it.
• The scripting sandbox: the single sandboxed environment and helper set shared by business-rule script bodies, workflow script steps, and the SDK. What you can call, what is blocked, and the return contract.
• Connect via MCP: point an AI client at your instance so it can work through the same governed surface, within a user’s permissions.

Before you start

Installing a blueprint or editing automation is an admin-level action. You need the capability that gates the surface you are writing for: platform.tables.write to create tables, platform.rules.write for business rules, platform.workflows.write for workflows, and so on. Each guide names the exact capability it needs.

Generated reference

These pages are generated directly from the platform code, so they never drift from what the product actually does:

• Typed schemas: the fields, types, and defaults for the agent and skill shapes.
• Capabilities: every platform.* permission and the tables each area governs.
• Operators: the condition and filter vocabulary.

For terms, see the Glossary. Each concept page’s “Exact shapes” block also links to the reference for its primitive.