architecture-validator logo

architecture-validator

Free

Validates a project's requirements / design against the General Principles (policy-as-code) + the reg KB, and auto-injects the missing non-functional requirements at intake. Its residency module (ex-Rsk4) scans IaC /...

Visit Website
generative-aiai-agentsassure-monitorgovernance-risk-complianceports-and-adaptersaiai assistantautomation

Overview

architecture-validator validates a project's requirements and design against the 12 General Principles (P-01..P-12) expressed as policy-as-code. It cross-checks a regulatory knowledge base and auto-injects missing non-functional requirements so a project cannot start non-compliant. It is described as the system rule R6 points to, the enforcer the other systems defer to.

It also carries an in-repo residency and IaC scanner, so one gate covers both design and cloud posture. Given Terraform plan JSON, a directory of .tf files, or a live GCP scope, the scanner emits a PASS/FAIL ResidencyScan over region and residency violations. The file-based scan is pure stdlib and exits non-zero on FAIL, so it can be used as a CI gate.

The system is built as ports-and-adapters on the Gemini Enterprise Agent Platform, with region pinned to asia-southeast1 for data residency. The domain core is pure standard library and runs the full validation pipeline offline with no Google Cloud SDK installed. Validation produces three artifacts: ValidationReport, PrincipleFinding[], and InjectedRequirement[]; the residency scan produces a fourth, ResidencyScan.

Pricing

Free

Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.

Visit Website

Prices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.

Use Cases

  • Teams use architecture-validator to validate a project's requirements and design against the 12 General Principles at intake.
  • Teams use architecture-validator to auto-inject missing non-functional requirements so a project cannot start non-compliant.
  • Teams use architecture-validator to scan Terraform plan JSON, .tf files, or a live GCP scope for residency violations.
  • Teams use architecture-validator as a CI gate because the file-based scan is pure stdlib and exits non-zero on FAIL.
  • Teams use architecture-validator to run the full validation pipeline offline with no Google Cloud SDK installed.
  • Teams use architecture-validator to produce a ValidationReport with per-principle findings and injected requirements.
  • Teams use architecture-validator to check region and residency violations such as disallowed region, global/multi-region endpoint, missing regional CMEK, public egress, or no VPC-SC perimeter.

Features

AI assistant

Natural language interface

Workflow automation

Reviews

No reviews yet. Be the first to share your experience!

Rankings & collections