diff --git a/.vit/config.json b/.vit/config.json index e4a449fbd..26bdca112 100644 --- a/.vit/config.json +++ b/.vit/config.json @@ -1,4 +1,4 @@ { - "beacon": "vit:github.com/solpbc/solstone", + "beacon": "vit:github.com/solpbc/solstone-journal", "secondaryBeacon": "vit:tangled.org/solpbc.org/solstone" } diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1abd36ef9..e12767e26 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -47,8 +47,8 @@ brew install python git ripgrep ffmpeg uv ## Source-checkout install ```bash -git clone https://github.com/solpbc/solstone.git -cd solstone +git clone https://github.com/solpbc/solstone-journal.git +cd solstone-journal make install .venv/bin/sol setup ``` diff --git a/DATA-FLOW.md b/DATA-FLOW.md index a7439cdf2..71ac5dd85 100644 --- a/DATA-FLOW.md +++ b/DATA-FLOW.md @@ -47,4 +47,4 @@ this data-flow posture isn't a feature decision that could be reversed next quar --- -*solstone is open source (AGPL-3.0). every claim in this doc is verifiable in the code at https://github.com/solpbc/solstone — the provider call path is `solstone/think/providers/`.* +*solstone is open source (AGPL-3.0). every claim in this doc is verifiable in the code at https://github.com/solpbc/solstone-journal — the provider call path is `solstone/think/providers/`.* diff --git a/INSTALL.md b/INSTALL.md index 50a50396d..da2bcf3e7 100644 --- a/INSTALL.md +++ b/INSTALL.md @@ -104,11 +104,11 @@ uv tool upgrade solstone && sol setup once the observer is running, your observers experience your day along with you, transcribe conversations, surface people and projects, build a knowledge graph, and make everything searchable at http://localhost:5015. everything stays in your journal — one folder per day. -source code: https://github.com/solpbc/solstone +source code: https://github.com/solpbc/solstone-journal company: https://solpbc.org ## feedback -questions, feedback, or a bug? **follow and tag [@solstone.app](https://bsky.app/profile/solstone.app) on Bluesky** for discussion and updates, open an issue at https://github.com/solpbc/solstone/issues for bugs, or reach support at https://support.solstone.app. you don't need to know anyone — those are the front doors. +questions, feedback, or a bug? **follow and tag [@solstone.app](https://bsky.app/profile/solstone.app) on Bluesky** for discussion and updates, open an issue at https://github.com/solpbc/solstone-journal/issues for bugs, or reach support at https://support.solstone.app. you don't need to know anyone — those are the front doors. (running into trouble or want to develop on solstone yourself? see [CONTRIBUTING.md](CONTRIBUTING.md).) diff --git a/README.md b/README.md index 02dac5cab..c8698ed1f 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,10 @@ solstone -# solstone +# solstone journal your co-brain — observers experience your day along with you, sol curates your memories, and your journal holds everything. -solstone runs in the background on your computer, experiencing your day along with you. AI agents transcribe, extract entities, detect meetings, build knowledge graphs, and surface daily insights — all without any manual input. everything stays on your machine in daily journal directories. open source, local-first, no cloud required. +the python core of the solstone product family — the journal layer that the [solstone native apps](https://solstone.app) wrap. it runs in the background on your computer, experiencing your day along with you. AI agents transcribe, extract entities, detect meetings, build knowledge graphs, and surface daily insights — all without any manual input. everything stays on your machine in daily journal directories. open source, local-first, no cloud required. Python 3.11+, Linux + macOS, AGPL-3.0-only, maintained by [sol pbc](https://solpbc.org). @@ -119,7 +119,7 @@ Use `make dev` to run the full stack against test fixtures and `make ci` for pre ## feedback -Questions, feedback, or a bug? **Follow and tag [@solstone.app](https://bsky.app/profile/solstone.app) on Bluesky** for discussion and updates, open an issue at [github.com/solpbc/solstone/issues](https://github.com/solpbc/solstone/issues) for bugs, or reach support at [support.solstone.app](https://support.solstone.app). You don't need to know anyone — those are the front doors. +Questions, feedback, or a bug? **Follow and tag [@solstone.app](https://bsky.app/profile/solstone.app) on Bluesky** for discussion and updates, open an issue at [github.com/solpbc/solstone-journal/issues](https://github.com/solpbc/solstone-journal/issues) for bugs, or reach support at [support.solstone.app](https://support.solstone.app). You don't need to know anyone — those are the front doors. ## contributing diff --git a/pyproject.toml b/pyproject.toml index 89bc39666..0fcb62097 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -125,10 +125,10 @@ parakeet-onnx-cuda = [ sol = "solstone.think.sol_cli:main" [project.urls] -Homepage = "https://github.com/solpbc/solstone" -Repository = "https://github.com/solpbc/solstone" -Documentation = "https://github.com/solpbc/solstone/blob/main/README.md" -"Bug Tracker" = "https://github.com/solpbc/solstone/issues" +Homepage = "https://github.com/solpbc/solstone-journal" +Repository = "https://github.com/solpbc/solstone-journal" +Documentation = "https://github.com/solpbc/solstone-journal/blob/main/README.md" +"Bug Tracker" = "https://github.com/solpbc/solstone-journal/issues" [tool.setuptools.packages.find] include = ["solstone*"] diff --git a/solstone/observe/transcribe/parakeet_hints.py b/solstone/observe/transcribe/parakeet_hints.py index a02ccb7b9..54a5cc3bb 100644 --- a/solstone/observe/transcribe/parakeet_hints.py +++ b/solstone/observe/transcribe/parakeet_hints.py @@ -12,7 +12,7 @@ Whisper, the Gemini cloud backend, and the macOS observer app continue to work without the helper. If you want CoreML-accelerated parakeet transcription, install solstone -from a source checkout: see https://github.com/solpbc/solstone/blob/main/CONTRIBUTING.md.""" +from a source checkout: see https://github.com/solpbc/solstone-journal/blob/main/CONTRIBUTING.md.""" PACKAGED_LINUX_PARAKEET_HINT = """solstone packaged installs on Linux don't include the parakeet-onnx transcription stack — it ships as the `parakeet-onnx-cpu` (or diff --git a/solstone/talent/vit/SKILL.md b/solstone/talent/vit/SKILL.md index 2f248d7d6..47011a452 100644 --- a/solstone/talent/vit/SKILL.md +++ b/solstone/talent/vit/SKILL.md @@ -7,7 +7,7 @@ description: >- and consumption commands live in the user-wide `using-vit` skill. TRIGGER: ship a cap, publish solstone cap, vit ship, after hopper ship, final lode ship, capworthy feature, three-word ref, vit beacon, - vit:github.com/solpbc/solstone. + vit:github.com/solpbc/solstone-journal. --- # Vit Ship Skill @@ -18,7 +18,7 @@ Publish solstone capabilities as vit caps. Invoke via Bash: `vit ship ...` (othe vit is a CLI for publishing software capabilities (caps) to a decentralized social network built on ATProto. solstone participates in the vit network — when a capworthy feature ships, the VPE session publishes it as a cap so other projects and agents can discover, vet, and remix it. -**beacon:** `vit:github.com/solpbc/solstone` +**beacon:** `vit:github.com/solpbc/solstone-journal` **Scope**: this skill is intentionally narrow — VPE-session ship workflow only. For `vit skim`, `vit follow`, `vit learn`, `vit remix`, `vit vet`, and general vit usage, the `using-vit` skill has full coverage. Don't duplicate that reference here.