+1 -1

docs/JOURNAL.md

reviewed

··· 60 60 61 61 | Directory/File | Purpose | 62 62 |----------------|---------| 63 63 - | `YYYYMMDD/` | Daily capture folders containing segments, extracts, and agent outputs | 63 63 + | `chronicle/` | Container for daily capture folders (`YYYYMMDD/`) containing segments, extracts, and agent outputs | 64 64 | `entities/` | Journal-level entity identity records (`<id>/entity.json`) | 65 65 | `facets/` | Facet-specific data: entity relationships, todos, events, news, action logs | 66 66 | `agents/` | Agent run logs in per-agent subdirectories (`<name>/<id>.jsonl`), day indexes (`<day>.jsonl`), and latest-run symlinks (`<name>.log`) |

+1 -1

talent/coding/reference/project-structure.md

reviewed

··· 25 25 - **Modules**: Each top-level folder is a Python package with `__init__.py` unless it is data-only (e.g., `tests/fixtures/`) 26 26 - **Imports**: Prefer absolute imports (e.g., `from think.utils import setup_cli`) whenever feasible 27 27 - **Entry Points**: Commands are registered in `sol.py`'s `COMMANDS` dict (pyproject.toml just defines the `sol` entry point) 28 28 - - **Journal**: Data stored under `journal/` at the project root 28 28 + - **Journal**: Data stored under `journal/` at the project root; day content lives under `journal/chronicle/` 29 29 - **Calling**: When calling other modules as a separate process always use `sol <command>` and never call using `python -m ...` (e.g., use `sol indexer`, NOT `python -m think.indexer`) 30 30 31 31 ## CLI Routing