# Sample User Context Profile
# Based on user request: "I want to explore viable application ideas for extra $5k/month"
# This shows how the laboratory agent would capture and store user responses

user_context_template:
  metadata:
    template_type: "user-context-profile"
    version: "1.0"
    created_date: "2025-08-08"
    last_updated: "2025-08-08"
    profile_id: "user-20250808-001"
    agent_context: "laboratory"

  personal_profile:
    interests_and_expertise:
      technical_skills:
        preferred_languages: "[To be captured from user responses]"
        frameworks_enjoyed: "[User's preferred development tools]"
        technical_comfort_level: "[User's self-assessed skill level]"
        
      domain_expertise:
        industries_followed: "[Industries user understands well]"
        professional_background: "[User's work experience areas]"
        subject_matter_expertise: "[Areas of specialized knowledge]"
        
      personal_interests:
        hobbies_activities: "[What user enjoys doing outside work]"
        content_consumption: "[Podcasts, blogs, communities user follows]"
        passion_areas: "[What genuinely fascinates the user]"
        
      problem_sensitivity:
        personal_frustrations: "[Problems user personally encounters]"
        observed_gaps: "[Market gaps user has noticed]"
        community_pain_points: "[Issues in communities user participates in]"

  business_preferences:
    revenue_model_preferences:
      preferred_models:
        - model: "saas"
          appeal_level: "medium"
          reasoning: "Recurring revenue attractive but requires ongoing maintenance"
        - model: "one_time"
          appeal_level: "high" 
          reasoning: "Simpler to manage, clear value exchange"
          
      target_revenue:
        monthly_goal: "$5,000"
        timeline_to_goal: "6-12 months"
        acceptable_range: "$3,000 to $8,000"
        
      pricing_comfort:
        price_point_preference: "balanced"
        customer_type_preference: "[b2b|b2c preference to be determined]"
        billing_preference: "[User's preference to be captured]"

  development_constraints:
    time_availability:
      weekly_commitment: "[Hours per week user can dedicate]"
      preferred_schedule: "[When user prefers to work on this]"
      deadline_pressure: "[User's timeline flexibility]"
      
    technical_complexity:
      complexity_preference: "[User's complexity tolerance to be determined]"
      learning_appetite: "[User's willingness to learn new tech]"
      maintenance_tolerance: "[How much ongoing work user wants]"
      
    resource_constraints:
      budget_for_tools: "[Monthly tool budget user is comfortable with]"
      marketing_budget: "[Marketing spend user can handle]"
      external_help_budget: "[Budget for outsourcing if needed]"
      
    launch_timeline:
      target_launch: "[User's desired timeline to market]"
      mvp_timeline: "[Time to basic working version]"
      feature_iteration: "[Post-launch development pace preference]"

  market_experience:
    previous_launches:
      app_launch_history: "[Has user launched apps before?]"
      success_metrics: "[What worked/didn't work in past]"
      lessons_learned: "[Key insights from previous experience]"
      
    validation_experience:
      customer_interviews: "[User's research experience level]"
      market_research_skills: "[Comfort with market analysis]"
      mvp_testing_experience: "[Experience testing concepts]"
      
    community_involvement:
      active_communities: "[Communities user participates in]"
      network_strength: "[User's professional network quality]"
      influence_areas: "[Where user has credibility/audience]"

  goals_and_objectives:
    primary_goals:
      financial_goal: "$5,000/month additional income to accelerate development of larger projects"
      learning_goals: "[Skills user wants to develop through this]"
      strategic_purpose: "Fund development of larger projects - this is a stepping stone"
      
    success_definition:
      minimum_viable_success: "Consistent $3,000+/month with manageable time investment"
      stretch_success: "$8,000+/month with potential for scaling"
      failure_criteria: "Less than $1,000/month after 12 months, or consuming too much time"
      
    risk_tolerance:
      financial_risk: "[User's comfortable upfront investment]"
      time_risk: "[Acceptable time investment before seeing results]"
      reputation_risk: "[Comfort level with public failure]"

  current_context:
    active_projects:
      current_commitments: "Larger development projects that need funding acceleration"
      available_focus: "[Percentage of attention this project can receive]"
      integration_opportunities: "Revenue from this should fund larger project development"
      
    immediate_priorities:
      urgent_needs: "Validate app concept and move through market research quickly"
      blocking_factors: "[What might prevent progress - to be identified]"
      enablers: "[What would accelerate success - to be explored]"
      
    motivation_factors:
      primary_drivers: "Financial goal to accelerate other projects"
      energy_sources: "[What gives user energy for projects - to be discovered]"
      momentum_builders: "[What helps maintain progress - to be identified]"

  contextual_memory:
    previous_explorations:
      topics_explored: "Revenue-generating app ideas based on personal interests"
      ideas_generated: "[Concepts from this and future sessions]"
      validation_results: "[Feedback or testing outcomes from future validation]"
      
    preferences_discovered:
      confirmed_interests: "[To be validated through exploration process]"
      rejected_approaches: "[Ideas determined not good fit]"
      surprising_discoveries: "[Unexpected insights about preferences]"

# SYSTEM NOTES:
# This context eliminates the need to ask:
# - The $5k/month target (already established)
# - The purpose (accelerate other project development)
# - The approach preference (build app not necessarily large)
# - The process desired (interests → validation → market research → create → launch)
# 
# Future laboratory sessions can immediately focus on:
# - Specific interest areas
# - Technical skill/preference details
# - Resource constraints
# - Market validation approaches