nomos mark
nomos
what you would be walking into.
Technical brief
for a prospective cofounder · september 2026

You would not be starting from zero. Four products are built and running, on two deliberately different architectures. What follows is what exists today, what is missing, and how I know. Every line is traceable to a dependency-graph extraction of a named commit.

Munus household operating system · preparing beta
React Native · Expo · Supabase · Postgres
built
Four sign-in paths (Apple, Google, magic link, salted and hashed parent passcode) behind a routing auth gate · five edge functions · multi-provider AI routing with retry and model mapping · RevenueCat subscriptions, entitlements and webhook · household membership and invite claiming · local-first stores with remote commit
open
Row-level security review, analytics wiring, beta hardening
Acesa Health family health memory · private beta
React Native · Expo · local-first, no cloud account by design
built
Body-region taxonomy with aliases, bilateral handling and life-stage gating · medication, trigger and treatment ontologies · episode lifecycle with recovery scoring and snapshot correction · versioned store migrations · environmental context (air quality, geocoding, daylight phase) captured at save · on-device passcode
IP
A provisional patent application has been filed for aspects of the health intelligence layer behind Acesa Health.
open
Backup and family sync through the user's own iCloud · demo seed sits on the production entry path
Tekton Mechanics trades office and field · in build
TypeScript monorepo · React · Express · Postgres via Drizzle · serverless
built
Contract-first API generating a typed client and Zod response parsers · jurisdictional sales tax engine · invoice PDF generation · object storage with access groups and signed URLs · structured logging with field redaction · chunked offline-tolerant voice capture with silence trimming · speech-to-text evaluation harness comparing providers on annotated fixtures
open
Auth and tenancy. Billing. This is the critical path
Text It capture to memory · waitlist open
Expo · local SQLite with six migrations · hosted analysis, anonymous session
built
Hybrid semantic and lexical retrieval with corpus IDF and literal-match capping · query intent classification (temporal, historical, event-order) · an evidence-sufficiency gate that declines to answer on weak support · provider abstraction with a fixture provider for deterministic tests · retrieval evaluation with holdout sets, per-query graders, regression tests, failure-subtype classification, and checks for invented facts and omitted commitments
open
Consolidation onto main

Patterns across the portfolio

Two spines, on purpose. Personal and local-first products run on Expo with data on the device. Multi-user business products run as a monorepo with Express, Postgres and a generated API contract. That second spine already carries authentication, a generated client shared across web and mobile, and AI services in another product in the portfolio. Several more products exist and are deliberately left off this sheet.

Zero circular dependencies across 31 repositories. Versioned data migrations in three of them. Evaluation harnesses in two.

Where I would want you first

1
Auth and tenancy for Tekton. The pattern already exists elsewhere in the portfolio and needs doing properly here
2
Backup and sync for Acesa through the user's own iCloud, so a lost phone is not a lost record and I still hold nothing
3
A security review of the household data model in Munus, row-level security first
4
Take the evaluation work further and make it the way we ship intelligence, not a thing I did twice

how I know all of this

Static dependency-graph extraction, per repository, at a named commit, AST only. It proves what exists and how it connects. It does not prove correctness, security, or test coverage. Node and edge counts describe structure, not maturity. I am happy to walk any repository with you and let you judge for yourself.

Kassandra Nolan · [email protected] nomos industries inc. · 2026