> 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/sessions.md).

# sessions

Archived session artifacts live here. A session directory can include the session spec, task checklist, implementation notes, code review, security report, validation report, and implementation summary from the time the work was completed.

## Current Policy Lookup

Before using archived session wording such as read-only, metadata-only, default-off, admin-gated, manual admin, admin-disabled, observe-only, or limited-access as current product guidance, read [`../CURRENT-POLICY.md`](https://github.com/moshehbenavraham/ai-os/tree/main/.spec_system/archive/CURRENT-POLICY.md).

Current AI OS local operator goals default to full local access, write access, and edit access. Archived session language is historical evidence unless an active PRD, current docs, or current implementation evidence deliberately keeps a named exception.

## Artifact Interpretation

| Artifact                    | How To Use It Now                                                                                             |
| --------------------------- | ------------------------------------------------------------------------------------------------------------- |
| `spec.md`                   | Historical scope and acceptance criteria. Do not copy stale access defaults into new work.                    |
| `tasks.md`                  | Historical implementation checklist and file scope. Use as evidence, not current policy.                      |
| `implementation-notes.md`   | Historical decisions, commands, and verification evidence. Re-check current code before relying on details.   |
| `code-review.md`            | Historical findings and fixes. Current reviews must inspect the active diff.                                  |
| `security-compliance.md`    | Historical threat model and proof limits. Apply current Phase 41 security posture first.                      |
| `validation.md`             | Historical gate evidence. Do not treat old passing validation as proof that current local goals are complete. |
| `IMPLEMENTATION_SUMMARY.md` | Historical handoff summary. Verify active docs and code before reusing claims.                                |

## High-Impact Session Clusters

The Session 16 archive inventory identified 77 archived session directories in the high-impact scope for Phases 16, 17, 18, 19, 20, 23, 24, 25, 26, 31, 38, and 40. These clusters contain useful implementation evidence, but their old read-first, default-off, or admin-gated language must be classified through current policy before planning new local operator work.

Use the phase index at [`../phases/README.md`](/ai-os-and-trend-finder-docs/.spec_system/archive/phases.md) for the cluster table and counts.


---

# 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/sessions.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.