Purpose and scope

OpenOS-Project-OSP preserves operational access to open systems work. Its role is to make recovery paths, synchronization boundaries, and provenance visible without treating any single forge as the definition of the project.

Responsibilities

• Maintain accessible repository or project copies and recovery endpoints.
• Record the authoritative upstream and synchronization direction.
• Prefer open formats, replaceable components, and portable automation.
• Treat documentation, accessibility, recovery, and operability as core work.
• Preserve upstream attribution and licensing at every hosted endpoint.

Repository boundaries

A copy does not automatically become an authoritative upstream. Every hosted repository or project should state whether it is canonical, a maintained mirror, an archival copy, or an experimental integration. Its local README, license, and contribution guidance govern participation at that endpoint.

Platform independence

Git hosting services use different terms—including organization, group, workspace, repository, and project—for similar concepts. OSP documentation uses neutral terms where possible and confines provider-specific configuration to deployment adapters such as an individual forge's workflow directory.