Skip to content
nanohypenanohype

Repos

Every repo in the org is one of three things: factory context,factory output, or the factory itself. The public ones are below; the GitOps state repos the portal drives are private.

Each repo below ships an AGENTS.md — the entry point an agent reads before working on it. Those are rendered here from the repos themselves, so what you read is what an agent reads.

nanohypeThe factory's vocabularyTemplates, composites, standards, the SDK and the MCP server. What every other repo is described in terms of.fabThe factory clientOrchestration across the build phases, the agent roster, the merge gate, and the baseline skills. Open source, so the factory can be cloned and run rather than only described.landing-zoneCloud substrateThe slow-moving AWS layer — VPC, base IAM, KMS, DNS, cluster vending — as OpenTofu components driven by Terragrunt, plus the generic module that provisions a tenant's datastores from its declaration.eks-gitopsCluster addon catalogWhat ArgoCD installs on a cluster once it exists: cert-manager, external-secrets, Kyverno, the observability stack. Charts, not cloud resources.eks-agent-platformThe control planeThe CRDs a tenant is declared in — Platform, AgentFleet, ModelGateway, BudgetPolicy, EvalSuite — and the operator that reconciles them, including the per-tenant AWS identity and access it mints.eks-fleetThe cluster factoryVending EKS clusters from a namespaced Cluster resource, via a Crossplane composition that runs the landing-zone modules and writes the result back to status.kxThe local clusterA kind workspace mirroring the eks-gitops catalog, so the same charts run locally before they run on EKS.portalThe operations portalRunning the substrate from one UI with one audit trail: a Go API and a React SPA over the same components the CLI drives.cloudgovGovernance CLIAWS security and cost posture — IAM least-privilege, spend, infrastructure hygiene, drift — plus a conformance auditor for Platform tenants.

Factory output

Standalone Platform tenants, each a Helm chart plus a Platform CR. They are what the factory produces rather than part of what produces it, so they ship an application and not an agent contract.

Design principle

This is a greenfield system: every repo presents as a single-generation design, architected in its current shape rather than evolved into it. Shared primitives and tooling presets live in consumed packages, not in per-repo copies that drift.