anyulled Architectural Quantum and Deployability Validator
Analyze service boundaries to verify independent deployability and isolation.
When to Use
- Periodic architecture reviews
- PRs introducing cross-service synchronous calls
- PRs introducing shared database usage
- Microservice deployability audits
Scope
- Scans: outbound HTTP/gRPC calls, database connection strings, schema configs, and IaC files that affect independent deployability.
- Exclusions: generated/vendor artifacts, sample or benchmark repos, and static references that do not alter deployability boundaries.
- Fallback: if deployability boundaries are unclear, apply the shared conventions heuristic order and downgrade to warning with low confidence.
- Routing: defer shared-table ownership to Data and Database Coupling, inter-service workflow shape to Distributed Workflow and Integration, and platform bleed to Platform and Infrastructure Boundary.
Workflow
- Map synchronous dependencies.
- Trace HTTP, gRPC, and similar outbound calls on critical paths.
- Merge services into one quantum when a downstream dependency is required at runtime.
- Detect shared data stores.
- Inspect connection strings, schemas, and IaC for shared databases or schemas.
- Merge services that share a store.
- Calculate quantum size.
- Summarize the connected deployable unit and its scope.
- Flag distributed monolith patterns.
- Report findings.
- List coupled services, databases, and synchronous calls.
- Format output for CI/CD or review dashboards.
Rules
- Use static analysis only.
- Rely on code, config, and IaC.
- Keep analysis deterministic and language-agnostic.
- Treat shared database schemas as a high-risk coupling signal.
Shared Conventions
- Follow the repository-wide conventions in shared-skill-conventions.
- Use the canonical output contract, severity levels, confidence rubric, routing rules, and false-positive downgrades defined there.
- If this skill is not the closest match, defer to the routing guidance in the shared conventions file.
Output
Return:
- Architecture quantum boundaries
- Coupled services and databases
- Blocking synchronous dependencies
- CI-ready pass or fail output