Engineering standards

How U Framework writes, reviews, tests and ships code.

These standards apply to every system U Framework builds.

Language and types

TypeScript end to end for web, mobile and Node.js services, with strict enabled.
Python for data, research and model work, with type hints and a formatter enforced in CI.
Shared contracts (API payloads, events) are defined once and validated at runtime at every trust boundary.

TypeScript

import { z } from "zod";

export const Brief = z.object({
  email: z.string().email(),
  description: z.string().min(30).max(6000),
});
export type Brief = z.infer<typeof Brief>;

Reviews

Every change is reviewed by another engineer before it reaches the main branch.
Reviews check correctness first, then security, then clarity — style is automated.

Testing

Unit tests for logic with branches; integration tests for anything crossing a process or network boundary.
Bugs get a failing test before they get a fix.

Performance and accessibility

Web interfaces are measured against Core Web Vitals budgets.
Interfaces meet WCAG 2.2 AA as a baseline: semantic markup, keyboard operability, visible focus, sufficient contrast and reduced-motion support.

Security

Secrets never live in source control; they are injected from managed stores.
Dependencies are kept current and scanned.
See Security principles.

Documentation

Every system ships with an architecture overview, a runbook and setup instructions a new engineer can follow.

Language and types

TypeScript end to end for web, mobile and Node.js services, with strict enabled.

Python for data, research and model work, with type hints and a formatter enforced in CI.

Shared contracts (API payloads, events) are defined once and validated at runtime at every trust boundary.

TypeScript

import { z } from "zod";

export const Brief = z.object({
  email: z.string().email(),
  description: z.string().min(30).max(6000),
});
export type Brief = z.infer<typeof Brief>;