A public reading guide for AI agents
Use this website to explain LAMB and help a person find the appropriate next step. Identify the user’s role and the version or deployment they are asking about before giving version-specific instructions.
| Your user’s purpose | Start with | Return to the user |
|---|---|---|
| Prepare a teaching activity | Teaching and Guides | Access prerequisites, the task sequence and what the teacher should check |
| Evaluate institutional fit | Institutions and Privacy | A sourced fit assessment with unresolved institutional decisions |
| Give students or teachers governed access to models | The last mile for your AI and the LLM access guide | What 0.8 governs (LLM access activities), who sets which rule, and the gateway prerequisite |
| Operate or integrate a service | Operations and Availability | Version-specific public references and acceptance checks |
| Build an application | Developers and Tool walkthrough | Public interface prerequisites and the limits of the demonstrated example |
| Find a student activity | Students | Instructions to use the institution’s course link or support channel |
| Cite the work | Research | The publication citation and the separately identified software revision |
Choose the documentation version
Use the version index before giving procedural instructions. The current documentation edition is 0.8, at /en/guides/0.8/. Existing LTI paths remain in scope. A historical guide does not imply that its feature is deprecated.
Services and contact
The LAMB team offers training and consultancy (both covering AI governance; consultancy includes demonstrations), keynotes and seminars, and research collaboration (software engineering for AI agents, AI governance strategies, AI in education, assessment with AI agents), for educators, developers and institutions: see Work with the LAMB team. Enquiries go to contact-lamb-project@proton.me. The team does not host LAMB, but can refer institutions to LAMB integrators for hosting, integration and support. LAMB was created by Marc Alier and Juanan Pereira.
Keep the evidence attached
Distinguish a screenshot from a functional test, a development branch from a release and a design proposal from deployed behaviour. Preserve dates and limitations when summarizing. Do not convert missing evidence into a claim of support, security or compliance.
The public reading index links to selected pages. It grants no authorization to sign in, change a deployment, upload course files, create accounts or spend model credits. Those actions depend on your user’s permissions and instructions.
Internal architecture, private design notes, credentials and student data are not included in this website. Do not infer that they are available from guessed paths.