From bd5d189a8f8aeea669bcb93e68af6c046b567939 Mon Sep 17 00:00:00 2001 From: Kaoru0822 Date: Wed, 21 Oct 2026 21:20:02 -0700 Subject: [PATCH] docs(javascript): state that duplicate unmapped content stays ambiguous (#6238) Co-authored-by: Claude Opus 5.5 --- docs/javascript-runtime-reconciliation.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/javascript-runtime-reconciliation.md b/docs/javascript-runtime-reconciliation.md index a274deba12..068353661d 100644 --- a/docs/javascript-runtime-reconciliation.md +++ b/docs/javascript-runtime-reconciliation.md @@ -108,9 +108,10 @@ nodes. REA evaluates compatible static candidates conservatively: 6. Missing authorization mappings and incomplete or truncated input coverage remain unknown or truncated rather than becoming absence claims. A runtime location with no automatic artifact-root or caller-declared mapping into - any layer, and no unique content match, is `unknown` with - `no-authorized-location-mapping`, with or without captured bytes. Only a - mapped location can be `unmatched` with `no-static-content-match`. + any layer, and no content match, is `unknown` with + `no-authorized-location-mapping`, with or without captured bytes; several + content matches remain `ambiguous` under rule 4. Only a mapped location can + be `unmatched` with `no-static-content-match`. Every successful cross-layer `observed_as` edge has `authority: cross-layer-reconciliation` and `state: inferred`. The underlying