READINESSOS

Policy: Closed Beta Participation Agreement

Version: 1.0

Effective Date: 06/06/2026

Last Updated: 06/06/2026

Contact: ReadinessOS@proton.me

1. Document Purpose

This Closed Beta Participation Agreement establishes the terms governing participation in the ReadinessOS Closed Beta Program.

The purpose of the Closed Beta is to evaluate platform functionality, identify defects, validate operational workflows, collect user feedback, and improve the platform prior to public release.

Participation in the Closed Beta is voluntary and subject to approval by ReadinessOS.

2. Scope

This agreement applies to:

• Founding Vessel participants
• Invited vessel operators
• Captains
• Designated vessel administrators
• Closed Beta testers
• Future invited professional users
• Any individual granted pre-release access to ReadinessOS

3. Definitions

For the purposes of this agreement:

Closed Beta means a limited-access pre-release version of ReadinessOS.

Beta Participant means any individual or vessel granted access to the Closed Beta.

Experimental Feature means any unfinished or developmental functionality that may change or be removed without notice.

Feedback means bug reports, suggestions, comments, feature requests, screenshots, or other information submitted by participants.

4. Nature of the Beta Program

The Closed Beta is intended solely for evaluation and testing.

Participants acknowledge that:

• Features may be incomplete.
• Errors and bugs are expected.
• Platform behavior may change without notice.
• User interfaces may be redesigned.
• Functionality may be added or removed at any time.
• Data structures may change during development.

The Beta platform should not be considered a production-ready system.

5. Eligibility

Participation is available only by invitation or approval from ReadinessOS.

ReadinessOS may approve or deny participation at its sole discretion.

Beta access may be limited based on vessel type, operational profile, geography, or program capacity.

6. Participant Responsibilities

Participants agree to:

• Use the platform responsibly.
• Test features in good faith.
• Report bugs when practical.
• Avoid intentional misuse.
• Protect account credentials.
• Maintain confidentiality where requested.
• Avoid disrupting platform operations.

Participants remain responsible for all activity occurring under their account.

7. Feedback

Participants are encouraged to provide feedback regarding:

• Bugs
• User experience
• Performance
• Missing features
• Workflow improvements
• AI recommendations
• Readiness scoring
• Scenario generation
• Operational usability

Feedback submitted to ReadinessOS may be used without compensation to improve the platform.

8. Experimental AI Features

The Closed Beta may include artificial intelligence features that generate:

• Scenario recommendations
• Readiness suggestions
• Operational summaries
• Educational content
• Competency recommendations
• Risk analysis
• Automated insights

Participants acknowledge that AI-generated content may contain inaccuracies, omissions, or inappropriate recommendations.

Human review remains essential before relying on AI-generated outputs.

9. Confidentiality

Certain Beta features, screenshots, documentation, or unreleased functionality may be confidential.

Participants agree not to publicly disclose confidential Beta information that has not been officially released by ReadinessOS unless authorized in writing.

This provision does not restrict lawful reporting or rights provided by applicable law.

10. Platform Availability

The Closed Beta is provided on an "as available" basis.

ReadinessOS does not guarantee:

• Platform uptime
• Continuous availability
• Data preservation
• Performance
• Feature stability
• Compatibility
• Error-free operation

Service interruptions should be expected.

11. Data Resets

Participants acknowledge that during development:

• Databases may be reset.
• Test data may be deleted.
• User settings may be lost.
• Uploaded files may be removed.
• Platform configurations may change.
• Development migrations may affect stored information.

Participants should avoid relying on Beta environments for permanent storage.

12. Account Removal

ReadinessOS may suspend or terminate Beta participation at any time, including for:

• Misuse
• Fraud
• Abuse
• Security concerns
• Violation of platform policies
• Inactivity
• Program restructuring
• End of the Beta program

Removal from the Beta does not create any right to compensation.

13. Intellectual Property

All platform software, documentation, interfaces, algorithms, AI systems, branding, and related intellectual property remain the exclusive property of ReadinessOS.

Participation in the Beta does not transfer ownership or licensing rights beyond the limited right to access the platform.

14. Safety Disclaimer

ReadinessOS is an operational readiness support platform.

The Beta platform does not replace:

• Captain judgment
• Company procedures
• Safety Management Systems
• Regulatory compliance
• Flag State requirements
• Classification society requirements
• STCW requirements
• SOLAS obligations
• MARPOL obligations
• Professional maritime decision-making

Participants remain solely responsible for operational decisions.

15. Limitation of Liability

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

• Beta software defects
• Downtime
• Missing functionality
• Incorrect recommendations
• AI-generated content
• Data loss
• Service interruptions
• Platform changes
• Development resets

Participants use the Beta platform entirely at their own discretion and risk.

16. Relationship to Other Policies

This agreement should be interpreted together with:

• Terms of Service
• Privacy Policy
• Data Ownership Policy
• Founding Vessel Program Terms
• Account Suspension and Fraud Policy
• Readiness Engagement Policy

Where conflicts exist regarding privacy matters, the Privacy Policy shall govern.

17. Policy Updates

ReadinessOS may revise this agreement as the Beta program evolves.

Continued participation after publication of updated terms constitutes acceptance of the revised agreement where permitted by applicable law.

18. Revision History

END OF DOCUMENT