Team standards

The standard for each surface comes first, followed by the platform-wide baseline. Each team’s pages list the exact tools used in each area.

By surface

Platform-wide

Version-support policy

A language name alone can become outdated. Set the supported version range so readers know the minimum version, not just the tool name.

Keep the JVM on Java SE LTS releases. Set the minimum version in the build config, not just in prose:

// build.sbt, the version floor is enforced, not documented
ThisBuild / scalaVersion := "2.13.14"
ThisBuild / javacOptions ++= Seq("--release", "17")
ThisBuild / scalacOptions ++= Seq("-release:17", "-Werror", "-Wunused:all", "-deprecation")

Quality-tooling baseline

Each surface sets a formatter, a linter, and a type or static-analysis check. These are the specific checks that the quality gates run in CI.

Run locally the same checks that CI runs:

sbt scalafmtCheckAll compile   # compile carries -Werror

ruff format --check . && ruff check . && mypy .

pnpm prettier --check . && pnpm eslint . && pnpm tsc --noEmit

dart format --set-exit-if-changed . && dart analyze

dotnet format --verify-no-changes && dotnet build

gofmt -l . && go vet ./... && staticcheck ./...

cargo fmt --check && cargo clippy -- -D warnings && cargo build

Build and dependency management

List the build and dependency manager for each surface so “one build toolchain” has a clear meaning.

Commit the lockfile for every project. Pin direct dependencies. Use Renovate to keep dependencies current, so the minimum version stays clear instead of drifting:

// renovate.json, org-wide dependency currency policy
{
  "extends": ["config:recommended"],
  "lockFileMaintenance": { "enabled": true },
  "vulnerabilityAlerts": { "labels": ["security"] }
}

Supply chain

The registry process is build once and promote (see The Twelve-Factor App build/release/run separation and the Artifact Registry docs). Add these supply-chain rules:

• Generate an SBOM at build time and retain it with the artifact.
• Scan dependencies with Renovate or Dependabot; treat vulnerability alerts as work.
• Sign images and record build provenance so a promoted digest is verifiable downstream.

Governance

This table is a standard, not a suggestion. Changes require review.

• An owner group owns the table and reviews it on a set cadence; the exact owner and cadence are still being ratified (see the note below).
• Changing an existing standard requires an ADR that records the decision and its context.
• Introducing a new language or tool routes through the exceptions process before it lands here.
• The shared CI toolchain lives in NT-NinjaTrader/gh-actions; reuse those actions rather than re-implementing per repository.
• Define the domain model once in tradovate/master-scheme, and generate downstream. Never redefine a shared entity in a service.