- Get Started

Demos

Step-by-Step Walkthrough

Follow the complete journey from GitHub issue to merged pull request. See how each agent contributes to the autonomous development workflow.

1

1. Issue Discovery

NEXUS polls GitHub for open issues and creates tickets in the SharedStore

javascript
// NEXUS discovers open issues
const issues = await github.listIssues({ state: 'open' });
for (const issue of issues) {
  await sharedStore.createTicket({
    issueNumber: issue.number,
    title: issue.title,
    body: issue.body
  });
}
2

2. Task Assignment

NEXUS assigns tickets to idle FORGE workers based on availability

javascript
// NEXUS assigns work
const worker = await sharedStore.getIdleWorker();
const ticket = await sharedStore.getNextTicket();
await sharedStore.assignTicket(ticket.id, worker.id);
3

3. Planning Phase

FORGE creates a PLAN.md file outlining the implementation approach

markdown
# PLAN.md

## Problem
Fix pagination offset calculation in API endpoint

## Solution
1. Update calculateOffset() function in pagination.rs
2. Add unit tests for edge cases
3. Update API documentation

## Risks
- Breaking change for existing API consumers
- Need to verify with integration tests
4

4. Code Implementation

FORGE writes the actual code changes based on the plan

rust
// src/api/pagination.rs
pub fn calculate_offset(page: u32, per_page: u32) -> u32 {
    if page == 0 {
        0
    } else {
        (page - 1) * per_page
    }
}

#[cfg(test)]
mod tests {
    use super::*;
    
    #[test]
    fn test_first_page() {
        assert_eq!(calculate_offset(1, 10), 0);
    }
}
5

5. Code Review

SENTINEL reviews the code for correctness, security, and style

javascript
// SENTINEL review results
{
  "correctness": "PASS",
  "security": "PASS", 
  "style": "PASS",
  "tests": "PASS",
  "comments": [
    "Good edge case handling for page 0",
    "Consider adding more test cases"
  ],
  "approved": true
}
6

6. Pull Request

FORGE creates a pull request with all changes

markdown
# Pull Request: Fix pagination offset calculation

## Changes
- Updated calculate_offset() to handle page 0 correctly
- Added comprehensive unit tests
- Updated API documentation

## Testing
- All unit tests passing
- Integration tests verified
- Manual testing completed

Fixes #142
7

7. CI/CD & Merge

VESSEL monitors CI status and merges when all checks pass

markdown
// VESSEL monitors CI
while (!ci.complete) {
  const status = await github.getCIStatus(pr.number);
  if (status.success) {
    await github.mergePR(pr.number, {
      merge_method: 'squash',
      commit_title: 'Fix pagination offset (#142)'
    });
    break;
  }
  await sleep(10000);
}
8

8. Documentation

LORE updates documentation and creates an ADR for the change

markdown
# ADR-001: Pagination Offset Fix

## Status
Accepted

## Context
The pagination offset calculation was incorrect for page 0,
causing API responses to skip the first item.

## Decision
Updated calculate_offset() to return 0 when page is 0,
matching expected API behavior.

## Consequences
- Fixes bug #142
- Breaking change for clients expecting old behavior
- Requires API version bump

Try it yourself

Ready to see this in action with your own repository? Get started with OpenFlows and watch your autonomous development team in action.