docs: migrate performance evidence report

This commit is contained in:
Jason Woltje
2026-08-10 16:16:31 -05:00
parent 46d29d82e9
commit 94fc3e55f5
5 changed files with 26 additions and 18 deletions
+5 -5
View File
@@ -192,10 +192,10 @@ For every documentation change:
## Migration policy
This initial pass defines the target structure only. It does not move or rewrite the existing documentation set.
The initial structure pass defined the target structure without moving or rewriting the existing documentation set. Subsequent migration slices may move or rewrite classified pages deliberately, with repository references and indexes updated together.
- Treat `_old_structure/` as read-only migration quarantine. Do not add new content there.
- Treat the current root-level legacy pages (`QUICKSTART.md`, `PERFORMANCE.md`, `SSO-PROVIDERS.md`, `openapi-tess.yaml`, and the task/mission documents) as migration backlog, not permission to create more root files.
- Treat the current root-level legacy pages (`QUICKSTART.md`, `SSO-PROVIDERS.md`, `openapi-tess.yaml`, and the task/mission documents) as migration backlog, not permission to create more root files. Historical evidence such as the P8-003 performance report belongs under `reports/qa/`.
- Candidate destinations include `USER-GUIDE/getting-started/`, `ADMIN-GUIDE/security/`, `DEVELOPER-GUIDE/architecture/`, `API/`, `tasks/`, `plans/`, and `archive/`; classify each page before moving it.
- Existing source code and tests still reference legacy paths such as `docs/fleet/` and `docs/federation/`. Update those references deliberately as part of the relevant migration slice; do not delete a referenced path blindly.
- When a page is moved, update all repository links, source comments, tests, book indexes, and `SITEMAP.md` in the same logical change.
@@ -205,12 +205,12 @@ This initial pass defines the target structure only. It does not move or rewrite
## Current transition state
The structure is being established before content migration. During this transition:
The structure is being established incrementally while classified content migration proceeds. During this transition:
- The target directories listed above are a blueprint; not all indexes or chapters exist yet.
- `docs/_old_structure/` remains available for reference but is not current documentation.
- Existing root documentation files remain until their migration destinations are reviewed.
- `docs/SITEMAP.md` still contains legacy paths and will be refreshed as pages are migrated.
- Existing root documentation files remain until their migration destinations are reviewed; migrated pages must leave a verified navigation path.
- `docs/SITEMAP.md` has current scaffold entry points but still contains legacy paths and will be refreshed as pages are migrated.
- No external publishing platform is assumed. The canonical source remains this repository under `docs/`.
## Non-goals for this pass