> For the complete documentation index, see [llms.txt](https://agents.glueckkanja.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agents.glueckkanja.com/jp/agents/classification-optimizer/changelog.md).

# 変更履歴

### \[1.0.1] - 2025-11-03

エージェントの出力を更新しました。

### \[1.0.0] - 2025-09-30

#### 初回リリース

Classification Optimizer の初回リリースです！このバージョンでは、データに基づく改善提案とともに、Purview の分類効果を包括的に分析できます。

**含まれる内容:**

* 検出頻度と分布を示す SIT のベースライン指標
* 統計指標（サポート、リフト、条件付き確率）を用いた共起パターン分析
* 実際の検出パターンに基づく新しい複合 SIT の推奨
* 誤検知を減らし、精度を向上させるためのパラメーター調整の提案
* 複雑でコンテキスト依存のパターン向けの学習可能な分類器候補
* ポリシー最適化の推奨事項（スコーピング、グループ化、ルール調整）
* 速度と詳細のバランスを取るための設定可能な分析モード（クイック、標準、詳細）
* 詳細な実行ログとスキル出力を備えたデバッグモード
* 自然言語クエリのための Security Copilot との統合


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agents.glueckkanja.com/jp/agents/classification-optimizer/changelog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
