A system you
can trace.
Follow the foundations into runtime composition, then out to every direct and transitive consumer.
Start at a leaf. Follow the impact.
This graph describes local manifest dependencies, including optional edges. It is not a resolved Cargo feature graph or a promise that every path runs by default. Dev dependencies are listed separately.
Small contracts. Explicit connections.
Types, authority, filesystem contracts
harw-types, harw-authority, and harw-fsutil carry the identities, permission algebra, and file boundaries used above them.
Context, tools, plans, and state
Separate contracts define what can be executed, what can be remembered, and how a unit of work is admitted.
Core sessions and runtime assembly
harw-core owns the turn loop; bridges connect child agents and durable plans. harw-runtime composes services under the selected entry profile.
CLI, TUI, SDK, and restricted transports
The CLI composes the application. TUI, web, jobs, and gateways each use their own profile rather than inheriting a universal tool surface.