89114ac126
Added strategically positioned question addressing governance gaps in Copilot deployments for client correspondence: Question (ID: 2): "We're deploying Copilot across our organisation for client correspondence—what governance gaps should concern us, and how does Tractatus address them?" Answer highlights: - Liability exposure: unauthorised commitments, confidentiality breaches - Regulatory compliance gaps: GDPR Article 22, SOC 2 CC2.1 - Tractatus as governance layer above Copilot - Compliance-grade audit trails - Phased implementation path (observation → soft → hard enforcement) - Board-ready cost-benefit analysis - Architectural vs aspirational governance distinction Target audience: General Counsel, AI Vice President, Executive Leadership Placement: Second question in Leader section (prominent positioning) Keywords: copilot, microsoft, client, correspondence, deployment, governance, risk, liability, compliance, audit, general counsel, legal Version: 1.0.9 → 1.1.0 Files modified: - public/js/faq.js (new question ~1,400 words) - public/service-worker.js (version bump) - public/version.json (changelog update) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
11 lines
345 B
JSON
11 lines
345 B
JSON
{
|
|
"version": "1.1.0",
|
|
"buildDate": "2025-10-14T01:15:00Z",
|
|
"changelog": [
|
|
"NEW: Copilot governance Q&A for General Counsel and AI VPs",
|
|
"Addresses liability exposure in client correspondence deployments",
|
|
"Covers compliance gaps (GDPR, SOC 2) and audit trail requirements"
|
|
],
|
|
"forceUpdate": true,
|
|
"minVersion": "1.1.0"
|
|
}
|