Powered by HEX 165

AI help on your documents, under your rules.

TOPAS for Word is an add-in for Microsoft Word. Your people draft, review and analyse documents in the Word they already use, and every request for AI help goes through HEX 165 first.

HEX 165 decides what information the AI may receive, which approved models may process it and when a person must approve the result. Each decision is recorded for audit.

How it works

Work in Word. HEX 165 governs the AI.

01

Work in Word

Draft, review or analyse a document in your usual workflow, using the TOPAS panel inside Word.

02

HEX 165 governs

HEX 165 decides what the AI may receive and which approved models may process it, before any model is called.

03

Evidence is retained

The controls applied and the decisions made are recorded, so you can show how AI was used on each document.

One document, two controlled views

The officer sees the document. The AI sees what policy allows.

An illustrative task: reviewing a case summary with personal identifiers removed before AI processing.

Human view Authorised officer
Case ref
24/0817
Witness
John Doe
Contact
07700 900123
Bank account
12-34-56 / 12345678
AI view What policy permits
Case ref
TOKENISED
Witness
REDACTED
Contact
REDACTED
Bank account
MASKED

Fictional details. The officer keeps authorised access to the original text, and the AI receives only what policy permits.

A document task, step by step

From request to approved result

What a user does in Word, and what HEX 165 does at each step.

  1. 1

    Open the document

    Work on the original text as usual. TOPAS marks sensitive details such as names and contact numbers so they are redacted before anything goes to AI.

  2. 2

    Ask for help

    Choose a task such as a review, a summary or a draft. The request goes to HEX 165 with your Microsoft sign-in, never straight to a model.

  3. 3

    Your rules apply first

    HEX 165 applies your policy, checks the budget and screens the document for hidden instructions before anything is sent.

  4. 4

    Approved models only

    The request goes only to an approved model in an approved region. If the destination does not match policy, nothing is sent.

  5. 5

    A person decides

    Results come back as a preview with citations. Nothing goes into the document until someone has checked it, and changes that need approval need a second named person.

  6. 6

    Every step recorded

    Decisions, approvals, model calls and costs go into a hash-chained audit log. Seeing redacted text needs a request and an approval, and the access expires.

What HEX 165 controls

Governance on every AI request

01

Sensitive data

Finds and protects sensitive information before any AI processing.

02

Models and sovereignty

Limits processing to approved models in approved regions.

03

Policy

Sets what the AI may receive and do, using your roles and approval rules.

04

Audit

Keeps a traceable record of policy decisions and AI activity.

05

Tokens and cost

Cuts unnecessary tokens and measures what each AI task costs.

Where it runs

You host, or we host

Each organisation gets its own HEX 165 environment, built from the same signed release. Your people, documents and identity stay in your Microsoft 365.

You host

In your own cloud

HEX 165 runs in your own cloud subscription in a UK region. Your team runs it, with support from Grace Blackwell.

We host

Run by Grace Blackwell

A dedicated environment for your organisation in a UK data centre, under UK law, operated by Grace Blackwell staff.

The 14-day trial runs in Grace Blackwell's evaluation environment with synthetic or public content only. Nothing is installed on your devices: your IT team approves browser access to Word and the add-in. Sovereign Edge hosting for the most sensitive workloads is in progress.

Under the hood

The TOPAS engine

TOPAS for Word runs on the TOPAS engine, Engine 04 of HEX 165. The Governance Engine decides and TOPAS executes: it applies each decision to the request, routes it to an approved model, controls tokens and cost, and records the evidence.

01

Cost and routing

Select the lowest-cost compliant model path after policy, residency, SLA and accuracy checks.

02

Context and payload efficiency

Optimise repeated and structured context through cache alignment and Group of Tokens (GOT).

03

Accuracy and restore

Validate compressed outputs against full-context reference results, with original source material retained in the Restore Vault.

04

Task-level ROI

Compare AI execution cost with equivalent human effort, using approved role, skill and rate benchmarks.

05

Audit evidence

Record every material route, cost, compression, restore, approval and value decision to the hash-chained audit log.

TOPAS for Developers

A sidecar for applications, agents and delivery pipelines, bringing TOPAS policy, routing, budgets, GOT optimisation and audit telemetry into AI-enabled software through the HEX 165 API.

Part of HEX 165

Four engines, one control plane

The Compliance Engine assures and the STPM Engine (in progress) protects. Both inform the Governance Engine, which decides. TOPAS executes each decision on every AI request.

Try TOPAS for Word for 14 days

Registration is subject to availability and usage limits.