feat: Oracle CRM Page, Synthetic Client Data and Live Snapshot when hitting emotion hotpoint

.Agent Context/Sprint 1/Templates/07 - Mission Contracts and JSON Schemas Template.md

@@ -0,0 +1,62 @@
+# Mission Contracts and JSON Schemas Blueprint
+
+**Date:** [YYYY-MM-DD]  
+**Status:** [Draft | In Review | Approved]  
+**Owner:** [Name]  
+**Reviewers:** [Names]  
+**Scope:** [Mission family or contract layer]  
+**Purpose:** Define the internal artifact contracts, schema boundaries, versioning rules, and validation strategy.
+
+## 1. Purpose
+
+State what contract system is being defined.
+
+## 2. Contract Design Principles
+
+Describe the rules governing schema design.
+
+## 3. Canonical Artifact Set
+
+List every artifact that exists in this runtime.
+
+## 4. Schema Rules
+
+Define:
+
+- required metadata
+- versioning model
+- identity keys
+- producer and consumer rules
+
+## 5. Artifact Definitions
+
+For each artifact, include:
+
+- purpose
+- required fields
+- example JSON shape
+- validation rules
+
+## 6. Storage Mapping
+
+Map artifacts to tables, files, or services.
+
+## 7. Validation Strategy
+
+State how validation happens in:
+
+- service layer
+- root layer
+- persistence layer
+
+## 8. Compatibility Strategy
+
+Define how future schema evolution will be handled.
+
+## 9. Implementation Order
+
+State the correct order for introducing the contracts.
+
+## 10. Bottom Line
+
+Summarize the contract spine.