<aside>
<img src="notion://custom_emoji/49de0235-e8bc-4eca-bf20-2a9d6d267a02/13d2d19c-5547-8036-8175-007a2d47ee9d" alt="notion://custom_emoji/49de0235-e8bc-4eca-bf20-2a9d6d267a02/13d2d19c-5547-8036-8175-007a2d47ee9d" width="40px" />
Working control sheet — November 7, 2026. Not an approval to operate, renovate, admit residents or promise accommodation. Verify permitted use, insurance and approvals before any activity begins.
</aside>
The pilot flies the plane; the airport owns the ground. Oikos is the fixed operator at 175B. Its duty of care is not to direct anyone's calling but to keep the surfaces safe for whoever transits: the runway, the apron, the terminal, the tower, and the investigation that follows a failure.
Serious harm rarely follows one bad decision. It follows several safeguards degrading at once — the Swiss Cheese model this workspace applies to Oikos through the Sentosa Cable Car, Hotel New World and SQ006 cases. This sheet exists to keep the holes from aligning.
1 · Runway — lawful use and structural safety
- Obtain written, site-specific confirmation of permitted use for each activity before it starts. URA's religious-use arrangement applies only to certain approved venue types, requires that premises not be owned by or leased exclusively to religious organisations, and generally limits religious use to two days a week.
- Verify structural, fire-safety and accessibility conditions for every space people are expected to use, including the L3 residential group and the protected pottery studio.
- Stop rule: no activity runs in a space whose permitted use is unconfirmed.
2 · Apron — arrival and handover
- Name a receiving person for every arrival and complete a written handover: keys, room allocation, house rules, emergency contacts.
- Assign transport, night-duty roster and supervision before arrival, not on the day.
- Document storage, cleaning and room-reset routines that do not depend on goodwill.
- Stop rule: no unaccompanied arrival after hours.
3 · Terminal — welcome and safeguarding
- Name a safeguarding lead and publish one escalation path for concerns about a child, a vulnerable adult or a guest in crisis.
- State consent and privacy boundaries at intake: what is recorded, who sees it, how long it is kept.
- Hold a duty-of-care covenant for participants and hosts, distinct from any programme agreement.
- Stop rule: any concern about a minor or vulnerable adult halts the activity until the safeguarding lead has ruled on it.
4 · Tower — watchkeeping and escalation
- Name a duty manager for every operating day, in advance.
- Maintain one visible route to raise a concern and one person authorised to halt an activity.