kickside

Shared frontend vocabulary (CSS) that modules consume at build time.

Component service and registry for user-owned resources

KickSide engine root — threads, events, projections, retention, lifecycle reaping, thread notifications, proc supervision

KickSide durable leased-job engine and projection scheduler — jobs service/api/persist/workers, effect-intent machinery, and the leased cursor scheduler

KickSide base contracts

Convert PDF, Office, legacy Office, or RTF input into Markdown, with optional image extraction

KickSide uploads — upload API, storage pipeline, preview endpoints, artifact storage, file capabilities, and default text/image/document processors.

KickSide settings — runtime, admin-editable, DB-backed application settings. Modules declare typed setting definitions in the registry; the DB stores only admin overrides; reads fall back to declared defaults.

KickSide connections — provider credentials, resource discovery, and reply targets as components.

Typed executable Blocks for headless and visual Flow composition.

KickSide Widgets — shared UI web components reused across modules. Ships icon/model/multiselect/schedule pickers used by agents, knowledge, skills, and navigation appearance.

KickSide Models — the LLM model catalog, app-level provider profiles, DB-backed model overlays, resolver binding, discovery APIs, and settings web component. Registry ships defaults; runtime profiles/discovered models live in DB/cache.

The generic install/control/uninstall engine for the unified automation model.

KickSide users — auth, token storage, user/group persistence, directory lookup, per-user profile field store, admin API, and admin web component.

KickSide knowledge bases — KB registry, document/graph KB schema and data-access stores, ingestion/injection workers, concept-graph enrichment, and a user-facing CRUD API.

KickSide user agents — agent/tool registries, user-created agent components, the agent resolver, runner, and capability library, with a user-facing CRUD API.

KickSide security — scope and policy administration surface for app-owned security scopes.

KickSide dashboard — a registry-driven deployment overview. Discovers the installed navigable surfaces (view.components / ui.nav_items) and renders each as a card with the human description pulled from the entry meta and the owning module's ns.definition. No hardcoded module list; the page reflects whatever is installed.

KickSide inbox — central review/approval inbox with declarative, web-component-rendered item types and realtime updates.

Renders a PDF from a URL or a binary blob into per-page PNG, JPEG, or WEBP images