meta.language.envelopes.reads

reads self.field; permits reading a field declared on this receiver’s class or inherited from a base. Unknown fields and non-self field paths are errors.

Read in specification context · design/meta/language.md

Tests and review

Indexed tests and the implementation-completeness and test-adequacy review; no test run is implied.

Implemented sage_meta::reads_accept_inherited_fields_and_reject_unknown_or_foreign_fields

crates/sage-meta/tests/envelopes.rs · test:envelopes

#![allow(unused)]
fn main() {
#[test]
#[sage::test(meta.language.envelopes.reads)]
fn reads_accept_inherited_fields_and_reject_unknown_or_foreign_fields() {
    let source = r#"class Base { """Base.""" input value: u32; }
        class Child extends crate::Base { """Child."""
            fn work() -> u32 { """Read input.""" envelope { reads self.value; } }
        }"#;
    valid(source);
    for path in ["self.missing", "crate::Base::value"] {
        let document = parse(&source.replace("self.value", path));
        let errors = sage_meta::validate(&[document]);
        assert!(!errors.is_empty(), "accepted invalid field read: {path}");
    }
}
}

See more source ↗

Review: Accepted · Codex /root/anchor_198.

Reviewed the complete claim, sole ordinary implementation association in validate.rs, and sole ordinary test reads_accept_inherited_fields_and_reject_unknown_or_foreign_fields. Model::check accepts reads only when the root is self, exactly one field segment exists, and the field occurs in ancestors(key). ancestors begins with the receiver class itself and follows bases, accounting for both directly declared and inherited fields; missing fields or non-self paths produce a diagnostic. The test accepts an inherited input field through valid (captured helper asserts no validation errors), then changes only the path and explicitly asserts errors for self.missing and crate::Base::value. These positive/negative scenarios and the common ancestry lookup substantiate the prior direct/inherited-field rationale; there is no separate direct-field assertion, but direct fields use the same search including its first receiver entry. The negative assertions would catch accepting either invalid read. Captured parse/valid helpers establish fixture construction and positive assertion semantics. No TODO/N/A entries or deferred prerequisites exist. Independently verified exact byte equality of current validate.rs and envelopes.rs with historical implementation_sources/test_sources; historical approval was context, and current evidence was reassessed. This is source inspection and byte-comparison evidence. I ran review start/read and record, not behavioral tests or a build; coordinator-reported 321 passing functional tests and root build are separate execution evidence. No changes required.

Browse meta anchors

116 anchors

Anchor Implementation Tests

meta (116) 102 Implemented24 TODO 103 Implemented36 TODO

meta.anchors (22) 22 Implemented 21 Implemented12 TODO

anchor_pages Implemented ImplementedTODO

Every specification anchor has a stable page identifying the rule and showing its definition, context, implementation entries, and tests/evidence. The page includes Rust excerpts and access to surrounding source, and exposes each entry’s placeholder status and explanation. Multiple sites remain individually inspectable rather than being reduced to a single coverage badge.

Symposiun AGentic Environment (SAGE)

meta.language.envelopes.reads

Implementation

Tests and review