published-digest-generator-scalar-review

Availability: opt-in. Severity: info. Confidence: high.

The rule observes selected native and cast operand/result snapshots in ordinary data flow. Selection enables the observer token; default scans retain their prior transfer paths. Legacy admission checks the resolved canonical native overload consumes Field; modern admission checks the canonical JubjubScalar overload. The legacy trace contains no invented cast. ZKIR 3 captures the ordinary scalar-cast result after its existing transfer; native interpretation and cast semantics are unchanged. Other compiler profiles remain explicitly unsupported when applicable.

Matching uses owned semantic identities and immutable value keys, not function names, witness dependence alone, or wildcard storage paths. Later writes invalidate point survival. Both instruction/reference engines and cached/uncached execution use the shared transfer machinery. Exhausted observation or matching budgets produce incomplete diagnostics. Unsupported profiles produce a selected-rule diagnostic.

A bounded resolved-call walk first checks whether an entry can reach canonical native generator multiplication. Unrelated entries need no scalar observations and are recorded as structurally absent. Renamed native imports and ordinary helpers retain their canonical targets; represented callbacks remain relevant even at zero iterations. Unresolved callable models and exhausted applicability budgets remain incomplete. Relevant entries still require the exact observations and qualified profile. The candidate is appended to the registry, preserving prior rule order.

The finding establishes that the published digest determines the scalar in this exact source recipe. It does not establish encryption use, unsafe enrollment, ciphertext compromise, deployed impact or path feasibility. Root point Cells only; aggregate, collection and exported-return publication/registration patterns are outside the candidate's bounded support. Domain-tagged hashes and independent witness invocations do not match. Other deterministic scalar recipes are outside support.

Preparation, source observation, exact matching, immutable-key work and retained allocations share unchanged 40k entry steps, 256 entry paths and 50k cumulative rule values. Selected facts carry their original limits and spent entry work; matching is aggregated after completion or refusal. Exhausted facts are not retried. No-entrypoint sources skip nonexistent entry preparation and keep their explicit complete label.

Publishing a digest that determines a scalar can be an intentional protocol choice. Review how that scalar is used before treating the source relationship as a privacy or enrollment defect; this rule does not infer encryption or key management intent.