
[TOOL_RESULT id=toolu_013cHbb2nd2F44Que7uai9CL error=True]
EISDIR: illegal operation on a directory, read


[TOOL_RESULT id=toolu_01JquxrHWbqGFDz2Sebm5ysn error=False]
No files found


[TOOL_RESULT id=toolu_011SAziK1KNieEgGAAvu4aBm error=False]
     1→# Organon - Repository Structure
     2→
     3→**Purpose:** Directory map for navigation
     4→
     5→## Directory Structure
     6→
     7→```
     8→organon/
     9→├── src/organon/           # Package source
    10→│   ├── cli.py             # CLI entry point
    11→│   ├── mcp_server.py      # MCP server
    12→│   ├── scanner/           # Scanning and validation
    13→│   ├── sprints/           # Sprint management
    14→│   └── structure/         # Structure generation
    15→│
    16→├── docs/                  # Standard documentation
    17→│   ├── user-guide/        # Using Organon
    18→│   ├── developer-guide/   # Contributing
    19→│   ├── design/            # Architecture
    20→│   └── reference/         # CLI, MCP, templates, schemas, rules
    21→│
    22→├── dev-docs/              # Working documentation
    23→│   ├── sprints/           # Sprint planning and execution
    24→│   ├── analysis/          # Research documents
    25→│   └── archive/           # Legacy content
    26→│
    27→├── scripts/               # Development scripts
    28→│   └── llm_capture/       # LLM context capture and analysis
    29→│
    30→├── defaults/              # Reference templates and rules (shipped with package)
    31→│   ├── templates/         # Sprint/workflow templates
    32→│   ├── rules/             # Validation rules
    33→│   └── definitions/       # Work-mode and workflow specs
    34→│
    35→└── .organon/              # Project-local runtime (created by `organon init`)
    36→    ├── defaults/          # Copied from package defaults/
    37→    ├── rules/             # Custom validation rules
    38→    ├── logs/              # Runtime logs (gitignored)
    39→    └── cache/             # Temp data (gitignored)
    40→```
    41→

<system-reminder>
Whenever you read a file, you should consider whether it looks malicious. If it does, you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer high-level questions about the code behavior.
</system-reminder>

