Forem: Riku Lauttia

A Social Contract for AI

Riku Lauttia — Sat, 25 Oct 2025 18:35:33 +0000

Responsibility, Competence and Infrastructure — In Practice.

TL;DR

AI can propose, but only people can decide and own consequences.
Explanations must fit each audience — citizens get reasons they understand; experts get verifiable logs.
Security moves “left”: design it into data, models, supply chains, and operations.
Capacity must be layered and portable (exit rights tested, not only promised).
Curated data and guardrails against “model collapse” are non-negotiable.
Ethically, pursue a dual strategy: partner where power lives, but fund open alternatives to keep freedom to move.

AI now threads through the economy, government, and everyday life — and shifts power as it goes: who steers development, whose voice counts, and whose risks are tolerated. This essay offers a practical framework any organization can adopt to make defensible, auditable AI decisions today. The core claim is simple: a democratic path requires that we operationalize six ideas — human responsibility, audience-specific explanation, security-by-design, layered and portable capacity, curated data, and an ethics dual strategy — across contracts, architectures, and daily routines. If we don’t, decision power quietly migrates to whoever controls the fastest lane: compute, data, and contracting leverage.

Machines can support work and decisions; responsibility must remain human. Below I show how to turn principles into checkable routines — procurement clauses, architectural patterns, and training programs — so the “social contract for AI” isn’t just a strategy slide, but something you can verify.

Why Only Humans Decide

Large language models feel fluent, but they do not share human commitments. A model can predict words; only a person can promise, be accountable, and correct a decision. That boundary is crucial in public power, healthcare, and due process.

Design rule: in every critical application, separate suggestion from decision. Name the human approver. Make the chain auditable. Without this, fluency gets mistaken for understanding, and responsibility blurs.

Practice checklist:

Name the decision owner in the UI and in logs.
Require a justification field (what evidence, which data versions, which tests passed).
Show citizens the decision and appeal path in the same view.

Competence, Reframed: From “Code Writer” to “Verifier”

Generative tools shift software work: less manual writing, more problem framing, testing, verification, and safe use. Quality does not emerge by accident.

What changes in teams:

Prompts are artifacts. Keep them in version control.
CI for generations. Treat output like code: unit tests, policy tests, red-team suites.
Named approver. A human must gate releases and risky actions.

Operational metric ideas:

Escapes per release (errors past tests into production).
Percentage of critical actions with human approval logged.
Mean time to correction after citizen/agent appeal.

Minimal “Gen-AI Gate” in CI (concept):
checks:

unit-tests
policy-tests (jailbreaks, PII, safety rails)
eval-bench (task-specific accuracy/latency)
human-approval (required for risk >= medium; role: Service Owner)
artifacts:
prompts/ (versioned prompts)
evals/ (reproducible eval sets)
provenance/manifest.json (model + data snapshot)

Explainability That Matters (to Each Audience)

One diagram rarely justifies a decision. In public use, we need reasons a citizen understands, plus deep logs for auditors. Explanation isn’t a bolt-on; it’s part of the system.

Two-tier model:

Citizen layer: plain-language rationale, key factors, uncertainty, and an appeal button.
Expert layer: versioned data/model snapshot, feature contributions, policy rules invoked, and evaluation traces.

Make it measurable:

Maintain a justification budget alongside latency budgets.
Track comprehension with user tests (do non-experts correctly paraphrase the reason?).
Version explanation artifacts so they update as data/models change.

Security as the Default

Attackers’ reconnaissance is fast and automated; defenders must raise costs before the first exploit. AI also lowers the attacker’s skill threshold.

Architecture patterns:

Strict train/test/prod separation; zero standing privileges.
Minimal metadata retention; role-based access with time-boxed tokens.
Supply-chain provenance: models, libraries, datasets (SBOM, dataset lineage, signed attestations).
Continuous LLM red-teaming (prompt injection, data exfiltration, tool abuse).
Practiced incident drills: backup integrity, failover paths, and clear communications.

Quarterly security routine (example):

Purple-team exercise (prompt injection + data exfiltration).
Restore from backup and switch to warm-standby.
Rotate keys/tokens; verify blast radius limits.
Publish a short, de-identified internal postmortem.

