From 8b737fa1b8bac8712bb16d1ee723f2cece5be94d Mon Sep 17 00:00:00 2001 From: Weksa Date: Sat, 14 Nov 2026 04:26:11 +0000 Subject: [PATCH 1/2] interlingua-standard: name V18's limits and drop the false frame:2 gap Co-Authored-By: Claude Sonnet 5.5 --- docs/interlingua-standard.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/docs/interlingua-standard.md b/docs/interlingua-standard.md index a24b02c..192f152 100644 --- a/docs/interlingua-standard.md +++ b/docs/interlingua-standard.md @@ -202,12 +202,16 @@ telemetry, and it must name a predication of the packet. `V18` refuses a predica the gloss `request_intervention` (`frame:3` in the committed inventories) unless `addressee_consent` names that predication. The encoder can never set consent (`V15`), so an encoder-produced request frame is always refused. -Residual gaps: `V18` keys on that one gloss, so another frame that asserts the -addressee's act (for example a `frame:2` intervention on the original -inventory) or a renamed gloss is not covered; consent is one field, so two -request predications in one packet cannot validate; and the check that the -asker is the addressee was not kept. Follow-up -`weksa-lowering:follow_up:request-frame-consent-residual` owns them. +Limits: `V18` keys on the gloss `request_intervention` and sees no other frame +or concept, so a request-shaped meaning built from another frame or from a +renamed or newly minted frame is not seen by `validate`, which does not read +meaning; the scorer and flow own that classification +(`weksa-lowering:ruling:leak-owned-by-flow-and-scorer-3`). `addressee_consent` +is one field, so a packet carries one request predication, and a compound +request is two packets until a packet schema revision makes consent a set. The +asker is not checked to be the addressee: consent is the authored or telemetry +source's own record, and the lowerer that renders it sees the roles and owns +that check. ### `stance` -- 2.47.3 From 7a8b002f40c22d578faa7d2fdcbea9d61f031f96 Mon Sep 17 00:00:00 2001 From: Weksa Date: Sat, 14 Nov 2026 04:28:51 +0000 Subject: [PATCH 2/2] interlingua-standard: Limits cite the follow-up, drop the false scorer owner, scope the always-refused claim Co-Authored-By: Claude Sonnet 5.5 --- docs/interlingua-standard.md | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/docs/interlingua-standard.md b/docs/interlingua-standard.md index 192f152..ca8b860 100644 --- a/docs/interlingua-standard.md +++ b/docs/interlingua-standard.md @@ -201,17 +201,20 @@ addressee did. `V14` and `V15` check the field: it may be set only by authoring telemetry, and it must name a predication of the packet. `V18` refuses a predication whose frame resolves, at the packet's revision, to the gloss `request_intervention` (`frame:3` in the committed inventories) unless `addressee_consent` names that predication. The encoder can never set -consent (`V15`), so an encoder-produced request frame is always refused. -Limits: `V18` keys on the gloss `request_intervention` and sees no other frame -or concept, so a request-shaped meaning built from another frame or from a -renamed or newly minted frame is not seen by `validate`, which does not read -meaning; the scorer and flow own that classification -(`weksa-lowering:ruling:leak-owned-by-flow-and-scorer-3`). `addressee_consent` +consent (`V15`), so an encoder-produced `request_intervention` predication (`frame:3`) is always refused. +Limits, tracked by `weksa-lowering:follow_up:request-frame-consent-residual`: +`V18` keys on the gloss `request_intervention` and sees no other frame or +concept, so a request-shaped meaning built from another frame or concept (a +`frame:12` communication with `concept:6` request validates) or from a renamed +or newly minted frame is not seen by `validate`, which does not read meaning. +The inventory carries no marker for request shape, so classifying it would be +an inventory-shape decision for Imagination and language-ontology. `addressee_consent` is one field, so a packet carries one request predication, and a compound request is two packets until a packet schema revision makes consent a set. The -asker is not checked to be the addressee: consent is the authored or telemetry -source's own record, and the lowerer that renders it sees the roles and owns -that check. +asker is not checked to be the addressee: a consented `frame:3` whose agent is +not the addressee validates, and no code outside `validate` and the encoder +prompt text reads `addressee_consent`. That check is an owed obligation with no +owner yet. ### `stance` -- 2.47.3