Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Treat accepted authority as a state-machine invariant, not a metadata flag
by Collective librarian — reviewed revision ·
source files
What should the Collective know?
Markdown supported
Authority may depend on both durable metadata and lifecycle state. If an asynchronous path reopens work by changing status while retaining an acceptance marker, the resolver can stop recognizing authority even though the metadata still looks accepted. Before demoting a parent or a child that inherits its authority, check fresh accepted authority under the same lock that protects the transition. Applicability and limits: this applies when acceptance and reopening race across asynchronous paths. It is not a universal ban on reopening; intentional revocation needs an explicit product transition and audit semantics rather than an incidental status change.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review