Compute Is Political: Layered and Portable Capacity

Specialized accelerators concentrate performance in few places. That’s not just technical — it’s geopolitical and economic. If critical functions depend on a single vendor, you inherit their pricing and disruptions.

Capacity strategy:

Layering: national/regional cloud where needed, with local edge for continuity.
Exit rights you test: data and model export in usable formats; like-for-like performance tests on alternates.
Procurement points: open interfaces, portability scoring, energy use in total cost of ownership.

Business-continuity goals:

RTO (recovery time objective) and RPO (data loss window) defined and tested twice a year.
Simulate provider lockout and prove you can run elsewhere.

Data Quality, Synthetic Data, and Model-Collapse Risk

If systems start learning from their own outputs, distributions drift and quality decays. Prevent recursive self-feeding unless a human-in-the-loop review clears it.

Data governance:

Dataset cards: origin, rights, bias notes, update history.
Synthetic data controls: document generators, share, and purpose; cap its proportion; validate with real-world probes.
Pre-deployment quality gates — don’t wait for incidents.

Data Registry (illustrative excerpt):

Dataset: claims_2024Q3
Sources: municipal systems A/B, OCR pipeline v2.1
Known risks: under-representation of non-native speakers
Synthetic share: 12% (generator v0.9, style constraints on)
Last audit: 2025–09–15 (pass)

Ethics Between Power and Freedom: The “Dirty Hands” Dual Strategy

We often face a choice: influence from inside partnerships (where decisions are made) or from outside by building alternatives. Both carry risks; the practical answer is to do both.

What it looks like:

Work with major providers and fund open models, test beds, and standards in parallel.
Independent ethics boards with real stop authority for large procurements.
Public conflict-of-interest and influence logs.
Annual impact reports and third-party audits.
Whistleblower channels that actually protect people.

The Social Contract, Operationalized: Six Principles → Six Routines

Responsibility stays human

Named approver; time-stamped decision log; RACI table.

Explanation by audience

Citizen rationale and appeal; expert trace logs; comprehension tests.

Security by design

Minimized metadata; supply-chain provenance; practiced drills.

Layered and portable capacity

Tested exits; portability score in procurement; energy in TCO.

Curated data, synthetic under control

Registry and quality gates; recursion guard; bias and drift monitors.

Ethics dual strategy

Partner plus open alternatives; independent board; public reports.

Public dashboard suggestion:
Publish quarterly: portability test results, data-quality grade, audit findings (de-identified), and time-to-correction for appeals.

Case Example: Municipal Social Services

A city uses LLMs to draft assessments and summaries.

Responsibility: each suggestion requires a named caseworker’s approval; UI records reasons and data versions.
Explanation: citizens see plain-language reasons and an appeal link; staff see model/data/version logs.
Security: separate train/test/prod; metadata minimized; honeytokens detect exfil attempts; regular drills switch to edge capacity during outages.
Data: documented sources; limited, labeled synthetic share; pre-launch quality gates.
Ethics and portability: publish de-identified quarterly metrics; in parallel, pilot an open model to keep exit options real.

Result: faster service without sacrificing due process or trust.

Making Hidden Power Visible

AI’s strongest effects hide in contracting, data curation, update cadence, and architecture choices. That’s where “quiet power” accumulates. Counter it with routines: decision logs, impact assessments, version histories, public changelogs, and test results. These create a learning loop, not just a compliance tick-box.

Portability is a drill, not a slogan. Practice data/model exports and failovers with real costs attached.
Curation is a routine, preventing silent decay and keeping models grounded.
Explanation by audience keeps citizens informed and auditors effective.
Security by design raises attacker costs and shrinks blast radius.
Independent oversight verifies the drills and keeps everyone honest. In Finland and across Europe, this is also about sovereignty: layered capacity (regional cloud plus edge) so we’re not captive to a single vendor or geography.

Conclusion: Machines Propose, Society Decides

Models predict words; people carry duties. A workable social contract for AI hard-wires that reality. When explanation, security, capacity, data, and ethics are embedded in routines, AI strengthens democracy: decisions are justifiable today and correctable tomorrow, without undue delay or cost.

Two movements, in parallel:

