UserROOTThe person remains above the system. Consent, revocation, custody, and emergency governance are first-class design constraints.
FoundationTSARO · NICOLETSARO governs admissibility. NICOLE governs evidence, consent, denial, release, and auditability.
Core systemsW-X · SSI · CivOS · SOSThe public branches translate environmental, structural, and degraded-infrastructure context into governed state.
Bridge modulesBFB / TABBridge logic routes bounded packets when a scenario requires responder-facing coordination.
10-second orientation

Safety without extraction.

LAKANA keeps raw state local and releases only bounded, role-scoped claims when evidence gates allow it.

Inspect evidence
2-minute orientation

How the stack works.

Local sensing is filtered by physics, governed by custody, converted into a bounded claim, and blocked when the evidence surface overreaches.

View architecture
10-minute orientation

Run the public surface.

The Proof Theater shows local state, role-scoped output, hash/seed/state-log export, and explicit claim boundaries.

Open Proof Theater
local-firstphysics-boundedevidence-governedfail-closednon-weaponizedclaim-bounded

System flow: from raw state to bounded claim

A compressed executive diagram for first-time visitors and reviewers.

1 · local sensing

Raw state begins on-device or in a governed local simulation boundary.

2 · admissibility

TSARO checks whether claims remain physics-plausible and bounded.

3 · custody

NICOLE applies consent, scope, revocation, and audit logic.

4 · claim class

The result is admitted, held, degraded, or blocked.

5 · role release

Only the minimum bounded claim moves to the allowed role.

What is LAKANA?

LAKANA is a sovereign safety-systems architecture for protecting people without turning their lives into continuous data products.

It combines local computation, physics-bounded interpretation, evidence custody, role-scoped release, and fail-closed behavior into a public research and engineering stack.

The guarantee is narrow by design: raw state stays local by default, and only a governed bounded claim can move.

LAKANA does not make a person safer by knowing more about them. It makes the system safer by governing what it is allowed to act on.

Why LAKANA exists

The problem is not simply weak networks or slow response. The deeper problem is that many safety tools require institutions to collect, retain, or reconstruct private human-state information before help can be delivered.

The conventional trade

Continuous location, identity, biometrics, context, and behavioral traces become the price of protection. That creates adoption resistance, institutional liability, and replayable evidence risk.

more collection · more reconstructive exposure

The LAKANA contract

Raw state remains local by default. The system moves only the bounded claim needed for the scenario, with TSARO admissibility and NICOLE custody determining what can leave the device.

bounded packet · governed release

Core systems

Listed once in operational flow order, with Blue Force Bridge separated as a bridge module instead of a core system.

WX-AgW-XSSITSARONICOLEBFBCivOSSOSbounded context → admissibility → audit → governed packet
WX-Ag

Agronomic Extension

Ground-state, soil, water, field, and agricultural context feeding W-X and downstream safety models.

feeds W-X
W-X

Weather / World Exchange

Environmental truth layer for freshness, source class, uncertainty, RF/spectrum context, and physics honesty.

feeds TSARO admissibility
SSI

Sovereign Structural Intelligence

Structural human-safety layer for heat, load, recovery, rest, burden, and role-bounded outputs.

governed by TSARO · outputs to NICOLE
CivOS

Civilization Operating Substrate

Local fail-closed runtime substrate for degraded infrastructure and governed safety state.

substrate for SOS
SOS

Safety Operating System

Civilian protection layer for consent-gated, evidence-aware, degraded-condition safety workflows.

governed by NICOLE
BFB

Blue Force Bridge

Bridge layer for routing bounded packets when a scenario requires responder-facing coordination.

routes bounded packets from CivOS

Proof Theater & evidence posture

The sandbox is the interactive proof surface for local state, audit entries, role-scoped output, and governed release.

Runtime
Client-side
No remote telemetry needed for the public demonstrator.
State model
Explicit
Inputs, outputs, hashes, and audit log entries are visible.
Boundary
Simulation evidence
Not field validation. Not diagnostic authority.
Release
Bounded
Only role-scoped, governed claim classes are exported.

Claim classes: what LAKANA allows the public surface to say

Every public output is sorted by evidence posture before it becomes a claim.

Admit

Release the bounded claim.

Evidence path, denominator, source status, and boundary are complete enough for public display.

Hold

Do not release yet.

A value may exist, but a source path, denominator, figure/table link, or boundary is incomplete.

Degrade

Release with narrower language.

The evidence supports a weaker claim, such as simulation-stage pathway evidence instead of field proof.

Block

Refuse the claim.

Forbidden claims include clinical validation, emergency replacement, crop guarantees, privacy certification, and production readiness.

Choose your review path

The homepage now routes different stakeholders without forcing every visitor through the full technical stack at once.

Technical reviewer

Architecture and proof surface.

Inspect TSARO, NICOLE, subsystem flow, and public claim gates.

View architecture →
Research partner

Methods and evidence.

Read Monte Carlo posture, SSES outputs, run limits, and artifact-backed results.

Review evidence →
Safety stakeholder

Operational model.

See what the demonstrator does, what it exports, and what it refuses to claim.

Open demonstrator →
Funder / institution

Mission and milestones.

Start with pitch materials, company posture, and collaboration boundary.

Open pitch →

What LAKANA is — and is not

This is the single public boundary section for the homepage.

LAKANA is

  • Local-first safety infrastructure.
  • Physics-bounded state interpretation.
  • Evidence-governed release and audit design.
  • Fail-closed under uncertainty or infeasibility.
  • Non-extractive, non-weaponized, and claim-bounded.

LAKANA is not

  • Not a medical device or diagnostic system.
  • Not a return-to-play authority.
  • Not an emergency-service replacement.
  • Not a targeting, profiling, or discipline system.
  • Not a privacy/security certification or field-validation claim.
  • Not a user-data resale model.
Evidence discipline: LAKANA public materials separate completed simulation evidence, client-side demonstration behavior, future validation targets, and commercialization discussion. None of those are allowed to silently upgrade into field validation.

LAKANA does not make you safer by collecting more about you. It makes safety infrastructure safer by governing what the system is allowed to act on.

Local · physics-bounded · evidence-governed · fail-closed · non-weaponized