Choose your path

Choose the path that matches the system relationship you are designing now. The paths are not a maturity ladder, skill ranking, or organization-size ranking. A reader may overlap them; use the one whose deployment and operating responsibility is in scope today.

Builder

You are a person or small team adding AnswerUp to an application, private agent, automation, or privately operated business workflow you control. This can be a real business system, not a toy or learning exercise. A compact representative shape is a private field-service or consulting application that approves and sends a customer estimate. The builder owns the application, credentials, policy, durable action record, and user-facing wording. Read the Core lifecycle, Trusted context, Grounding and candidates, and Authorization.

Business

You are an organization integrating AnswerUp into internal or customer-serving systems with centralized identity, policy, multiple authoritative systems, operational teams, and governance requirements. For example, an employee-facing enterprise assistant may request revocation of a departing contractor’s access. The organization owns shared controls, credentials, durable records, monitoring, and operator wording. Read Provider and verifier responsibilities, Reconciliation, Safe claims, and Security and privacy.

Product Maker

You are a team embedding AnswerUp into a reusable product used by your own customers or tenants. You own the customer-facing product boundary, tenant isolation, public claims, support behavior, and product-level operational records. A representative product may let an authorized logistics customer reroute a shipment. Begin with the Core lifecycle, then use Package and SDK boundaries, Handling every result, Durable action records and logging, and Current release status.

In every path, learn the lifecycle first and keep proposal, authority, evidence, effect truth, and claim distinct. The same person or organization can occupy more than one path; choose the relationship and responsibility that the current architecture must make explicit.