TTI Coding Standards

Agency-wide engineering standards for NIS-supported codebases. This repo is load-bearing: every AI panel code review on the forge retrieves from it with guaranteed weight, so what's written here is checked against every pull request across the agency — automatically, on every review.

Why this exists

• Consistency across codebases — a change can be correct in its file and still wrong for the agency. Reviews ground against these documents to catch that.
• Supportability — NIS supports a deliberately narrow language set (see languages.md). Fewer stacks, deeper competence, easier handoffs.
• Reduced attack surface — fewer runtimes, pinned supply chains, and one set of security rules enforced everywhere (see security.md).

How it evolves (the wheel)

Standards are mined from reality, not invented in meetings:

1. Panel reviews record every confirmed finding (with evidence and the cross-examination tally) in the review transcript store.
2. A weekly job clusters recurring confirmed findings and drafts amendments to these documents as a pull request on this repo.
3. The panel reviews that PR like any other; a human merges it.
4. The next review cycle enforces the amended standards.

Defect → confirmed finding → standard → prevention. Propose changes the same way: open a PR. Nothing here is sacred; everything here is versioned.

Layout

File	Scope
languages.md	Supported language policy (the narrowing)
python.md	Python services and tooling
typescript.md	TypeScript / web front ends
rust.md	Rust (desktop, systems tooling)
shell.md	Bash / POSIX shell for ops glue
security.md	Cross-language security rules