Stories and architecture

precon · case-study

A Download Is Not Publication

An external file arriving in storage is evidence that something was observed. It is not evidence that the file is the current, relevant, or authoritative document for an operational workflow. In preconstruction, confusing those two events…

platform · case-study

Failures Are Work Items, Not Just Log Lines

An operational workflow regularly encounters missing mappings, ambiguous identities, incomplete evidence, and provider mismatches. Those are not all software defects, and they are not all reasons to stop an entire run. They are often work…

data · case-study

One Database, Several Kinds Of Truth

LKCI currently uses one Postgres database, but it does not treat that physical fact as permission to blur responsibility. Lakehouse schemas hold ingestion, canonicalization, historical truth, enrichment, and analytical publication.…

platform · case-study

Humans And Agents Share Controls

The interesting design question for an engineering agent is not whether it can read a page, write a draft, or suggest a change. It is how that capability enters the operating system around it. LKCI's answer is deliberately ordinary:…

geo · case-study

Geography Becomes An Operating Decision

A map is good at making patterns visible. It is poor at preserving the exact decision that follows from those patterns. LKCI's geo system treats spatial analysis as an operating workflow: source data becomes canonical parcel and feature…

platform · architecture

Platform Layers

The platform layers separate runtime surfaces, capability services, shared contracts, external adapters, deterministic pipelines, executable jobs, and durable documentation.

platform · architecture

Monorepo As Operational Platform

The monorepo gives LKCI one place to evolve operational data, automation, review, integrations, UI, infrastructure, and documentation together.

data · architecture

One Database, Many Responsibilities

LKCI currently uses one Postgres database for multiple responsibilities, but the architecture treats those responsibilities as separate from the start.

data · architecture

Designing For Future Separation

Future database, service, and deployment splits are easier when current code already respects conceptual boundaries.