Policy library

ReadinessOS policy framework

Operational Disclaimer Policy

Public ReadinessOS policy document for governance, transparency and operational trust.

Document status

Version1.0
Source24_operational_disclaimer_policy.md
FormatMarkdown

READINESSOS

Policy: Operational Disclaimer Policy

Version: 1.0

Effective Date: 06/06/2026

Last Updated: 06/06/2026

Contact: ReadinessOS@proton.me


1. Document Purpose

This Operational Disclaimer Policy establishes the limitations of ReadinessOS and clarifies the role of the platform in supporting maritime operational readiness.

ReadinessOS is an educational, documentation, readiness management, and decision-support platform designed to assist users in organizing operational information and promoting a culture of preparedness.

ReadinessOS does not direct vessel operations and does not replace qualified human judgment.


2. Scope

This policy applies to:

  • Professional user accounts
  • Vessel accounts
  • Future fleet accounts
  • Readiness Passport records
  • Scenario libraries
  • Drill execution
  • Corrective actions
  • Readiness analytics
  • AI-generated content
  • Operational recommendations
  • Educational material
  • Future platform modules

3. Platform Purpose

ReadinessOS exists to:

  • Improve operational preparedness
  • Encourage readiness culture
  • Facilitate drill planning
  • Organize operational knowledge
  • Track readiness participation
  • Document observations
  • Document corrective actions
  • Support continuous improvement
  • Assist training initiatives

The platform is designed as a support tool for maritime operations.


4. No Operational Authority

ReadinessOS does not exercise operational authority over:

  • Vessel navigation
  • Machinery operation
  • Emergency response
  • Engineering decisions
  • Maintenance decisions
  • Medical treatment
  • Security operations
  • Pollution response
  • Crew management
  • Safety management

Operational authority remains with the vessel command structure.


5. Captain's Authority

Nothing within ReadinessOS replaces or limits the authority of the Master.

The Captain remains solely responsible for:

  • Safe navigation
  • Safe vessel operation
  • Emergency command
  • Crew management
  • Regulatory compliance
  • Operational decisions
  • Voyage planning
  • Safety management

Platform recommendations remain advisory only.


6. Department Responsibility

Department Heads remain responsible for their respective areas including:

  • Engineering
  • Deck
  • Interior
  • Galley
  • Safety
  • Security
  • Medical response

Use of ReadinessOS does not transfer responsibility to the platform.


7. Regulatory Compliance

ReadinessOS is not a regulatory authority.

Use of the platform does not demonstrate compliance with:

  • STCW
  • SOLAS
  • MARPOL
  • MLC
  • ISM Code
  • ISPS Code
  • Flag State requirements
  • Classification Society requirements
  • Company Safety Management Systems
  • Local regulations

Users remain responsible for independent regulatory compliance.


8. AI-Generated Content

Future AI-generated content may include:

  • Scenario recommendations
  • Drill suggestions
  • Readiness analytics
  • Educational summaries
  • Risk observations
  • Equipment suggestions
  • Operational insights
  • Career summaries

AI-generated content may contain inaccuracies or incomplete information.

Human review remains mandatory before operational implementation.


9. Scenario Library Disclaimer

Scenario templates provided by ReadinessOS are educational tools.

Scenarios should be adapted to:

  • Vessel configuration
  • Equipment installed
  • Flag State requirements
  • Company procedures
  • Safety Management System
  • Operational environment
  • Crew competence
  • Current risk profile

No scenario should be executed without appropriate operational review.


10. Drill Disclaimer

Drills organized through ReadinessOS remain under the authority of vessel management.

ReadinessOS does not supervise:

  • Crew safety
  • Equipment use
  • Emergency simulations
  • Machinery operation
  • Navigation safety
  • Live exercises

Users remain responsible for conducting drills safely.


11. Technical Information

Technical information stored within ReadinessOS may originate from:

  • User uploads
  • Equipment manuals
  • AI-generated summaries
  • Administrative records
  • Community contributions
  • Historical documentation

Users should independently verify technical information before operational use.


12. Medical Disclaimer

ReadinessOS does not provide medical diagnosis or treatment.

Medical scenarios, educational material, and AI-generated recommendations are informational only.

Medical emergencies should always be managed by qualified medical personnel or recognized telemedical assistance providers where appropriate.


13. Engineering Disclaimer

Engineering-related information generated or stored within ReadinessOS does not replace:

  • Manufacturer documentation
  • Technical manuals
  • Service bulletins
  • Engineering calculations
  • Professional engineering judgment
  • Classification requirements

Engineering decisions remain the responsibility of qualified personnel.


14. Employment Disclaimer

Professional profiles, badges, readiness history, and Readiness Passports should not be interpreted as:

  • Employment recommendations
  • Competency certifications
  • Hiring endorsements
  • Performance evaluations
  • Professional licensing
  • Qualification validation

Employers remain responsible for independent hiring decisions.


15. Limitation of Reliance

Users should not rely exclusively upon ReadinessOS for:

  • Emergency response
  • Engineering diagnosis
  • Navigation
  • Regulatory interpretation
  • Medical treatment
  • Safety management
  • Operational planning
  • Legal compliance

Independent professional judgment remains essential.


16. Limitation of Liability

To the maximum extent permitted by applicable law, ReadinessOS shall not be liable for losses arising from:

  • Operational decisions
  • Emergency response outcomes
  • AI-generated recommendations
  • Scenario implementation
  • Drill execution
  • Technical information
  • User-generated content
  • Platform downtime
  • Inaccurate records
  • Misinterpretation of platform information

Users assume responsibility for operational implementation.


17. Relationship to Other Policies

This policy should be interpreted together with:

  • Terms of Service
  • AI Usage & Responsible AI Policy
  • Readiness Engagement Policy
  • Platform Security Policy
  • Professional Profile Policy
  • Readiness Passport Policy
  • Privacy Policy

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


18. Policy Updates

ReadinessOS may revise this policy as platform capabilities, AI functionality, maritime regulations, or operational practices evolve.

Updated versions become effective upon publication unless otherwise specified.


19. Revision History

VersionDateDescription
1.006/06/2026Initial production release

END OF DOCUMENT