Distinguish scoped read-only access evidence #116
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-ipc!116
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/scoped-read-only-access-evidence"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Carry the original scope read-only ceiling in access and permission evidence. Preserve it independently of provider mode bits so metadata cannot restore mutation authority the scope never held.
Depends on #115.
WIP: Distinguish scoped read-only access evidenceto Distinguish scoped read-only access evidenceReconciled at
2a5cccafc46fc05ea86ed2829f1c257f80130aaaonfeature/scoped-read-only-access-evidence-merge-ready-2a5cccaf. The read-only refusal remains specific to scoped permission evidence. Generic transport and ACL-page result domains still reject it; no metadata value upgrades the original scope.The original work branch is unchanged. Please review the exact prepared commit; earlier approval does not cover this rewritten history.