fraim-framework 2.0.55 → 2.0.56

package/dist/registry/workflows/marketing/domain-registration.md

@@ -0,0 +1,323 @@
+# Workflow: domain-registration
+
+**Path:** `workflows/marketing/domain-registration.md`
+
+---
+
+# Domain Registration Research & Analysis
+
+## INTENT
+To systematically research, evaluate, and recommend domain names for the product, including competitive pricing analysis across major registrars and structured decision-making templates.
+
+## PRINCIPLES
+- **Brand Alignment**: Domain should reflect the product's core value proposition
+- **Memorability**: Easy to remember, spell, and share
+- **SEO Consideration**: Consider keyword relevance and search optimization
+- **Future-Proofing**: Consider scalability and brand evolution
+- **Cost Efficiency**: Balance quality with budget constraints
+
+## DOMAIN RESEARCH WORKFLOW
+
+### Step 1: Product Analysis & Brainstorming
+**Objective**: Generate a comprehensive list of potential domain names
+
+**Actions**:
+1. **Product Context Review**
+   - Review product documentation, value proposition, and target audience
+   - Identify core keywords, benefits, and brand attributes
+   - Note any existing brand guidelines or naming conventions
+
+2. **Domain Name Brainstorming**
+   - **COLLABORATIVE APPROACH**: Always brainstorm WITH the stakeholder, not independently
+   - Generate 20-30 initial domain ideas using various approaches:
+     - **Direct naming**: Product name + common TLDs
+     - **Descriptive**: What the product does (e.g., taskmanager.com)
+     - **Invented words**: Brandable made-up names (e.g., fraim.ai)
+     - **Compound words**: Combining relevant terms (e.g., fraimworks.ai)
+     - **Abbreviated**: Acronyms or shortened versions
+     - **Alternative TLDs**: .ai, .io, .co, .app, .dev, etc.
+     - **Playful variations**: Slogan-style domains (e.g., justfraimit.ai)
+   - **Ask for user suggestions** and explore their creative ideas
+   - **Discuss trade-offs** between different naming approaches in real-time
+
+3. **Initial Filtering**
+   - Remove obviously unavailable domains (major brands, common words)
+   - Filter for length (ideally 6-12 characters)
+   - Ensure pronunciation clarity
+   - Check for negative connotations or meanings in other languages
+
+**Output**: List of 15-20 candidate domain names
+
+### Step 2: Availability & Trademark Check
+**Objective**: Verify legal availability and reduce list to viable options
+
+**Actions**:
+1. **Domain Availability Check**
+   - Use multiple domain checkers (Namecheap, GoDaddy, Domain.com)
+   - Check primary TLD (.com) and relevant alternatives (.ai, .io, .co)
+   - Note premium domains and their asking prices
+
+2. **Trademark Research**
+   - **CRITICAL**: Search for existing businesses using similar names, not just trademarks
+   - Search USPTO trademark database for exact and similar marks
+   - **Google search for existing companies** using the domain name or similar variations
+   - Check domain ownership history (WHOIS data) for active businesses
+   - **Industry-specific conflicts**: Pay special attention to businesses in the same sector
+   - Check international trademark databases for key markets
+   - **Document specific conflicts found** with business names, URLs, and risk assessment
+   - Check social media handle availability (@username on major platforms)
+
+3. **Competitive Analysis**
+   - Research competitors' domain strategies
+   - Note industry naming patterns and trends
+   - Identify potential conflicts or confusion risks
+
+**Output**: Narrowed list of 5-8 legally available domains
+
+### Step 3: Registrar Price Comparison
+**Objective**: Compare pricing across major registrars for informed purchasing decisions
+
+**Actions**:
+1. **Browser-Based Price Research**
+   - **CRITICAL**: Always verify pricing by navigating to actual registrar websites
+   - **Do not rely on estimates** - pricing can vary significantly from published rates
+   - Open browser and systematically check each domain across registrars:
+     - **Namecheap**: Check actual search results for verified pricing and renewal rates
+     - **GoDaddy**: Check standard and premium pricing, note promotional vs. renewal rates
+     - **IONOS**: Check their domain search for competitive pricing
+     - **Google Domains/Squarespace**: Check integrated services pricing
+     - **Cloudflare**: Check their registrar pricing
+     - **Domain.com**: Check promotional offers
+     - **Porkbun**: Check competitive pricing options
+
+2. **Pricing Matrix Creation**
+   - **Document verified pricing only** - mark estimates clearly as "estimated"
+   - **Focus on 2-year total cost** - many domains require minimum 2-year registration
+   - Note first-year promotional pricing vs. standard renewal rates
+   - Document included services (privacy protection, email, etc.)
+   - Check for bulk discounts or multi-year savings
+   - Document any premium domain pricing or auction details
+   - **Include additional fees**: Domain Guard/protection services, setup fees
+
+3. **Service Comparison**
+   - DNS management capabilities
+   - Email hosting options
+   - SSL certificate inclusion
+   - Domain privacy protection (often free vs. paid)
+   - Transfer policies and fees
+   - Customer support quality ratings
+   - **Minimum registration periods** (especially important for .ai domains)
+
+### Step 6: Domain Registration Process
+**Objective**: Complete the actual domain purchase with proper configuration
+
+**Actions**:
+1. **Pre-Registration Checklist**
+   - Confirm final domain choice with stakeholders
+   - Verify budget approval for total cost (including protection services)
+   - Prepare registration information (contact details, business info)
+   - Decide on additional services (privacy protection, email, hosting)
+
+2. **Registration Process**
+   - Navigate to chosen registrar's website
+   - Search for the exact domain name to confirm availability and pricing
+   - **Verify pricing matches research** - if different, document discrepancies
+   - Add domain to cart and review all included/additional services
+   - **Review minimum registration periods** (especially for .ai domains)
+   - Consider domain protection services (Domain Guard, privacy protection)
+   - Proceed through checkout process but **stop before payment**
+
+3. **Final Review & Approval**
+   - Document final pricing including all fees and services
+   - Confirm registration period and renewal dates
+   - Get final stakeholder approval for total cost
+   - Complete payment and registration
+   - **Save confirmation details** and login credentials securely
+
+**Output**: Successfully registered domain with proper configuration
+
+### Step 7: Post-Registration Setup
+### Step 5: Final Analysis & Recommendations
+**Objective**: Complete evaluation matrix and provide structured recommendations
+
+**Actions**:
+1. **Scoring Matrix Completion**
+   - Rate each viable domain (1-10) on all criteria in template
+   - Calculate total scores and rank options
+   - Document detailed evaluation notes for top candidates
+
+2. **Risk Assessment Documentation**
+   - Complete legal, business, and technical risk sections
+   - Provide specific mitigation plans for identified risks
+   - Assess implementation complexity and timeline
+   - **Document specific trademark conflicts** and business risks found
+
+3. **Final Recommendations**
+   - Select primary, alternative, and backup domain options
+   - Complete budget summary with **verified 2-year cost projections**
+   - Create implementation plan with specific action items
+   - Prepare stakeholder approval section
+   - **Include trademark clearance requirements** if any conflicts found
+
+**Output**: Complete domain analysis with final recommendations ready for stakeholder review
+   - Select primary, alternative, and backup domain options
+   - Complete budget summary with 3-year cost projections
+   - Create implementation plan with specific action items
+   - Prepare stakeholder approval section
+
+**Output**: Complete domain analysis with final recommendations ready for stakeholder review
+
+### Step 7: Post-Registration Setup
+**Objective**: Configure domain for immediate use and long-term management
+
+**Actions**:
+1. **Essential Configuration**
+   - Configure DNS settings for immediate use
+   - Set up domain privacy protection if not already enabled
+   - Configure email forwarding or professional email accounts
+   - Set up SSL certificate if hosting is immediate
+   - Document all login credentials and account information securely
+
+2. **Business Integration**
+   - Update business documentation with new domain
+   - Configure domain forwarding from old domain if applicable
+   - Update marketing materials and business cards
+   - Set up Google Analytics and Search Console for new domain
+   - Configure social media profiles with new domain
+
+3. **Long-term Management**
+   - Set up renewal reminders (60-90 days before expiration)
+   - Document renewal dates and costs in business calendar
+   - Set up monitoring for domain expiration and DNS issues
+   - Create backup contact information for domain management
+   - Plan for potential domain expansion (subdomains, additional TLDs)
+
+**Output**: Fully configured domain ready for business use with proper management systems in place
+
+### Step 4: Document Creation & Analysis
+**Objective**: Create comprehensive domain analysis document using the standard template
+
+**Actions**:
+1. **Template Setup**
+   - Retrieve the Domain Registration template: `get_fraim_file({ path: "templates/marketing/DOMAIN-REGISTRATION-TEMPLATE.md" })`
+   - Create analysis document at: `docs/marketing/domain-analysis/{YYYY-MM-DD}-{kebab-case-title}.md`
+   - Fill in all template sections systematically
+
+2. **Product Context Documentation**
+   - Complete product analysis section with current brand attributes
+   - Define budget parameters and timeline requirements
+   - Identify required vs. nice-to-have TLD extensions
+
+3. **Domain Research Documentation**
+   - Document all brainstormed domain options in organized categories
+   - Record availability status for each option
+   - Note any premium pricing or special conditions
+
+**Output**: Structured analysis document with complete product context and domain research
+
+## TEMPLATE & OUTPUT LOCATIONS
+
+### Required Template
+Use the Domain Registration Analysis template: `get_fraim_file({ path: "templates/marketing/DOMAIN-REGISTRATION-TEMPLATE.md" })`
+
+### Output Location
+**Primary Document**: `docs/marketing/domain-analysis/{YYYY-MM-DD}-{kebab-case-title}.md`
+- Example: `docs/marketing/domain-analysis/2026-01-23-fraim-domain-research.md`
+- Example: `docs/marketing/domain-analysis/2026-01-23-product-rebrand-domains.md`
+
+
+## EXECUTION CHECKLIST
+
+### Pre-Research
+- [ ] Gather product documentation and brand guidelines
+- [ ] Define budget parameters and timeline
+- [ ] Identify key stakeholders for final approval
+- [ ] **Schedule collaborative brainstorming session** with stakeholders
+
+### Research Phase
+- [ ] Complete product analysis with stakeholder input
+- [ ] **Conduct collaborative brainstorming session** - do not work independently
+- [ ] Generate initial list of 20-30 domain ideas together
+- [ ] Filter to 15-20 viable candidates
+- [ ] Check availability across multiple registrars
+- [ ] **Conduct thorough trademark and business conflict research**
+- [ ] Narrow to 5-8 available options with no major conflicts
+
+### Analysis Phase
+- [ ] **Open browser and verify actual pricing** at each registrar
+- [ ] **Do not rely on estimates** - get verified pricing only
+- [ ] Create comprehensive pricing matrix with **2-year total costs**
+- [ ] Document service comparisons and features
+- [ ] **Note minimum registration periods** and additional fees
+- [ ] Complete scoring matrix for each domain
+- [ ] **Document specific trademark conflicts** and legal considerations
+
+### Recommendation Phase
+- [ ] Prepare final recommendation report with **verified pricing**
+- [ ] Create implementation timeline
+- [ ] Calculate total cost of ownership including protection services
+- [ ] **Include trademark clearance requirements** if needed
+- [ ] Present findings to stakeholders
+- [ ] Secure approval for domain purchase
+
+### Registration Phase
+- [ ] **Navigate to chosen registrar and verify final pricing**
+- [ ] Add domain to cart and review all services
+- [ ] **Get final approval for total cost** including all fees
+- [ ] Complete registration process
+- [ ] **Save all confirmation details and credentials securely**
+
+### Post-Registration
+- [ ] Configure essential DNS and privacy settings
+- [ ] Set up email forwarding or professional email
+- [ ] Update business documentation with new domain
+- [ ] **Set up renewal reminders** (60-90 days before expiration)
+- [ ] Configure monitoring and backup management contacts
+
+## SUCCESS METRICS
+- **Speed**: Complete research and recommendation within 2-3 business days
+- **Thoroughness**: Evaluate at least 5 viable domain options with verified pricing
+- **Cost Efficiency**: Identify savings opportunities across registrars with actual pricing
+- **Risk Mitigation**: Zero trademark or legal conflicts through comprehensive research
+- **Stakeholder Satisfaction**: Clear, actionable recommendations with rationale
+- **Collaborative Process**: Stakeholder actively involved in brainstorming and decision-making
+
+## CRITICAL LESSONS LEARNED
+
+### Pricing Verification
+- **Never rely on estimated pricing** - always verify by navigating to actual registrar websites
+- **Focus on 2-year total costs** - many premium domains (.ai, .io) require minimum 2-year registration
+- **Include all fees** - domain protection services, setup fees, and renewal rate increases
+- **Promotional vs. renewal pricing** - first-year discounts can be misleading for long-term costs
+
+### Trademark Research
+- **Search for existing businesses**, not just trademark registrations
+- **Industry-specific conflicts** are critical - same sector businesses pose higher risk
+- **Document specific conflicts** found with business names, URLs, and risk levels
+- **Different industries may have lower risk** - business consulting vs. AI development tools
+
+### Collaborative Process
+- **Always brainstorm WITH stakeholders** - never work independently on creative naming
+- **User suggestions often lead to better options** - be open to their creative input
+- **Explain trade-offs in real-time** - help stakeholders understand naming implications
+- **Get approval at each major decision point** - pricing, trademark risks, final selection
+
+### Registration Process
+- **Verify pricing at checkout** - registrar pricing can differ from search results
+- **Review all included services** - privacy protection, domain guard, email options
+- **Understand minimum registration periods** - especially important for .ai domains
+- **Save all credentials securely** - registration confirmations, login details, renewal dates
+
+## OUTPUT DELIVERABLES
+All deliverables should be saved in the designated output location: `docs/marketing/domain-analysis/{YYYY-MM-DD}-{kebab-case-title}.md`
+
+1. **Complete Domain Analysis Document** - Using the standard template with all sections filled
+2. **Pricing Comparison Matrix** - Detailed registrar analysis (included in main document)
+3. **Risk Assessment Report** - Legal and business risk evaluation (included in main document)  
+4. **Implementation Plan** - Step-by-step execution timeline (included in main document)
+5. **Stakeholder Approval Section** - Ready for decision-maker review (included in main document)
+
+**File Naming Examples**:
+- `docs/marketing/domain-analysis/2026-01-23-fraim-domain-research.md`
+- `docs/marketing/domain-analysis/2026-01-23-product-rebrand-domains.md`
+- `docs/marketing/domain-analysis/2026-01-23-new-feature-subdomain.md`

