Live · Validated · Pilot · Roadmap · Not live
States what the available implementation, test, release, and deployment evidence establishes within a named scope.
Evidence model
Show the work behind the statement.
Each material claim has two independent dimensions: delivery maturity and publication approval. Working code is not automatically live, and a live capability is not automatically approved for public wording.
Two dimensions
Technical maturity does not approve marketing copy.
Public approved · Review needed · Internal only
States whether accountable business and technical reviewers have approved the exact public meaning.
Initial architecture claims
A conservative register for review.
These entries show the intended public wording and maturity discipline. They remain review material until the named owners approve the exact build.
| Claim | Maturity | Evidence establishes | Approval |
|---|---|---|---|
| Four backend images are independently built in the current delivery configuration. BAST-DELIVERY-001 | Validated | Pipeline and Docker definitions; not an immutable runtime observation. | Review needed |
| Specialized agents are configuration-defined components inside bounded runtimes. BAST-AGENT-001 | Validated | Agent configuration and runtime packaging; not one deployed microservice per agent. | Review needed |
| Container health checks provide repeatable unhealthy-instance detection signals. BAST-RELIABILITY-001 | Validated | Health endpoints and image checks; not the complete autonomous recovery loop. | Review needed |
| Self-healing functions combine detection, bounded remediation, verification, and safe rollback. BAST-RELIABILITY-ROADMAP-001 | Roadmap | Approved target definition; implementation evidence remains incomplete. | Review needed |
| The current configured path uses DuploCloud-backed service management; post-Duplo operation remains the target. BAST-INFRA-001 | Validated | Version-controlled pipeline and Terraform configuration; not proof of every live environment. | Review needed |
Evidence strength
Different records prove different things.
Code path
Proves implementation exists at an immutable revision. It does not prove deployment.
Test or evaluation
Proves the recorded behavior under bounded conditions. It does not prove general quality superiority.
Deployment or release record
Ties a built artifact to a named environment or distribution channel.
Metric snapshot
Supports a quantitative statement only for its defined population and measurement window.
See it operate