Vision to Production — EHR¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
This page applies the Vision-to-Production workflow to Electronic health record (example page). The steps are the Factory's reference run flow; the right-hand columns say what is specific to this vertical.
| # | Step | Platform | Specific to EHR |
|---|---|---|---|
| 1 | Run submitted with the prompt and constraints | Control plane | residency tenant-region (restricted data); edition ManagedPlus |
| 2 | Policy and snapshot resolved; budget reserved | Control plane, Governance | — |
| 3 | Vision Blueprint produced and validated | Agent Mesh, Template & Library | A clinic network needs patient records, scheduling and referrals that satisfy health-data rules and work in Hebrew and English. |
| 4 | Product plan and personas | Agent Mesh | A clinical record with patients, encounters, scheduling, referrals and prescriptions under restricted-data controls, RTL-first. |
| 5 | Service Blueprint: contexts, aggregates, events | Agent Mesh, Template & Library | Patients, Encounters, Scheduling, Referrals |
| 6 | Context map and domain models derived | Template & Library (BC-02) | 4 contexts |
| 7 | Security, database, integration blueprints | Agent Mesh | database, security |
| 8 | UX and frontend blueprints | Agent Mesh, UX track | ux, frontend, localization |
| 9 | Recipe proposed from the context map | Template & Library (BC-15) | Microservice ×4, API gateway, Clinic shell, Identity |
| 10 | Recipe validated against manifests and the compatibility matrix | Template & Library (BC-14) | templates: connectsoft-microservice, connectsoft-apigateway, connectsoft-blazor-saas-shell, connectsoft-identity |
| 11 | Recipe approved | Control plane (approval) | Requester or Reviewer per policy |
| 12 | Generation run: scaffold in the sandbox | Agent Mesh, Tools & MCP | Vision Architect Agent, Security Architect Agent, Backend Developer Agent, UX Designer Agent, Frontend Developer Agent, QA Agent, Compliance Officer Agent |
| 13 | Tests and validators | Tools & MCP, Knowledge (artifacts) | test blueprint thresholds |
| 14 | Change proposal (branch, pull request) | DevOps / GitOps (BC-23) | shared-write class |
| 15 | Review and merge in the system of record | DevOps / GitOps | human review |
| 16 | Pipeline run with typed results | DevOps / GitOps | build, tests, scan, SBOM, images |
| 17 | Release assembled with evidence | DevOps / GitOps (BC-24) | immutable release |
| 18 | Evaluation of agent-generated assets | Observability (BC-22) | regression gates (D32) |
| 19 | Promotion to staging; verification | DevOps / GitOps, Runtime Cloud | — |
| 20 | Production promotion with approval | DevOps / GitOps (production class) | separation of duties |
| 21 | Provisioning applied; descriptor published | Runtime Cloud (BC-25), the product | Pulumi stacks; GW-07 |
| 22 | Managed-operations handover acknowledged | the product owner | ManagedPlus |
| 23 | Fleet onboarding; objectives; probes | Product Fleet Operations (BC-35) | ManagedPlus with restricted-data residency; the reference lineage of DerechHaLev applies. |
| 24 | Feedback, learning proposals, re-scaffold on template releases | Observability (BC-22), Fleet (BC-36) | continuous |