> ## Documentation Index > Fetch the complete documentation index at: https://docs.tisabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Platform development > How TIBS development is organized across the main platform, operations, and learning services This page is for developers, technical partners, and teams working on TIBS services. ## Development scope TIBS development is currently organized across three connected application surfaces: * the main rider platform * the survey and operations platform * the learning platform These services are related, but they do not all serve the same audience or use case. ## Main development areas ### Main platform The main platform supports the public rider experience, including: * incident reporting * vehicle lookup * ride feedback * incidents and alerts * corridors, routes, and transport context ### Survey and operations The survey and operations platform supports approved participants and internal operations, including: * surveyor sessions * assignments * vehicle data collection * project workflows * payouts and operational administration ### Learning The learning platform supports: * onboarding * guided learning content * assessments * role-based readiness and progress ## Shared platform model Although these areas are separate, they are designed to work together. Current shared assumptions include: * one connected TIBS identity across services * linked product, survey, and learning experiences * shared transport context across rider and operations workflows At the same time, public, participant-only, and administrator-only experiences remain separate. ## Local development approach Teams working on TIBS commonly need to run multiple services together during development. A practical local setup is: * main platform on one local origin * survey platform on a second local origin * learning platform on a third local origin This separation matters because sign-in state is shared at the identity level, but each service still needs to establish its own session on its own origin. ## Development priorities Current development work across TIBS generally falls into these areas: * product experience and rider trust * transport data quality * survey and operational workflows * learning and readiness flows * legal, privacy, and policy alignment * future external integration surfaces ## Related sections If you are looking for more specific technical material, continue to: * [Repositories](/repositories) * [Shared auth](/repositories/shared-auth) * [API introduction](/api-reference/introduction)