meta.anchors.content.next_anchor

A new anchor definition ends the preceding anchor’s content immediately before the new marker. The new definition belongs to its own anchor; content extents do not overlap.

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

Tests and review

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

Implemented sage_meta::claims_retain_all_blocks_until_the_next_definition_or_document_end

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

#![allow(unused)]
fn main() {
#[test]
#[sage::test(meta.anchors.content.blocks)]
#[sage::test(meta.anchors.content.next_anchor)]
#[sage::test(meta.anchors.content.source_end)]
#[sage::test(meta.anchors.content.explicit_end)]
#[sage::test(meta.anchors.content.unmatched_end)]
fn claims_retain_all_blocks_until_the_next_definition_or_document_end() {
    let body = "Cachés retain **results**.\n\nA later paragraph qualifies the rule.\n\n- Keep unchanged inputs.\n- Recompute edited inputs.\n\n| Input | Result |\n| --- | --- |\n| same | reused |\n\n```rust\nlet résultat = cached();\n```\n\n    An indented example.\n\n> A quoted qualification.";
    let text = format!(
        "# Règles\n\n{{anchor}}`meta.first`\n{body}\n\n{{anchor}}`meta.second` Réévaluate.\n\nFinal qualification.  \n\n"
    );
    let index = SpecIndex::from_sources(&[source("rules.md", &text)]);
    assert!(index.diagnostics.is_empty(), "{:?}", index.diagnostics);
    let first = &index.anchors["meta.first"];
    let second = &index.anchors["meta.second"];
    assert_eq!(first.content, body);
    assert_eq!(second.content, "Réévaluate.\n\nFinal qualification.");
    for anchor in [first, second] {
        assert_eq!(
            &text[anchor.content_span.start..anchor.content_span.end],
            anchor.content
        );
    }
    assert!(first.content_span.end < second.span.start);
}
}

See more source ↗

Review: Accepted · final_quality.

Fresh final marker followup of meta.anchors.content.next_anchor. Preserved the previous input/output, started fresh, read the complete claim, associated implementation and test, and recaptured the prior source helper at tests/spec.rs lines 10–15. Compared all fragments by path/selector and implementation/test metadata. The sole change is an implementation_references comment on spec.rs validate_implementation_references. All claim, behavior, test, helper and metadata contents are unchanged; no fragments were removed. I assessed this unrelated marker delta against the complete prior findings and current relevant source.

The sole ordinary implementation association is the new-definition branch of parse_anchors. After validating definition syntax, paragraph position, identifier and prose, it calls finish_anchor with the new marker start, then creates a fresh active SpecAnchor with its own marker span and content start after the new name token. finish_anchor takes the previous active anchor, slices only up to that supplied boundary, trims surrounding whitespace and computes matching original source content spans. Therefore the new marker/text cannot enter the previous claim, and the new claim owns subsequent content. A first definition is allowed when no preceding active anchor exists. All helpers are within the captured implementation file.

The sole ordinary test claims_retain_all_blocks_until_the_next_definition_or_document_end creates a first marker on its own line and a second with same-line prose, without explicit ends. The first body contains Unicode prose, multiple paragraphs, a list, table, fenced and indented code and quotation. It asserts no diagnostics, exact first content equal to that body and exact second content equal to its own Unicode rule plus final qualification. For both anchors it verifies original-source content_span slices equal stored text, then explicitly asserts first.content_span.end < second.span.start. These assertions establish closure before the next marker, independent ownership and nonoverlap; the gap is boundary whitespace trimmed by finish_anchor. The captured source helper directly creates SpecSource, and the test invokes production from_sources. No TODO/N/A entries exist.

All claim aspects remain supported; the added association comment has no semantic effect. No source edits, formatting, test runs or workspace build were performed. Executed review start/read, capture comparisons and record only. No 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.anchors.content.next_anchor

Implementation

Tests and review