Skip to content

Add OSCCO business-as-code workflow functions#43

Open
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
devin/1754864477-oscco-business-workflows
Open

Add OSCCO business-as-code workflow functions#43
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
devin/1754864477-oscco-business-workflows

Conversation

@devin-ai-integration
Copy link

Add OSCCO business-as-code workflow functions

Summary

This PR adds a comprehensive MDX file for OSCCO (AI Online Sales Counselor) that defines their business processes as executable TypeScript code. The implementation creates platform/content/startups/oscco.mdx with 478 lines of well-structured workflow functions covering all core business operations.

Key additions:

  • New startups/ directory under platform/content/
  • Complete OSCCO business definition with lean canvas data in YAML frontmatter
  • 15+ TypeScript workflow functions across 5 main categories:
    • Customer acquisition (acquireCustomer, qualifyBuilderLead, generateCustomProposal)
    • Lead processing with sub-60s response requirement (processInboundLead, qualifyLead)
    • Product development (developAICapability, enhanceBuilderIntegration, optimizeConversationFlows)
    • Revenue generation (generateRevenue, optimizePricing, expandCustomerValue)
    • Operational procedures (maintainSystemHealth, ensureCompliance, manageCustomerSuccess)
    • Decision-making workflows (makeStrategicDecision, optimizeResourceAllocation, evaluateMarketOpportunity)
  • Event-driven workflows using oscco.on() for real-time processing
  • Scheduled workflows using oscco.every() for automated operations
  • Comprehensive TypeScript interfaces and type definitions

Review & Testing Checklist for Human

⚠️ High Priority (5 items)

  • Business logic validation - Verify that the workflow functions accurately represent OSCCO's intended business processes and align with the provided lean canvas data
  • MDX rendering test - Navigate to the file in the platform UI and confirm it renders correctly without errors, especially the large TypeScript code blocks
  • Complete CI verification - Ensure all GitHub Actions pass, including any platform-specific checks for MDX files and content validation
  • Directory structure validation - Confirm that the new startups/ directory follows the expected platform patterns and doesn't break any existing functionality
  • Function structure review - Verify that the pseudocode approach with non-existent function references is acceptable for the platform's intended use

Recommended test plan:

  1. Visit the OSCCO page in the platform UI to verify MDX rendering
  2. Test any content search/indexing features that might include the new file
  3. Verify the lean canvas data displays correctly in any business model views
  4. Check that the TypeScript syntax highlighting and code blocks render properly

Diagram

%%{ init : { "theme" : "default" }}%%
graph TD
    Platform["platform/"]:::context --> Content["content/"]:::context
    Content --> BusinessAsCode["business-as-code.mdx"]:::context
    Content --> Startups["startups/"]:::major-edit
    Startups --> OSCCO["oscco.mdx<br/>(478 lines)"]:::major-edit
    
    OSCCO --> Frontmatter["YAML Frontmatter<br/>Lean Canvas Data"]:::major-edit
    OSCCO --> Workflows["TypeScript Workflows<br/>15+ Functions"]:::major-edit
    OSCCO --> Events["Event-driven<br/>oscco.on()"]:::major-edit
    OSCCO --> Scheduled["Scheduled Tasks<br/>oscco.every()"]:::major-edit
    
    BusinessAsCode -.-> OSCCO
    
    subgraph Legend
        L1[Major Edit]:::major-edit
        L2[Minor Edit]:::minor-edit  
        L3[Context/No Edit]:::context
    end
    
    classDef major-edit fill:#90EE90
    classDef minor-edit fill:#87CEEB
    classDef context fill:#FFFFFF
Loading

Notes

  • Local verification passed: pnpm lint ✅ and pnpm check-types
  • The workflow functions use a pseudocode approach where they reference other functions that don't exist yet, as requested in the requirements
  • All business logic is based on the provided OSCCO lean canvas data for AI OSC services to home builders
  • The file follows the same structure and patterns as the existing business-as-code.mdx file
  • Functions include comprehensive error handling and async/await patterns throughout

Session details:

- Create comprehensive MDX file with TypeScript workflow functions
- Define customer acquisition, lead processing, product development workflows
- Include revenue generation, operational procedures, and decision-making functions
- Add event-driven and scheduled workflows for automated operations
- Implement proper TypeScript typing with interfaces for all data structures
- Follow business-as-code pattern with async/await and error handling

Co-Authored-By: unknown <>
@devin-ai-integration
Copy link
Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@vercel
Copy link

vercel bot commented Aug 10, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
ai ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 10, 2025 11:25pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants