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

# Agent Development Lifecycle

> From a blank directory to a running, managed agent.

Building an agent follows the same four phases regardless of language or framework. The first two need no cluster.

<Steps>
  <Step title="Scaffold">
    `nasiko new` generates an `AgentCard.json`, a `Dockerfile`, and starter source for your framework. `nasiko card` keeps the card in sync with your code; `nasiko validate` checks the structure.
  </Step>

  <Step title="Run and chat locally">
    Run the agent as a plain container. It speaks A2A on start, so you can chat with it over HTTP or in a TUI and iterate before anyone else sees it.
  </Step>

  <Step title="Deploy and manage">
    Nasiko builds (or takes a pre-built image), pushes it to the cluster registry, and starts the container — instrumented for observability and wired to its secrets. Then: logs, scaling, restarts, teardown.
  </Step>

  <Step title="Versions and lifecycle">
    Redeploying the same name updates in place. The `AgentCard.json` version is the image tag tying a deployment to a build. Artifacts published to the registry carry their own version history.
  </Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Scaffolding" icon="wand-magic-sparkles" href="/adlc/agent-scaffolding">
    Generate a project and its agent card.
  </Card>

  <Card title="Run and chat locally" icon="play" href="/adlc/build-run-test">
    Build, run, and chat before touching a cluster.
  </Card>

  <Card title="Deploy and manage" icon="rocket" href="/adlc/deploy">
    Logs, scaling, restarts, secrets, teardown.
  </Card>

  <Card title="Versions and lifecycle" icon="code-branch" href="/adlc/versions-lifecycle">
    How versions map to deployments.
  </Card>
</CardGroup>

## Before you start

You need Docker and the `nasiko` CLI — see [CLI installation](/cli/setup).