meta.language.methods.kinds

Methods retain their declared operation kind: query or fn. Resolving a method’s contract preserves that distinction.

Queries describe memoized semantic products; functions describe ordinary computation. These annotations document boundaries; the model has no evaluator or cache.

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::query_and_function_kinds_survive_contract_resolution

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

#![allow(unused)]
fn main() {
#[test]
#[sage::test(meta.language.methods.kinds)]
fn query_and_function_kinds_survive_contract_resolution() {
    let document = valid(
        r#"class Item { """Item."""
            query signature() -> u32 { """A product.""" envelope {} }
            fn work() -> u32 { """A computation.""" envelope {} }
        }"#,
    );
    assert_eq!(class(&document, "Item").methods[0].kind, MethodKind::Query);
    assert_eq!(
        class(&document, "Item").methods[1].kind,
        MethodKind::Function
    );
    let model = ContractModel::new(&[document]).unwrap();
    assert_eq!(
        model.operations()["demo::Item::signature"].kind,
        MethodKind::Query
    );
    assert_eq!(
        model.operations()["demo::Item::work"].kind,
        MethodKind::Function
    );
}
}

See more source ↗

Review: Accepted · Codex /root/anchor_202 independent review.

Independently verified exact byte equality of current parser.rs, validate.rs, and envelopes.rs against the supplied historical snapshots, then reassessed the current complete claim, both ordinary implementation entries, and the sole ordinary associated test. Parser::method selects Query for query and requires fn for Function, and stores kind in Method. resolve_contracts copies method.kind into each OperationContract; later permission/dispatch construction does not replace it. Captured ContractModel::new/operations confirms the test observes this resolved map. The complete query_and_function_kinds_survive_contract_resolution test declares one of each operation kind and explicitly asserts Query and Function both on parsed methods and on their corresponding resolved operations. Thus either collapsing, swapping, or losing the distinction is detected. Captured parse/valid/class helpers establish that these assertions inspect the parsed, validated fixture. The claim's memoized-semantic-product versus ordinary-computation wording describes boundary metadata, expressly excluding an evaluator/cache; the inspected parser and contract construction preserve this metadata without evaluating methods or memoizing results. It does not require runtime cache behavior or cache tests. There are no TODO/N/A entries or deferred prerequisites. Historical approval was supporting baseline context, not substituted for this assessment. I ran review start, review read, and byte-comparison commands; no behavioral tests or build were run by me. The coordinator separately reports 321 passing functional sage-meta tests and a successful root cargo build. No source changes or requested edits.

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.methods.kinds

Implementation

Tests and review