# Runlight Full Public Context ## Product Runlight gives a bookable business a Presence inside ChatGPT. Internally, the shorthand is: Runlight turns a business into an app inside ChatGPT. Runlight's primary category is bookable service businesses. The initial wedge is salons and adjacent appointment businesses. Support for any exact business depends on current representation authority, publication state, provider and native capability, and verified completion semantics. ## Canonical model The product chain is: business identity -> representation authority -> approved context -> Presence -> provider and social capabilities -> customer activity -> owner attention -> evidence -> owner decision -> approved change Runlight owns canonical business state, authority, evidence, policy, customer intent, and completion semantics. Providers remain capability edges. A provider may ingest, normalize, execute, reconcile, or project within its exact supported and authorized scope. Machine Presence compiles one canonical authority-backed business model into synchronized human, search, answer-engine, agent, and ChatGPT representations. It is a projection layer, not an authority source. ## Authority boundaries - Anyone may privately organize or self-attest a business. Public representation requires current independently sourced evidence under explicit policy for the exact scope. - Representation Assurance is separate from fact truth, provider access, transaction authority, payment authority, and publication approval. - A provider connection does not grant owner, publication, booking, or payment authority. - A business can be understood or published without implying that every action is executable. - Repository implementation does not establish deployment, configuration, provider currentness, activation, publication, or customer usability. ## Booking Runlight's direction is first-class booking inside ChatGPT. A booking route is presented as complete only when it preserves the customer's exact selected business, service, staff, time, applicable requirements, confirmation lineage, and completion truth. Execution may use a faithful provider-direct commit, exact hosted completion, reserved provider transaction, or Runlight-native execution. A generic provider page that makes the customer repeat material choices is guidance or handoff, not equivalent first-class completion. Runlight does not unnecessarily recreate card entry, payment processing, or a generic scheduler. Provider compatibility remains configuration and capability specific. ## Current availability Availability is exact-business specific. When its owner runtime is configured, the Control Centre is the intended surface for business-specific state and limitations. A source route does not establish hosted owner access, and source contracts at different stages do not establish a live or usable customer route. ## Retired agency offer The founder-delivered manual Runlight Review has retired, together with Solo and Studio fixed pricing, checkout, intake, and follow-on agency services. The `/review` page remains only to explain the retirement to old bookmarks and previous buyers. Source retirement does not establish the state of external Stripe links, hosted forms, prior purchases, or third-party bookmarks. Those remain UNKNOWN until a separately authorized closure check is completed. ## Public context files - /llms.txt - /runlight.json - /api/runlight/context These surfaces explain product direction and boundaries. They do not establish deployment, connection, publication, or availability for an exact business.