Platform API
Shared platform and product-facing capabilities packaged behind an independently built service boundary.
Architecture · Current and target
Bounded services. Inspectable decisions.
Bast separates public architectural truth from architectural direction. The current system packages specialized capabilities into independently built runtime services. Configuration-defined agents operate inside those service boundaries; one microservice per agent remains a direction, not a current system claim.
Current operating model
What the implementation supports today.
The current development delivery path builds four named backend images. That count describes deployable images in the inspected pipeline—not every API package, agent, library, or future service.
Organization services
Organization-scoped services packaged for the current deployment path.
CAT runtime
Configuration-defined specialized agents and orchestration execute inside this runtime boundary.
BastCare summarizer
BastCare processing is built as a bounded backend image supporting the product workflow.
Control path
Five layers connect intent to evidence.
- DefineSpecification, policy, ontology, and approved knowledge.
- PackageBounded code and agent configuration become build artifacts.
- DeployInfrastructure and runtime configuration establish the operating boundary.
- ObserveHealth, requests, tests, and content-free operational evidence show behavior.
- ExplainClaims point back to evidence, maturity, ownership, and review dates.
Reliability & recovery
Self-healing is a testable sequence.
We reserve the term for a complete loop: detect, remediate within bounds, verify recovery, and roll back or fail safely. The documentation shows which parts are current and which remain target state.
Health and orchestrator recovery
Health checks provide infrastructure-level detection signals. Environment-specific restart or replacement behavior still requires deployment evidence.
Autonomous functional recovery
Application-level detection, bounded remediation, post-recovery verification, and safe rollback must be proven end to end before being described as live.
Current Duplo path
Version-controlled deployment configuration continues to reflect DuploCloud where it remains in use; this does not assert every environment is currently healthy.
Post-Duplo infrastructure
Directly managed cloud infrastructure remains separately labeled until migration and operational verification are complete.
Next