Skip to content
Hylen

CAPABILITY · 02 · OPERATING PRINCIPLES

How we work. Who we work with. What we promise.

Twelve principles, in plain English, in the order we apply them. Read in any boardroom. Defended in any audit. The same doctrine for every engagement we take.

Begin inquiry

THE TWELVE

The doctrine, plate by plate.

Each principle is one sentence we'll defend, with one paragraph of how it shows up in the work. We sign them at the start of every engagement.

IPRINCIPLE · 01

We work inside your stack, not on top of it.

No SaaS overlay you'd be embarrassed to depend on. We integrate at the protocol layer — your systems remain the system of record.

IIPRINCIPLE · 02

Every output cites its source.

Recommendation, alert, summary, model decision — all carry the documents and rules they leaned on. Black boxes are not licensed to run.

IIIPRINCIPLE · 03

The licensed human keeps the seat of judgement.

AI proposes. The human signs. We do not ship systems where a model is the final decision on a regulated act.

IVPRINCIPLE · 04

Auditability is the product, not a feature.

Append-only log of every read, write, approval, override. Replayable by your regulator without involving us. Built before day one.

VPRINCIPLE · 05

Two-person rule, by default.

Every consequential action — payment, schema change, access grant — requires two distinct authorised humans. Enforced at the platform layer.

VIPRINCIPLE · 06

Reversibility before convenience.

If we can't show you how to roll an action back, we don't ship the action. Convenience comes after reversibility, never before.

VIIPRINCIPLE · 07

Your data leaves nothing behind with us.

Single-tenant, your-keys-only. We do not aggregate, anonymise-and-pool, or 'general-improve' on your data. Inference stays in your tenant.

VIIIPRINCIPLE · 08

Plain English. In contracts. In dashboards. In code.

If a sentence needs a glossary, we rewrite the sentence. If a UI needs training, we redesign the UI. Plainness is a load-bearing principle.

IXPRINCIPLE · 09

Externally validated before production.

Models, integrations, and security postures pass independent review before they touch a real customer. Internal sign-off is not enough.

XPRINCIPLE · 10

Architecture is doctrine.

We draw the boundaries on day one. Modules have one purpose. Interfaces are written down. The system stays understandable as it grows.

XIPRINCIPLE · 11

The codebase is yours from day one.

Your repository, your CI, your secrets. We work in your environment, push to your main, hand over fully, and leave.

XIIPRINCIPLE · 12

We say no when no is the right answer.

We turn down engagements we can't run to this bar. We do not chase logos. The list of engagements we've declined is longer than the list we've taken.

THREE PILLARS

What the doctrine means in the work.

An open notebook on a walnut desk filled with hand-drawn architecture diagrams — boxes, arrows, the words 'abstract systems' visible — beside a brass cup of sharpened pencils.

01 · ARCHITECTURE

Architecture is doctrine, not afterthought.

We draw boundaries on day one. Every module has one job. Every interface is written down. The architecture is the artefact we'll defend in the audit — not the demo.

Talk to us
A handmade plate of cream paper marked with a single Roman numeral IV in navy ink, calligraphed below with a signature line, beside a fountain pen and a small brass paperweight.

02 · AUDITABILITY

Plate IV — the audit is the product.

Every read, every write, every approval, every override — sealed and signed at the moment it happens. Replayable by your compliance team without involving us. Built before day one.

Talk to us
A sheet of aged cream paper marked with a single Roman numeral XI in navy ink, surrounded by other handwritten manuscript pages, a glass ink bottle and a feather quill resting on the desk.

03 · SOVEREIGNTY

Plate XI — your codebase is yours from day one.

Your repository, your CI, your secrets. We work inside your environment, push to your main branch, and leave when the work is done — full handover, no lock-in, no aftermarket.

Talk to us

THE THROUGH-LINE

“We are not hired to be clever. We are hired to leave behind a system the next operator can defend without us in the room.”

Founding line · Hylen Technologies

A hand resting on a brown leather portfolio on a walnut desk by a window — a cream envelope sealed with electric-blue wax laid beside it, a brass cylinder paperweight pinning a corner of paper, soft natural light.

SIGNED — DAY ONE

We sign the principles before we sign the work order.

Every engagement begins with these twelve, countersigned by our engagement lead and your accountable executive. They are contractually binding — invoke any of them at any time.

SIGNED — Founded

the founding team · Hylen Technologies

Founded · 2024 · revised quarterly

Hylen

STATUS · OPEN

Read the principles. Then test them.

The fastest way to know if Hylen's doctrine fits your operation is one conversation. First conversation is on us. We respond within four business hours.