The PIOS 2.0 repository is the canonical neutral framework documentation: concepts, architecture, and specifications for any implementer.
What belongs here: framework-level concepts, architecture decisions, system design, terminology definitions — written to apply universally, independent of any specific person's setup.
What does not belong here: personal implementation details (machine names, vault paths, personal identifiers, specific agent configs). Those belong in the owner's own knowledge environment.
If you are contributing a change, keep this separation in mind. When in doubt, ask whether the content would make sense for any PIOS implementer, not just one specific setup.
The peecos.org website source. Contributions welcome for content accuracy, accessibility, and design improvements.
- Treat independent implementations and forks as welcome participants in the ecosystem; do not write as if a hosted provider or one organization controls PIOS.
- Open an issue before starting significant work
- Keep PRs focused — one concern per PR
- Follow the terminology defined in pios - consistency matters
- Preserve license and attribution boundaries: framework documentation is CC BY 4.0, implementation code is Apache-2.0, and project names/logos are not licensed as brands.
See OPENNESS.md for the plain-language public position.