Kubemoot Crew Fitness Functions

Mon, 01 Jan 0001 00:00:00 +0000

Kubemoot implements architectural fitness functions as first-class Kubernetes resources. The CrewFitness CRD allows operators and crew designers to define, execute, and observe fitness tests against deployed agent crews - declaratively, headlessly, and with automatic cleanup.

This document describes how Kubemoot adapts the fitness function concept from Architecture as Code (Richards, Ford, and Johnson) to the domain of AI agent crew orchestration.

From ADL to Kubernetes

An architectural fitness function is “any mechanism that provides an objective integrity check on some architectural characteristic,” as defined in Building Evolutionary Architectures (Ford, Parsons, and Kua); Architecture as Code (Richards, Ford, and Johnson) builds on the idea. In Kubemoot, the architectural characteristic under test is the crew’s discussion behavior - does the crew answer questions correctly, does it stand aside on irrelevant input, does the coordinator synthesize Tooler and Analyst contributions?

Gherkin, ADL, and Fitness Functions

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Kubemoot uses two structured languages: ADL (the Architecture Definition Language, applied to agents) to compose agent prompts, and a fitness-function format to specify executable acceptance checks for a crew. A natural question - especially for anyone arriving from a Behavior-Driven Development (BDD) background - is: why not use Gherkin (Cucumber’s Given/When/Then) for either of these?

This document answers that. It is a general compare-and-contrast, not a proposal. It explains where Gherkin overlaps with what Kubemoot already does, where it diverges, and why Kubemoot settled on ADL plus a purpose-built fitness format. Gherkin remains a credible alternative substrate for one of the two surfaces; the reasoning below makes clear which, and why.

Fitness on Kubemoot

Kubemoot Crew Fitness Functions

From ADL to Kubernetes

Gherkin, ADL, and Fitness Functions

Purpose