READINESSOS

Policy: Vessel Seat Management Policy

Version: 1.0

Effective Date: 06/06/2026

Last Updated: 06/06/2026

Contact: ReadinessOS@proton.me

1. Document Purpose

This Vessel Seat Management Policy establishes how ReadinessOS manages vessel subscriptions, crew seats, user assignments, relief personnel, temporary personnel, and future multi-user access permissions.

The objective of this policy is to clearly separate professional identities from vessel-owned crew positions while providing a scalable subscription model for vessel operations.

2. Scope

This policy applies to:

• Vessel accounts
• Vessel administrators
• Captains
• Designated operators
• Crew memberships
• Vessel crew positions
• Relief crew
• Temporary crew
• Contractors
• Future fleet accounts
• Subscription seat allocation

3. Definitions

For the purposes of this policy:

Seat means an active crew allocation available within a vessel subscription.

Crew Position means a vessel-owned operational role.

Member means a professional user assigned to a vessel.

Relief Crew means a temporary replacement assigned to an existing vessel position.

Temporary Seat means an additional subscription seat purchased beyond the included allocation.

4. Core Architecture

ReadinessOS separates:

• Professional User
• Vessel Membership
• Vessel Position
• Subscription Seat

These represent independent entities.

A user profile belongs to the individual.

A vessel position belongs to the vessel.

A membership connects a user to a vessel.

A subscription seat permits active participation within the vessel account.

These relationships remain independent throughout the platform.

5. Included Seats

Each active vessel subscription includes a predefined number of crew seats.

At the time of publication:

• One vessel subscription includes ten (10) active crew seats.

ReadinessOS reserves the right to modify subscription structures and future pricing models.

Existing subscription agreements remain subject to their applicable commercial terms.

6. Additional Seats

Vessel operators may purchase additional seats beyond the included allocation.

Additional seats may be:

• Permanent
• Temporary
• Seasonal
• Relief assignments

Future pricing structures may apply discounted rates for additional seats according to the active subscription schedule.

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
• Engineer

Positions remain part of the vessel structure regardless of who occupies them.

8. User Assignment

A vessel position may be assigned to a professional user profile.

Example:

Position:

2nd Engineer

Assigned User:

ROS-000128

The user occupies the position without acquiring ownership of the position itself.

Changing personnel does not remove the vessel position from the vessel structure.

9. Position Status

Each vessel position may maintain an operational status including:

• Active
• Vacation
• Rotation Leave
• Training Leave
• Medical Leave
• Relief Assigned
• Vacant
• Inactive
• Terminated

Position status is managed by authorized vessel administrators.

10. Relief Crew

Relief personnel may temporarily occupy an existing vessel position.

Examples include:

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

Relief users maintain their own independent professional profiles and readiness history.

Participation during relief assignments is recorded against the relief individual.

11. Vacation and Leave

Crew members on vacation or leave remain associated with the vessel unless removed by an authorized vessel administrator.

Vacation status does not automatically:

• Remove vessel membership
• Release a subscription seat
• Delete historical records
• Remove position assignments

Vessel administrators determine how leave periods are managed.

12. Temporary Personnel

Vessels may assign temporary personnel for operational purposes including:

• Contractors
• Temporary crew
• Dayworkers
• Survey support
• Shipyard personnel
• Seasonal crew

Temporary personnel may require additional subscription seats depending upon platform configuration and active participation.

13. Seat Ownership

Subscription seats belong to the vessel subscription.

Seats do not belong to individual users.

Changing personnel does not transfer ownership of the seat.

Seat allocation remains under the control of authorized vessel administrators.

14. Seat Reassignment

Authorized vessel administrators may:

• Assign seats
• Remove seats
• Replace crew
• Assign relief crew
• Transfer positions
• Release inactive members
• Purchase additional seats

Historical readiness records remain attached to the participating professional user.

15. Readiness Participation

Readiness activities must always be recorded against the actual individual who participated.

Participation is not automatically assigned based upon vessel position.

Example:

If a Relief 2nd Engineer participates in an Engine Room Fire Drill, the participation record belongs to the relief engineer rather than the absent permanent crew member.

16. Future Multi-User Permissions

Future versions of ReadinessOS may support permission levels including:

• Vessel Owner
• Vessel Administrator
• Captain
• Department Head
• Engineer
• Crew Member
• Observer
• Auditor

Permission models may evolve as platform functionality expands.

17. Subscription Changes

Changes to vessel subscription plans may affect:

• Included seat allocation
• Maximum active users
• Additional seat pricing
• Temporary seat availability
• Fleet integration
• Administrative permissions

Subscription modifications remain subject to applicable commercial agreements.

18. Relationship to Other Policies

This policy should be interpreted together with:

• Terms of Service
• Crew Membership Policy
• Professional Profile Policy
• Data Ownership Policy
• Account Suspension and Fraud Policy
• Readiness Passport Policy
• Privacy Policy

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

19. Policy Updates

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

Updated versions become effective upon publication unless otherwise specified.

20. Revision History

END OF DOCUMENT