# NEW_FEAT — Filesystem Resource Layout

## Summary
Introduce filesystem-backed resource folders under `${openclaw dir}/yonexus` (data-only, no plugin code). These resources are created automatically when orgs/teams/identities are created.

## Root
- `${openclaw dir}/yonexus/organizations/<org-name>/`

### Organization folders
Create on **create_organization**:
```
teams/
docs/
notes/
knowledge/
rules/
lessons/
workflows/
```

### Team folders
Create on **create_team**:
```
${openclaw dir}/yonexus/organizations/<org-name>/teams/<team-name>/
  agents/
  docs/
  notes/
  knowledge/
  rules/
  lessons/
  workflows/
```

### Agent folders
Create on **assign_identity**:
```
${openclaw dir}/yonexus/organizations/<org-name>/teams/<team-name>/agents/<agent-id>/
  docs/
  notes/
  knowledge/
  rules/
  lessons/
  workflows/
```

## Notes
- The plugin must not store code in `${openclaw dir}/yonexus`, only data.
- If folders already exist, creation should be idempotent.

---

# NEW_FEAT — Document Query Tool

## Summary
Add a tool to retrieve documentation files based on scope, topic, and keyword.

## Tool
`get_docs(scope, topic, keyword)`

### Parameters
- **scope**: enum `organization | department | team | agent`
- **topic**: enum `docs | notes | knowledge | rules | lessons | workflows`
- **keyword**: string (supports regular expressions)

## Behavior
- Search matching files under `${openclaw dir}/yonexus/organizations/...` based on the given scope/topic.
- `keyword` is applied to filenames (regex supported).
- Output grouped by scope in the following format:
```
----ORG
<file list>
----DEPT
<file list>
----TEAM
<file list>
----AGENT
<file list>
```
- If no match in a group, output the header with no files beneath.

## Notes
- Search should be read-only.
- Pattern errors should return a structured error (invalid regex).