meta.book.browser_structure

Readers can navigate from crates to modules, declarations, and their members, with the owning crate, module, and declaration visible at each level. Crate views show purpose and dependencies. Declaration views show kind, descriptive prose, generic parameters, and the modeled structure: struct fields, enum variants and their fields, or the description of an opaque type. Class and context views show fields, base classes, and methods, distinguishing declared, inherited, abstract, and overriding methods. Method views show query/function kind, signature, and prose. References to modeled types, bases, and methods link to their declarations.

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

Implementation

TODO crates/sage-meta/tests/spec_plan.rs:144–151

sage_meta::todo · test:spec_plan

TODO: Exercise every declaration shape, ownership breadcrumb, inherited method, signature, and type link in book and standalone browser views.

#![allow(unused)]
fn main() {
    // {anchor}`meta.book.browser_structure`<<
    #[test]
    #[sage::test(meta.book.browser_structure)]
    fn browser_presents_declarations_and_members() {
        // TODO: Exercise every declaration shape, ownership breadcrumb, inherited
        // method, signature, and type link in book and standalone browser views.
    }
    // >>

}

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

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

#![allow(unused)]
fn main() {
#[test]
    #[sage::test(meta.book.browser_structure)]
    fn browser_presents_declarations_and_members() {
        // TODO: Exercise every declaration shape, ownership breadcrumb, inherited
        // method, signature, and type link in book and standalone browser views.
    }
}

See more source ↗

Review: Accepted · final_quality.

Reviewed the complete meta.book.browser_structure claim and all associated evidence. The sole implementation entry and sole test entry are the explicit todo::browser_presents_declarations_and_members region in spec_plan.rs. The test contains only its TODO comment, no assertions. The anchor therefore remains deferred, with no ordinary or N/A evidence and no claim of completed implementation or test adequacy. No behavior tests were run.

The full required matrix comprises navigation from crates through modules/declarations/members with visible ownership; crate purpose and dependencies; declaration kind/prose/generic parameters; struct fields, enum variants and their fields, opaque descriptions; class/context fields, bases and methods with declared/inherited/abstract/override distinctions; method query/function kind, signature and prose; and corresponding declaration links for modeled types, bases and methods. The TODO calls for every declaration shape, ownership breadcrumbs, inherited methods, signatures and type links in both book and standalone views. Crate purpose/dependencies and method distinctions belong within that same complete shape/navigation matrix and are not implicitly proven by the placeholder.

Captured web/browser.js provides concrete existing components for future assertions. The renderer has crate/module/item/method/member routes, breadcrumbs, purpose/dependency rendering, distinct struct/enum/opaque branches, generic parameter headings and recursive type links. Class/context branches render base/subclass links, declared fields/methods and inherited-method links; method cards display query/function kind, result type, prose and abstract/override badges. Named member routes resolve through their owning declaration with selected-member markup. This inspection identifies likely implementation paths and fixture needs, but does not establish that every required shape, ownership relationship and link behaves correctly.

Replacing the existing TODO requires validated fixtures covering multiple crates/modules, structs, generic and opaque types, enum unit/tuple/named variants, classes/contexts, inheritance and all method distinctions. Visible assertions must verify the exact displayed structure, owner breadcrumbs, signatures/prose and type/base/method/member destinations, then exercise navigation in standalone and embedded book views. The current explicit TODO honestly records that comprehensive work; its empty body is not runtime coverage. All claim aspects remain accounted for as deferred, not silently promoted based on source presence. No source edits or additional requested edits are necessary for this review.

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.browser_structure

Implementation

Tests and review