Removing numbering from headings

Author: msdavidram

learn-pr/wwl/design-alm-process-ai-powered-business-solutions/includes/3-design-alm-process-copilot-studio-agents-connectors-actions.md

@@ -4,7 +4,7 @@ This unit guides solution architects through designing an Application Lifecycle
 
 Architects learn how to structure solution components into managed lifecycles, establish promotion and approval workflows, manage data and environment boundaries, and integrate development tooling—enabling a predictable, repeatable process that aligns with enterprise governance.
 
-## 1. ALM Foundations for Copilot Studio
+## ALM Foundations for Copilot Studio
 
 Copilot Studio solutions typically include:
 
@@ -30,7 +30,7 @@ A mature ALM process ensures:
 
 * Sustainable lifecycle for updates and deprecations
 
-## 2. Recommended Environment Strategy
+## Recommended Environment Strategy
 
 ### Establish at least three core environments:
 
@@ -64,11 +64,11 @@ A mature ALM process ensures:
 
      Iterate & Author      Test, Approve, QA       Support & Monitor
 
-## 3. ALM for Agents
+## ALM for Agents
 
 Agents should move through lifecycle stages with predictable governance:
 
-### 3.1 Development Stage
+### Development Stage
 
 * Draft agent scope, intents, and behaviors
 
@@ -78,7 +78,7 @@ Agents should move through lifecycle stages with predictable governance:
 
 * Test agent workflows with edge-case prompts
 
-### 3.2 Testing Stage
+### Testing Stage
 
 * Validate reasoning quality and output patterns
 
@@ -88,7 +88,7 @@ Agents should move through lifecycle stages with predictable governance:
 
 * Run regression tests on all agent topics
 
-### 3.3 Production Stage
+### Production Stage
 
 * Deploy via managed solutions
 
@@ -98,7 +98,7 @@ Agents should move through lifecycle stages with predictable governance:
 
 * Document change history
 
-## 4. ALM for Connectors
+## ALM for Connectors
 
 Connectors enable Copilot to interact with systems.
 
@@ -118,7 +118,7 @@ Connectors enable Copilot to interact with systems.
 
  Author → Validate Auth → Apply DLP → Approve Security → Publish to Prod
 
-## 5. ALM for Actions
+## ALM for Actions
 
 Actions represent executable steps triggered by agents.
 
@@ -134,17 +134,17 @@ Actions represent executable steps triggered by agents.
 
 * **Monitor** - Track success/failure rates and performance metrics
 
-## 6. Version Control and Release Management
+## Version Control and Release Management
 
 To maintain consistency and avoid configuration drift:
 
 ### Use source control
 
-Export solution packages and store them in source repositories
+* Export solution packages and store them in source repositories
 
-Track configuration changes for agents, connectors, and actions through a strong change management process.
+* Track configuration changes for agents, connectors, and actions through a strong change management process.
 
-Use Visual Studio Code for Copilot connector development where applicable
+* Use Visual Studio Code for Copilot connector development where applicable
 
 ### Adopt release cadence
 
@@ -156,7 +156,7 @@ Use Visual Studio Code for Copilot connector development where applicable
 
 * Change management plan for users
 
-## 7. Governance and Compliance Controls
+## Governance and Compliance Controls
 
 ALM must align with enterprise governance rules:
 
@@ -183,7 +183,7 @@ ALM must align with enterprise governance rules:
 * [✓] Risk & Safety Assessment Passed
 * [✓] Monitoring Enabled
 
-## 8. Monitoring and Continuous Improvement
+## Monitoring and Continuous Improvement
 
 ### Monitoring signals include:
 

learn-pr/wwl/design-alm-process-ai-powered-business-solutions/includes/5-design-alm-process-custom-ai-models.md

@@ -4,7 +4,7 @@ This unit provides solution architects with a structured, enterprise-grade Appli
 
 Custom AI models introduce unique ALM challenges such as data drift, model drift, regulatory alignment, and high-impact deployment risks. This unit provides architects with an actionable framework for governing model evolution from ideation through retirement.
 
-## 1. ALM Foundations for Custom AI Models
+## ALM Foundations for Custom AI Models
 
 ### A strong ALM process ensures:
 
