Skip to main content

Agent-Native SDLC designed

GPUaaS relies on agents, so the SDLC needs explicit work authority, scoped lanes, review domains, evidence, and release ownership.

Rules​

  • Queue task or documented work item is the source of authority.
  • Agents work inside scope, non-goals, stop conditions, and acceptance checks.
  • Non-trivial tasks record evidence before completion.
  • High-risk changes get architecture/governance/security review as appropriate.
  • Implementation agents do not self-approve critical work.
  • Production release remains human-approved.

Practical Execution Model​

The normal path is:

  1. Fairway task defines durable scope.
  2. Provider session attaches to the task.
  3. Desktop coordinates, tmux/CLI executes trusted loops.
  4. Utilities produce deterministic evidence.
  5. Merge/release happens only after the right boundary review.
Canonical sources