gnomonlearn
Docs/RFC-0042/Design Q&A

RFC-0042 · Design Q&A

Versioned draft snapshot

RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.

Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.

← Read the authored RFC

Q: Must a grant statement point to the exact resource under authorization?

Status: Open

Source: RFC-0042 §§1, 3.4, 4.2 Issue: The policy definition grants access when a subject’s statement points to the resource, but the evaluation algorithm also permits a statement whose object is merely in the same kind. That can grant access to every resource of the kind from one relationship. Recommendation: Require statement.object = requested resource for predicate-policy grants. Treat kind-wide grants as a distinct, explicit policy form with separate authorization review.

Q: How are the statement’s effective time and deletion state enforced during authorization?

Status: Open

Source: RFC-0042 §§4.2, 5.2; RFC-0036 §4.2 Issue: The algorithm searches statements without requiring a currently valid bitemporal interval or a non-deleted endpoint. An expired or retracted relationship can continue to grant access. Cache invalidation names validTo updates but not an interval becoming inactive as time advances. Recommendation: Define the as-of evaluation time and active-statement predicate, include endpoint lifecycle state, and expire cached decisions at the earliest relevant temporal boundary.

Q: How does the permission cache handle conditional policy inputs?

Status: Open

Source: RFC-0042 §§3.5, 4.5, 5.1–5.3 Issue: when can depend on principal scopes, session, resource data, and current time, but the cache key contains only subject/resource identity and does not list invalidation on those changes. A cached read decision can be reused for a different principal or after a condition becomes false. Recommendation: Either bypass persistent caching for conditional grants or include all relevant context in a bounded cache key with time-based expiry and invalidation on subject/resource data changes.

Q: What grammar and namespace apply to preset names?

Status: Open

Source: RFC-0042 §§3, 3.6, 9 invariant 10; RFC-0043 Issue: The declaration types preset as DnsLabel, but examples use dotted names such as app.read; the invariant makes names globally unique across the runtime without defining ownership or versioning. Recommendation: Define a qualified preset path grammar, resolve it through module imports, and make uniqueness apply to the qualified identity rather than an unqualified label.

Q: How are ResourcePolicy and StatementPolicy grants evaluated without a predicate?

Status: Open

Source: RFC-0042 §§3.1, 4.2, 7, 9 invariant 1 Issue: Every predicate policy requires a predicate and the algorithm begins by matching relationship statements. §7 calls a predicate-free ResourcePolicy equivalent and says both legacy forms participate in that same algorithm. The stated equivalence cannot satisfy the required declaration or matching rule. Recommendation: Define an explicit tagged direct-grant path for legacy policies, including subject binding and precedence, then specify how its resulting bits combine with predicate-policy grants.

Q: How is the requesting principal bound to the subjectId supplied for a permission check?

Status: Open

Source: RFC-0042 §§2, 4.1–4.2, 8; RFC-0048 Issue: The service request takes subjectId and subjectType, but the algorithm does not require them to match the authenticated principal or a delegated identity. A caller that can choose a different subject may borrow that subject’s grants. Recommendation: Bind the subject to the authenticated session or an explicitly authorized delegation before evaluating graph grants, and reject mismatches with a stable diagnostic.