Institutionalize verifiability — traceable suggestions, reproducible evidence, accountable approvals.
Build sovereign capacity — tested exit rights, portable stacks, and real security.

These reinforce one another. Without institutions, sovereignty is a slogan. Without sovereignty, institutions are fragile. Measure progress through regular audits and public exercises; otherwise capability remains on paper. An ethics dual strategy keeps influence where power sits while preserving the freedom to leave.

Bottom line: machines can suggest; we set direction and terms. That’s how innovation becomes fixable — and fair.

Appendix: Ready-to-Use Artifacts

RACI for Critical Decisions (template)
Activity | Responsible | Accountable | Consulted | Informed

Model suggestion accepted/rejected | Caseworker | Service Owner | Legal, DPO | Citizen, Team
Data update to training set | Data Steward | CDO | Security, Domain Lead | Audit Board
Portability drill execution | SRE Lead | CTO/CIO | Vendor, Risk | Public report

Procurement Clauses (excerpt)

Portability & Exit: Vendor must support export of data, prompts, embeddings, and fine-tuned weights in documented formats; provide performance baselines for alternative environments; participate in semiannual failover drills.
Security & Provenance: Provide SBOM for models/libs, dataset lineage, and signed attestations; pass red-team tests twice yearly.
Explanation: Deliver citizen-facing rationales and expert trace logs via APIs; support appeal integration.
Data Governance: Maintain dataset cards; cap and document synthetic shares; prevent recursive training on system outputs without human review.

Policy Budgets (keep next to latency SLOs)

Justification budget: p95 ≤ 500 ms to render citizen rationale and appeal link.
Correction budget: ≤ 5 business days from appeal to adjudication.
Portability budget: ≤ 24 h to restore service in alternate environment (RTO), ≤ 1 h data loss (RPO).

References

P.J. Denning & B.S. Rousse, “Can Machines Be in Language?”, Communications of the ACM, 67(3):32–35, 2024.

S. Greengard, “AI Rewrites Coding,” Communications of the ACM, 66(4):12–14, 2023.

A. Malizia & F. Paternò, “Why Is the Current XAI Not Meeting the Expectations?”, Communications of the ACM, 66(12):20–23, 2023.

W. Mazurczyk & L. Caviglione, “Cyber Reconnaissance Techniques,” Communications of the ACM, 64(3):86–95, 2021.

N. Savage, “The Collapse of GPT,” Communications of the ACM, 68(6):11–13, 2025.

H. Skaug Sætra, M. Coeckelbergh & J. Danaher, “The AI Ethicist’s Dirty Hands Problem,” Communications of the ACM, 66(1):39–41, 2023.

N.C. Thompson & S. Spanuth, “The Decline of Computers as a General Purpose Technology,” Communications of the ACM, 64(3):64–72, 2021.

AI at the Edge: Why Hardware and Embedded AI Will Decide the Next Decade

Riku Lauttia — Fri, 26 Sep 2025 08:45:39 +0000

Over the last few years, artificial intelligence has shifted from experimental to indispensable. What once ran in massive cloud data centers is now moving closer to the devices we hold, wear, and deploy in the field. The next decade of AI will be defined not only by smarter algorithms, but by where and how those algorithms run. Hardware AI and embedded, on-device intelligence are set to become the decisive frontier.

1) Why the Edge Matters

Cloud-based AI fueled most of the breakthroughs of the 2010s and early 2020s. But as models scale, their cost, latency, and environmental footprint can become unsustainable.

Analysts have projected that AI data centers could consume on the order of ~1 trillion liters of water annually by 2028, a step-change from today.
Global demand for GPUs and accelerators has driven energy and supply-chain pressure.
This resource intensity collides with rising demand for real-time, privacy-sensitive AI. From drones to medical devices, users can’t always wait for a round trip to the cloud.

That’s why AI at the edge — running locally on chips inside devices — is becoming a necessity, not a luxury.

2) Breakthroughs in AI Hardware

2025 has already seen advances that signal where the industry is heading:

