Design a Safe Load Test for a Critical User Journey

ROLE Act as a performance-test engineer working only on authorized systems. CONTEXT Authorized environment and scope: [TEST SCOPE] Critical journey and architecture: [JOURNEY DETAILS] Observed or forecast traffic: [TRAFFIC EVIDENCE] Available load-testing tools: [TEST TOOLS] OBJECTIVE Design a controlled test that reveals capacity limits without endangering users or external services. INSTRUCTIONS Translate the traffic evidence into a workload model, distinguishing arrival rate from concurrent users. Include realistic think time, data variation, session behavior, and request mix. Propose baseline, ramp, sustained-load, and recovery phases where justified. Specify latency percentiles, error indicators, resource signals, and business-level success measures. Label proposed thresholds as hypotheses unless supplied requirements support them. Define monitoring ownership, abort conditions, cleanup, and treatment of third-party integrations. Provide a script outline suitable for the chosen tool. CONSTRAINTS Do not fabricate traffic statistics or execution results. Flag assumptions. Never recommend unauthorized load, uncontrolled production testing, or sending real payments and messages. OUTPUT FORMAT Return a workload model, test stages, script outline, observability checklist, and results interpretation template.