# AGENTS.md - Infrastructure And Hardware Scope: `4-Infrastructure/` ## Repository Extraction Notice (2026-06-02) The following infrastructure components have been extracted to `distributed-compute-fabric` repository: - `kubernetes/` - Kubernetes manifests and configurations - `k3s-flake/` - K3s flake configurations - `kube/` - Additional Kubernetes configurations - `shim/ray-actors/` - Ray actor implementations - `shim/vcn_*.py` - VCN compute substrate shims - `shim/hermes/` - Hermes orchestration layer - `shim/vectorless_spatial_hash_backend*.py` - Spatial hash backends - `docs/vcn-lupine-setup.md` - VCN setup documentation - `docs/mesh-networking-over-ray-plan.md` - Ray networking documentation This AGENTS.md now covers only the remaining infrastructure components: hardware bring-up, storage stack, cloudflare edge, and non-VCN shims. ## Rules - Keep infrastructure scripts receipt-bearing: every probe should have a machine-readable output or update an existing receipt. - Separate software witnesses from live hardware witnesses. - Do not claim FPGA acceleration from bitstream generation alone. - Do not claim UART/fabric success without observed bytes or a matching hardware receipt. - Treat `/usr/bin/sem` as GNU Parallel on this machine unless proven otherwise; use the isolated `sem` binary documented in stack solidification receipts when needed. - Remote model/API probes must be secret-clean. Read provider credentials from environment variables only (`OLLAMA_API_KEY`, `DEEPSEEK_API_KEY`, etc.); never embed literal keys in scripts, receipts, prompts, or docs. - LLM/model outputs are reviewer receipts, not validation. If a model review is promoted, store the answer and a machine-readable receipt with prompt/answer hashes under `shared-data/artifacts/`, and state which files formed the context. ## Preferred Checks ```bash python3 -m py_compile 4-Infrastructure/shim/