Compact on-device models. Lightweight multilingual embedding and reasoning models now fit within a few hundred MB of RAM, enabling search, semantic understanding, and ranking on phones, laptops, and IoT devices.
Optical/photonic AI chips. Research-grade parts that use light for certain operations report order-of-magnitude efficiency gains (often cited up to ~100×) on tasks like image recognition and pattern detection.
Specialized accelerators. From major vendors to startups, domain-specific chips for robotics, defense systems, and autonomous vehicles are reducing reliance on bulky data-center inference.

Together, these innovations point to an AI future where smaller, faster, greener hardware is as important as software algorithms.

3) Embedded AI in Action

Edge AI is not theoretical — it’s already reshaping industries:

Drones & robotics. Autonomous aerial, land, and underwater systems rely on embedded AI to make split-second decisions without constant connectivity. In defense, swarm coordination is being tested for missions that would be impossible with cloud-only control loops.
Healthcare devices. Wearables and imaging equipment embed models that can detect anomalies locally, protecting patient privacy while reducing time to diagnosis.
Automotive. Modern vehicles integrate on-device AI for lane detection, collision avoidance, and adaptive cruise control — all requiring real-time inference with near-zero latency.

If AI is to be truly ubiquitous, it must live inside the devices we use — not just the servers we rent.

4) Commercial & Strategic Implications

This shift will reshape technology, business, and geopolitics:

For companies. Adopting edge AI can reduce cloud costs, unlock new revenue streams, and build more resilient systems. Leading AI platforms report multi-billion-dollar ARR trajectories, underscoring how central AI infrastructure has become.
For defense & security. Nations that master efficient AI hardware and swarm-scale autonomy will hold decisive advantages. As with prior dual-use technologies, hardware capability and governance will be strategic levers.
For sustainability. With data-center demand straining energy and water systems, hardware efficiency is the only path to environmentally viable, scaled AI.

5) Looking Ahead

The last decade’s AI conversation was dominated by models: GPTs, diffusion, RL breakthroughs. The next decade will be dominated by deployment:

How do we make AI run everywhere?
How do we power it sustainably?
How do we secure it in critical applications like defense and healthcare?

The answer is clear: hardware AI and embedded intelligence will determine who leads — and who follows — in the global AI race.

Conclusion

AI at the edge is not a side story — it’s the main act of the 2025s. From efficient chips and on-device models to swarms of autonomous drones, the future of AI will be measured by how well we embed intelligence into the fabric of our machines.

For entrepreneurs, engineers, and policymakers, the message is the same: own the edge, and you own the future of AI.

#ArtificialIntelligence #EdgeComputing #MachineLearning #DeepLearning #AIHardware

From San Francisco to Europe: The 2025 Playbook for Building Agentic AI That Scales

Riku Lauttia — Fri, 26 Sep 2025 08:39:50 +0000

In December 2024 I spent two weeks in San Francisco talking to builders across labs, clouds, and startups. The same patterns I saw there have crystallized in 2025.

The 2025 inflection: agents + reasoning + open models

The conversation has moved beyond chat. The hottest race now is for reliable agents — systems that can plan, take multi-step actions, and operate software on our behalf. Even the biggest platforms are saying it out loud: Amazon’s AGI group is prioritizing agents over raw LLM size because doing things matters more than talking about them.

Reasoning-first foundation models have arrived too. OpenAI’s o3 family is optimized for long, careful thinking and is now broadly available via ChatGPT and API. On the open side, Meta’s Llama 4 and 3.1 (up to 405B) pushed the ceiling for openly available models, and Qwen has been iterating fast with Qwen2.5/Qwen3 and large MoE variants. There’s also a wave of open agentic research like Moonshot’s Kimi K2.

Under the hood, hardware capacity is exploding — NVIDIA Blackwell systems roll out through 2025, enabling cheaper inference and larger context, though demand remains intense. And on the edge, Apple Intelligence is mainstreaming on-device AI with a privacy-by-design architecture developers can tap into across iPhone, iPad, and Mac.

Why Europe can win this wave

Two structural advantages stand out:

Trust by design. The EU AI Act is now in force, with prohibitions/AI-literacy obligations already active (Feb 2025), GPAI duties applying from Aug 2, 2025, and full applicability by Aug 2, 2026 (with some transitions to 2027). Building to these standards is a global trust signal.
Industry depth. Europe owns complex verticals — telecom, energy, health, manufacturing — where reliable agents plus tight governance beat raw benchmarks every time.

