Logic Foundry best practices

An AI assistant connected to Logic Foundry builds real artifacts in your environment. Treat it like a fast, capable new team member: give it a safe place to work, clear instructions, and review its work before it goes anywhere near production.

Environments

• Build in development. Connect your AI client to a development environment whose projects belong to unmanaged solutions. That is where the assistant can create and change artifacts.
• Rely on managed solutions downstream. Deploy to test and production as managed solutions. Logic Foundry refuses changes to artifacts in managed solutions, so even an assistant connected to the wrong environment can’t edit production logic.
• One entry per environment. Give each Logic Foundry entry in your AI client a name that includes the environment, and enable only the one you need.
• Deploy with the CLI. Move finished work between environments with the Logic Fabric CLI, not by asking the assistant to rebuild it.

Requests

• Start read-only. Ask the assistant to explain or find something before asking it to change something. It confirms you are both talking about the same artifacts.
• Ask for a plan on bigger work. For a suite of blocks and flows, ask for the plan first, approve it, then let the assistant build.
• Check impact before changes. Ask for the dependencies of a block, flow or recipe before you change it, and decide whether the callers need to change too.
• Be specific about data. Name tables and columns as your users see them. The assistant looks up the real names, but it needs to know which ones you mean.

Reviews

• Review every new or changed artifact in the designer before you publish it, the same way you would review a colleague’s work.
• Keep tool confirmations on in your AI client for tools that change data, especially run_logic_flow, which really runs the flow and can change records.
• Test what was built. Run blocks with sample inputs, or use Logic Assurance to generate and run test suites. Use Logic Guard to check it against your governance rules.
• Publish at the end of a session. If the assistant made several changes, ask it to publish Dataverse customizations once at the end.

Access

• Prefer per-user sign-in for any shared Logic Foundry installation, so every call runs with the requesting person’s permissions and is attributed to them.
• Grant access to builders. Logic Foundry is a design-time tool for designers and consultants. Business users who should only run approved logic belong on Logic Conductor.

Related

• Set up Logic Foundry
• Working with AI
• Composer best practices