mirror of
https://github.com/morluto/rea.git
synced 2026-11-20 05:32:44 +00:00
docs: clarify parser coverage and verification ownership
This commit is contained in:
1 parent
0be83b62fc
commit
5664a6fbd4
15 files changed
+119
-115
No files matched your search
@@ -214,8 +214,9 @@ candidates. A boundary nested inside another expression or compound assignment
|
||||
does not establish a direct result binding.
|
||||
The query declares backward provenance, forward influence, callers, or
|
||||
ownership and can restrict admitted relation kinds. REA returns every matching
|
||||
seed and the complete reachable subgraph; callers do not choose node, relation,
|
||||
depth, function, module, seed-match, or page budgets.
|
||||
seed and its complete reachable subgraph within the admitted graph. Callers
|
||||
do not choose node, relation, depth, function, module, seed-match, or page
|
||||
budgets. Extraction limits and unknowns can still leave coverage partial.
|
||||
|
||||
The extractor covers lexical definitions and reads, literal seeds, static
|
||||
property slots, object reads/writes/spreads/destructuring, closure captures,
|
||||
@@ -241,6 +242,14 @@ assignment. Computed method keys belong to the enclosing callable; parameter
|
||||
defaults and method bodies belong to the method. Uncertain later property reads
|
||||
remain opt-in through `include_ambiguous_dynamic_edges`.
|
||||
|
||||
Destructuring retains dependencies from the source slots proved at the time
|
||||
of the read. A later write does not replace an earlier proved dependency.
|
||||
A numeric key in an object pattern selects a named property directly.
|
||||
Nested array patterns can preserve dependencies for later bindings when
|
||||
element selection is known and iterator closing cannot invoke a return hook.
|
||||
Holes, accessors, and unknown iteration keep the affected dependencies
|
||||
uncertain.
|
||||
|
||||
Binary, logical, unary, template, conditional, and sequence expressions retain
|
||||
`influences` edges from supported immediate inputs to the result, then to a
|
||||
direct declaration, assignment, call argument, or return. These are static
|
||||
@@ -248,7 +257,8 @@ dependencies, not aliases or proof that the expression executed; conditional
|
||||
operands and logical-assignment writes carry `conditional: true`. Unsupported
|
||||
operand dependencies, unmodeled receiving containers, dynamic call results,
|
||||
and sequence side effects remain unknown. An applicable
|
||||
unknown makes the trace status `partial` even when a seed was found. Literal
|
||||
unknown makes the trace status `partial` when no applicable ambiguity takes
|
||||
precedence, even when a seed was found. Literal
|
||||
operator operands, direct call arguments and directly returned scalar literals
|
||||
can also be seeds. Older graphs that only recorded a call-site literal remain
|
||||
searchable. The offered per-file node capacity also bounds the producer's
|
||||
@@ -318,7 +328,9 @@ behavioral absence.
|
||||
Semantic relations use static-inference authority. `resolved` means the static
|
||||
target identity was unique within admitted analysis; it does not mean the path
|
||||
executed. Candidate edges are excluded by default, require explicit opt-in, and
|
||||
keep the result ambiguous. Runtime Evidence can later corroborate an exact
|
||||
keep the result ambiguous. An exact edge may still be present when other
|
||||
possible dependencies make the overall trace ambiguous. Runtime Evidence can
|
||||
later corroborate an exact
|
||||
mapped candidate, but structural reachability, semantic influence, runtime
|
||||
observation, and causal proof remain separate claims.
|
||||
|
||||
@@ -521,9 +533,10 @@ properties. Dynamic child writes such as `copy[key].value = 2` remain conservati
|
||||
about which original slot was selected. Object rest
|
||||
excludes consumed keys, array rest excludes the consumed prefix for known
|
||||
arrays, and later explicit data properties and methods replace earlier object
|
||||
spread references. A known array prefix does not expose values from a following
|
||||
spread. Accessors, custom or uncertain iteration, unknown computed keys, and
|
||||
unknown spread lengths retain conservative uncertainty.
|
||||
spread references. A bounded dense inline array spread can supply exact slots
|
||||
and keep the positions of later elements known. Accessors, sparse or unknown
|
||||
spread sources, custom or uncertain iteration, and unknown computed keys keep
|
||||
the affected reads uncertain.
|
||||
Getter-local aliases of `this`, including direct destructuring and assignments,
|
||||
retain their receiver when a returned shared reference is written. These writes
|
||||
invalidate the earlier literal instead of claiming the getter executed or the
|
||||
@@ -545,8 +558,8 @@ Writes through an object getter's returned receiver retain that uncertainty
|
||||
when the object is an array element, nested inside mixed object/array
|
||||
containers, or assigned to a previously declared identifier. Saving the getter
|
||||
result in an alias does not make its old field values immutable. Known array
|
||||
indices include holes; an element after a spread has only a minimum possible
|
||||
index. For these returned-reference writes, unrelated properties and known
|
||||
indices include holes. After a spread with unknown length, a later element
|
||||
has only a minimum possible index. For these returned-reference writes, unrelated properties and known
|
||||
array prefixes remain precise. Accessor applicability uses the shared object
|
||||
reference owner for literal definition order, own-property shadowing, known
|
||||
array elements and explicit literal prototypes. Getter invocation effects
|
||||
|
||||
Reference in new issue
Block a user