a0p-self-declaring-modules

Build a Python registry without centralized dispatch by having each module declare its own metadata and handler in a single file. A filesystem scanner discovers them at boot and generates the registry automatically. This eliminates manual central edits.

Auto-discover route modules for boot-time registry generation by using deterministic file scanning. Each route module colocates its SCHEMA and handler, allowing a scanner to assemble them into a live registry at boot without manual registration.

Self-declaring module metadata prevents drift by colocating the SCHEMA and handle function in one file. This ensures metadata and logic stay synchronized, so the registry generated by the filesystem scanner matches the actual implementation.

Yes, self-declaring module discovery requires the a0p-style single-file pattern. Modules must colocate their SCHEMA and handler in the same file and adhere to the 400-line cap enforced by a0p-module-doctrine for deterministic discovery.

When you add or remove a tool module from the registry directory, it appears or disappears from the registry after a reboot. The deterministic discovery scanner regenerates the live registry based on the current filesystem state.

Use filesystem scanning instead of a central registry to allow scalable growth without drift. New tools or modules appear by file addition and disappear by deletion, removing the need to manually update a central dispatch list.