iyanmv
Not only it is confusing but I think it can also by ambiguous.
There's nothing ambiguous about it.
Does a full 2025-10-01 security patch level implies it also contains the 2025-09-05?
Yes, the whole point is that all previous patch levels are included.
Can it be the case that you get early access to the the Android patches of the next month, but still no patches for the (I guess proprietary) hardware patches for the current month?
Yes, but the patch level cannot be set beyond the point that patches are provided. You're missing the whole point of the patch level.
If that happens, would you keep the old date, even though some patches from the next month are already included?
We won't not set a fake patch level. The 2025-10-01 patch level was set once all of the 2025-09-05 patches were included. That's the reason it was raised.
Perhaps GrapheneOS can create a new less ambiguous and less confusing way to define the "Android security update". And who knows, if it makes sense, maybe Google copy that as well and stops using random YYYY-MM-01 and YYYY-MM-05 dates.
The patch level is in no way ambiguous. The whole point of the patch level is that it's defined in a way that's broader than GrapheneOS. We already have our own version numbers and release notes.