diff --git a/ASG_Framework.md b/ASG_Framework.md
index a5fcdcf..cc5eb41 100644
--- a/ASG_Framework.md
+++ b/ASG_Framework.md
@@ -450,45 +450,94 @@ Each documentation artifact has associated KPIs. Track these to ensure quality:
 # PRD: Feature Name
 
 ## 1. Business Context & Success Metrics
-- Business Goal
-- User Stories (with acceptance criteria)
-- **Functional Requirements (FR)**: List each FR ID with its corresponding KPI target
-- **Non-Functional Requirements (NFR)**: Define quality/constraint requirements (e.g., "Support 10K TPS", "99.9% uptime", "TLS 1.3+")
-- **Success Metrics (KPIs)**: Define measurable targets that validate NFRs (e.g., "95th percentile latency <200ms", "MTTR <10min", "100% TLS 1.3")
+
+### Business Goal
+[Clear statement of the business problem being solved and why]
+
+### User Stories
+- **US-XXX**: [User story with clear action and value]
+- *Example: US-001 - As a wine retailer customer, I want to access the sommpanion chat so that I can get wine-related help quickly*
+
+### KPIs & Targets
+- **KPI-XXX**: [Measurable target with validation reference]
+- *Example: KPI-001 - 95% of chat messages receive responses within 3 seconds (validates FR-001)*
 
 ## 2. Technical Boundaries
-- In Scope
-- Out of Scope
-- Dependencies (e.g., "Requires Stripe API v2023-08")
+
+### In Scope
+[List features and capabilities included in this release]
+
+### Out of Scope
+[List features explicitly excluded from this release]
+
+### Dependencies
+[List external services, APIs, or systems this feature depends on]
+
+### Deployment Constraints
+- **NFR-XXX**: [Deployment-specific requirement]
+- *Example: NFR-501 - System shall be deployed to MicroK8s cluster with relative URL support*
 
 ## 3. Functional Requirements (FR)
-- **FR-XXX**: [Requirement ID] - [Clear, testable functional requirement]
-- **FR-XXX**: [Requirement ID] - [Clear, testable functional requirement]
-- *Example: FR-001 - System shall allow users to invite teammates via email address*
+
+### FR-XXX: [Requirement Title]
+[Detailed description of what the system shall do]
+- [Specific behavior 1]
+- [Specific behavior 2]
+- [Specific behavior 3]
+
+**Traceability**: US-XXX, US-XXX
+
+### FR-XXX: [Requirement Title]
+[Detailed description of what the system shall do]
+- [Specific behavior 1]
+
+**Traceability**: US-XXX
 
 ## 4. Non-Functional Requirements (NFRs)
+
 ### 4.1 Performance & Scalability
-- [e.g., Support 10K TPS, scale horizontally to 100 nodes]
+- **NFR-XXX**: [Performance requirement with measurable threshold]
+- *Example: NFR-101 - Support page shall load in <1 second on 3G networks*
 
 ### 4.2 Availability & Reliability
-- [e.g., SLO: 99.9% monthly uptime, MTTR < 10min]
+- **NFR-XXX**: [Reliability requirement]
+- *Example: NFR-201 - Chat functionality shall have 99.9% monthly uptime*
 
 ### 4.3 Privacy & Security
-- Data Classification: [e.g., PII, PHI]
-- Threat Model Outcomes: [e.g., "Mitigates replay attacks via nonce + timestamp"]
-- Auth/Z Expectations: [e.g., RBAC with 3 roles: viewer, editor, admin]
-- Encryption: [e.g., TLS 1.3+, AES-256 at rest]
-- Compliance: [e.g., GDPR Art. 32, SOC2 Type II]
+- **Data Classification**: [e.g., PII, PHI, commercial data]
+- **Encryption**: [e.g., TLS 1.3+, AES-256 at rest]
+- **Authentication**: [e.g., Session-based, OAuth2, API keys]
+- **Compliance**: [e.g., GDPR Art. 32, SOC2 Type II, HIPAA]
 
 ### 4.4 Observability & Telemetry
-- Required Logs: [e.g., `user_id`, `request_id`, `status`, `latency_ms`]
-- Critical Metrics: [e.g., `auth_failures_total`, `api_latency_seconds{quantile=0.99}`]
-- Tracing: [e.g., Zipkin/B3 propagation, 10% sampling]
-- Alerting: [e.g., `auth_failure_rate > 5%/min` triggers PagerDuty]
-- Retention: [e.g., Logs: 30 days, Metrics: 1 year]
+- **Required Logs**: [e.g., `session_id`, `user_id`, `message_id`, `event_type`, `timestamp`, `latency_ms`]
+- **Critical Metrics**:
+  - `metric_name_1`
+  - `metric_name_2`
+- **Tracing**: [e.g., Zipkin/B3 propagation, 10% sampling]
+- **Alerting**: [e.g., `chat_delivery_rate < 95%` triggers PagerDuty]
+- **Retention**: [e.g., Logs: 30 days, Metrics: 1 year]
 
 ## 5. Acceptance Conditions
-- [List verifiable conditions for sign-off, including validation gates]
+
+- [ ] **FR-XXX**: [Verifiable acceptance condition]
+- [ ] **FR-XXX**: [Verifiable acceptance condition]
+- [ ] **NFR-XXX**: [Verifiable acceptance condition]
+- *Example: [ ] FR-001: Sommpanion landing page renders with all required elements*
+
+## 6. Requirements Traceability Matrix
+
+| Requirement ID | Description | Implementation File | Test File |
+|----------------|-------------|---------------------|-----------|
+| FR-XXX | [Brief description] | `path/to/file.ext` | `tests/file.spec.js` |
+| NFR-XXX | [Brief description] | `path/to/file.ext` | `tests/file.spec.js` |
+
+**Notes**:
+- Functional Requirements (FR) define what the system shall do
+- Non-Functional Requirements (NFR) define system qualities (performance, availability, security, etc.)
+- KPIs are measurable targets that validate whether requirements were met post-deployment
+- Each requirement must include a clear requirement ID for traceability
+- All acceptance conditions must be verifiable through testing or manual inspection
 ```
 
 ### Solution Design Template