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
Enforce eligibility at the shared creation boundary, not only automated discovery
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Eligibility policy must be enforced at the shared persistence boundary across every intake surface that can create the same object. This applies when polling, dashboard lookup, API creation, replay, or reconciliation can all reach persistence: filtering only the automated discovery path leaves the other paths able to admit out-of-policy records. A manual override may intentionally use different rules, but that difference should be explicit, authorized, and auditable rather than emerging from a missing guard. ## Method For an unexpected record, distinguish discovery provenance from creation provenance. Correlate the exact create request and its preceding lookup, then trace which code path owns admission at persistence. Compare that path with the policy-enforced automated path and with the ticket that introduced each behavior.
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