Governance and Safety
Access classes
| Class | Meaning |
|---|---|
| Public | Metadata or artifacts approved for public distribution. |
| Restricted | Known maintainers may access; redistribution is not authorized. |
| Private | Project-sensitive material with named access rules. |
| Quarantine | Untrusted or legally unclear acquisition awaiting review. |
Classification applies to the bytes and their metadata independently. Public metadata may describe a restricted artifact without exposing it.
Legal and ethical boundaries
- Retain and publish material only when the project has a lawful basis to do so.
- Document licenses and source provenance. Absence of a notice does not mean unrestricted use.
- Reverse engineering is limited to authorized preservation, interoperability, compatibility, security research, and repair work under applicable law.
- Do not use this ecosystem for unauthorized access, bypassing live-service controls, cheating, credential theft, or evasion.
- When rights are uncertain, preserve privately if lawful, record the uncertainty, and seek qualified guidance before redistribution.
- Honor valid takedown, privacy, and security-reporting processes while preserving an audit trail of project decisions.
Security
- Treat legacy binaries, installers, scripts, database dumps, and toolchains as untrusted.
- Inspect and run them in isolated VMs/containers or disposable hosts with minimal privileges and constrained networking.
- Use throwaway credentials. Never reuse personal or production passwords.
- Expose services on loopback by default; document every intentional network exposure.
- Do not commit credentials to source, wiki, manifests, logs, screenshots, packet captures, or clean snapshots.
- Review binary patches and privileged helper changes separately and test rollback.
- Redact personal data and unrelated traffic before sharing findings.
Decision records
Material decisions—such as publishing an artifact, changing preservation format, adopting a compatibility patch, or declaring a baseline—must record date, decision, evidence, alternatives, risks, and responsible maintainer. Link the record from the affected profile.
Wiki permissions
This repository is public and the wiki is readable by anyone with repository read access. Do not enable broad editing without a review process. A compromised or mistaken wiki edit can erase context just as easily as a code change; keep the wiki Git repository in normal backup and review routines.
Private Server Preservation
- Home
- Preservation Status
- Compatibility Matrix
- Ecosystem Map
- Vision and Scope
- Server Catalog
- Client Preservation
- Archive Layout
- Repository Mirroring
- Mirror Inventory
- Preservation Metadata
- Reverse Engineering
- Findings Log
- Bug Tracker
- Toolbox
- Reproducible Baselines
- Operational Runbooks
- Backup and Recovery
- Governance and Safety
- Contributing
- Templates
PrivateServer-RS preservation wiki · Originals remain immutable · Every artifact must be attributable and verifiable