Skip to main content
This is preview documentation. The official release is not yet available.
Connect Agent creation, application integration, Team collaboration, task feedback, and human acceptance through three complete business scenarios. Start with the path closest to your deployment model.

​
How to use these cases

Each case includes roles, prerequisites, steps, inputs, failure paths, and acceptance. Engineering provides Java starter files, checks, an Issue, and CI template. Fulfillment provides business fixtures and SDK integration fragments; implement or connect the business tools. Presales provides customer requirements and knowledge ready for Memory. Complete quickstart and validate individual Agents before building a Team. GitHub commands create or change objects in an exercise repository, so configure identities and authorization scope first. Business and customer fixtures are fictional. The Java fixture was validated before and after repair. Real GitHub, enterprise systems, models, and Team execution require acceptance in your environment. Inputs and expected results are not live execution records. Retain versions, inputs, Issue/Run/Invocation IDs, commits, and real artifacts for future regression checks.