Process63
Constructors
Layers & Serving
configureconstA config-patch layer for the process tag — merge it with the process's layer and its patch (polling / a (previous) => next wrap of effect) folds onto the base config at build.layerfunctionThe local layer for a process: build its driver (auto-started) and provide its service.layerMemoryfunctionAlias of layer — soft-default in-memory Storage (override the same way).servefunctionServe a process and grant its local instance from one materialization.serveMemoryfunctionAlias of serve.serveRemotefunctionServe a process remotely (served-only) — mounts its RPC handlers without granting the local instance, preserving the requirement R for a per-resource Layer.provide.serveRemoteMemoryfunctionAlias of serveRemote.storefunctionRegister this process on an app Store.Service — built-in execution analytics with an optional bare spec object merged in: ts Process.store(Daily) Process.store(Daily, { audit: auditSchema, }, ({ audit, event }) => ({ appendAudit: audit.append, })) Schedule
atfunctionA point window (open-ended — no stop).currentScheduleIdconstIdentifier attached to the schedule entry that started the current run.processScheduleEntryconstOne scheduled run window on the wire — the wire form of the engine's ProcessScheduleEntry.schedulefunctionAttach a schedule to a process (pipeable).ScheduleconstDefine a standalone Schedule resource — a reusable, RPC-capable window manager one or more processes can be gated by (via .pipe(schedule(ThisSchedule))).scheduleControlsconstSchedule controls for the currently running process runtime.scheduleDefineconstA declarative schedule layer from a builder DSL: Process.scheduleDefine(({ at, window }) => [at("daily", d), window("game", start, end)]).scheduleGroupSpecconstThe schedule mutation verbs a process gains when it scheduleowns.scheduleHyperlinkSpecconstThe full CRUD contract of a standalone Schedule resource — the reusable window manager one or more processes can be gated by.scheduleInMemoryconstAn in-memory schedule layer seeded with entries — the Layer you hand to make's scheduleLayer.scheduleKindconstThis contract's canonical kind for a standalone Schedule resource.scheduleLayerconstThe local layer for a standalone Schedule resource — an in-memory window manager (optionally seeded with initial windows) that any number of processes can be gated by.scheduleServeconstServe a standalone Schedule resource and grant its local instance.windowfunctionA bounded window (start + stop).Models
ProcessinterfaceManaged process handle for the process manager.ProcessDefinitioninterfaceCanonical process declaration that can be registered with a typed the process manager.ProcessEffectRequirementstypeExtract service requirements from a Process handle.ProcessExecutionEventtypeProcessInstanceSpectypePer-tag process spec — control surface, live events, plus stamped run success/error on the wire.ProcessLayerConfiginterfaceConfig for layer / serve / serveRemote.ProcessLiveEventtypeOne process execution lifecycle fact — shared by live Process.events and durable store rows (Started | Completed | Failed | Interrupted).ProcessMaketypeProcessMakeOptionsinterfaceConfiguration for Process.make when using the config-object form (id is separate).ProcessPollingInputtypeProcessScheduleContextinterfaceContext for the currently running scheduled window.ProcessScheduleControlsinterfaceUser-facing controls for a process's schedule — enumerate, set, add, and clear entries.ProcessScheduleInitializertypeA function that seeds a process's schedule via its ProcessScheduleControls.ProcessScheduleInputtypeProcessScheduleLayerInputtypeProcessServiceBuildertypeProcessServiceDefinitioninterfaceCanonical process service declaration.ProcessServiceFactorytypeProcessSnapshotinterfaceA one-shot read of a managed process's runtime mirror — the observable state the supervisor maintains as it reconciles the schedule and spawns instances.ProcessSpectypeThe base (schedule-less, result-less) process spec.ProcessSupervisorRequirementstypeServices still required at the fork site for Process.effect for a given ProcessMakeConfig.ProcessTagBuildtypeCallable shape for Tag — overloads for positional schemas + config object.ProcessTagOptionstypeOptions for Tag — use as the sole 2nd argument (config-object overload) or merge with positional success / error args.ScheduleControlstypeThe subset of schedule controls handed to a ProcessScheduleInitializer (entries / set / add / clear) and available inside the process effect via scheduleControls.ScheduleEntrytypeA native engine schedule entry — { id?, startAt, stopAt? }, the same shape as a ScheduleWindow (at / window build these).ScheduleHyperlinkSpectypeThe standalone Schedule resource's spec.ScheduleReconcileResulttypeThe diff produced by ScheduleService.reconcile — the entry ids that were added / updated / removed / left unchanged.ScheduleServicetypeThe engine schedule service — run-window storage + controls (entries / changed / CRUD / reconcile) that a make supervisor watches for arming decisions.ScheduleWindowinterfaceA schedule window template produced by at / window — the declarative form of a schedule entry.Wire Schemas
buildProcessSpecconstBuild a process instance spec — control surface, live events stream, and a typed manual run RPC.kindconstThis contract's canonical kind — stamped on every process tag so consumers (e.g.processControlSpecconstThe base process control + observation contract — shared by every process.processExecutionEventconstExecution event union for void processes (no success field on Completed).processExecutionEventForconstBuild an execution event union when the process tag carries a ProcessTagOptions.success.processLogEntryconstLog entry wire schema — alias of LogEntrySchema.processSpecconstErased baseline process spec (Void success, Never error).processStatusconstThe current-state snapshot of a managed process — the wire form of the engine's ProcessSnapshot (plus supervising).