INIO Tooling

Published: 2026-06-23

INIO Tooling

Every project eventually accumulates tools.

Some organisations collect them intentionally. Others discover, several years later, that they have accidentally built a small nation-state with its own infrastructure, communication systems, governance model, transportation network, archives, and occasionally a functioning economy.

The INIO environment sits somewhere between those two extremes.

At first glance it looks like a collection of open-source tools running on a handful of virtual machines. In reality it is an experiment in coordinating humans, services, processes, and increasingly autonomous agents across a shared operational landscape.

The objective is not to build the largest platform, the most fashionable architecture, or the most complicated deployment pipeline. The objective is to reduce vagueness.

Every component exists because it helps answer one or more of the following questions:

  • What is happening?
  • What is about to happen?
  • Why is it happening?
  • Who decided this was a good idea?
  • What did we learn last time?
  • Is somebody already working on it?
  • Can we prove it?

The result is a collection of infrastructure, tooling, processes, and knowledge systems that together form the operational foundation for Trinity.

Some tools move packets.

Some tools move code.

Some tools move knowledge.

A few occasionally move the organisation forward.

The sections below describe the current state of the ecosystem, knowing full well that by the time this document is published, at least three versions, two architectures, and one strongly held opinion will already have changed.

Infrastructure & Hosting

  • Proxmox (PVE 9.1.5) — VM hypervisor
  • Debian 12 (Bookworm) — OS on all VMs
  • OpenTofu 1.11.5 — IaC for VM provisioning
  • Ansible 7.7.0 — configuration management

Networking & Proxy

  • Nginx — reverse proxy (proxy-int + proxy-ext)
  • dnsmasq — internal split-brain DNS
  • WireGuard — VPN (wg5, stuanet peer)
  • Let's Encrypt / Certbot — TLS certificates

Application

  • Java 21 (Temurin) — risk game engine runtime
  • Javalin 6.7.0 — web/REST framework (API)
  • Gradle — build tool (shadow jar)
  • H2 — embedded database
  • HTMX — frontend reactivity

CI/CD

  • Woodpecker CI v3.13.0 — pipelines
  • Forgejo — git hosting + issue tracker
  • Docker — container runtime for CI steps
  • GitHUB - pipelines

Observability & Data

  • OpenObserve — logging (replaces Grafana/Loki)
  • OpenTelemetry — instrumentation (gRPC :4317 / HTTP :4318)
  • Neo4j 5 — shared agent knowledge graph
  • JBake - knowledge document presentation and blog.
  • Kafka — event bus (6 topics: intent, momentum, touches, observation,
    coordination, dead_letter)
  • Umami — web analytics
  • Grafana — dashboards (partially)
  • Kafka Connect — Neo4j sink (partially deployed)

Secrets & Auth

  • OpenBao (HashiCorp Vault fork) — secrets management (deployed, agent write
    path incomplete)

Languages & Tooling

  • mise — tool version manager (Node 24, Python 3.12, Go 1.24, Rust stable)
  • Node.js 24 — agent scripting / opencode-ai
  • Rust — TaskeJuggler 2.0
  • Python 3.12 — scripts, Neo4j tooling
  • LaTeX (pdflatex) — presentation documents
  • D2 — diagram tool

Agent Coordination

  • Claude — infra, CI/CD, planning
  • Gemini — SMC engine, UX, optimization
  • OpenAI — governance and policwork
  • Orchestrator (orch001) — KI, Knowledge base, WIP enforcement, PR assignment, Task-scheduler