diff --git a/NOTES.md b/NOTES.md
index ec79fd5..c6b0b20 100644
--- a/NOTES.md
+++ b/NOTES.md
@@ -2,21 +2,6 @@
 
 Temporary notes from the SBFS v2 and CosmOS review, in priority order.
 
-## Streaming writes: reject a final size larger than the reservation
-
-`osFileStart` reserves an extent and `osFileWrite` correctly refuses a block index outside
-that extent. `sbfsStreamDone`, however, appears to accept a final block/tail count larger
-than the extent reserved at the start. It writes the larger size into the descriptor and
-then subtracts that size from the reservation when updating the free-block count.
-
-A caller could reserve one block, finish while claiming two, and make the file descriptor
-claim a neighboring block that was never allocated and may belong to another file.
-
-Before deleting the old destination or modifying the temporary entry, compare the final
-extent (`whole blocks + a possible tail block`) with the reserved extent. Refuse the commit
-if the final extent is larger. Add tests for a final size that is smaller than, equal to,
-and larger than the reservation, including tail/no-tail boundaries.
-
 ## Protect the temporary-file namespace
 
 Whole-file saves and streamed writes use the fixed names `sbfs.part` and `sbfs.out`.
@@ -36,25 +21,6 @@ Possible resolutions:
 Whatever rule is chosen should be enforced in both SplitDisk and the native SBFS code and
 documented as part of the format or CosmOS policy.
 
-## Correct stale CosmOS memory-map documentation
-
-`Programs/CosmOS/README.md` currently gives overlapping Data Memory ranges:
-
-```text
-CosmOS:      0x0000 through 0x3FFF
-Application: 0x2000 and above
-```
-
-The intended 8 KiB system allocation appears to be `0x0000` through `0x1FFF`, with
-applications at `0x2000` and above. The minimal application in the same section still uses
-the old bases (`0x2000` Program and `0x1000` Data), while current applications use `0x4000`
-and `0x2000`. The opening comments in `cosmos.asm` and several monitor examples also retain
-old addresses.
-
-The README says `make test` checks these boundaries, but the overlapping table passed.
-Strengthen `Tests/docs.sh` so the documented system endpoints and application bases are
-parsed and checked for agreement/non-overlap.
-
 ## Establish one portable path-length limit
 
 SplitDisk carries paths up to 511 characters, while the native path machinery appears to
@@ -77,18 +43,6 @@ Define and validate a maximum directory-block/entry count such that every direct
 can be named as a parent. Apply the check while formatting and mounting/reading malformed
 images in both implementations.
 
-## Document the save/stream crash guarantee precisely
-
-The temporary-first ordering protects the old file from expected failures such as no
-contiguous run or a refused block write. It is not power-loss atomic: a reset between
-deleting the old entry and renaming the temporary can lose the destination and leave the
-temporary behind.
-
-That is an appropriate tradeoff for SBFS; it does not call for a journal. Document the
-guarantee as protection against normal operation failures rather than full crash
-atomicity. A future boot cleanup or small consistency checker could reclaim unmistakable
-temporary entries, especially if they receive a descriptor flag.
-
 ## Design strengths worth preserving
 
 - Parent-as-index-plus-one makes every version one entry a valid root child without