builder

apex solar kiss

governed domain architectures

apex solar kiss is the builder practice. ASK builds governed domain architectures: systems that make a decision-owner's intent, constraints, references, and judgment explicit such that generative work stays explainable, auditable, and answerable in its domain.

A deterministic governance architecture brackets the generative execution span. The governing rules and decision rights stay explicit while generation varies inside the bound, and human judgment stays at the apex rather than merely in the loop. The underlying primitive is bounded generativity: define the grammar, permit bounded variance, make selection and governance explicit.

The practice is one thing; the projects are several. The current portfolio includes two domain applications and the builder machine used to build and govern them. All of it is open source.

domain applications

asset-pipeline-ASK

repo >>

Commercial image production. It turns brand rules, creative direction, references, required outputs, and approval boundaries into a structured definition a production system can carry — a definition layer that sits above changing tools and models rather than inside any one of them.

urban-observatory

repo >>

Public-planning implementation intelligence. It reads public data to reconstruct how civic commitments move from decision into delivery, showing progress, delay, change, and uncertainty rather than collapsing implementation into a single verdict — and recording what the evidence cannot show as an observability limit.

the builder machine

The method, execution protocol, and design architecture used to build and govern the applications above. Each lives in a separate open-source repository.

method-ASK

repo >>

The method: how to design systems that build systems, carried as doctrine, topology, and worked examples above any single project.

control-surface

repo >>

The execution protocol: the shared workflow rules, review gates, and templates that govern how work gets done in a session, resolved locally into each project's operating rules.

design-system-ASK

repo >>

The design architecture: the visual foundations shared across the ASK ecology — tokens, type, and the wordmark. Downstream surfaces use them without redefining them. A-S-K.studio vendors those foundations from design-system-ASK.

all repositories >> the writing >>