meta.anchors.implementation_coverage

Every specification anchor has at least one explicitly declared Rust implementation entry. An anchor without one is an error. A test annotation or #[sage::item(...)] correspondence alone does not supply this entry. A placeholder implementation counts as an entry with its explicit status.

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

Implementation

Implemented crates/sage-meta/src/spec.rs:123–128

sage_meta::spec · lib:sage_meta

#![allow(unused)]
fn main() {
    // {anchor}`meta.anchors.implementation_coverage`
    pub fn validate_implementations(
        &self,
        rust: &crate::correspondence::CorrespondenceIndex,
    ) -> Vec<Diagnostic> {
        self.anchors

}

See more source ↗

Tests and review

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

Implemented sage_meta::tests_and_model_correspondence_do_not_replace_explicit_implementation_entries

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

#![allow(unused)]
fn main() {
#[test]
#[sage::test(meta.anchors.implementation_coverage)]
fn tests_and_model_correspondence_do_not_replace_explicit_implementation_entries() {
    let spec = SpecIndex::from_sources(&[source(
        "rules.md",
        "{anchor}`demo.rule` An independently covered rule.",
    )]);
    let rust = sage_meta::correspondence::CorrespondenceIndex::from_sources(&[sage_meta::correspondence::RustSource {
        crate_name: "demo".into(), target: "lib:demo".into(), file: "src/lib.rs".into(),
        source: "#[sage::item(crate)] mod model {}\n#[test] #[sage::test(demo.rule)] fn evidence() {}".into(),
    }]).unwrap();
    assert!(spec.validate(&rust.tests).is_empty());
    assert_eq!(spec.validate_implementations(&rust).len(), 1);
    assert!(
        spec.validate_implementations(&rust)[0]
            .message
            .contains("no associated Rust implementation")
    );
}
}

See more source ↗

TODO sage_meta::todo::independent_implementation_coverage

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

#![allow(unused)]
fn main() {
#[test]
    #[sage::test(meta.anchors.implementation_coverage)]
    fn independent_implementation_coverage() {
        // TODO: Missing implementation fails even when a test or Sage item
        // mapping exists; explicit placeholder entries retain their status.
    }
}

See more source ↗

Review: Accepted · Codex /root/anchor_094.

Fresh final followup review of implementation_coverage. Saved/read prior report and inputs, started fresh, recaptured all six dependencies and compared every fragment. Claim, both test bodies and all evidence/correspondence/check/helper captures are unchanged. The sole spec.rs delta is the implementation_references association comment on the separate unknown-reference validator; coverage behavior is unchanged.

The full claim requires every anchor to have an explicit Rust implementation entry, errors for missing entries, no substitution by tests or modeled-item correspondence, and placeholder entries counted with their explicit status. The sole ordinary implementation validate_implementations checks each anchor against only the implementations map and requires a nonempty vector. Missing and empty vectors produce a diagnostic at the defining source location. Test and item maps cannot satisfy this predicate. The captured main check invokes it independently from test validation; correspondence invokes the dedicated evidence indexer into the separate implementation map. Captured evidence construction preserves module-derived Ordinary/Todo/NotApplicable status, rationale and source metadata. Coverage accepts any nonempty entry vector without relabeling placeholders; conflicting placeholder ancestry produces its own error. The new marker does not affect any path.

The complete ordinary test tests_and_model_correspondence_do_not_replace_explicit_implementation_entries constructs a definition and real indexed Rust with both sage::item and sage::test but no implementation comment. It requires successful test validation, exactly one implementation diagnostic and the missing-Rust-implementation message. This directly exercises independence even when both other evidence types exist. Its captured source helper forwards actual text into SpecSource.

The sole TODO independent_implementation_coverage remains empty and explicit about the broader missing-entry/placeholder-status matrix. The ordinary test covers the combined negative scenario; separate cases and direct positive ordinary/TODO/N/A acceptance/status assertions remain deferred. Completing that verification requires distinct inventory fixtures and explicit acceptance/status assertions. Current source supports the predicate and retained statuses, but the TODO is not counted as behavioral proof or silently retired. No N/A evidence entry exists for this anchor.

The actual marker-only change was checked against the complete prior assessment, and all other relied-on inputs were verified unchanged. Full claim aspects remain implemented with the stated visible test deferral. No source edits, build or behavior tests occurred in this review; fresh start/read/record and source inspection 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.implementation_coverage

Implementation

Tests and review