Meta: Enterprise Example Strategy (upgrade examples to production quality)

[teilomillet]

Goal

Transform examples/ from demo scripts into enterprise-grade learning material that shows companies how to use enzu in production.

Context

Current examples are functional but don't showcase production patterns companies need. We want examples that rival LangChain/other frameworks in quality while staying focused on enzu's strengths: budgets-as-contracts + reliable execution.

Strategy

Phase 1: Cleanup (Issues #27, #28, #29)

1. Audit and organize existing examples (Cleanup: Audit and organize existing examples #27)
2. Add architecture docs and diagrams (Enhancement: Add architecture docs and diagrams to examples #28)
3. Standardize structure and add tests (Enhancement: Standardize example structure and add tests #29)

Goal: Make existing examples production-quality

Phase 2: New Production Examples (Issues #22-26)

4. Invoice Processing Pipeline (Example: Invoice Processing Pipeline (document extraction at scale) #22) - document extraction at scale
5. Multi-Tenant API Service (Example: Multi-Tenant API Service (FastAPI + enzu) #23) - FastAPI + enzu integration
6. Cost-Controlled Research Agent (Example: Cost-Controlled Research Agent (advanced RLM) #24) - advanced RLM patterns
7. Resume Parser at Scale (Example: Resume Parser at Scale (1M documents, budget optimization) #25) - 1M documents, budget optimization
8. Interactive CLI Tool (Example: Interactive CLI Tool (enzu-powered git assistant) #26) - git assistant with sessions

Goal: Showcase real-world enterprise use cases

Phase 3: Documentation & Promotion

• Create examples/README.md as comprehensive index
• Add "Enterprise Examples" section to main docs
• Write blog posts for each production example
• Create video walkthroughs (optional)
• Update landing page with example highlights

Success Metrics

• 5 production-ready examples with tests
• All examples have architecture docs
• Clear learning path (beginner → advanced)
• Examples run in CI
• Positive feedback from companies evaluating enzu

Issues

• Cleanup: Audit and organize existing examples #27 - Cleanup: Audit and organize existing examples
• Enhancement: Add architecture docs and diagrams to examples #28 - Enhancement: Add architecture docs and diagrams
• Enhancement: Standardize example structure and add tests #29 - Enhancement: Standardize structure and add tests
• Example: Invoice Processing Pipeline (document extraction at scale) #22 - Example: Invoice Processing Pipeline
• Example: Multi-Tenant API Service (FastAPI + enzu) #23 - Example: Multi-Tenant API Service
• Example: Cost-Controlled Research Agent (advanced RLM) #24 - Example: Cost-Controlled Research Agent
• Example: Resume Parser at Scale (1M documents, budget optimization) #25 - Example: Resume Parser at Scale
• Example: Interactive CLI Tool (enzu-powered git assistant) #26 - Example: Interactive CLI Tool

Timeline

• Phase 1 (Cleanup): 1-2 weeks
• Phase 2 (New Examples): 2-3 weeks
• Phase 3 (Docs): 1 week

Total: 4-6 weeks for complete transformation

Notes

Focus on quality over quantity. Better to have 3 excellent examples than 10 mediocre ones.
Each example should teach something companies can apply directly.