Evidence notes


Technical notes with a review date.

No daily AI commentary. Each note must identify its author, sources, evidence class, reviewed date, next review and the boundary beyond which a new test is required.

Planning

How much accelerator memory does a local model need?

Weights are only the beginning: KV cache, context, batching, engine overhead and headroom decide fit.

Read the evidence note →
Method

What belongs in a benchmark contract?

Freeze workload, runtime, concurrency, quality, refusal, leakage, power and negative-result handling before the run.

Open the benchmark method →
Custody

Swiss-hosted is not the same as client-controlled.

Residency, tenancy, administrators, support paths, keys and exit are separate decisions.

Read the evidence note →
Recovery

Backup is not tested recovery.

A backup becomes evidence only after a bounded restore, index rebuild and ownership record.

Inspect recovery and exit →
Models

What does Kimi K3 availability change?

Weights unblock sovereign evaluation, while workload, licence, hardware, safety and operations remain to be proved.

Read the evidence note →
Thermal

When is AI heat recovery useful?

Only load profile, usable temperature, seasonal demand, hydraulics and failure design can answer.

Read the evidence note →

These are structured entry points to current reviewed material. Future standalone notes should be published only when they add original evidence or a durable decision aid.

Prefer one reproducible object to ten opinions.

The next authority milestone is one real benchmark packet with raw data and negative findings.

Open the Evidence Room