01-entry-points

To discover all entry points across a monorepo, inventory HTTP endpoints, event triggers, scheduled jobs, and WebSocket hubs. This reveals file paths, methods, routes, and auth levels grouped by project for architectural decisions.

System entry points in multi-language architecture are the surface area where external actors interact with the software. They include HTTP endpoints, message listeners, CLI commands, background workers, and startup hooks.

Classify authentication for API endpoints by inventorying each route and evaluating its access controls. This documents the auth classification for every entry point to support security reviews and boundary modeling.

Yes, you can identify non-HTTP triggers like background workers, CLI commands, event handlers, message listeners, and startup hooks. This reveals the full integration surface area beyond standard HTTP endpoints.

The best way to group endpoints by functional area is to inventory them by project and capability. This illuminates system boundaries, actors, and functional groupings for downstream architectural analysis.

Yes, entry point discovery works with SignalR and WebSocket hubs alongside scheduled jobs and startup hooks. It inventories these integration points with their file paths to reveal the complete system surface area.