Automated testing and performance benchmarking engine for CASTÚO-SYSTEM™
Cast-o is the quality assurance and performance engine of the ecosystem. It provides a unified environment to structure, automate, and validate the CASTÚO-SYSTEM ecosystem through tests, infrastructure-as-code, and integration tools.
Its scope covers:
- Automated Testing: Unit, integration, and E2E tests (
pytest, Playwright). - Infrastructure Validation: Terraform (Hetzner) and Kubernetes manifests.
- IoT & Edge Simulation: ESP32 code and MQTT integration testing.
- Performance Benchmarking: Regression detection and resource usage analysis.
- CI/CD Support: Reusable pipelines and hardening checklists.
Cast-o acts as the TOOLING anchor, providing the necessary infrastructure for technical validation across all layers.
Cast-o (Assurance)
│
├── castuo-evidence (Public Fabric)
│ Evidence verification target
│
├── CASTÚO-SYSTEM (Private Core)
│ Execution engine
│
└── castuo-evolution (Control Plane)
Policy & Governance SSOT
- Testing Framework: Unit, integration, and E2E tests for AI and IoT components.
- Dockerized Environments: Modular
docker-composefiles for IoT, Cloud, and HA scenarios. - Infrastructure as Code: Terraform assets for Hetzner and K8s manifests.
- Observability: Monitoring configurations for Prometheus and Grafana.
- Documentation & Diagnostics: System diagnostics, integration checklists, and contingency reports.
Following the Evidence-First principle, Cast-o provides the raw data that supports maturity claims in the ecosystem.
- Implemented: Unit and integration test suites, Docker environments, and IaC bases.
- Validated: Performance benchmarking for core API endpoints and CI/CD automation.
Every test run generates a verifiable record linked to the target commit, federated in CASTÚO-EVOLUTION.
git clone https://github.com/Traky12/Cast-o.git
cd Cast-o
cp .env.example .env
docker compose up -d
pytest tests/ -v← Profile | → Evidence | → Governance | → Architecture Docs
Build · Validate · Observe · Document · Evolve
This repository is governed through the CASTÚO-SYSTEM evidence chain. Its current role, visibility boundary, required provenance, security baseline and promotion rules are defined in docs/CASTUO_ARCHITECTURE_GOVERNANCE.md. A repository artifact or green workflow proves only the declared scope; it does not by itself prove certification, production operation, funding, customer contracts or commercial success.
The assurance suite must test both accepted and rejected paths: unregistered agent, unauthorised tool, incorrect tenant, revoked credential, duplicate replay, missing evidence hash, unapproved model, sensitive action without approval, disconnected node, synchronisation conflict, rollback request and incompatible version.
The minimum failure contract is:
denied request → logged → explainable → recoverable
A passing local test proves only the declared test scope. It does not prove federated operation, production security, customer adoption or regulatory conformity.
This repository is part of the CASTÚO-SYSTEM private-cloud target architecture. Its repository scope does not by itself prove cloud provisioning, DNS, production operation, customer traction, financing, certification or independent validation. The service identity is a governed target boundary until a deployment record, access control, health check, observability, backup, restore, rollback, owner and dated Evidence Center record are published.
The public state model is DOCUMENTED → IMPLEMENTED_LOCAL → TESTED → VALIDATED → OPERATIONAL. OpenClaw and n8n, where referenced, are optional compatibility adapters and not the sovereign governance control plane.\n