Components Index¶
This landing page mirrors every other section: quick orientation up top, then clear entry points into curated sub-guides. Start with the category that matches the kind of component you’re researching and follow the buttons to the detailed pages.
Runtime Apps¶
Executable CSApps (HubWindow, TriggerManager, ClipboardMonitor) each have their own deep dive covering launch flow, logging slugs, config locations, and operational notes.
Platform Services¶
Background services that keep automation stitched together: MouseHookPipe, Smrt.Web Host/Worker, and SmrtHubSupervisor. The detail page summarizes responsibilities and links to canonical READMEs.
Core Libraries¶
Shared libraries under SmrtApps/src (Smrt.Config, Smrt.Logging, Smrt.UI, Smrt.SupportBundle, etc.) with concise descriptions, stub callouts where documentation is still in flight, and links to the authoritative sources.
Python Modules¶
Everything under python_core: configuration resolver, runtime orchestrator, networking bridge, detection pipeline, SmrtSpace management, FlowEnhance, and the shared utilities—each with parity expectations and direct README links.
Why Components are grouped this way¶
- Runtime Apps map 1:1 with the packaged executables staged in
Apps/<Configuration>/<RID>/. - Platform Services are the headless processes those apps rely on for hooks, capture, supervision, and extraction orchestration.
- Core Libraries are referenced by multiple hosts and follow the central package/version policies.
- Python Modules provide the mirrored runtime surface so cross-language features stay predictable.
Each landing page uses the same layout (summary + buttons + curated highlights), so navigation stays consistent across the entire doc set.