SSLZ Agent documentation · Launch the agent · Classic direct-operator site
Implementation and Evidence Status
Authoritative implementation, execution-authority, and validation status for SSLZ
This page describes the implementation and execution boundaries of the integrated main branch.
PR #41 brought the SSLZ Agent profile, planners, contracts, and
documentation together at 8ceaa7f.
Installation uses main; no separate planning branch or pinned checkout is required.
The capability matrix separates implemented code, execution authority, and test evidence. A contract or planner can be implemented without being allowed to execute the operation it describes. Evidence links below identify the revision that was tested; they do not certify later revisions or current tenant readiness.
Evidence terms
- Local synthetic: deterministic fixtures, mocks, generated ephemeral signing identities, schema validation, and compiled-template or Terraform tests. It is not evidence about a real tenant, workload, recovery event, or migration.
- Hosted CI: repository tests on GitHub-hosted runners. All four
Validate IaCjobs passed on the PR #41 integration revision in run 41689880093. A separate website validation run rebuilt Jekyll, checked the rendered routes, and tested a clean publicmainclone without publishing. The earlier PR #31 run is historical evidence for8e96bd5, recorded on 2026-08-17 UTC. - Live preview: Azure-authenticated Bicep what-if or Terraform plan. The latest verified successful scheduled run in
the historical audit was 2026-08-10 on commit
a7acdbd, after PR #9. Both preview jobs passed and the deploy job was skipped. This predates PRs #10-#31 and is not current-mainlive evidence. - Live execution: an Azure, database, registry, pipeline, DNS, identity, network, cutover, rollback, or failback write
followed by relevant postchecks. No such evidence for the current
maincommit is checked into this repository or identified by the GitHub runs reviewed for this status.
Capability matrix
| Capability | Implementation state | Execution authority | Evidence on this baseline | Next gate |
|---|---|---|---|---|
| SSLZ Agent profile and launcher | Delivered for local Copilot CLI discovery from the default branch with greenfield, migration, and dual-cloud routing | Starts with local/read-only work; local artifact writes, live preview, and baseline deployment retain separate approval boundaries; provider-registration diagnosis/dry-run is exposed but live apply is blocked because its approval is not signature-authenticated | Static profile/launcher/journey contract test plus local CLI profile invocation; the profile’s broad execute capability is not a shell allowlist, while repository scripts retain the enforceable operation-specific boundaries | Add signature-authenticated provider approval; the GitHub.com custom-agent picker is not a supported launch path |
| Phase 0 contracts and result schemas | Delivered | None; schemas only | Local synthetic and hosted CI | Consumer-specific compatibility testing |
| Phase 1 account/topology preflight | Delivered read-only inspect path |
Azure reads under the operator identity; no writes | Local synthetic and hosted CI; no current-main tenant-read record retained here |
Authorized live read-only pilot with redacted evidence |
| Phases 2-3 workload, region, capacity, and PostgreSQL fallback planning | Delivered local planners | None; supplied JSON only | Local synthetic and hosted CI | Current workload, regional, quota, capacity, and owner evidence |
| Phase 4 IaC generation and preview | Delivered generator; preview is optional | Local file writes; Bicep what-if reads Azure; Terraform plan can acquire a remote-state backend lease; neither applies managed infrastructure | Local synthetic and hosted CI; historical live preview on the older PR #9 baseline only | Current-main Bicep what-if and Terraform plan in an approved test subscription |
| Phase 5 provider remediation | Delivered narrow writer | Separate single-use approval for one profile-allowlisted provider registration | Local synthetic and hosted CI; no current-main live registration evidence |
Approved nonproduction registration and readback |
| Phase 6 primary platform baseline | Delivered approval-gated Bicep/Terraform apply path and manual workflows | Signed single-use approval for one exact primary single-region-ready baseline on a protected runner |
Local synthetic and hosted CI; no current-main approved live apply/postcheck record |
Protected-runner nonproduction preview, approval, apply, postchecks, and rollback review |
| Phase 7 cool foundation and Container Apps cool profile | Planning artifacts delivered; execution disabled | None; Phase 6 rejects secondary and cool-infrastructure execution |
Local synthetic and hosted CI | Separate reviewed executor plus live activation, restore, RTO/RPO, traffic, and cleanup tests |
| PostgreSQL migration, rehearsal, and execution-contract planning | Planners and approval/evidence contracts delivered; executor absent | None; every planned operation remains unapplied | Local synthetic and hosted CI; no live database, rehearsal, cutover, or rollback evidence | Protected live evidence, separate migration authority, executor, rehearsal, cutover, and rollback validation |
| Container image and CI/CD migration planning | Planner delivered; execution disabled | None | Local synthetic and hosted CI; no live registry, image, pipeline, promotion, or rollback evidence | Protected live evidence, separate promotion authority, executor, and dual-publish/cutover test |
| Dual-cloud connectivity, DNS, identity, and egress planning | Planner delivered; execution disabled | None | Local synthetic and hosted CI; no live tunnel, route, DNS, federation, egress, or failback evidence | Protected live topology evidence, separate network authorities, executor, coexistence and failback tests |
| Program-lineage envelope and greenfield report v2 | Delivered local validator and canonical report contract | None; it preserves but does not expand baseline authority | Local synthetic and hosted CI | Protected external replay/trust store and a live-evidence report generated by an authorized system |
| Dual-cloud control-plane ownership and RACI | Planner, schemas, lineage stage, and canonical report binding delivered; execution disabled | None; every represented action requires separate future authority | Sanitized synthetic AWS, GCP, and generic fixtures; no live handoff evidence | Named live role mapping, protected handoff acceptance, rehearsed recovery, and capability-specific authorized executors |
| SaaS private endpoint runtime path | Bicep and Terraform example paths delivered by PR #27 | Direct operator IaC only; not an agent-approved workload path | Compiled/template and Terraform tests in hosted CI; no current-main live example deployment evidence |
Nonproduction deployment and end-to-end Container Apps-to-SQL/Redis DNS/connectivity test |
| Defender for Storage V2 | Default-off opt-in delivered by PR #28 | Direct operator IaC or an exact reviewed Phase 6 baseline decision | Compiled/template, Terraform, contract, and hosted CI validation; no current-main live opt-in evidence |
Workload and cost review, explicit approval, live tier readback, and budget monitoring |
The canonical
greenfield-journey-report.schema.json is version 2.0.0.
Its programLineage summary references the separately emitted envelope by exact envelopeDigest and
programIdentityDigest, and it separates baseline deployment readiness from PostgreSQL migration, container
image/CI/CD, and dual-cloud planning readiness. The checked-in report uses evidenceMode: "synthetic" and grants no
migration or dual-cloud execution authority.
Client and local validation limits
The shipped profile is for GitHub Copilot CLI. Claude Code and Codex do not have a maintained native adapter or client-specific acceptance suite in this repository. Reusing the documentation or scripts in another client does not give you the same discovery, tool permissions, or approval behavior.
The synthetic journey command writes and recreates .sslz/generated/greenfield-journey. It also creates and removes
the process-specific replay store .sslz/remediation-state/greenfield-${process.pid}. Approve both local targets and
use an isolated checkout if an earlier report must be preserved. Its fixed fixture timestamps and synthetic approvals
are test data, not current operational authority.
Copilot may request additional read-only confirmations for generated .bicepparam and .tfvars files. A successful
generation command does not prove that the agent read those files; report any blocked readback separately. Public Learn
retrieval also remains unverified if the runtime cannot expose the final response URL after redirects.
Direct operator boundary
The Quick Start and example az deployment ... create and terraform apply commands are direct operator IaC paths.
They do not invoke the startup-agent Phase 4 plan, Phase 5 remediation approval, or Phase 6 signed deployment approval.
This is an intentional compatibility path and does not bypass approvals inside the agent workflows. Operators using it own plan
review, credentials, permissions, state protection, change approval, validation, and rollback.
The repository must not contain tenant credentials, signing keys, approval identities, connection strings, billing documents, support transcripts, or live topology. Provision those through the protected runner, identity, secret, approval, billing, support, and evidence systems described by the relevant contracts.
Remaining human and live prerequisites
Before making broader claims, complete and retain sanitized evidence for:
- current tenant, subscription, billing-benefit, role, policy, provider, quota, capacity, and service-availability checks;
- security, architecture, IaC parity, cost, notification-recipient, and accountable-owner review;
- current-main Bicep what-if and Terraform plan against approved nonproduction targets;
- an approved Phase 5 registration where one is actually required;
- protected-runner Phase 6 deployment, postchecks, failure handling, and rollback review;
- workload health and private endpoint DNS/connectivity for the selected examples;
- measured restore, activation, RTO/RPO, traffic, and cleanup exercises before any Hot/Cool readiness claim;
- PostgreSQL rehearsal and migration, image dual-publish/promotion, and dual-cloud coexistence/cutover/failback under separate authorities before any execution claim.
Delivery history
The numbered phases are capability labels, not GitHub pull-request numbers. The original conceptual PR table in the implementation plan predates delivery. Actual merged delivery was:
| PR | Delivered scope |
|---|---|
| #4 | Startup agent contracts |
| #5 | Read-only startup preflight |
| #6 | Read-only workload planner |
| #7 | Read-only regional planner |
| #8 | Phase 4 IaC generation |
| #9 | Approved provider remediation |
| #10 | Phase 6 approved baseline integration |
| #11 | Readiness evidence binding |
| #13 | Deployment and review gate hardening |
| #14 | Execution-disabled cool foundation planning |
| #15 | Execution-disabled Container Apps cool profile |
| #16 | Startup billing/topology decisions |
| #17 | Defender workspace placement |
| #18 | Portable regional retry contracts |
| #19 | PostgreSQL regional fallback |
| #20 | AKS ingress contracts |
| #21 | Synthetic greenfield journey validation |
| #22 | PostgreSQL migration planner |
| #23 | PostgreSQL rehearsal planner |
| #24 | Approval-bound, execution-disabled PostgreSQL execution planner |
| #25 | Container image and CI/CD migration planner |
| #26 | Dual-cloud connectivity planner |
| #27 | SaaS private endpoint runtime path |
| #28 | Default-off Defender for Storage opt-in |
| #29 | Cross-program lineage and report v2 |
| #30 | Implementation and evidence status reconciliation |
| #31 | Dual-cloud control-plane ownership and RACI planning |
| #41 | SSLZ Agent and classic implementation unified on main |
PR #12 was closed without merge; its intended hardening scope was delivered through later merged work, beginning with PR #13.