> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases.md).

# phases

Archived phase PRDs and phase session stubs live here. These files are historical records, not current product requirements.

## Current Policy Lookup

For archived wording such as read-only, metadata-only, default-off, admin-gated, manual admin, admin-disabled, or limited-access, use [`../CURRENT-POLICY.md`](https://github.com/moshehbenavraham/ai-os/tree/main/.spec_system/archive/CURRENT-POLICY.md) before treating the text as current guidance.

Current AI OS local operator goals default to full local access, write access, and edit access. Automatic local controls still apply.

## High-Impact Phase Clusters

Session 16 identified these clusters as the highest-risk phase archives for reviving obsolete local posture. Keep their old plans intact, but classify stale access language through the current policy note.

| Phase | Files | Sessions | Current Interpretation                                                                           |
| ----- | ----- | -------- | ------------------------------------------------------------------------------------------------ |
| 16    | 5     | 3        | Hermes v2.3 read-first baseline and token/admin write controls are historical context.           |
| 17    | 5     | 3        | Hermes shell, chat, and Pantheon write gates are historical implementation details.              |
| 18    | 4     | 2        | Memory and Mnemosyne read-only records do not define new local defaults.                         |
| 19    | 4     | 2        | Mission and Documents admin-gated records must be interpreted through current all-access policy. |
| 20    | 4     | 2        | Long-tail Hermes read-only sections are history unless current docs name an exception.           |
| 23    | 5     | 3        | Non-Hermes limitations remain implementation gaps until real execution is proven.                |
| 24    | 11    | 9        | Trend Finder source and export boundaries remain valid only as compliance/privacy context.       |
| 25    | 11    | 9        | Mission Control preview and gated commit evidence informs safeguards, not default-off posture.   |
| 26    | 11    | 9        | Knowledge Graph read/gated ingest records require current dependency or safety classification.   |
| 31    | 9     | 7        | Public demo read-only constraints apply to hosted privacy mode only.                             |
| 38    | 12    | 10       | Voice, Intelligence, Dream, and bridge caveats require current shipped/proof/gap classification. |
| 40    | 20    | 18       | Claude OS v2.10.1 port records are superseded by Phase 41 local all-access policy.               |
| 41    | 18    | 17       | Completed local all-access migration and generated-data closeout evidence.                       |

Totals: 119 phase/archive files and 94 archived session directories in the high-impact scope.

## Phase Directory Pattern

Each `phase_NN/` directory may contain:

* `PRD_phase_NN.md`
* `README.md`
* `session_NN_*.md` stubs

Use these records to understand historical intent and validation context, then use active PRD/spec memory for current requirements.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.