FDE
FDE-Toolkit
Discuss a pilot

Checking execution plane

Verifying the signed control-plane-to-execution-plane channel.

The demo button should be used only when this status is connected.

Executive product demo

Watch a client ask becomea governed engineering decision.

Pick a real delivery situation. FDE-Toolkit turns the request into a working product proof, observed execution evidence, named approvals, and a reviewable PR package—without dictating the client’s coding agent or runtime.

What a decision maker gets

A decision brief

What changed, why it matters, and what must be approved.

Proof, not agent claims

Observed file hashes, commands, exit codes, and tests.

A measurable pilot

Ask-to-approved-PR, reuse, approvals, and adoption targets.

Northstar Bank · synthetic demoCOO · Chief Risk Officer · Head of AI

The boardroom question

Can we shorten exception handling without allowing an AI agent to make or obscure a regulated decision?

Risk today

Slow reviews, fragmented evidence, inconsistent escalation, and audit reconstruction work.

Decision-ready output

A working reviewer experience, observed test evidence, explicit approval gates, and a reviewable PR package.

Ask → approved PR

Current

15 business days

Pilot target

<48 hours

North-star pilot target, not an achieved claim.

Decision evidence

Current

Email + folders

Pilot target

100% linked

Ask, files, tests, commands, and approvals share one run ID.

Approval handoffs

Current

Ad hoc

Pilot target

3 named gates

Workflow, risk, and engineering retain decision authority.

Live governed delivery

Run the client ask through the control plane.

Client-approved coding agent

Bank VPC execution plane

GitHub Enterprise

Demo execution details

Repository reference: https://github.com/northstar-bank/operations-workbench

Public demo agent: deterministic FDE driver

Execution: isolated execution-plane service with no repository credentials

Promotion: package only; no branch is pushed

What FDE-Toolkit is doing

The buyer sees the delivery and governance journey—not a spinner.

Capture the client ask
Apply policy and tenancy
Route to the approved execution plane
Generate and test the candidate change
Observe provenance at the driver boundary
Prepare approvals and the PR decision brief
Under the hood: interchangeable providers

The executive flow stays the same while the client changes its approved coding agent, sandbox, and promotion system.

Coding agents

FDE deterministic demo agentDemo
OpenAI CodexDriver
Claude AgentDriver
CursorDriver
Customer coding agentDriver

Execution environments

Local ephemeral workspaceDemo
Docker EngineDriver
Kubernetes jobs or podsDriver
Managed sandbox providerDriver
Customer sandbox serviceDriver

Promotion systems

Reviewable PR promotion packageDemo
GitHubDriver
GitLabDriver
Azure DevOps ReposDriver
Customer SCM gatewayDriver

Pilot design

Use one real client ask and prove the full decision loop.

Select the client-approved agent, execution boundary, and SCM. Measure time to approved PR, evidence capture, reuse, active FDE adoption, and expansion potential.

Design a 30-day pilot

Product constitution

A neutral control plane around client-approved execution.

These principles determine the product boundary, procurement story, security model, and adapter architecture.

Own the workflow. Rent the horsepower.

FDE-Toolkit builds the control plane: workflow, policy, provenance, knowledge, and tenancy. Coding agents, models, sandboxes, speech services, SCMs, secret stores, and client systems remain replaceable drivers.

Neutrality is the product.

Bring the coding platform and runtime the client has already approved. The same governed delivery contract can route to OpenAI, Anthropic, Cursor, self-hosted models, SI accelerators, or customer-built agents.

Trust nothing the agent says.

The execution plane records file-system changes, exact commands, exit codes, output digests, and test outcomes. Provenance is written by toolkit instrumentation at the driver boundary, not self-reported by the coding agent.

The execution plane is deployable.

Anything touching client code or data can run in the toolkit cloud, a client VPC, or an air-gapped environment. The control plane sends signed metadata and receives normalized evidence—not source code or long-lived credentials.

Control plane

Workflow · policy · tenancy · knowledge

Stores intent, approvals, routing rules, and normalized evidence.

Execution plane

Agent drivers · sandbox drivers · instrumentation

Touches code, runs commands, and produces observed provenance.

Client systems

SCM · CI/CD · secrets · approved platforms

Remain customer-controlled and replaceable.