LEX ASTRA ACADEMY CS 260 / Relief reception and onward movement Lex Astra · School of Civil Practice Teaching edition 2956.3 / Hybrid ———————————————————————————————————————————————— LEARNER WORKSHEET For civil coordinators handing work between recovery, transport and reception services. This is a private working copy. Downloading submits nothing and records no completion. Use exercise identifiers, not private player information. ———————————————————————————————————————————————— SESSION DETAILS Learner identifier: ____________________________________________________________ Instructor / assessor: ____________________________________________________________ Session date / agreed role or variant: ____________________________________________________________ Vessel, configuration and equipment: ____________________________________________________________ LIVE build / capability test date / tested by (if practical): ____________________________________________________________ Stop signal / recovery contact / communication arrangement: ____________________________________________________________ ———————————————————————————————————————————————— PURPOSE Connect Solace Horizon Relief, CradleFleet and HavenGate so a completed flight does not leave the next need unassigned. COURSE CONTEXT The case uses the present 2956 responsibilities of Solace Horizon Relief, CradleFleet and HavenGate. It is a teaching extension, not a reconstruction of a historical evacuation. ———————————————————————————————————————————————— ENTRY Complete: CS 202, CS 220 Equipment: The Solace–CradleFleet–HavenGate case and a shared reception record. ———————————————————————————————————————————————— CASE: Arrival is accepted; onward places are not 1. Solace hands four participants to CradleFleet for transport after the agreed recovery drill. 2. CradleFleet can carry four. HavenGate acknowledges all four on the reception list. 3. HavenGate can plan onward places for two in this case; the other two need a later decision. ———————————————————————————————————————————————— TECHNICAL KNOWLEDGE AND GAME SKILLS Sustaining a relief group in the game Practical instruction revision 1 / 9 October 2026 Inspect the receiving location Confirm landing access, breathable areas, usable medical care and routes to supplies at the proposed reception site. A map label does not establish that the group can enter or use every service. Walk one person’s journey from ramp to reception and identify where a mobility limitation or missing permission stops it. Supply immediate playable needs Organise environmental equipment, food, drink and transport around the actual session. Demonstrate item transfer and confirm that recipients can equip or use the item. Keep helmets on until breathable conditions are confirmed. Medical supplies and symptom relief support movement, but do not erase the need for a bed that can heal an injury. Separate implemented services from the scenario Record live transport, item transfer and medical interactions as observed actions. Treat housing allocations, civic placements or longer-term settlement promises as tabletop arrangements unless that exact service is playable and demonstrated. A relief plan can be rigorous without pretending the game implements a permanent resettlement system. PRACTICAL DRILL Inspect a reception site, transfer a small practical supply kit and trace one passenger with a simulated mobility limitation to appropriate care. Record onward arrangements separately from completed game interactions. OBSERVED-SKILL CHECKS Access and essential services are physically checked. My action / observed result / assistance / evidence reference: ____________________________________________________________ Live, simulated or unobserved: ____________________________________________________________ Recipients can actually use the delivered supplies. My action / observed result / assistance / evidence reference: ____________________________________________________________ Live, simulated or unobserved: ____________________________________________________________ The record clearly distinguishes live assistance from tabletop commitments. My action / observed result / assistance / evidence reference: ____________________________________________________________ Live, simulated or unobserved: ____________________________________________________________ Apply the technical checks in the agreed role. Discussion and simulation do not certify live handling; Crew Support evidence does not confer Pilot qualification. GAME REFERENCES The linked pages were read for this revision. Community references mix release eras; each source note identifies what is used and what is excluded. Technical explanations below are an Academy synthesis, and drills and performance checks are Academy-designed. Before practice, compare the named actions with the installed LIVE build and actual equipment. Bind actions by name rather than copying old default keys. Research is not an in-game validation. Star Citizen Wiki — Medical https://starcitizen.tools/Medical Body-part injuries, Hemozal, symptom medication, BDL, bed tiers and regeneration. Ship tables, resource costs and ranges change; inspect the actual bed and tool. Star Citizen Wiki — Cargo https://starcitizen.tools/Cargo SCU, container geometry, grids and ownership. The page also contains obsolete automatic-loading descriptions and future design intentions; these are not instructions for the present cargo interface. Star Citizen Wiki — Controls https://starcitizen.tools/Guide:Controls Control categories, movement axes and targeting concepts. The page contains legacy bindings and flight-system descriptions; use the installed game’s bindings, not its key table. Official LIVE release check: https://robertsspaceindustries.com/patch-notes ———————————————————————————————————————————————— METHOD 1: Name the next service and receiver Solace Horizon Relief handles the recovery and medical-reception side of the case; CradleFleet handles passenger carriage; HavenGate handles onward reception and resettlement planning. Confirm the role accepting the next task, not just the institution named on the destination. A service chain transfers responsibilities, not merely lists of names. Ask each receiving role to state the task it accepts and the limit of that acceptance. In the case, transport may end at reception while onward placement remains a separate decision; make that boundary visible before the flight is treated as the end of assistance. Practise: Map the handovers across the three services. Ready when: Every stage has an accepting role and a clear limit to what it can provide. My action and observed result: ____________________________________________________________ Evidence reference: ____________________________________________________________ ———————————————————————————————————————————————— METHOD 2: Give unmet needs a next decision List what cannot be provided now, who will follow it up and when the receiving team will review it. Keep a deferred need separate from a completed transfer. Use the case information rather than asking participants for private histories. Use an open-needs register with a specific next action, responsible role and review point. “Awaiting assistance” does not tell the next coordinator what to do. Prefer “Onward place unconfirmed; reception coordinator to request capacity before the next movement brief,” which preserves both the gap and a practical route to resolving it. Practise: Prepare the open-needs list. Ready when: Every unmet need has an owner and a practical next review action. My action and observed result: ____________________________________________________________ Evidence reference: ____________________________________________________________ ———————————————————————————————————————————————— METHOD 3: Match the record to the work performed Distinguish the passenger movement you actually conduct from the reception and resettlement decisions discussed at the table. Record each for what it demonstrates. A well-written reception plan is useful work, but it is not proof of a service or mechanic that was never performed. Use the fictional reception setting to examine professional obligations without inventing a game service. Live movement, tabletop allocation and a proposed onward arrangement are different kinds of evidence. The value of the conference is its coherent plan and accepted responsibilities; it need not claim that an unimplemented settlement system performed the work. Practise: Mark which parts of the relief chain were performed and which were discussed. Ready when: The record accurately describes the delivery method and observed work at every stage. My action and observed result: ____________________________________________________________ Evidence reference: ____________________________________________________________ ———————————————————————————————————————————————— WORKED DECISION CradleFleet completes the flight. HavenGate accepts a reception planning task but has not assigned onward places. The receiving record keeps that need open. 1. Confirm the Solace-to-CradleFleet handover and carry the relevant game-status limits into transport. 2. Record four received only after the reception check. Keep the separate onward-placement field at two confirmed and two pending. 3. Give the pending pair a HavenGate follow-up role and next review. Do not retain the task vaguely with “civil services” or call the transport incomplete when reception itself was accepted. ———————————————————————————————————————————————— YOUR EXERCISE Map the three handovers and complete the open-needs register. Identify which actions you performed and which reception decisions were tabletop work. WHAT CHANGES The receiver accepts arrival but cannot commit to the next service. My decision and reason: ____________________________________________________________ ———————————————————————————————————————————————— YOUR WORKING RECORD Sending service / receiving role / exact task accepted ____________________________________________________________ ____________________________________________________________ Transported / received / onward arrangement status ____________________________________________________________ ____________________________________________________________ Unmet need / responsible service and contact / next review ____________________________________________________________ ____________________________________________________________ ———————————————————————————————————————————————— CHECK YOUR REASONING HavenGate has acknowledged the passenger list. Does that settle onward placement? My answer before consulting the explanation: ____________________________________________________________ ____________________________________________________________ ———————————————————————————————————————————————— EVIDENCE TO KEEP A receiving chain, open-needs list and clearly scoped case conference. Criterion 1: Every stage has an accepting role and a clear limit to what it can provide. Individual evidence / finding / assessor's reason: ____________________________________________________________ Criterion 2: Every unmet need has an owner and a practical next review action. Individual evidence / finding / assessor's reason: ____________________________________________________________ Criterion 3: The record accurately describes the delivery method and observed work at every stage. Individual evidence / finding / assessor's reason: ____________________________________________________________ ———————————————————————————————————————————————— FINDINGS AND NEXT ATTEMPT Demonstrated: observed work meets the criterion. Further practice required: an observed gap needs a specific practice task. Interrupted: conditions prevented valid assessment; not a failure. Not assessed: enough evidence has not yet been collected. All three criteria need individual evidence. A team result or quiz cannot replace an unobserved practical. Practice variant for a fresh attempt: Let HavenGate accept all onward planning but reduce CradleFleet capacity. The unresolved task should move to the correct service. My next practice task: ____________________________________________________________ Review contact: ____________________________________________________________ ———————————————————————————————————————————————— COMPARE AFTER ANSWERING Not unless it accepted that specific task and confirmed the arrangement. Record what it accepted and leave the placement need open with an owner and next update. ———————————————————————————————————————————————— SOURCE AND EDITION Case CS–3: one berth remaining /academy/archives/reception-case Civil Practice case issued by CDR Yuki Tanaka-Reis in 2956. These variants use present-day service responsibilities and new training lists; they are not transcripts of the Pyro Station Alpha response. The lessons are current Academy teaching, not newly discovered historical records. Lex Astra opened in 2891. Historical sources keep their original issuer and date; all case callsigns, quantities, times and conditions are supplied for practice. Course text revised 8 October 2026; fictional teaching edition 2956.3. ———————————————————————————————————————————————— PROFESSIONAL REFERENCES Instruction revised 9 October 2026. Lex Astra cases supply the teaching situations. Professional references inform communication, decision-making and instructional design; they do not confer external qualifications. LIVE capabilities remain subject to the recorded session check. AHRQ · structured team communication https://www.ahrq.gov/teamstepps-program/curriculum/communication/index.html Sphere · accountability and continuity in relief cases https://www.spherestandards.org/handbook/ RSI · verify release notes before live delivery https://robertsspaceindustries.com/patch-notes ———————————————————————————————————————————————— INSTRUCTOR CHECK Try the exercise with the ship and equipment you will use. Brief station assignments, callsigns, channel and recovery point. Explain the command “Stop exercise” before starting. If a bug prevents completion, repeat the affected task when it works. Ask before recording the session; use player handles in your notes. Review rules: /academy/archives/academy-ordinance Teaching basis: /academy/framework#research