meta.book.entity_links

Every declared Sage entity has an unambiguous direct link, including crates, modules, types, classes, contexts, methods/queries, and named members such as fields and enum variants. Opening a link selects the declaration or member in its rendered context without a prior search or browser session. Links resolve through the entity’s identity and owning scope: equal local names in different owners remain distinct, and relocating a chapter does not break links to unchanged model entities. Markdown and .sage sources can reference these identities; rendered references link to the corresponding entity and unresolved references are errors.

Entity links and specification anchors have different purposes. For example, $sage_ir::symbols::Symbol identifies a modeled declaration, whereas meta.book.entity_links identifies a testable rule. Making a declaration linkable does not create a specification rule or require an extra named paragraph. The authoring syntax for entity references and URL spelling remain implementation-plan decisions. Selection URLs and browser history follow the navigation rule.

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

Implementation

TODO crates/sage-meta/tests/spec_plan.rs:134–142

sage_meta::todo · test:spec_plan

TODO: Resolve every entity kind and named member without prior navigation; distinguish owners, retain links across chapter moves, and reject dangling Markdown/Sage references without inventing specification rules.

#![allow(unused)]
fn main() {
    // {anchor}`meta.book.entity_links`<<
    #[test]
    #[sage::test(meta.book.entity_links)]
    fn sage_entities_have_direct_links() {
        // TODO: Resolve every entity kind and named member without prior navigation;
        // distinguish owners, retain links across chapter moves, and reject dangling
        // Markdown/Sage references without inventing specification rules.
    }
    // >>

}

See more source ↗

Tests and review

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

TODO sage_meta::todo::sage_entities_have_direct_links

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

#![allow(unused)]
fn main() {
#[test]
    #[sage::test(meta.book.entity_links)]
    fn sage_entities_have_direct_links() {
        // TODO: Resolve every entity kind and named member without prior navigation;
        // distinguish owners, retain links across chapter moves, and reject dangling
        // Markdown/Sage references without inventing specification rules.
    }
}

See more source ↗

Review: Accepted · anchor_094 fresh final review.

Reviewed the full entity_links claim and every registered entry. The only implementation association is the explicit TODO region in spec_plan.rs around todo::sage_entities_have_direct_links; its only associated test has no assertions and is also TODO. Its explanation explicitly retains every entity kind/member, first-navigation resolution, owner disambiguation, moved chapters and dangling Markdown/Sage references without invented rules. Neither association is ordinary evidence, and no N/A entry exists.

Requirements accounted for: direct unambiguous links for crates/modules/types/classes/contexts/methods/queries/named fields/enum variants; immediate context selection without search or prior session; scoped identities disambiguating equal local names; resilience when a chapter moves but identities do not; references from both Markdown and Sage with rendered destinations and unresolved-reference errors; separation between model entities and named specification rules without an extra-paragraph requirement. Syntax and URL spelling are expressly left to implementation planning, so this review imposes no invented authoring syntax. The linked explorer_navigation claim additionally supplies selected-URL and history expectations; it was captured as a dependency rather than assumed proven here.

Captured browser.js shows partial foundations: buildModel keys declarations by namespace and owner and named variant fields by variant scope; entityRoute distinguishes crate/module/field/variant/item/method routes. Render dispatch selects declarations directly and renders named members in the owning declaration with selection markers. sourceOwner and bookHref use model scope and supplied chapter inventory, rather than deriving a current chapter from identity spelling. createNavigation reads encoded route/hash state and show renders that route and scrolls to a selected member; a missing model route displays Not found. These runtime helpers do not themselves establish build-time diagnostics for arbitrary unresolved authored entity references. The captured render_spec_markdown/prose_href code handles rendered Markdown/rule links and relative chapter URL rewriting. That machinery is not treated as proof of a fully specified, validated entity-reference authoring facility in both source formats.

Captured browser.test.cjs setup and three complete tests provide partial, unregistered assertions. Named-member tests assert route lookup, data-selected-member, owner resolution and searchable keys for actual fields/variants. The collision fixture gives First::value and Second::value distinct identities, checks distinct members, exactly one second selection marker and the correct descriptive content. The chapter-inventory test checks generated URLs across known entities and a relocated types chapter for a variant. These assertions support current pure-model/render helper behavior but do not launch a fresh browser session, validate authored references from both formats, prove published old URLs survive moves or exercise all declared kinds/history end to end. They therefore do not replace the registered TODO or justify changing its classification.

Deferral remains justified: completing this claim needs an agreed entity-reference authoring/resolution pipeline, its dangling-reference diagnostic coverage and integration tests covering every kind, same-named owners, a fresh selection URL and chapter relocation/history. The claim intentionally leaves syntax design open; those choices and browser-level test fixtures are prerequisites, not a reason to weaken the requirement. Making an entity linkable must continue to be independent of spec-anchor definitions and tests must assert that no synthetic specification rule is introduced. Existing navigation foundations can be reused when this planned work lands. This review accepts the explicit deferral, not a claim that every requirement is already implemented.

This was a source-only assessment: review start/read/record and source searches were executed, no tests/browser sessions were run, and no source edits were made. Central suite success is coordinator context and not independent execution by this reviewer. Dependency capture is complete for the assessment. 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.book.entity_links

Implementation

Tests and review