Advanced and Internals

Most applications begin with submit_auto(lambda) on the Executor Facade. Use an independent Executor only for isolated resources; enter public advanced interfaces only for custom cycle sources, direct real-time/GPU control, or queue-implementation analysis.

Start with the source structure and reading guide to understand modules, ownership, and synchronization domains, then choose the topic you need:

1. Advanced interfaces: responsibility boundaries for instance isolation, ExecutorManager, and direct executor pointers.
2. Custom cycle source: implement ICycleManager and own its lifecycle.
3. How tasks travel through Executor: ordinary and real-time state transitions, promise fulfillment, and completion invariants.
4. Lock-free and performance experiments: LockFreeTaskExecutor, MPSC slot protocol, object pool, and backoff.
5. Performance measurement and regression checks: a consistent method for measuring throughput, tail latency, jitter, and correctness.

These internal pages describe the current implementation for debugging and performance analysis. Only public declarations under include/executor/ carry integration and compatibility expectations; types, structures, and scheduling details under src/ may change without public-behavior change. Fact sources include docs/design/executor.md, docs/design/lockfree_user_api.md, and docs/API.md.