Three things make an agent yours. An identity says who it is, a pack gives it tools, and a site puts it on the web. Each section below shows the whole path in a few steps, then hands you to the guide that walks it through.
An identity is your agent's name, voice and routing, with the specialists it can ask and the packs it uses. It has no tools of its own.
demos/{name}/identity/, with its prompts embedded the way a pack's are.demos/puls/hosts/louis-agent.host-packs, then load it with IDENTITIES. demos/puls/identity/louis-agent.identity.puls is a real one to read beside the guide.A pack is a set of tools with a guide that tells the model when to use them. It names no identity and references no other pack, so an MCP server could serve it as it is.
packs/tools/, which references no other pack.CodingCatalog does, then try it in a chat. packs/tools/louis-agent.pack.where-to-buy is the closest real one, with one tool and no settings.A new site starts from the starter template, with a chat, an admin and a plain landing page. It holds only its own name and words. For now it works inside this repo, since the framework isn't a package yet.
dotnet new install demos/starter/web/louis-agent.starter, then dotnet new louis-site -n Acme -o demos/acme/web/acme. It comes with a chat, an admin and a landing page.louis-agent-solution.sln under demos/acme/web, since a test holds the solution's tree to the disk.demos/louis-agent/hosts/louis-agent.coding-api, name your identities and packs in it, and reference your site.