> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revolte.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI-SDLC with Revolte

> AI-native software development reimagines how engineering teams move from an idea to production. Instead of developers manually carrying every task through requirements, implementation, review, and delivery, AI agents can execute much of the software development lifecycle while engineers stay in control of intent, decisions, and approvals.

Revolte is the engineering workspace that makes this model practical for real teams. Developers can work interactively with AI or hand off structured work for autonomous execution, while Revolte provides the context, execution environment, approval gates, traceability, and delivery workflows needed to take work from requirement to code, pull request, and deployment—without bypassing the engineering practices teams already trust.

<div className="asdlc-page">
  <section className="asdlc-hero">
    <h2>AI is changing more than how code gets written.</h2>

    <div className="asdlc-hero-grid">
      <div>
        <p className="asdlc-sub">It's changing the developer's day — and the engineering lifecycle around them. Revolte is the system that runs that lifecycle: agents, human checkpoints, secure execution, and Workflows that continue from the first commit through production and back.</p>
        <p className="asdlc-thesis"><strong>From doing every step of development, to directing, reviewing, and owning engineering outcomes.</strong></p>
      </div>

      <div className="asdlc-hero-panel asdlc-reveal">
        <div className="asdlc-cap">A workflow, end to end</div>

        <div className="asdlc-mini-rail">
          <div><span className="asdlc-mini-dot" /><span>Sandbox opens, agent explores the repo</span></div>
          <div><span className="asdlc-mini-dot" /><span>Branch, commits, <strong>pull request</strong></span></div>
          <div><span className="asdlc-mini-dot asdlc-check" /><span><strong>Human reviews and approves</strong></span></div>
          <div><span className="asdlc-mini-dot" /><span>Preview, promotion, production release</span></div>
          <div><span className="asdlc-mini-dot" /><span>Scale, operate, support in the field</span></div>
          <div><span className="asdlc-mini-dot asdlc-check" /><span><strong>Signals return for the next workflow</strong></span></div>
        </div>
      </div>
    </div>
  </section>

  <section id="lifecycle" className="asdlc-section asdlc-rule-top">
    <div className="asdlc-kicker asdlc-reveal"><h2>01 / THE ENGINEERING LIFECYCLE</h2></div>
    <p className="asdlc-lede">Code generation is one stage among nine. Revolte carries a change from an isolated sandbox through review, verification, promotion, release, live operation, and back into the next round of work.</p>

    <div className="asdlc-rail-frame asdlc-reveal">
      <div className="asdlc-rail-legend"><span><i className="asdlc-legend-square" /> Lifecycle stage</span><span><i className="asdlc-legend-diamond" /> Human checkpoint</span></div>

      <div className="asdlc-rail">
        <div className="asdlc-rail-track" />

        <div><i /><small>01</small><strong>Secure Sandbox</strong><span>Agents explore, edit, and run code in isolation.</span></div>
        <div><i /><small>02</small><strong>Version Control</strong><span>Branches, commits, and history like any change.</span></div>
        <div><i className="asdlc-rail-check" /><small>03</small><strong>Pull Request</strong><span>A reviewable, human-inspected change.</span></div>
        <div><i /><small>04</small><strong>Preview & Verification</strong><span>Running software is validated, not just the diff.</span></div>
        <div><i /><small>05</small><strong>Environment Promotion</strong><span>Moves through staging and release stages.</span></div>
        <div><i className="asdlc-rail-check" /><small>06</small><strong>Production Release</strong><span>A controlled, traceable deployment path.</span></div>
        <div><i /><small>07</small><strong>Scale & Operate</strong><span>Stays healthy, exposes logs and metrics.</span></div>
        <div><i /><small>08</small><strong>Warranty & Support</strong><span>Incidents re-enter workflows, not inboxes.</span></div>
        <div><i className="asdlc-rail-check" /><small>09</small><strong>Measure & Improve</strong><span>DORA signals become the next workflow's context.</span></div>
      </div>

      <div className="asdlc-rail-loop">↻   Signals from stage 09 become new engineering work at stage 01</div>
    </div>
  </section>

  <section id="workflows" className="asdlc-section asdlc-rule-top asdlc-alt-bg">
    <div className="asdlc-kicker asdlc-reveal"><h2>02 / REVOLTE WORKFLOWS</h2></div>
    <p className="asdlc-lede">A workflow coordinates agents, engineering context, execution environments, human checkpoints, and external systems around one outcome—and it doesn't have to stop at a pull request.</p>

    <div className="asdlc-two-col">
      <div className="asdlc-reveal"><h3>Where a workflow can start</h3><div className="asdlc-entry-list"><div>→   A prompt from a developer</div><div>→   A Jira story or issue</div><div>→   A bug or defect report</div><div>→   Repository or codebase context</div><div>→   An operational or production signal</div></div><div className="asdlc-span-bar"><div className="asdlc-cap">What one workflow can span</div><div><b>DEVELOP</b><b>REVIEW</b><b>RELEASE</b><b>OPERATE</b><b>SUPPORT</b><b>MEASURE</b></div></div></div>
      <div className="asdlc-reveal"><h3>What a workflow coordinates</h3><div className="asdlc-chip-cloud"><span>requirements & intent</span><span>AI agents</span><span>repository context</span><span>secure sandbox execution</span><span>human approvals</span><span>testing & verification</span><span>pull requests</span><span>deployments</span><span>environment promotion</span><span>production operations</span><span>logs & metrics</span><span>DORA metrics</span></div><p className="asdlc-small-lede">A workflow can continue asynchronously and pause only where engineering judgment is required—then resume once a human has weighed in.</p></div>
    </div>
  </section>

  <section id="human" className="asdlc-section asdlc-rule-top">
    <div className="asdlc-kicker asdlc-reveal"><h2>03 / HUMAN-IN-THE-LOOP</h2></div>
    <p className="asdlc-lede">Developers define intent, make important decisions, and approve outcomes. Between those checkpoints, agents and workflows keep executing—even while the team is offline.</p>
    <div className="asdlc-human-frame asdlc-reveal"><div className="asdlc-human-line"><i /><b /><i /><b /><i /></div><div className="asdlc-human-labels"><strong>Define</strong><span>Understand → Plan → Build → Test <em>(autonomous)</em></span><strong>Review & approve</strong><span>Release → Operate <em>(autonomous)</em></span><strong>Ongoing oversight</strong></div><div className="asdlc-key"><span><i /> Workflow executing autonomously</span><span><b /> Human checkpoint</span></div></div>
    <p className="asdlc-callout asdlc-reveal">Well-defined work can continue asynchronously—and return only when human input is genuinely required.</p>
  </section>

  <section id="day" className="asdlc-section asdlc-rule-top asdlc-alt-bg">
    <div className="asdlc-kicker asdlc-reveal"><h2>How Revolte shapes the developer's day</h2></div>
    <p className="asdlc-lede">This isn't the same work done faster. It's a different set of things a developer spends the day doing.</p>
    <div className="asdlc-day-compare asdlc-reveal"><div className="asdlc-day-block"><small>TRADITIONAL</small><p>Understand → Explore → Code → Test → Fix → PR → Deploy → Monitor → Troubleshoot</p></div><div className="asdlc-day-arrow">WITH REVOLTE</div><div className="asdlc-day-block asdlc-day-new"><small>DEVELOPER</small><p>Define intent → Guide → Decide → Review → Own outcomes</p><div>Understand → Build → Test → Prepare → Release → Observe → Support</div></div></div>
    <p className="asdlc-callout asdlc-reveal">The developer moves higher in the engineering loop—from executing every step to directing the system that executes it.</p>
  </section>

  <section className="asdlc-section asdlc-rule-top">
    <div className="asdlc-kicker asdlc-reveal"><h2>Beyond AI coding</h2></div>
    <p className="asdlc-lede">Revolte isn't limited to the point where an agent finishes writing code. Work moves across the lifecycle without losing context, traceability, human control, or operational feedback.</p>
    <div className="asdlc-loop-list asdlc-reveal"><div>Development</div><i /><div>Delivery</div><i /><div>Deployment</div><i /><div>Operations</div><i /><div>Support</div><i /><div>Measurement</div><i /><div>Improvement</div></div>
    <div className="asdlc-loop-back">↻   feeds back into Development as new engineering work</div>
    <p className="asdlc-callout asdlc-reveal">One engineering lifecycle. Workflows across it. Humans in control.</p>
  </section>

  <section id="next" className="asdlc-section asdlc-rule-top asdlc-alt-bg">
    <div className="asdlc-kicker asdlc-reveal"><h2>Continue in the docs</h2><span>06 / WHERE TO GO NEXT</span></div>
    <div className="asdlc-next-grid asdlc-reveal"><a href="/get-started/quickstart"><strong>Get started with Revolte</strong><span>Connect a repository and run your first workflow end to end.</span><small>READ →</small></a><a href="/workflows/build-from-prompt"><strong>Build with workflows</strong><span>Start from a prompt, codebase, or structured requirement.</span><small>READ →</small></a><a href="/deploy-operate/overview"><strong>Deploy & operate</strong><span>Carry approved work through environments and releases.</span><small>READ →</small></a><a href="/reference/limits"><strong>Platform reference</strong><span>Review supported capabilities and current boundaries.</span><small>READ →</small></a></div>
  </section>
</div>