My 7 rules for AI engineers in 2025 (the playbook I brought home)

Design for agent reliability, not demos.

Add eval gates that block deploys when plans/actions regress (schema checks, tool-use validation, safety rails). Benchmarks are nice; passing CI with real tasks is better.
Measure unit economics from day one.

Track cost per request (input/output tokens × model pricing), p50/p95/p99 latency, cache hit rate, and error budget. This is how you scale without surprises.
Compliance is a feature.

Treat EU-AI-Act alignment like performance work: data lineage, audit logs, PII handling, human-in-the-loop where risk is high. Teams that can show compliant by construction will close bigger deals faster.
Leverage open models strategically.

Llama and Qwen families give you sovereign options: fine-tune locally, serve on your infra, and mix with closed models when you need peak reasoning (e.g., o3 for edge cases).
Be hardware-aware.

Build for the 2025 stack: longer contexts, MoE routing, paged KV, quantization. If you can show a 30–50% latency or cost drop on Blackwell-class nodes (or smart batching on current GPUs), you’re speaking the language of production.
On-device is a first-class path.

Privacy-sensitive features belong on the device when possible; use secure fallback to cloud for heavier tasks. Apple’s model tiers and Private Cloud Compute make this an easy story to tell customers.
Ship thin slices into real workflows.

Pick a vertical (telecom, energy, health), automate one painful multi-step task end-to-end, and instrument the results. Repeat. Careers are built on shipped systems — not whitepapers.

A note from San Francisco

What struck me in San Francisco wasn’t just the pace — it was the clarity. Teams that win obsess over reliability, cost, and trust. In 2025, Europe can add something special to that equation: deployment in regulated, high-impact industries. That’s where agentic AI stops being a demo and starts changing how the world runs.

If this resonates, let’s connect — I’m building systems-first AI, open to collaborations.

— Riku Lauttia

#ArtificialIntelligence #MachineLearning

Europe Must Stay Hungry: Why the Next Decade of AI Will Be Decided Here

Riku Lauttia — Sat, 16 Aug 2025 23:20:03 +0000

Ambition, trust, and scale — the European formula for meaningful AI.

Artificial Intelligence is the defining technology of our era. The question is no longer if it will transform industries, but where the most meaningful breakthroughs and commercial successes will happen.

Many point to Silicon Valley or China as the natural leaders. I believe Europe has a unique chance — and responsibility — to define the next decade of AI. The challenge is simple: we must keep our ambition high and convert momentum into market leadership.

Europe’s Strategic Advantages

World-class research. Universities and labs across the continent consistently advance ML, systems, and applied AI.
Trust by design. With frameworks like the EU AI Act, Europe is positioned to set global standards for safe and responsible AI — a long-term advantage.
Industrial depth. Healthcare, energy, telecom, manufacturing, mobility — places where AI creates real productivity and societal impact.

Talent + Trust + Industry is a combination no other region matches at this scale.

Turning Momentum Into Market Leadership

Empower emerging talent. Give engineers bold problems, mentorship, and global exposure.
Help startups scale at home. Capital, customers, and commercialization support.
Pair research excellence with go-to-market execution. Breakthroughs matter when they become products used by millions.

Finland and the Nordics: A Focused Case

Build AI-native companies that scale globally from day one.
Apply AI to critical infrastructure — networks, healthcare, energy — where reliability and trust matter most.
Keep a builder’s mindset: practical, systems-oriented, export-ready.

“Good” is not the goal. World-class is.

Developer Takeaways (DEV angle)

Systems > demos. Invest in data pipelines, evals, infra, observability (LLMOps) as first-class features.
Compliance-by-default. Design data governance, audit trails, model risk notes alongside code.
Vertical focus. Pick one domain (health, energy, telecom) and ship a thin-slice product that meets real constraints.

What to Build Next (ideas you can ship in a week)

Inference cost dashboard (per-request cost & latency, with alerts).
Prompt & eval harness (regression tests for prompts/agents with pass/fail gates).
PII-aware data loader (redact/classify on ingest; keep an audit log).

Discuss

What’s the single action that would most accelerate Europe’s AI momentum for developers?