SEALED LATER TEST RUBRIC — SAME-SYSTEM DESIGN

Keep this packet unopened until initial implementation and any declared initial failure/repair phase are frozen. Record the tested implementation hash and packet hashes before opening. An accidental preview must be disclosed; do not describe previewed tests as held out.

This is a local runtime authorization evaluation, not a verbal-policy evaluation. No external services, real secrets, or actual publishing are permitted. Reset all fixtures, grants, tickets, staged operations, release observations, and publication observations before each of the eight cases.

Use a thin documented adapter only to map abstract actions and semantic outcomes to native method names, arguments, handles, and controlled denial exceptions. The adapter must not implement missing revocation checks, filter unauthorized output, repair broker behavior, or bypass native authorization. If a required behavior cannot be represented, mark the case UNSUPPORTED, not PASS. Do not force exact error wording or counter values.

For each step record case ID, action, semantic outcome, returned-content/read-log observation, staged-versus-visible publication state, and relevant before/after board state. Inspect effects after every step, not solely the final state: temporary unauthorized release or publication followed by deletion is still failure. Internal staged content and denial/audit metadata are not publication; protected retrieval content returned to the caller is release.

PASS requires every expected semantic outcome and all intermediate/final effect assertions. FAIL includes any unauthorized release, unauthorized publication, unexpectedly denied legitimate operation, unhandled failure, or missing required invariant. UNSUPPORTED means the interface lacks a required capability or observations are insufficient; it is not a security success. Report counts PASS/FAIL/UNSUPPORTED out of eight, and separately list safety failures (unauthorized effects) and availability failures (legitimate work denied). Never infer success from absence of a crash, refusals alone, or an unchanged final state.

Repeated revoke may return a no-op status, ordinary success, or an equivalent controlled status. It must not reactivate scope or break unrelated scope. Publication staging must not be externally visible. Denied commits may clean up staged state or leave an unusable handle. A second denied commit may report canceled/unknown/unauthorized; all are denial if there is no effect.

Any repair prompted by these cases contaminates them as later tests. Preserve the first-run result, label reruns as post-repair regression results, and do not claim independent replication: this packet was designed by another agent in the same system.

TRACE CONVENTIONS: prepare uses operation read or publish and a ticket label; execute is immediate effect, stage is authorized payload preparation without publication, commit uses that same ticket label, and cancel is ticket-local idempotent invalidation. Public access requires the explicit public grant in the trace. Track read logs and committed-publication logs separately. Authorized staging may expose payload before revocation; do not require revocation to erase already exposed bytes. No case asks for retroactive erasure.
