type: decision
status: active
timestamp: 2026-06-25
tags: [filesystem, fleet, forks]
status: active
timestamp: 2026-06-25
tags: [filesystem, fleet, forks]
Own/frk split — two buckets on top of flat repos/
Repos split into repos/own/ (originals) and repos/frk/ (forks)
Two-folder split: repos/own/<slug>/ for repos I created, repos/frk/<slug>/ for repos forked from upstream.
Captured: 2026-06-25, post-scope-cut, after the fleet shrunk to 20 submodules (15 own + 5 frk).
Why this beats flat-always:
- Forks have different release semantics (upstream sync, PRs back) that originals don’t.
- Forks have different license-credit obligations.
- 15 own + 5 frk fits naturally; the categorize-once-per-repo rule isn’t violated (fork-status is a hard binary, not a soft category).
- Muscle memory still works inside each bucket —
cd repos/own/<slug>/andcd repos/frk/<slug>/are both predictable.
Supersedes: fs-own-frk-split (locked 3h earlier same day).
The 4 forks (2026-06-29; was 5 before claude-notifications-cli deletion):
- ai-rewrite-bs-ext (parent: SupratimRK/Ai-rewrite)
- dearrow-plus-bs-ext (parent: ajayyy/DeArrow)
- freellmapi (parent: tashfeenahmed/freellmapi)
- omniroute (parent: diegosouzapw/OmniRoute)
How to apply:
- New repo I create ?
repos/own/<slug>/ - New repo I fork ?
repos/frk/<slug>/ - Slug suffixes (
-api,-bs-ext, etc.) still encode functional category.
Related: fs-own-frk-split (superseded), github-repo-names-are-brand-identity, scope-cut-2026-06-25.