Trust

We issue evidence. We do not issue approval.

A passport is not a conformity assessment. A visa is not a regulatory authorisation. AL360° Oceans produces the record a human reviewer decides on — and can be held to afterwards. Where our authority stops is stated here, in full, because a reviewer relying on a boundary they misread is worse off than one with no evidence at all.

Findings travelRaw data never doesSigned and immutableEverything expires

Evidence Boundary Map

Stays inside

Special category data (GDPR Art. 9)
Model weights & fine-tune deltas
Prompts, completions, tool arguments
Retrieval corpus & case files
Embeddings — invertible, so treated as data

receipts only

Leaves as an Evidence Record

Metric value vs declared threshold
Pass / fail at the declared operating point
SHA-256 of the inputs — not the inputs
Model endpoint hash — catches a silent swap
Ed25519 signature · UTC timestamp · versions
raw_export: off (default) · Ed25519: required · verifiable_offline: true

What we are

An evidence engine — signed, offline-verifiable
Border control for AI reaching sensitive data
A third-party AI risk register (DORA)
Human review under seal, on the record

What we're not

A law firm
A notified body
A certifier under Art. 43
A regulator or market surveillance authority

Standard disclaimer — all exports

"Technical and operational evidence only. Not legal advice, certification, or regulatory approval."

Scope of authority

What AL360° Oceans is — and is not.

What it is

  • A border-control layer for AI: scan, passport, visa
  • An evidence scan that opens the file on an AI system (Currents)
  • An evidence passport that records what is proven about it (Ripples)
  • A context visa that clears it for ONE deployment, revocably (Droplets)
  • A diagnostic engine that seals results as signed, immutable Evidence Records
  • A federated execution layer — diagnostics run where the data lives
  • A register (Atlas) that holds every system, clearance, and open gap
  • A review workspace where a named human takes a decision they can defend

What it is not

  • Not a notified body, and not a conformity assessment body
  • Not a certification scheme under the EU AI Act or any other regulation
  • Not a CE marking, and not a presumption of conformity
  • Not a legal adviser or a legal interpretation engine
  • Not a substitute for the DPO, the CISO, or the notified reviewer
  • Not a generic governance dashboard or LLM observability tool
  • Not a guarantee that a system is safe, fair, or lawful
  • Not permanent — every passport and every visa expires

Evidence boundaries

What crosses the boundary, and what never does.

What crosses the boundary

Findings. A signed Evidence Record carries the diagnostic name, the runner and version, the parameters, the score, the pass/fail result, a hash of the inputs, and a signature. It carries no personal data, no clinical record, no prompt, no document, and no model weight.

What never crosses it

Raw special-category data under GDPR Art. 9, children's data under Art. 8, financial records, prompts, completions, retrieval corpora, training sets, and model weights. Raw export is disabled by default, cannot be enabled from the browser, and is refused by the container itself.

Why the diagnostics run where the data lives

Because for the three contexts we lead with — health AI, financial AI, minor-facing AI — the data cannot lawfully or practically be centralised, not even for a compliance check. So it is not. The diagnostic travels to the data; only the sealed result travels back.

What an Evidence Record proves, and what it does not

It proves that a named diagnostic, at a named version, produced a named result against a named model version, and that the record has not been altered since. It does not prove that the diagnostic was the right one to run, or that the result is sufficient. A human decides that — under seal, on the record.

Why every clearance expires

Because the evidence does. Distribution shift erodes accuracy claims from the day they are made. A silent vendor model swap invalidates every fairness figure attached to the endpoint. A passport that never expires is a claim that the world stopped moving.

The disclaimer that travels on every export

AffectLog provides technical and operational evidence to support AI access, supplier-risk, security, privacy, and governance review. AffectLog does not provide legal advice, certification, notified-body conformity assessment, or regulatory approval. That sentence is on every Wake, and it is not a formality.

Carried on every Wake, every export, every passport

“AffectLog provides technical and operational evidence to support AI access, supplier-risk, security, privacy, and governance review. AffectLog does not provide legal advice, certification, notified-body conformity assessment, or regulatory approval.”

Test the boundary

Read the architecture, then hold us to it.

The security architecture states exactly what the container refuses to export and how an Evidence Record is verified offline. If a boundary in it is not the one you need, tell us before you rely on it.