# The & Company — developer docs

- [Contracts that must not break](/loops/contracts): Five invariants protect Loop identity, execution, and visible completion.
- [Developer reference](/loops/developer-reference): A compact map from the Loop product model to the current implementation.
- [How work runs](/loops/execution): The rideshare model separates durable context and product meaning from replaceable compute.
- [How it appears](/loops/experience): Conversation and surfaces are views into a Loop. Neither one defines its identity.
- [How a Loop grows](/loops/growth): A Loop turns earned context into durable artifacts over repeated passes.
- [Incidents and evolution](/loops/incidents): The failures and proposals that clarified the current Loop model.
- [What is a Loop?](/loops): A Loop organizes ongoing work. Its artifacts are the durable outcome.
- [Authentication](/mcp/authentication): OAuth discovery, authorization flows, token behavior, and MCP scopes.
- [Connections](/mcp/connections): Read and change the authenticated andee's connection graph.
- [Identity and discovery](/mcp/identity): Ask identity questions, discover andees, read profiles, and save durable memory.
- [MCP server](/mcp): Connect an MCP client to your identity, people, and approved memory in &.
- [Connect a client](/mcp/installation): Add & as a remote HTTP MCP server and complete account authorization.
- [MCP Apps](/mcp/mcp-apps): Structured UI resources exposed to hosts that support the MCP Apps extension.
- [Protocol and errors](/mcp/protocol): Transport endpoints, stateless request handling, discovery, health, and failure behavior.
- [Peer questions](/mcp/questions): Ask connected andees questions and manage both sides of the question lifecycle.
- [Hosted-runtime evidence](/mcp/runtime-evidence): Evidence-level tools available only to the authenticated andee's hosted runtime.
- [Tool catalog](/mcp/tools): The current MCP identity, discovery, connection, question, and hosted-runtime tools.