Polyglot systems engineering
Use the language that fits each job, then make the handoff explicit enough to inspect, test, and replace.
Alpha · polyglot systems engineering
Several languages. One platform contract.
Platform Zero treats infrastructure as software. Shell owns the host-facing lifecycle, Python resolves and renders structured state, Kotlin coordinates runtime contracts, and TypeScript checks what users actually reach in a browser.
Alpha software: this page describes the current public architecture and test stack. Interfaces and module contracts are still changing.
- 01Manifest + module pinsJSON · YAML · Git revisions
- 02Resolve + renderPython
- 03Build + activateShell
- 04Verify contractsKotlin
- 05Exercise the browserTypeScript
One failure path can stop activation before the host is trusted.
The engineering proposition
The boundary matters more than the language count.
Infrastructure as software
Turn scattered host decisions into pinned inputs, generated output, repeatable activation, and reviewable rollback.
Full-stack platform work
Carry one change from source resolution and operating-system lifecycle through service contracts and browser behavior.
Core language boundaries · public source
Each layer has a job—and evidence.
These links point to source that is available while signed out. Private site values, credentials, and deployment-specific configuration are not part of the demonstration.
01Shell
Own the operating-system edge.
Build the release, reconcile host state, install units, activate services, collect diagnostics, and restore the prior release when activation fails.
- Build and deployment orchestration
- Lifecycle, readiness, and rollback
- Host-facing safety checks
02Python
Turn structured inputs into checked state.
Resolve exact module revisions, reject unsafe trees, render systemd user contracts, and emit deployment audit data where structured transformations matter more than shell composition.
- Module-lock resolution
- Runtime and systemd rendering
- Deployment auditing
03Kotlin
Express runtime contracts as typed suites.
Model blocking, optional, and advisory checks; compose suites; manage authenticated clients; and produce a consistent verification surface across unlike services.
- Typed suite catalogue
- Service and authentication clients
- Recovery and infrastructure checks
04TypeScript
Check the boundary a user experiences.
Describe public, edge-authenticated, OIDC, and non-UI routes; reuse login drivers; verify session behavior; and capture inspectable browser evidence.
- Route and authentication contracts
- Playwright browser flows
- Visual and screenshot evidence
What holds the layers together
Polyglot does not have to mean fragmented.
Language boundaries stay useful when the contract crossing them is smaller and more stable than either implementation.
Pinned source
A flat site manifest selects modules and records exact revisions before assembly begins.
Runtime model
Module-owned YAML becomes one validated description of services, dependencies, placement, and lifecycle.
Inspectable bundle
Generated Quadlets, systemd units, configuration templates, and helper commands can be reviewed before activation.
Executable evidence
Source checks, runtime contracts, browser flows, and recovery drills decide whether the result can be trusted.
Smaller integration edges
Use another language when the boundary requires it.
The platform does not treat incidental file types as equal evidence. These smaller surfaces exist because a host application, database, or build system defines the integration point.
One change, end to end
Add a service without adding another one-off deployment path.
A module brings its runtime definition, templates, dependencies, tests, and component metadata. The same generator and verification contracts then carry it through the system.
- 01Define
Describe the service contract and keep deployment-specific values outside shared source.
- 02Resolve
Pin the module revision and reject dependencies, paths, or placements that violate the build contract.
- 03Render
Generate the runtime and systemd artifacts without changing the host.
- 04Activate
Install a versioned release and restore the previous one if activation fails.
- 05Verify
Exercise readiness, service behavior, authentication, and the browser surface that users depend on.
The practical result
A platform change has one reviewable path from source to evidence.
The value is not using many languages. It is making each language responsible for a clear part of a system that can still be built, operated, and handed over as one.