Skip to content

docs: Mission makes Chromeria a personal app kept rebasable through modules #185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lukemaj merged 1 commit into from
Oct 8, 2026
Merged

docs: Mission makes Chromeria a personal app kept rebasable through modules #185

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions MISSION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,10 @@
# Mission

The toolboxmd fork of T3 Code is the user's working surface. It stays a thin,
rebasable layer on upstream `pingdotgg/t3code`: features live in new files and
packages, upstream files carry the smallest possible edits, and generic
extension points are offered upstream so the patch set shrinks over time.
The toolboxmd fork of T3 Code is the user's personal working surface, shaped
around their own tools and habits. It tracks upstream `pingdotgg/t3code` and
absorbs every update by rebasing: fork features live in their own modules and
reach upstream code through small hooks, so no feature is cut to keep the fork
small.

On T3's core the fork adds what the user's tools need instead of rebuilding
harness plumbing: Prism, the fork's router, chooses the model, harness and
Expand Down
6 changes: 3 additions & 3 deletions docs/fork.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Fork maintenance

This repo (`toolboxmd/t3code`) is a thin, rebasable layer on upstream
This repo (`toolboxmd/t3code`) is a personal, rebasable layer on upstream
`pingdotgg/t3code`. Upstream `main` is the base; fork work is a small stack of
topic commits kept on top of it. This document describes the model, the
maintenance routine, and the upstream extension points that would shrink the
Expand All @@ -19,8 +19,8 @@ patch set further.
new hashes and break the stack. An absorption is proven on its own branch
and then lands with `--force-with-lease` (see Routine). That push is a
human-approved step.
- **New files first.** Features go in new files and new packages. Edits to
upstream-owned files stay minimal and every edited file has a primary owner
- **Modules first.** Features live in their own files and packages. Upstream-owned
files carry only the hooks those modules need, and every edited file has a primary owner
in [the feature map](fork-features.md) and an entry in the machine-checked
allowlist `scripts/fork-upstream-edits.txt` (one path per line).
- **Remotes.** `origin` is `toolboxmd/t3code`; `upstream` is
Expand Down
Loading