Explain persistent ACL metadata acceptance #106
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/docs!106
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/docs-76-surviving-merge-127c5f7"
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?
Integrate the manual changes from #76 into the surviving branch for #72. The original target has already merged. The prepared history preserves both branches’ documentation in README.md, ARCHITECTURE.md and ROADMAP.md. The full manual and Markdown checks passed on this commit.
Describe original ACL fixtures, the native metadata sequence and independent read-only post-guest decoding. Keep complete-value checks, ext-only write authority and supplier/VM acceptance explicit.
Companion to Integration #363. Depends on #74.