One governed boundary. Several deployment shapes.

Start with PF Kernel at the point of action, wrap an existing workflow or memory service, or deploy the complete PF OS triad. The workflow determines the shape—not a forced platform replacement.

01Modular

Use one component, selected components or PF OS.

02Lightweight

Designed for local, edge and constrained deployment choices.

03Commercially flexible

Keep the models, systems and workflows already in place.

04UK sovereign

British-developed governance software with deployment choice.

Four tangible deployment shapes

See how PF Systems fits around what the customer already has.

Switch between examples, then follow one governed action through context, proposal, authority, effective action and linked evidence.

Illustrative deployment shape

A compact authority boundary where the action happens.

PF Kernel can sit close to a local agent, robot, drone or application without requiring the complete platform.

Local AI or autonomyProposes an action

PF KernelAllow · Deny · Modify · Step Up · Stop

Local systemReceives only the effective action

PF CoreAdd when linked evidence and governed replay are required.

Step-up authorityAdd an authorised approval provider when further authority is required.

Commercial resultSmall footprint, local authority and no requirement to replace the autonomy stack.

One governed action

See the information move.

The main path separates knowledge, proposal, authority and action. PF Core preserves the linked evidence beneath it; PF Trace can display that received evidence to an authorised operator.

01Context

PF Memory supplies relevant governed knowledge.

02Proposal

The AI proposes a consequential action.

03Authority

PF Kernel returns the governed outcome.

04Effective action

Only the permitted or modified action proceeds.

PF Core · linked evidenceRequestContext referencesAuthorityDecisionEffective action

Illustrative public architecture only. Exact interfaces, policies, evidence and deployment choices are customer- and workflow-specific.

Planning boundary

These diagrams explain modular roles and information flow. They are not production architectures, capacity guarantees, certifications or minimum resource requirements. Technical sizing and deployment assurance remain separate gates.

Review measured PF Kernel evidence and planning guidance

Choose the smallest sensible shape

Start with the action, then size the deployment.

A controlled briefing helps identify the authority boundary, integrations and evidence needed for one workflow.

Request a governed AI briefing