Skip to content

Explanation

Explanation pages are for understanding. They discuss why the platform is shaped the way it is, how its pieces fit together and what trade-offs were made. Nothing here is a step to follow; for steps, see the how-to guides.

  • Platform overview: the bench and its eight tools, the nine stages a project runs through, and the three interfaces.
  • Context before code: why Alis Ideate Projects keep the source, Interviews ask the people who know, and Artifacts carry it to people who act on it.
  • Define, Build, Deploy: why Alis Build DBD has three steps and what each one guarantees.
  • Organisations, products and services: the hierarchy of Alis Build Environments, from a build environment down to a service, and the two repositories behind every product.
  • Deployment environments and versions: where a version runs, immutable versions, designated branches, the production gate.
  • Agents, skills and the CLI: why the CLI is built for machines first, and how skills teach an agent the platform.
  • How skills work: the loop from capture to feedback, why skills load live, where they come from, the safety scan and policy-aware search.
  • How artifacts work: versions, publishing, links and who can open them, and what to check before you share.
  • How workstations work: your machine in a build environment, its addresses, why it sleeps rather than stops, ssh, work on a clock and sharing.
  • How build activity is measured: build time, agent orchestration and the flow score on Activity, and why a day can have no score.
  • How Makefiles work: Make's ideas, the Makefile contract every service follows and why, and the traps by symptom.
  • How code blocks work: a versioned snapshot of a working service, installed as a branch, with its own skill.
  • How releases work: release the build and keep the source, what crosses into another product, and moving code to a new owner safely.
  • How AlisX Specialists work: who receives a ticket, where it stands, how AI helps and never answers for people, and who sees what.
  • Accounts and billing: people, accounts, roles, Ideate access and Build access, the active account, one credit meter and the monthly invoice.