READINESSOS

Policy: Crew Membership Policy

Version: 1.0

Effective Date: 06/06/2026

Last Updated: 06/06/2026

Contact: ReadinessOS@proton.me

1. Document Purpose

This Crew Membership Policy establishes how professional users become associated with vessel accounts within ReadinessOS and defines the relationship between individual professional profiles and vessel-owned operational positions.

The objective of this policy is to maintain a clear separation between permanent professional identity and temporary vessel assignment while preserving accurate readiness history throughout a user's career.

2. Scope

This policy applies to:

• Professional user accounts
• Vessel accounts
• Vessel administrators
• Captains
• Designated operators
• Crew assignments
• Relief crew
• Temporary crew
• Contractors
• Future fleet accounts
• Future Readiness Passport records

3. Definitions

For the purposes of this policy:

Professional User means an individual who owns a ReadinessOS professional profile.

Crew Membership means the relationship connecting a professional user to a vessel account.

Crew Position means a vessel-owned operational role.

Assignment means the temporary or permanent connection between a professional user and a vessel position.

4. Core Architecture

ReadinessOS distinguishes between:

• Professional User
• Vessel Membership
• Vessel Position
• Readiness Participation

These represent separate entities within the platform.

Professional users own their identity and readiness history.

Vessels own their crew structure and operational positions.

Membership connects the two without transferring ownership.

5. Professional Identity

Every professional user maintains a permanent ReadinessOS Identity.

Examples:

• ROS-000128
• ROS-000254

Professional identity remains associated with the individual regardless of vessel changes, employer changes, or geographic location.

A user's readiness history follows the user throughout their career.

6. Vessel Membership

A professional user may become a member of a vessel through assignment by an authorized vessel administrator.

Membership may include:

• Captain
• Officer
• Engineer
• Interior
• Deck
• Galley
• Contractor
• Relief Crew
• Observer

Membership does not transfer ownership of vessel records to the user.

7. Crew Positions

Crew positions belong exclusively to the vessel.

Examples include:

• Captain
• Chief Officer
• Chief Engineer
• 2nd Engineer
• Bosun
• Deckhand
• Chief Stewardess
• Stewardess
• Chef
• Mate

Positions remain part of the vessel structure regardless of the assigned individual.

8. Assignment Rules

A professional user may be assigned to a vessel position.

Example:

Position:

2nd Engineer

Assigned User:

ROS-000128

The user occupies the position while assigned but does not own the position itself.

Position ownership remains with the vessel.

9. Membership Status

Crew membership may have one of the following statuses:

• Pending
• Active
• Vacation
• Rotation Leave
• Training Leave
• Medical Leave
• Relief Assignment
• Suspended
• Removed

Status changes do not automatically remove historical participation records.

10. Relief Crew

A vessel may temporarily assign relief personnel without permanently replacing the assigned crew member.

Examples include:

• Relief Captain
• Relief Engineer
• Temporary Steward
• Contractor
• Dayworker

Relief personnel maintain their own independent ReadinessOS Identity and professional history.

Readiness participation is recorded against the relief individual who actually participated.

11. Multiple Vessel Membership

Future versions of ReadinessOS may permit professional users to maintain relationships with multiple vessels over time.

Historical vessel memberships remain attached to the user's professional history unless removed in accordance with applicable law or platform policy.

12. Readiness Participation

Readiness records must always reflect the actual individual participating in the activity.

Examples include:

• Drill participation
• Scenario reviews
• Observations
• Corrective actions
• Readiness meetings
• Training sessions

Participation records belong to the participating user while simultaneously contributing to vessel readiness history.

13. Membership Removal

Removing a professional user from a vessel:

• Ends the active vessel membership
• Does not erase historical participation
• Does not remove Career Timeline history
• Does not remove Readiness Passport history
• Does not delete professional profile information

Historical records remain preserved for auditability and continuity.

14. Privacy

Professional profile information remains subject to user visibility settings and platform privacy controls.

Vessel administrators may access membership information necessary for operational management.

Professional information outside vessel operations remains subject to applicable privacy settings.

15. Future Expansion

Future platform versions may support:

• Multi-vessel memberships
• Fleet organizations
• Rotational assignments
• Contractor management
• Agency personnel
• Temporary assignments
• Marketplace integration
• Recruiter visibility
• Professional networking

Future functionality will preserve the separation between professional identity and vessel ownership.

16. Relationship to Other Policies

This policy should be interpreted together with:

• Terms of Service
• Professional Profile Policy
• Vessel Seat Management Policy
• Readiness Passport Policy
• Career Timeline Policy
• Data Ownership Policy
• Privacy Policy

Where conflicts exist regarding personal information processing, the Privacy Policy shall govern.

17. Policy Updates

ReadinessOS may revise this policy as membership models, platform architecture, subscription structures, or legal requirements evolve.

Updated versions become effective upon publication unless otherwise specified.

18. Revision History

END OF DOCUMENT