Governed Excel Execution

The BlazeXL Excel Add-in makes Excel a first-class surface for governed business logic.

It is designed for financial analysts, operations teams, and subject-matter experts who already work in spreadsheets but need stronger control over how logic is executed, shared, and trusted.

With BlazeXL, Excel remains the interface. BlazeXL becomes the execution and governance layer underneath.

What Changes with BlazeXL

Instead of relying on fragile local formulas, ad hoc scripts, or hidden workbook logic, teams can:

• Execute logic on the BlazeXL Execution Grid without local Python dependencies
• Turn reusable logic into versioned Blaze Blocks
• Share governed workbooks as Blaze Sheets
• Enforce strict mode, consent checks, and approved dependency resolution
• Produce execution trails through the Governance Gateway

This is the spreadsheet wedge for BlazeXL: keep Excel where users already work, but move critical logic into a deterministic, auditable runtime.

Exploratory Mode vs Governed Mode

The add-in supports two distinct workflows:

1. Exploratory Mode

Use =BLAZEXL.PY() to draft, test, and explore logic quickly inside Excel.

This is useful for:

• prototyping calculations
• exploring data transformations
• testing Python logic before formalizing it

2. Governed Mode

Publish reviewed logic as Blaze Blocks, declare those dependencies in the workbook, and execute only approved logic through the add-in.

=BLAZEXL.PY() is still the function used in-sheet. In governed mode, the difference is that execution is restricted to approved Block functions rather than arbitrary new function definitions.

This is the production workflow for:

• pricing models
• approval rules
• risk and policy checks
• forecasting and reconciliation logic

In governed mode, Excel is the input and output surface, not the system of record for business logic.

Installation Steps (Beta)

During the current Beta phase, you must "sideload" the add-in. This gives you direct access to the latest Execution Grid features.

1. Download Your Manifest

Download BlazeXL Excel Add-in manifest from here. This file contains your unique security handshake.

2. Sideloading on Windows

1. Create a folder on your local drive (e.g., C:\BlazeXL).
2. Move the manifest.xml into this folder.
3. Right-click the folder > Properties > Sharing > Share.
4. Copy the Network Path.
5. In Excel, go to File > Options > Trust Center > Trust Center Settings > Trusted Add-in Catalogs.
6. Paste the Network Path and click Add Catalog.
7. Restart Excel and find BlazeXL under Insert > My Add-ins > Shared Folder.

3. Sideloading on Mac

1. Open Finder and press Cmd + Shift + G.
2. Paste: ~/Library/Containers/com.microsoft.Excel/Data/Documents/wef/
3. Move your manifest.xml into this folder (create wef if it doesn't exist).
4. Restart Excel. Go to Insert > My Add-ins and look under Developer Add-ins.

---

The "Blaze Sheet" Difference

Once installed, your Excel experience changes:

• Zero Local Dependencies: You don't need Python installed locally. The Execution Grid handles everything.
• Governed Logic: Logic can be published as versioned Blaze Blocks and reused across workbooks and teams.
• Deterministic Execution: The same governed logic runs consistently across Excel, apps, APIs, and agents.
• Auditable Results: The Governance Gateway records execution events for review, lineage, and compliance.

Why This Matters

Many enterprise decisions still depend on spreadsheet logic, but spreadsheets alone are a weak control boundary.

BlazeXL makes it possible to:

• keep Excel in the workflow
• centralize critical logic outside the workbook
• share workbooks without logic drift
• make AI-assisted spreadsheet logic safer to operationalize

That is the real difference between a spreadsheet with scripts and a spreadsheet connected to BlazeXL.

---

Troubleshooting

• Connection Error: Ensure your Access Token is active in the Access tokens page.
• Function Not Found: Verify you are pinned to the correct version of the Blaze Block in your module settings.

For the full lifecycle from spreadsheet logic to API and agent execution, see Cross-Surface Workflow.