@@ -16,7 +16,7 @@ Custom AI models introduce unique ALM challenges such as data drift, model drift
 
 * **Operational Readiness**: Runtime monitoring, governance logs, and rollback plans ensure business resilience.
 
-## 2. Environment Strategy for Model Development
+## Environment Strategy for Model Development
 
 Establishing a multi-environment design prevents configuration drift and ensures safe promotions.
 
@@ -36,35 +36,35 @@ Establishing a multi-environment design prevents configuration drift and ensures
 
 → [Production]
 
-## 3. ALM Lifecycle for Custom AI Models
+## ALM Lifecycle for Custom AI Models
 
 The lifecycle includes the following stages:
 
-### 1. Plan & Design
+### Plan & Design
 
 * Define business use case, success criteria, constraints.
 
 * Identify necessary data sources, governance rules, and privacy boundaries.
 
 * Document intended model behavior, limitations, failure paths.
 
-### 2. Data Preparation
+### Data Preparation
 
-*  Build data contracts and schema standards.
+* Build data contracts and schema standards.
 
-*  Establish curated datasets and "golden" evaluation datasets.
+* Establish curated datasets and "golden" evaluation datasets.
 
-*  Use versioned data pipelines to prevent drift and ensure reproducibility.
+* Use versioned data pipelines to prevent drift and ensure reproducibility.
 
-### 3. Model Development
+### Model Development
 
-*  Build, fine-tune, or incorporate "bring your own model" (BYOM) components.
+* Build, fine-tune, or incorporate "bring your own model" (BYOM) components.
 
 * Apply responsible AI requirements such as fairness, clarity, consistency, and safe response patterns.
 
 * Maintain metadata: hyperparameters, training data versions, environment configuration snapshots.
 
-### 4. Evaluation & Approval
+### Evaluation & Approval
 
 * Validate accuracy, relevance, reliability, and failure handling.
 
@@ -74,23 +74,23 @@ The lifecycle includes the following stages:
 
 * Produce a **Model Card** containing metrics, constraints, and recommended usage boundaries.
 
-### 5. Deployment
+### Deployment
 
 * Promote model via managed deployment artifacts.
 
 * Apply model registries with version locking and rollback paths.
 
 * Enforce access control, encryption, and runtime audit logging.
 
-### 6. Monitor & Optimize
+### Monitor & Optimize
 
 * Track telemetry: latency, error frequency, safety blocks, user satisfaction signals.
 
 * Detect model drift (output deviates from expected performance).
 
 * Trigger retraining cycles with updated data.
 
-### 7. Retirement
+### Retirement
 
 When model no longer meets accuracy, safety, cost, or business expectations: 
 
@@ -100,7 +100,7 @@ When model no longer meets accuracy, safety, cost, or business expectations:
 
 * Document transition plan to the next model version.
 
-## 4. Promotion Gates for Enterprise Readiness
+## Promotion Gates for Enterprise Readiness
 
 Promotion gates ensure only compliant, validated models move forward.
 
@@ -124,19 +124,19 @@ Promotion gates ensure only compliant, validated models move forward.
 
 ### Text Visual: Gate Checklist
 
-* Data quality validated
+* [] Data quality validated
 
-* Evaluation metrics achieved
+* [] Evaluation metrics achieved
 
-* Safety checks completed
+* [] Safety checks completed
 
-* Model Card produced
+* [] Model Card produced
 
-* Governance approvals obtained
+* [] Governance approvals obtained
 
-* Rollback plan documented
+* [] Rollback plan documented
 
-## 5. Governance and Compliance Requirements
+## Governance and Compliance Requirements
 
 ### Solution architects must ensure:
 
@@ -150,7 +150,7 @@ Promotion gates ensure only compliant, validated models move forward.
 
 * Transparent audit trails for every deployment.
 
-## 6. Monitoring and Drift Management
+## Monitoring and Drift Management
 
 ### Effective monitoring requires:
 
@@ -174,7 +174,7 @@ Cost          ●●●○○
 
 Consistency   ●●●●○
 
-## 7. Architect Responsibilities Checklist
+## Architect Responsibilities Checklist
 
 * Define model development standards.