Skip to content

RFC-0005: filesystem host-surface plugin RFC (draft, bitty.fs successor) #440

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
Xuepoo merged 3 commits into from
Oct 5, 2026
Merged

RFC-0005: filesystem host-surface plugin RFC (draft, bitty.fs successor) #440

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9a95e48
[CTX-0279] docs(decisions): draft RFC-0005 filesystem host-surface (I…
Xuepoo Oct 5, 2026
0b0bab1
[CTX-0279] [CTX-0280] docs(rfc-0005): apply security-review F-01..F-0…
Xuepoo Oct 5, 2026
5dc321a
[CTX-0281] [CTX-0280] docs(decisions): flip RFC-0005 draft to accepte…
Xuepoo Oct 5, 2026
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
1 change: 1 addition & 0 deletions docs/decisions/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -322,6 +322,7 @@ the historical conversation:
- Repository metadata and `.github` baseline across the estate. (Proposed: [ADR 0011](adrs/ADR-0011-repository-metadata-baseline.md) and the [Repository Metadata and GitHub Baseline](../development/repository-metadata-baseline.md) guide — byte-identical, parameterized, and per-repository tiers; required-check naming atomic with branch protection; action SHA pinning and rust-channel pinning. Extended from the 2026-09-11 configuration-drift audit under `CTX-0155`; not yet accepted and authorizes no consumer-repository change.)
- AI consent to generic scope mapping. (Draft: [AI Consent to Generic Scope Mapping RFC](rfcs/RFC-0003-ai-consent-scope-mapping.md) — maps the AI consent vocabulary to the shipped 13-scope generic IPC registry, marks workspace-context and memory-persistence terms as uncovered with candidate resolutions, and defines the ai-docs adoption path; closes CTX-0407 gap G-6 under docs `CTX-0190` while [OQ-066](open-questions.md) remains open; frontmatter `draft` on 2026-09-14.)
- Read-only history, search, and selection plugin surface. (Accepted: [History Read Surface RFC](rfcs/RFC-0004-history-read-surface.md) — fixes a NEW read-only capability family (not `terminal.*`) of bounded snapshot queries with explicit per-plugin grants, no live streaming or subscription, secret-minimizing storage with redaction per W-131, transcript/history/KV stores as queryable sources under the same ceilings, and typed denials; the closed `terminal` family stays closed and v1 stays frozen; targets [OQ-056](open-questions.md), which stays open; successor to the W-139 block per DEC-W139-1 with the chain RFC accepted, Core host implementation, SDK, plugin parity, then W-144 deletion; frontmatter `accepted` on 2026-10-04; Issue #430.)
- Filesystem host surface. (Accepted: [Filesystem Host Surface RFC](rfcs/RFC-0005-filesystem-host-surface.md) — reconciles the draft `bitty.fs.open/append/read/list` sketch against the accepted `fs.read:PATTERN`/`fs.write:PATTERN` split as decided verbs read/write/list under a NEW `bitty.fs.*` root (never `bitty.terminal.*`), with scoped grants and no wildcard reusing the 4096/32/8KiB bounds, typed oracle-tight denials, untrusted labeling with preview-equality, read-into-VM-only grant combination, and no watch or tail-follow; v1 stays frozen with no `fs` namespace; targets [OQ-056](open-questions.md), which stays open; rollout is RFC draft, security review, Core host bridge, SDK, then file-manager/editor-preview/Wheel parity; frontmatter `accepted` on 2026-10-05; Issue #439.)

Each candidate is represented by an item in the
[open-question register](open-questions.md). Acceptance requires an ADR, RFC,
Expand Down
Loading
Loading