{"slug":"architecture/CAPABILITY_FIRST_ARCHITECTURE","title":"IntegrateWise: Capability-First Operational Architecture","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/CAPABILITY_FIRST_ARCHITECTURE.mdx","bytes":24225,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n\n> **Tier C — Historical.** This document is a point-in-time snapshot preserved for reference. For current architecture, see [CANONICAL_PLATFORM_ARCHITECTURE.md](../architecture/CANONICAL_PLATFORM_ARCHITECTURE.md).\n\n## The Architectural Shift\n\n### From Departments to Capabilities\n\n**Wrong way (what I built):**\n```\nDepartments → Workbenches → Cross-Domain Context\nSales Workbench / Finance Workbench / CSM Workbench\nProblem: Still fragmented by org structure\nProblem: Capabilities scattered across workbenches\nProblem: User thinks \"which app?\" instead of \"what do I need to do?\"\n```\n\n**Right way (what you're proposing):**\n```\nHuman Goal → Operational Capability → Entity Assembly → AI Collaboration\n\"I have a meeting in 20 min\" → Prepare Meeting → Context synthesis → AI brief\nProblem: SOLVED. User thinks \"what do I do?\" AI handles everything\n```\n\n## Foundation: 8 Architectural Layers\n\n### Layer 1: Identity\n**Who is acting?**\n- User profile\n- Role (Sales, CSM, Finance, Engineer)\n- Skills\n- Permissions\n- Digital Twin (AI context about this person)\n- Working hours, location, availability\n- Organizational relationships\n\nAI needs this to know: \"Should this person be involved? Do they have access? What's their context?\"\n\n### Layer 2: Organization\n**Why do we exist?**\n- Company mission/vision\n- OKRs (Objectives & Key Results)\n- Departments & Functions\n- Policies & Approval Rules\n- Organizational Structure\n- Governance Framework\n\nAI needs this to know: \"Why is this work important? What rules apply?\"\n\n### Layer 3: Operational Memory (The Spine)\n**What do we know?**\n- Customers\n- Accounts\n- Contacts\n- Opportunities\n- Tickets\n- Projects\n- Documents\n- Products\n- Contracts\n- Meetings\n- Emails\n- Knowledge\n- Decisions\n\nThis is your Spine. **Canonical source of truth.**\n\n### Layer 4: Execution\n**What must happen?**\n- Decisions (to be made)\n- Tasks (to be done)\n- Follow-ups (pending)\n- Reviews (scheduled)\n- Approvals (required)\n- Risks (to be mitigated)\n- Escalations (needed)\n- Deadlines (critical)\n- Handoffs (between teams)\n- Commitments (made and tracked)\n\n**This layer is where most CRMs fail.** They store records but don't model work.\n\nExample: Customer health dropped to 30\n- Don't just display it\n- AI should propose:\n  - Notify CSM\n  - Create urgent task\n  - Draft email\n  - Schedule emergency call\n  - Alert manager\n  - Update risk forecast\n  - Suggest win-back strategy\n\n### Layer 5: Collaboration\n**Who is working together?**\n- Conversations (emails, Slack, Teams, WhatsApp)\n- Comments & Mentions\n- Meetings & Voice Notes\n- Decisions & Approvals\n- Async updates\n- Real-time handoffs\n\nThese become organizational memory.\n\n### Layer 6: Intelligence\n**What should happen next?**\n- Observations (anomalies, patterns)\n- Predictions (what might happen)\n- Recommendations (what to do)\n- Summaries (what matters)\n- Simulations (what if we...)\n- Alternatives (other options)\n- Automation Proposals (what could be automatic)\n\n### Layer 7: Governance\n**Can we do this?**\nBefore AI executes:\n- Policy check (allowed?)\n- Approval chain (who signs off?)\n- Compliance (regulations met?)\n- Audit trail (evidence?)\n- Lineage (who changed what?)\n- Ownership (who's responsible?)\n\n### Layer 8: Learning & Continuity\n**What did we learn?**\n```\nObservation\n    ↓\nDecision\n    ↓\nExecution\n    ↓\nOutcome\n    ↓\nEvidence Captured\n    ↓\nLearning Extracted\n    ↓\nFuture Recommendation Improved\n```\n\nEvery completed action becomes organizational memory.\n\n---\n\n## Living Operational Objects\n\n### Instead of Database Records\n\n**Traditional approach:**\n```\nCustomer\n- Name: Acme Corp\n- Email: contact@acme.com\n- Status: Active\n```\n\n**Living operational approach:**\n\n```\nCustomer: Acme Corp\n├── Identity\n│   ├── Legal name\n│   ├── Company type\n│   ├── Industry\n│   ├── Size\n│   ├── Location\n│   └── Tax ID\n│\n├── Relationships\n│   ├── Contacts (3)\n│   ├── Deals (2 active, 1 closed)\n│   ├── Invoices (12)\n│   ├── Support tickets (5)\n│   ├── Projects (1)\n│   ├── Contracts (2)\n│   ├── Products (4 using)\n│   └── Success plans (1)\n│\n├── Operational State\n│   ├── Health score: 72\n│   ├── Churn risk: Medium\n│   ├── Renewal date: Mar 2025\n│   ├── MRR: $8,200\n│   ├── NRR contribution: 12%\n│   ├── Open risks: 2\n│   └── Active projects: 1\n│\n├── Timeline\n│   ├── Signed: Jan 2023\n│   ├── Meetings: 12 this quarter\n│   ├── Last contact: 3 days ago\n│   ├── Upcoming renewal: 45 days\n│   ├── Recent escalations: 1\n│   └── Payment history: Excellent\n│\n├── Tasks\n│   ├── Schedule QBR (due Friday)\n│   ├── Follow up on feature request (due Wed)\n│   ├── Collect renewal signatures (urgent)\n│   └── Resolve open support ticket (due Mon)\n│\n├── Decisions\n│   ├── Expand to new business unit? (TBD)\n│   ├── Offer discount? (pending review)\n│   ├── Escalate to CEO? (yes, risk flag)\n│   └── Approval status: Under review\n│\n├── Conversations\n│   ├── Emails: 24 this month\n│   ├── Slack threads: 8\n│   ├── Meetings: 3 this month\n│   ├── Call notes: Latest from 3 days ago\n│   └── Action items: 3 open\n│\n├── Documents\n│   ├── Contract: SLA v2.0\n│   ├── Success plan: FY2025\n│   ├── Executive summary: Updated quarterly\n│   └── Meeting notes: 12 recent\n│\n├── Intelligence (Digital Twin)\n│   ├── CTO prefers technical discussions\n│   ├── Finance asks for invoice 5 days early\n│   ├── Never responds on Friday\n│   ├── Budget cycle: Q4 planning\n│   ├── Recent pain point: Integration complexity\n│   ├── Expansion opportunity: 2-3x logo growth likely\n│   ├── Churn signals: declining usage + escalation\n│   └── Next best action: Proactive executive call\n│\n├── Memory (Learning)\n│   ├── This customer historically churns after discount\n│   ├── CTO relationship critical; CFO doesn't care\n│   ├── Security concerns slower decision-making by 30 days\n│   ├── Expansion requires Executive sponsorship\n│   ├── Support responsiveness drives renewal\n│   └── Best timing: Tuesday 10am PST\n│\n├── Governance\n│   ├── Owner: Sarah (CSM)\n│   ├── Secondary: Tom (Account Exec)\n│   ├── Approval required for: discount >10%, expansion\n│   ├── Escalation path: Sarah → VP CS → CEO\n│   ├── Data classification: Confidential\n│   └── Audit status: Last reviewed quarterly\n│\n├── Health\n│   ├── Overall: Yellow (trending down)\n│   ├── Engagement: Good\n│   ├── Support: Excellent\n│   ├── Finance: On track\n│   ├── Product usage: Declining 5% MoM\n│   ├── Relationship: Strong, but CTO leaving next month\n│   └── Risk score: 6/10 (moderate)\n│\n├── Signals (Live from connected systems)\n│   ├── GitHub: Deployment activity dropped\n│   ├── Stripe: Failed payment attempt (retried, succeeded)\n│   ├── Support: Escalation opened\n│   ├── Calendar: No meeting scheduled for 30 days\n│   ├── Email: No outbound from us in 2 weeks\n│   └── Slack: One mention (support thread)\n│\n├── Automation\n│   ├── Email on risk escalation: Ready\n│   ├── Slack notification to CSM: Ready\n│   ├── Calendar reminder for renewal: Ready\n│   ├── Financial forecast update: Ready\n│   ├── Alert finance on churn risk: Ready\n│   └── Trigger expansion workflow: Ready\n│\n├── Twin Context (What AI knows)\n│   ├── Buying process: 120 days\n│   ├── Decision style: Consensus-driven\n│   ├── Price sensitivity: Moderate\n│   ├── Support dependency: High\n│   ├── Expansion timing: Post-renewal\n│   ├── Communication channel: Email (CTO), Slack (Team)\n│   └── Relationships matter: Critical\n│\n├── Capabilities (Available Actions)\n│   ├── Observe() → Real-time health status\n│   ├── Understand() → Context + relationships + signals\n│   ├── Analyze() → Trend analysis + risk assessment\n│   ├── Summarize() → Executive brief\n│   ├── Recommend() → Next best action\n│   ├── Predict() → Renewal likelihood, churn risk\n│   ├── Collaborate() → Surface to right team member\n│   ├── Approve() → Route for signature/decision\n│   ├── Execute() → Schedule, email, task, escalate\n│   ├── Learn() → Extract patterns from this account\n│   ├── Remember() → Store learnings for future\n│   ├── Explain() → Why did we recommend this?\n│   ├── Audit() → Show decision trail\n│   ├── Govern() → Policy check before action\n│   ├── Notify() → Alert stakeholders\n│   └── Automate() → Propose what could be automatic\n│\n└── Metrics & KPIs\n    ├── ARR: $98,400\n    ├── NRR contribution: 12%\n    ├── Health score: 72 (target: 80+)\n    ├── Engagement: 8/10\n    ├── Expansion potential: $30k\n    ├── Churn risk: 6/10\n    ├── Renewal likelihood: 85%\n    ├── Support satisfaction: 4.8/5\n    ├── Time to response: 2h avg\n    └── QBR completion: On track\n```\n\nThis is a **living, multidimensional operational object**, not a flat database record.\n\n---\n\n## 200+ Operational Capabilities\n\nNot departments. Not screens. Capabilities.\n\n### Revenue Domain (12 Capabilities)\n1. Find Prospect → Apollo/LinkedIn data assembled\n2. Research Account → Company intelligence synthesized\n3. Qualify Opportunity → Fit assessment with AI recommendation\n4. Understand Decision Makers → Stakeholder analysis + influence mapping\n5. Schedule Meeting → Calendar + context + suggested agenda\n6. Run Meeting → Real-time notes + next steps capture\n7. Create Proposal → Data-driven positioning + pricing\n8. Negotiate Deal → Policy check + approval chain + alternatives\n9. Close Deal → Signature + revenue recognition + handoff coordination\n10. Onboard Customer → Project creation + success plan + communication\n11. Renew Customer → Risk assessment + pricing + messaging\n12. Expand Account → Opportunity identification + cross-sell positioning\n\n### Customer Success Domain (8 Capabilities)\n1. Monitor Health → Real-time scoring + signal detection\n2. Prepare Meeting → Context synthesis (usage, issues, renewal, risks)\n3. Review Adoption → Feature usage + benchmarks + recommendations\n4. Detect Risk → Early warning + suggested interventions\n5. Build Success Plan → Goal-setting + milestone tracking\n6. Coordinate Internally → Cross-team alignment + task management\n7. Prepare QBR → Data compilation + talking points + recommendations\n8. Drive Renewal → Risk assessment + messaging + terms + approval\n\n### Support Domain (7 Capabilities)\n1. Triage Ticket → Urgency + routing + suggested response\n2. Diagnose Issue → Root cause analysis + knowledge base search\n3. Resolve Ticket → Solution + customer communication\n4. Escalate Risk → Severity assessment + stakeholder notification\n5. Identify Patterns → Recurring issues + engineering feedback\n6. Prepare For Meeting → Customer context + issue history + sentiment\n7. Close & Learn → Resolution capture + knowledge update\n\n### Finance Domain (9 Capabilities)\n1. Invoice → Auto-generation + payment terms + customer data\n2. Track Payment → Aging report + risk flagging + collection strategy\n3. Collect Payment → Outreach + approval chain for discounts + alternatives\n4. Forecast Revenue → AI prediction + scenario modeling + confidence scoring\n5. Budget → OKR alignment + headcount planning + approval workflow\n6. Manage Expense → Policy check + approval routing + reimbursement\n7. Process Payroll → Headcount + hours + deductions + compliance\n8. Recognize Revenue → Spine data + accounting rules + audit trail\n9. Tax Planning → Compliance check + quarterly estimated tax + reporting\n\n### Engineering Domain (8 Capabilities)\n1. Plan Sprint → Backlog prioritization + capacity planning + commitment\n2. Review PR → Code quality + architecture check + recommendation\n3. Deploy Release → Testing status + rollback plan + customer impact\n4. Monitor Incident → Severity + customer impact + team coordination\n5. Post-Incident Review → Root cause + learning capture + prevention\n6. Architecture Review → Technical debt assessment + recommendation\n7. Plan Roadmap → Feature prioritization + customer requests + strategy alignment\n8. Manage Dependencies → Upstream/downstream coordination + release planning\n\n### People Domain (7 Capabilities)\n1. Plan Hire → Requisition + budget → role definition → job posting\n2. Recruit → Candidate sourcing + screening + interview coordination\n3. Onboard → Documentation → training → team introduction\n4. Manage Performance → Goal setting → feedback → review → rating\n5. Develop Talent → Learning plans → skill gaps → promotion path\n6. Offboard → Knowledge transfer → access removal → final payments\n7. Manage Workload → Capacity → burnout detection → team rebalancing\n\n### Operations Domain (9 Capabilities)\n1. Vendor Management → Contract → payments → performance → renewal\n2. Procurement → Requisition → approval → purchase → receipt → payment\n3. Facilities → Real estate → equipment → booking → maintenance\n4. Security & Compliance → Audit → policy → training → attestation\n5. Knowledge Management → Documentation → search → updates → archival\n6. Process Improvement → Identify bottleneck → design → test → rollout\n7. Policy Management → Create → publish → training → audit\n8. Risk Management → Identify → assess → mitigate → monitor\n9. Data Governance → Classification → retention → deletion → privacy\n\n### And more...\n\n---\n\n## The Execution Lifecycle\n\nEvery capability follows the same pattern:\n\n```\nUser Goal\n    ↓\nAI Context Assembly\n    (pulls from Spine, connected systems, shared memory)\n    ↓\nAI Shared Understanding\n    (builds the situation)\n    ↓\nDigital Twin Analysis\n    (applies experience, patterns, rules)\n    ↓\nAI Recommendations\n    (what to do + why + expected outcome)\n    ↓\nHuman Decision\n    (judgment call, approval, override)\n    ↓\nAI Execution\n    (implements, coordinates, notifies)\n    ↓\nOutcome Captured\n    (what actually happened)\n    ↓\nLearning Extracted\n    (patterns, predictions, improvements)\n    ↓\nMemory Updated\n    (becomes shared knowledge)\n    ↓\nFuture Recommendation Improved\n    (AI gets smarter)\n```\n\n---\n\n## Example: \"Prepare Customer Meeting\"\n\n### User Goal\nCSM thinks: \"I have a meeting in 20 minutes. What do I need to know?\"\n\n### AI Context Assembly\nAI automatically:\n- Reads CRM: Account profile, health score, renewal date, previous calls\n- Reads Zendesk: Open tickets, satisfaction, escalations\n- Reads Slack: Recent conversations, team mentions\n- Reads Calendar: Previous meetings, agenda context\n- Reads Contracts: Terms, renewal coming, expansion potential\n- Reads Stripe: MRR, payment history, failed charges\n- Reads GitHub: Product usage patterns, feature adoption\n- Reads Email: Recent communication, tone, decision-making timeline\n- Reads Roadmap: Customer has been asking for feature X (launching next week)\n- Reads Incident: Critical issue 2 weeks ago, now resolved\n\n### Digital Twin Understanding\nAI understands:\n- CTO drives product decisions, prefers data\n- CFO controls budget, approves after quarter-end\n- \"Never replies on Friday\" (pattern from history)\n- Post-incident customer is sensitive, needs reassurance\n- Expansion opportunity: They use 40% of platform, could upsell\n- Churn risk: 3 (mild) due to one critical incident\n- Decision timeline: Budget cycle next month\n\n### AI Recommendations\n\n**Meeting Brief**\n- Health score: 78 (good, was 72 post-incident)\n- Status: Stable, trending up\n- Sentiment: Resolved, but cautious\n\n**Risks**\n- Recent critical incident (2 weeks ago, now fixed)\n- Recommendation: Lead with incident resolution confidence\n\n**Expansion Opportunities**\n- Currently using 40% of platform\n- 3 upsell paths available\n- CTO interested in data features (best fit)\n- Timing: Post-budget cycle (next month) for budget approval\n\n**Support Escalations**\n- 3 open tickets (1 urgent, 2 normal)\n- All less than 48h old\n- Resolution in progress\n\n**Renewal Status**\n- Contract renews: April 2025 (4 months away)\n- Current MRR: $8,200\n- Expansion potential: +$3,000/mo if upsell succeeds\n\n**Suggested Agenda**\n1. How is the incident resolution going? (Reassurance)\n2. New feature roadmap item they requested ships next week (excitement)\n3. Three expansion options to explore (growth)\n4. Timeline for next steps (decision)\n\n**Suggested Questions**\n- \"How are your teams feeling after that incident?\"\n- \"We're launching the feature you requested—can we show you next week?\"\n- \"We've identified three ways to expand the product—which resonates?\"\n- \"If you wanted to expand, when would budget be available?\"\n\n**Next Steps to Suggest**\n- Follow-up call after incident fully validated\n- Demo of new feature (next week)\n- Business case for expansion (if interest)\n- Budget planning conversation (next month)\n\n### Human Decision\nCSM reads brief.\n- Adjusts: \"Skip incident—they've moved on\"\n- Adjusts: \"Emphasize support quality instead\"\n- Agrees: \"Expansion conversation makes sense, focus on data features\"\n\n### AI Execution\nAI automatically:\n- Updates call notes template with agreed agenda\n- Sends meeting calendar invite reminder (to participants)\n- Drafts follow-up email template (CSM will personalize)\n- Sets 3-day follow-up reminder for CSM\n- Alerts Sales: \"Expansion discussion happening, deal potential $3k/mo\"\n- Pulls product demo link for new feature\n- Creates task: \"Send expansion business case by Friday\"\n\n### Outcome Captured\nMeeting happens. CSM logs:\n- Notes: CTO very interested in data features, CFO will review expansion in budget cycle\n- Actions: Send product demo, schedule follow-up in 2 weeks\n- Customer sentiment: Positive, confident in vendor\n\n### Learning Extracted\nAI learns:\n- Post-incident: Customer moves on quickly (pattern for next time)\n- Expansion timing: Wait until budget cycle (for this customer)\n- Communication style: Data and efficiency matter (CTO preference)\n- Success signal: Feature interest + budget cycle awareness = high close rate\n\n### Memory Updated\nSpine + Twin Context:\n- \"Post-incident customer: Focus on resolution confidence + forward momentum\"\n- \"Expansion window: Next budget cycle (post-quarter)\"\n- \"CTO data interest: Strong expansion signal\"\n- \"Demo after incident: High engagement (note for future)\"\n\n### Future Recommendation Improved\nNext time CSM meets with this customer:\n- AI recommends: \"Last time, data features resonated strongly\"\n- AI recommends: \"Budget cycle timeline matters—wait for May planning\"\n- AI suggests: \"Demo new features early (drives engagement)\"\n\n---\n\n## Every Entity Has a Digital Twin\n\nNot just users. Not just sales.\n\nExamples:\n\n### Customer Twin\n- Understands buying behavior\n- Predicts churn probability\n- Identifies expansion opportunities\n- Learns communication preferences\n- Recommends optimal engagement timing\n\n### Deal Twin\n- Assesses probability to close\n- Identifies blockers\n- Suggests positioning against competitors\n- Learns from won/lost deals\n- Predicts close date +/- 10 days\n\n### Project Twin\n- Understands scope + blockers + risks\n- Predicts on-time completion\n- Identifies dependency risks\n- Learns from similar projects\n- Recommends contingency planning\n\n### Financial Twin\n- Forecasts cash flow\n- Predicts revenue recognition timing\n- Identifies collection risks\n- Learns from seasonal patterns\n- Recommends collection strategy\n\n### Employee Twin\n- Understands skills + capacity + development\n- Predicts performance\n- Identifies burnout risk\n- Learns work preferences\n- Recommends growth opportunities\n\n### Product Twin\n- Understands feature adoption\n- Predicts product-market fit\n- Identifies customer pain points\n- Learns from usage data\n- Recommends roadmap priorities\n\n### Organization Twin\n- Understands health status\n- Predicts quarterly performance\n- Identifies operational risks\n- Learns from execution patterns\n- Recommends strategic actions\n\n---\n\n## Operating Rhythms\n\nBusinesses don't just execute randomly. They operate in rhythm.\n\nAI participates in every rhythm:\n\n### Daily Rhythms\n- Stand-ups (prepare agenda from blockers + risks)\n- Priorities (surface urgent items + recommendations)\n- Customer follow-ups (prepare context + suggested messaging)\n- Sales pipeline review (show leads prioritized by AI scoring)\n- Support escalations (surface critical issues + recommended actions)\n\n### Weekly Rhythms\n- Sales forecast (update based on deal probability + signals)\n- Sprint planning (prioritize backlog + capacity check)\n- Marketing review (surface underperforming campaigns + recommendations)\n- Finance reconciliation (flag discrepancies + suggest corrections)\n- Team reviews (surface performance issues + talent development)\n\n### Monthly Rhythms\n- Payroll (pre-validate + flag exceptions)\n- Invoice & collections (prioritize AR + suggest strategy)\n- Performance reviews (surface feedback + prepare rating)\n- Board metrics (pre-compile dashboard + highlight exceptions)\n- OKR review (track progress + suggest mid-course corrections)\n\n### Quarterly Rhythms\n- Planning (surface historical data + market insights + constraints)\n- Hiring (surface skill gaps + salary benchmarks + candidate assessment)\n- Budget forecasting (model scenarios + sensitivity analysis)\n- Product roadmap (prioritize features + story estimation + dependency check)\n- Compliance audit (pre-validate controls + flag gaps)\n\nAI doesn't replace these rhythms. It makes them dramatically more effective.\n\n---\n\n## The Result\n\nInstead of:\n- Users switching between Sales/Finance/Support apps\n- Each app having fragmented data\n- Teams not knowing what other teams are doing\n- Decisions made with incomplete information\n- Manual handoffs causing delays\n- Learned patterns disappearing\n\nYou get:\n- Users thinking in capabilities, not apps\n- Spine as canonical source of truth\n- Full cross-team visibility + collaboration\n- Decisions informed by 100% of relevant data\n- AI orchestrating handoffs automatically\n- Learning captured + systematized\n\n---\n\n## Implementation Approach\n\nInstead of:\n```\nBuild 12 workbenches\nAdd cross-domain context\nHope teams use it\n```\n\nBuild:\n```\n1. Capability Layer\n   - Define 200+ operational capabilities\n   - For each: required data, AI prompt, response template, execution rules\n\n2. Entity Layer\n   - Enrich every entity with 13 dimensions (identity, relationships, state, etc.)\n   - Build Digital Twin for each entity type\n\n3. Execution Layer\n   - Implement capability lifecycle (context → recommend → execute → learn)\n   - Build orchestration for handoffs\n\n4. Intelligence Layer\n   - Predictive alerts, scenario modeling, anomaly detection\n   - Learning from completed capabilities\n\n5. UX Layer\n   - Goal-driven (what do you want to achieve?)\n   - Context-rich (all relevant information)\n   - Decision-clear (what should you do?)\n   - Action-ready (one-click execution)\n```\n\n---\n\n## The Competitive Advantage\n\nBy Phase 2 (8 weeks), you have:\n\n**Speed**\n- Decisions in hours, not weeks\n- Handoffs automatic, not manual\n- Context assembly instant, not manual research\n\n**Quality**\n- 100% data visibility (not 60%)\n- Prediction accuracy improving (AI learns from outcomes)\n- Organizational alignment (not silos)\n\n**Scale**\n- Processes scale without proportional headcount\n- Learning captured + reused\n- Continuous improvement built-in\n\n**Experience**\n- Users feel augmented, not replaced\n- \"AI is helping me do my job better\"\n- Work feels seamless, not fragmented\n\nThis is an operating system for organizational execution.\n\n"}