meta.book.browser_dependencies

Method views render each declared envelope clause with its effect kind and target: invocations, input reads, context creation, and transitive prohibitions. They expose possible direct callees, reverse callers, and overriding implementations, using the validator’s conservative dispatch resolution. Inherited prohibitions retain their declaring method. Linked targets lead to the corresponding entities. These views label declared permissions and prohibitions as such; they do not imply that a permitted call happened or that runtime conformance has been established.

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

Implementation

TODO crates/sage-meta/tests/spec_plan.rs:162–169

sage_meta::todo · test:spec_plan

TODO: Compare every rendered effect, reverse caller, virtual target, and inherited prohibition with the validator, without implying execution.

#![allow(unused)]
fn main() {
    // {anchor}`meta.book.browser_dependencies`<<
    #[test]
    #[sage::test(meta.book.browser_dependencies)]
    fn browser_shows_declared_dependency_envelopes() {
        // TODO: Compare every rendered effect, reverse caller, virtual target, and
        // inherited prohibition with the validator, without implying execution.
    }
    // >>

}

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_shows_declared_dependency_envelopes

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

#![allow(unused)]
fn main() {
#[test]
    #[sage::test(meta.book.browser_dependencies)]
    fn browser_shows_declared_dependency_envelopes() {
        // TODO: Compare every rendered effect, reverse caller, virtual target, and
        // inherited prohibition with the validator, without implying execution.
    }
}

See more source ↗

Review: Accepted · final_quality.

Reviewed the entire meta.book.browser_dependencies claim and its complete current associated evidence. Both the sole implementation entry and sole test entry are the explicit todo::browser_shows_declared_dependency_envelopes region in spec_plan.rs. The function has only a TODO comment, so it establishes no executed assertion and must remain visibly deferred. No ordinary or N/A evidence is associated. No behavior tests were run in this review.

The claim requires four effect kinds and their targets (invocation, reads, context creation, transitive prohibition); possible direct callees and reverse callers; overriding implementations with validator-conservative dispatch; retained declaring-method provenance for inherited prohibitions; working links to corresponding entities; and clear declared-permission/prohibition semantics without claims of execution or runtime conformance. The TODO explicitly calls for comparing every rendered effect, reverse caller, virtual target and inherited prohibition with the validator without implying execution. This covers the integrated dependency-display work rather than treating one passing rendering assertion as sufficient.

To assess the deferral's prerequisites I captured browser.rs, web/browser.js and validate.rs. Existing browser code validates documents before serialization, builds a client-side method/call graph, resolves inherited method names and descendant targets, renders Invokes/Reads/Creates/ForbidTransitive clauses, constructs direct/incoming/override lists, and gathers inherited prohibition effects with their inherited method context. Method views include the explicit Permissions do not imply execution note and describe incoming edges as declared calls. Validator targets conservatively include the resolved declaration and known descendant implementations; resolve_contracts retains prohibition rule.operation ownership. These are useful existing components, but the browser independently reconstructs dispatch and the associated test does not establish parity, source-method presentation, link correctness or complete semantics. I do not promote this source inspection into an implementation-completeness approval for the deferred feature.

Replacing the existing TODO requires a validated multi-class/multi-method fixture containing all four effects, inheritance and overrides, inherited prohibitions, and resolvable field/context/method links. Assertions must compare displayed callee/reverse/override sets with validator resolution, verify the declaring method remains observable for each inherited prohibition, follow/check corresponding entity routes, and check permission/prohibition wording never claims execution or conformance. Only then can substantive implementation/test associations replace this placeholder. The existing TODO is an honest explicit deferral of that full matrix; this review records its status and prerequisites, not that the claim is implemented or tested. No source changes or additional edits are requested.

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_dependencies

Implementation

Tests and review