Crate engenho_types 

engenho-types

The typed Kubernetes resource catalog for engenho.

Per pleme-io/theory/ENGENHO.md §II.1, every Kubernetes kind is a #[derive(KubeResource, TataraDomain)] struct mechanically emitted by forge-gen from upstream OpenAPI v3 (Pillar 12 — generation over composition). The non-negotiable rule of this crate: no hand-authored resource types. If you reach for a hand-written struct, you are violating the prime directive — extend the generator instead.

Crate layout (target)

engenho-types/
├── src/
│   ├── lib.rs                 (this file — module roots + invariants)
│   ├── kind.rs                (trait KubeResource — the typed contract)
│   ├── meta.rs                (ObjectMeta, ListMeta, TypeMeta)
│   ├── api.rs                 (GroupVersionKind, GroupVersionResource)
│   ├── core_v1/               (generated — Pod, Service, Namespace, …)
│   ├── apps_v1/               (generated — Deployment, ReplicaSet, …)
│   ├── rbac_v1/               (generated — Role, ClusterRole, …)
│   ├── networking_v1/         (generated — NetworkPolicy, Ingress, …)
│   ├── storage_v1/            (generated — StorageClass, …)
│   ├── coordination_v1/       (generated — Lease, …)
│   ├── apiextensions_v1/      (generated — CustomResourceDefinition)
│   └── …                      (~16 generated kind groups total)
├── vendor/
│   └── openapi/v1.34.0/       (BLAKE3-attested upstream schemas)
└── tests/
    ├── openapi_roundtrip.rs   (each kind ↔ openapi-spec/v3/*.json)
    ├── bit_repro.rs           (forge-gen regenerate == tree source)
    └── lisp_authoring.rs      (TataraDomain round-trip per kind)

Status — M0.0

Crate scaffold only. The first kind (Pod) lands in M0.0.1 as a hand-authored target shape, validated by tests/openapi_roundtrip.rs against vendor/openapi/v1.34.0/api__v1_openapi.json — that hand-author is the generator’s bullseye, the byte-for-byte target that forge-gen --backend kube-resource must emit by M0.0.3. The kind itself is then deleted from the tree and replaced by the generator’s output.

Ship gate (theory/ENGENHO.md §XIII)

Engenho ships ONLY when Sonobuoy --mode=certified-conformance passes on Kubernetes 1.34 with zero skips. Until M4 lands, the kasou

• kikai bridge runs k3s v1.34 in production locally and supplies the operator kubectl experience while engenho catches up.

Re-exports

pub use consistency_tier::tier_from_metadata;

pub use consistency_tier::ConsistencyTier;

pub use consistency_tier::CONSISTENCY_TIER_ANNOTATION;

Modules

api

API discovery helpers — GroupVersion parsing + path construction.

auth

KubeAuth — the typed surface every connection negotiates against.

client

KubeClient — the typed CRUD + watch surface against a kube apiserver.

consistency_tier

C5 — per-resource consistency-tier annotations.

error

KubeError taxonomy.

generated_v1_34

GENERATED — engenho-kube-codegen — every K8s kind we currently emit.

informer

Informer — cached state-sync for a single resource type.

kind

The KubeResource typed contract.

meta

Object / List / Type metadata — the upstream meta/v1 types.

nomad_v1

Typed Nomad job + task + group + driver-config shapes.

patch

Typed patch operations. Maps to the apiserver’s PATCH endpoint with the correct Content-Type per variant.

primitives

Cross-kind typed primitives.

reconciler

Reconciler<R> — the typed contract every engenho controller satisfies.

translator

WorkloadTranslator — typed cross-architecture workload translation.

watch

WatchEvent<R> — typed stream events the apiserver emits over the ?watch=true channel.