package/dist/registry/workflows/marketing/hbr-article.md

@@ -0,0 +1,73 @@
+# Workflow: hbr-article
+
+**Path:** `workflows/marketing/hbr-article.md`
+
+---
+
+# Harvard Business Review Article Phase
+
+## INTENT
+Design a repeatable reviewable process for researching, drafting, and submitting an HBR or similar thought-leadership article that follows the Harvard Business Review author guidelines and documents each review before publication.
+
+## PRINCIPLES
+- **Strategy First** – Explain why the piece matters to HBR readers and how it advances the product roadmap.
+- **Evidence-Led Storytelling** – Back every claim with customer insights, data, or experiments and include proper citations.
+- **Executive Clarity** – Keep the tone structured, concise, and professional while still being compelling.
+- **Review Discipline** – Require sign-offs during every milestone so the article progresses with confidence.
+
+## HARVARD BUSINESS REVIEW GUIDELINES SUMMARY
+- **Audience & Outcome**: HBR serves ambitious senior leaders with rigorous, evidence-backed insights they can apply today.
+- **Topic Scope**: Strategy, leadership, culture, operations, technology change, innovation, communication, decision-making, talent, and transitions.
+- **Five Quality Criteria**: Expertise, evidence, originality (or a counterintuitive twist), practical usefulness, and excellent writing.
+- **Responsible Storytelling**: Represent diverse organizations, avoid bias/stereotypes, disclose conflicts, and explain any generative AI usage.
+- **Pitch Checklist** (covered during Step 2 and in the template): central message, importance/counterintuition, novelty, leader application, authority/backing, supporting research/examples, and relevant experiences.
+
+## HBR ARTICLE WORKFLOW
+
+### Step 1: Confirm the story belongs with HBR
+- Articulate the insight, the proposed HBR section (Strategy, Leadership, Technology, etc.), and why the timing is right.
+- Cite the HBR guidelines (https://hbr.org/guidelines-for-authors) for exclusivity, word count, bylines, and conflict-of-interest disclosures.
+- Document how the story ties to the product roadmap, clarify the customer problem, and capture any embargo or exclusivity constraints with marketing and executive reviewers.
+
+### Step 2: Research & angle sharpening
+- Gather customer data, experiments, interviews, or telemetry that demonstrate the thesis.
+- Review two recent HBR pieces in the target section to understand structure, tone, and citation style.
+- Identify outstanding sourcing needs (people, metrics, visuals) and schedule them before drafting.
+- Use the HBR prompts to refine the story:
+  - What is the central message of the article?
+  - Why is it important, useful, or counterintuitive?
+  - What is new about the idea?
+  - Why do senior leaders need to know about it today, and how can they apply it?
+  - What is the source of the team’s authority (prior work, credentials, experience)?
+  - What research or examples will back the idea?
+  - What academic, professional, or personal experience will you draw on?
+
+### Step 3: Outline and structure guardrails
+- Draft an outline covering:
+  - Hook and problem framing
+  - Diagnostic/evidence blocks (data, quotes, frameworks)
+  - Practice-ready recommendation and product-specific next steps
+- Annotate each section with required references and attachments.
+- Share the outline with product and marketing reviewers, collect feedback, and incorporate it prior to drafting.
+
+### Step 4: Draft, iterate, and polish
+- Adhere to HBR word limits and formatting expectations; note disclosures, partnerships, or competing interests directly in the draft.
+- Run two review passes: one focused on clarity (peer reviewer) and one on strategic voice (executive reviewer).
+- Track edits through versioned drafts, doc comments, or PR history and finalize the headline/angle with the marketing lead.
+- Capture approvals for accuracy, voice, and compliance before locking the draft.
+
+### Step 5: Finalize submission + collateral
+- Verify the draft satisfies the HBR checklist (tone, length, references, conflicts) and secure the final sign-off.
+- Draft the submission email (subject line, synopsis, attachments) and log it in `docs/marketing/hbr/submission-log.md` or an equivalent tracking document.
+- Plan accompanying collateral (blog post, newsletter snippet, executive update) that repurposes the article's insight and assign owners.
+- Note follow-up steps for publication tracking and audience engagement.
+
+## OUTPUT
+- Thesis/angle memo that explains the fit for HBR.
+- Approved outline and draft with reviewer notes and version history.
+- Submission package (email, attachments, compliance checklist).
+- Launch collateral plan with asset owners and delivery status.
+
+## DOCUMENT TEMPLATE STRUCTURE
+
+Use `get_fraim_file({ path: "templates/marketing/HBR-ARTICLE-TEMPLATE.md" })` to capture the thesis, outline, draft, review log, submission log, and launch collateral plan for each HBR article. 

package/dist/registry/workflows/marketing/launch-checklist.md

@@ -0,0 +1,37 @@
+# Workflow: launch-checklist
+
+**Path:** `workflows/marketing/launch-checklist.md`
+
+---
+
+# Launch Checklist Phase
+
+## INTENT
+To ensure a smooth and successful feature launch by systematically verifying all marketing, technical, and operational readiness.
+
+## PRINCIPLES
+- **Meticulous Preparation**: Leave no stone unturned before launch.
+- **Cross-Functional Alignment**: Ensure all teams are ready for the launch.
+- **Timely Execution**: Follow the schedule for maximum impact.
+- **Post-Launch Verification**: Monitor performance and address issues immediately.
+
+## LAUNCH CHECKLIST WORKFLOW
+
+### Step 1: Readiness Check
+- Is the feature deployed and verified?
+- Are the marketing assets ready?
+- Is the support team briefed?
+
+### Step 2: Launch Execution
+- Post to social channels.
+- Send announcement emails.
+- Update documentation.
+
+### Step 3: Post-Launch Monitoring
+- Check for user feedback.
+- Monitor error rates.
+- Engagement metrics.
+
+## OUTPUT
+- Launch Status Report
+- Post-Launch Feedback Summary

package/dist/registry/workflows/marketing/marketing-strategy.md

@@ -0,0 +1,45 @@
+# Workflow: marketing-strategy
+
+**Path:** `workflows/marketing/marketing-strategy.md`
+
+---
+
+# Marketing Strategy Phase
+
+## INTENT
+To define the value proposition, target audience, and launch strategy for new features, ensuring clear communication of benefits and effective market entry.
+
+## PRINCIPLES
+- **Value-First**: Focus on the problem solved and the value delivered.
+- **Audience-Centric**: Identify exactly who the feature is for.
+- **Clear Messaging**: Ensure simplicity and clarity in all marketing materials.
+- **Channel Alignment**: Choose appropriate channels for the target audience.
+
+## MARKETING STRATEGY WORKFLOW
+
+### Step 1: Feature Analysis
+- What is the core problem being solved?
+- What are the key benefits?
+- Who is the primary persona?
+
+### Step 2: Value Proposition Definition
+- Draft 1-2 sentences describing the feature's value.
+- Identify the "Hero" benefit.
+
+### Step 3: Target Audience Identification
+- Define the specific segment of users this is for.
+- Identify there pain points.
+
+### Step 4: Channel Strategy
+- Where will we announce this? (Twitter, LinkedIn, Email, In-app)
+- What is the tone for each channel?
+
+### Step 5: Marketing Brief Creation
+- Create a `docs/marketing/strategy/{issue_number}-{feature-name}.md`
+- Use `MARKETING-STRATEGY-TEMPLATE.md`
+
+## OUTPUT
+- Marketing Strategy Doc
+- Value Prop
+- Target Audience
+- Launch Checklist status

package/dist/registry/workflows/marketing/storytelling.md

@@ -0,0 +1,65 @@
+# Workflow: storytelling
+
+**Path:** `workflows/marketing/storytelling.md`
+
+---
+
+# Marketing Storytelling Workflow
+
+## INTENT
+To transform product development experiences into compelling founder narratives for events, conferences, and speaking opportunities that connect technical reality with broadly applicable lessons.
+
+## PRINCIPLES
+- **Grounded in Reality**: All narratives based on actual product development experiences
+- **Story Arc Focus**: Follow intent → friction → insight → outcome structure
+- **Audience-Specific**: Tailor messaging to event type and audience expectations
+- **Authentic Voice**: Avoid sales pitch tone, focus on genuine founder lessons
+
+## STORYTELLING WORKFLOW
+
+### Step 1: Artifact Collection
+Gather source materials that tell the product development story:
+- Product documentation (specs, architecture notes, design docs)
+- Development retrospectives or post-mortems
+- Code repositories and key commits
+- Prior pitches, emails, or presentations
+
+### Step 2: Story Arc Extraction
+Extract the core narrative following the story structure:
+- **Intent**: What was the original vision and why it mattered?
+- **Friction**: What unexpected challenges or failures occurred?
+- **Insight**: What key learnings or "aha moments" emerged?
+- **Outcome**: What was built and why it works?
+
+### Step 3: Founder Lessons Development
+Transform technical experience into broadly applicable lessons:
+- Identify 3-5 key takeaways that apply to other founders
+- Remove internal jargon and technical complexity
+- Focus on decision-making processes and trade-offs
+- Highlight counterintuitive or surprising discoveries
+
+### Step 4: Event-Specific Adaptation
+Customize content for target event and audience:
+- Research event format (conference, panel, workshop, podcast)
+- Adapt language for audience (technical, business, mixed)
+- Create appropriate time formats (5min, 15min, 30min, 45min)
+- Develop supporting materials and Q&A preparation
+
+### Step 5: Content Package Creation
+Generate complete materials for event submission:
+- Email pitch with compelling subject line
+- Session title with clear hook
+- 1-2 sentence session description
+- Speaker bio highlighting relevant experience
+- Presentation outline and talking points
+
+## TEMPLATE USAGE
+
+Use `get_fraim_file({ path: "templates/marketing/STORYTELLING-TEMPLATE.md" })` to create:
+- `docs/marketing/storytelling/{issue_number}-{event-name}.md`
+
+## OUTPUT
+- Compelling founder narrative grounded in product reality
+- Event-ready submission materials
+- Multi-format presentation content
+- Reusable story framework for future opportunities

package/dist/registry/workflows/performance/analyze-performance.md

@@ -0,0 +1,65 @@
+# Performance Analysis Phase
+
+## INTENT
+To diagnose production performance issues (CPU, Memory, Swap) and provide actionable recommendations for stabilization without performing direct application or infrastructure modifications.
+
+## PRINCIPLES
+- **Observational Only**: Do not modify code or infrastructure during this phase.
+- **Data-Driven**: Base all recommendations on metrics collected from the environment.
+- **Non-Invasive**: Use non-destructive commands that do not impact server stability.
+- **Actionable**: Provide clear, prioritized recommendations for remediation.
+
+## ANALYSIS WORKFLOW
+
+### Step 1: Run the Performance Profiler
+Execute the profiling script against the production environment to collect plan-level and process-level metrics.
+
+**Note**: `profile-server.ts` has FRAIM dependencies and requires ephemeral execution.
+
+```bash
+# Get the profile-server script ephemerally (has FRAIM dependencies)
+# Use get_fraim_file({ path: "scripts/performance/profile-server.ts" }) and save to tmp/profile-server.ts
+npx tsx tmp/profile-server.ts --prod
+```
+
+### Step 2: Inspect Automated Diagnosis
+Review the "Step 4: Automated Diagnosis" section of the output. 
+It will specifically check for:
+- **Swap Death**: If >95% swap is used, the server is thrashing.
+- **Absent Application**: If `server.js` is missing, the infrastructure is healthy but the app is crashed/not starting.
+- **Infrastructure Hogs**: If Azure agents (Kudu/dotnet) are consuming excessive RAM.
+
+### Step 3: Deep Dive Log Analysis
+If a crash loop or high operation frequency is suspected, collect and analyze application logs using the same script with the `--logs` flag.
+
+```bash
+# Use the same ephemeral script with logs flag
+npx tsx tmp/profile-server.ts --prod --logs
+```
+Look for:
+- Frequency of initialization logs (e.g., "Ensured unique index").
+- Patterns indicative of OOM events or unhandled exceptions.
+- High volume of specific operations (e.g., decryptions) suggesting an infinite loop.
+
+### Step 4: Formulate Recommendations
+Based on the diagnosis, provide specific recommendations in your response or an implementation plan (if a fix is needed in a subsequent phase).
+Examples:
+- **Restart**: If swap usage is high or rogue processes are detected.
+- **Upgrade Plan**: If physical memory is chronically saturated (B1 to P1v3).
+- **Code Optimization**: If log analysis reveals initialization loops or leaks.
+
+## EXAMPLES
+
+### Good Analysis
+> "The profiler shows 98% CPU usage and 'Swap Death'. The logs show 'Ensured unique index' occurring 100 times per minute. I recommend implementing an initialization guard in `PrismaDatabaseService` to break this loop."
+
+### Bad Analysis (Do not do)
+> "I found a loop, so I've updated `server.ts` to fix it." 
+> *Correction: Propose the fix first, do not implement it within the analysis workflow.*
+
+## COMPLETION CHECKLIST
+- [ ] Profiler run successfully on production.
+- [ ] Resource bottlenecks (CPU/Mem/Swap) identified.
+- [ ] Application process stability verified.
+- [ ] Root cause hypothesis formulated based on metrics and logs.
+- [ ] Prioritized recommendations delivered to the user.