Juha Huotari systems · evidence · recovery

Solution analyst · operator · builder

I make complicated systems legible enough to change.

My work starts where requirements stop being sentences and become data, state, interfaces, controls, and recovery paths. Professionally that means financial and insurance platforms. At home it becomes infrastructure, small tools, and experiments in accountable agent work.

Enter the system map Read Kotona ↗
Field index / 04 domains 60.9° N · FIN
01 / DATA

Turning policy, source systems, and consumer needs into models people can inspect and operate.

850kregulated documents / year
5,500+source attributes mapped
130+mapping releases
72executable SQL controls

Selected systems / public edges

Projects are arguments
with failure modes.

These are not a product portfolio pretending everything is finished. Each project states what it owns, what it refuses to own, and the next proof that would make its claims less provisional.

View
SYS / 01 active use

Governed agent work

Vuoro

A family of small tools for sprint state, claims, queues, dispatch, knowledge, audit, and operator views. The composition is allowed to be useful; it is not allowed to become a new source of truth.

Owns
Explicit work state and hand-offs between actors
Refuses
A cockpit-shaped monolith with privileged writes
Open edge

Cross-repository version drift and recovery still need more operating mileage than the clean boundaries do.

Inspect the project
SYS / 02 operating

Declarative infrastructure

Appservice

A private GitOps repository for a Talos-based Kubernetes cluster. Desired state sits beside upgrade rules, recovery gates, restore evidence, and the incidents that made those controls necessary.

Owns
Desired state, recovery rules, and operational evidence
Refuses
Durable repairs that exist only in operator memory
Open edge

A stored backup is still only a hypothesis until restore evidence is renewed against the actual failure domain.

Inspect the project
SYS / 03 active platform

Semantics at household scale

Household operating platform

Reporting, scenarios, policy, approvals, and agent-facing retrieval built around one explicit semantic model. Device state remains at the edge; longer-lived household meaning does not live in a switch entity.

Owns
Meaning, scenarios, policy, provenance, and proposals
Refuses
Autonomous action disguised as a convenient assistant
Open edge

A second serious integration still has to prove that the adapter boundary was extracted rather than renamed.

Inspect the project
SYS / 04 public corpus

Notes as durable context

Kotona

A public technical notebook where project evidence, decisions, failures, and recurring patterns become stable artifacts. Pages are useful projections; the corpus remains the source.

Owns
Published memory, editorial posture, and dated claims
Refuses
Confusing public access with authority or finished truth
Open edge

The site serves people, future self, and agents. Optimizing for one reader can quietly bleach the others out.

Enter the notebook

The working contract

A system is not clear
until failure has a route.

I prefer mechanisms that preserve judgment under change: one owner for each state, evidence that survives the session, and a recovery path defined before the interesting failure arrives.

  1. 01

    Find the authority

    Decide which system may establish a fact before designing the surface that displays it.

    prevents shadow truth
  2. 02

    Turn prose into a boundary

    Move important conventions into schemas, interfaces, permissions, tests, or gates that are harder to bypass accidentally.

    prevents ceremonial policy
  3. 03

    Keep the receipt

    Record what was requested, attempted, accepted, rejected, and superseded—without mistaking a transcript for proof.

    prevents confident amnesia
  4. 04

    Design the way back

    Backups, migrations, retries, and hand-offs count only when the return path can be exercised and explained.

    prevents decorative recovery
  5. 05

    Let reality edit the architecture

    Dogfood early, keep the failed directions, and remove machinery that cannot justify its operational cost.

    prevents elegant fiction

Professional record / generalized

The work behind
the working style.

Years inside financial and insurance data platforms made ambiguity expensive in useful ways. The examples below preserve the scale and the responsibility while leaving employer and customer detail where it belongs.

15 → 10sources to governed views

Requirements ownership

One reporting pipeline, traced end to end

Owned the requirements across trading, custody, customer, product, agreement, and fee data; translated them into 185 explicit mappings.

regulated reporting
5,500+unique source attributes

Cloud migration

Legacy meaning carried into new products

Shaped more than 130 mapping releases and six cloud data products without pretending a field copied is a meaning preserved.

data product design
72executable controls

Assurance

Checks that could fail in public

Converted mapping and delivery expectations into SQL controls that made defects reproducible instead of merely discussable.

quality as contract
10+analysts in practice

Leadership

A craft made easier to share

Co-led a solution-analysis chapter across templates, demonstrations, AI enablement, documentation practice, and outside perspectives.

practice leadership

What I am useful for

Turning an enterprise problem into a system shape, then staying close enough to notice where the shape lies.

requirements decompositiondata architectureplatform boundariestechnical facilitationoperational proofagent governance

Current questions / September 2026

Questions worth
keeping open.

The projects move. These questions are the more stable thread underneath them—and a useful warning against turning the latest implementation into a worldview.

Q / 01

What may an agent settle?

Not just what it can execute, but which facts and outcomes it may establish without consulting the slower human loop.

Q / 02

When does a team of one need governance?

When multiple actors—or one operator across time—share neither memory nor judgment, organizational controls stop being about headcount.

Q / 03

Which context deserves to survive?

A log is abundant. Durable knowledge is selected, dated, attributable, and allowed to be superseded.

Outside the control plane

The curiosity leaks.

I live in Finland and spend the remaining cycles on ancient history, cooking, travel, fabrication, 3D printing, and game ideas that usually acquire an economy before they acquire a title.

Read “The workshop is learning my accent”