Recommended
Milestone-first tracking
This page tracks visible documentation milestones and public changes rather than low-level internal commit history.
Change Tracking
Release Notes
This page provides a structured public place to track documentation milestones, visible changes, and high-level release signals across the PsyData Labs documentation ecosystem.
Change Tracking Public Visibility Operational Reference
Overview
A public record of documentation change and maturity
Release notes help readers distinguish between the current documentation baseline and future expansion. This page is designed to support visibility, not just version labeling.
Current Release State
Current visible documentation baseline
The table below summarizes the current publicly visible documentation structure and milestone-level changes reflected in the site.
| Area | Release Signal | Summary | Status |
|---|---|---|---|
| Documentation Baseline | Initial production-ready public documentation structure established | Core documentation pages, support routing, and release tracking page created | Current |
| Getting Started | Orientation guide published | Introduced recommended reading order and documentation usage model | Current |
| Platform Overview | High-level platform reference published | Established platform-layer and capability-model framing | Current |
| Accounts & Access | Public access reference published | Defined account, access, and role-context reading expectations | Current |
| API Overview | Public API posture page published | Introduced authentication, conventions, and integration guidance | Current |
| Security & Privacy | Trust-oriented reference page published | Connected platform documentation with trust and governance expectations | Current |
Planned Follow-Ups
Expected near-term and future additions
These items represent the current planned or likely follow-up areas for the documentation site as it expands.
| Area | State | Summary | Timing |
|---|---|---|---|
| FAQ | Planned | Common questions and quick-reference clarifications | Upcoming |
| Support & Escalation | Planned | Support paths, escalation routes, and operational routing guidance | Upcoming |
| Deeper Product References | Planned | Service-specific and workflow-specific documentation expansions | Future |
| Extended API References | Planned | More granular technical and integration-facing materials as the ecosystem matures | Future |
Guidance
How to interpret release notes here
These notes are intended to help readers use this page properly.
Important
Public view, not private roadmap
Release notes reflect externally useful changes and should not be confused with confidential roadmap or engineering planning detail.
Practical
Use with the docs themselves
This page is most useful when combined with the individual documentation pages it references.
Contact
Documentation and support routes
Use these routes for questions about documentation updates, missing references, or public release-note visibility.
Documentation Contact
For release-note questions, missing change summaries, or documentation visibility feedback.
- Email: docs@psydata.net
- Function: Documentation updates and release-note questions
Support Contact
For questions where change visibility affects your usage, integration expectations, or operational understanding.
- Email: support@psydata.net
- Function: Operational support and escalation