ido4

    Core Concepts: The ido4 Way

    Now that you've experienced the basic workflow, let's explore the core concepts that make ido4 a powerful new way to manage software projects.

    These concepts are rooted in the Hydro methodology - a framework developed specifically for hybrid AI-human development teams. ido4 provides the tooling infrastructure to make Hydro's dependency-driven approach practically executable.

    Understanding these principles is key to unlocking the full potential of Possibility-Driven Development and effective Human-AI collaboration.

    From Sprints to Waves: A New Rhythm for Development

    In traditional Agile, the sprint is a fixed time-box (usually two weeks) where you try to fit a certain amount of work.

    ido4 replaces sprints with Waves. A Wave is not defined by time, but by its content. It is a collection of tasks that are logically grouped together because they depend on each other to deliver a coherent piece of functionality.

    • Time-Based (Sprints): "What can we do in the next two weeks?"
    • Dependency-Based (Waves): "What can we do now that feature-X is complete?"

    A Wave begins when its dependencies are met and ends when all of its tasks are complete. This creates a natural, continuous flow of work, allowing your team (and your AI assistant) to move as fast as possible without being constrained by artificial deadlines.

    Epics and the Rule of Integrity

    In ido4, an Epic represents a significant business capability or feature that is broken down into smaller, manageable tasks. For example, "User Authentication System" could be an Epic.

    To ensure that these large features are developed and delivered as a cohesive whole, ido4 enforces a simple but critical rule:

    The Principle of Epic Integrity: All tasks belonging to a single Epic must be assigned to the same Wave.

    This rule prevents features from being partially completed and scattered across different development cycles. It ensures that when a Wave is finished, a complete, testable, and valuable piece of functionality is delivered.

    The AI Task Classification Framework

    In a hybrid Human-AI team, not all tasks are created equal. Assigning the right task to the right team member (whether human or AI) is critical for efficiency and quality.

    ido4 provides a simple framework for classifying tasks based on their suitability for AI, which determines the workflow and level of human oversight required.

    ai-only

    • What it is: A task that the AI can complete entirely on its own with high confidence.
    • Characteristics: Well-defined, follows existing patterns, low risk.
    • Example: "Create a TypeScript interface based on an existing data model."

    ai-reviewed

    • What it is: The AI performs the implementation, but a human review is mandatory before completion.
    • Characteristics: Involves some business logic or integration, but is based on standard patterns.
    • Example: "Implement a standard REST API endpoint for user profiles."

    hybrid

    • What it is: A collaborative task where a human provides the high-level design and strategic decisions, and the AI assists with implementation details.
    • Characteristics: Complex, involves novel logic, or has significant architectural impact.
    • Example: "Design and implement a new caching strategy for the application."

    human-only

    • What it is: A task that requires human expertise, strategic thinking, or critical decision-making that should not be delegated to an AI.
    • Characteristics: High risk, involves security, or defines core system architecture.
    • Example: "Design the database schema for a new multi-tenant system."

    By classifying tasks this way, your team can leverage your AI assistant for what it does best (speed and pattern implementation) while reserving human brainpower for what truly matters (strategy, architecture, and quality).

    Next Step: User Guide: Day-to-Day with ido4