Module families 

First-party tool families shipped through the open execution plane.

Each family is registered by the composition root exactly like a third-party one — catalog entries via Psp9AgentRuntime::with_tool_family and handlers via CandidateHandlerRegistry::register — so they double as the standing proof that the plane stays open. A future family is a crate depending on this handler contract; nothing in the loop, the candidate, or the node assembly names these tools.

Modules

db

Local DB explorer family: read-only, bounded queries over data files the workspace already contains (CSV, Parquet, JSON, DuckDB).

system

System explorer family: read-only operating-system and toolchain facts.

Functions

register_standard_families

Register every shipped family’s handlers.

standard_family_entries

Catalog entries for every shipped family.