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.
Technical maturity and publication readiness are different. Routine architecture facts can be reviewed together as a release artifact; consequential claims receive explicit human approval.
Two dimensions
Technical maturity does not approve marketing copy.
Release reviewed · Elevated review · Internal only
Routine code-derived facts are reviewed as a coherent release. Customer, privacy, security, regulated, quantified, competitive, and live claims require explicit approval.
Initial architecture claims
A conservative register for review.
These entries establish the initial baseline for one architecture review. The process verifies artifacts; it is not a system for scoring or monitoring individual contributors.
| 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; multitenant post-Duplo operation remains the target. BAST-INFRA-001 | Validated | Migration away is the completion criterion; BastCare operating there is the first planned milestone. | 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