Microsoft Windows [Version 10.0.19045.0]
(c) Conduit x Waypoint. All runtime contracts reserved.
CONDUIT + WAYPOINT SDK
A professional crossover between Conduit and WaypointSDK: Conduit provides the terminal command surface, while WaypointSDK provides the creator-agent runtime framework that makes the system executable, inspectable, and ready for production integrations.
:: system map
+----------------------+ +------------------------+
| CONDUIT | | WAYPOINT SDK |
| terminal interface | ---> | TypeScript framework |
| operator command UX | | creator-agent runtime |
+----------------------+ +------------------------+
| |
v v
+----------------------+ +------------------------+
| live run visibility | | typed pipeline stages |
| docs / status / CLI | | deterministic handoffs |
| product surface | | provider adapters |
+----------------------+ +------------------------+
| |
+--------------+-----------------+
v
+----------------------+
| MEMORY + ARTIFACTS |
| commits, analytics, |
| traces, next actions |
+----------------------+:: what it is
C:\CONDUIT> Conduit is the terminal-facing command layer for autonomous creator operations.
C:\CONDUIT> WaypointSDK is the TypeScript runtime framework that coordinates the work underneath.
C:\CONDUIT> The collaboration turns creator-agent execution into a visible system instead of a hidden automation chain.
C:\CONDUIT> Waypoint defines the pipeline: stages, agents, inputs, outputs, artifacts, provider boundaries, analytics, and memory commits.
C:\CONDUIT> Conduit explains and operates that pipeline: what is running, which agent owns it, what was produced, and what should happen next.
C:\CONDUIT> The current framework is deliberately local-first and deterministic, so the workflow can be tested before real social, media, render, or publishing credentials are connected.
:: how the runtime works
WaypointSDK runs creator objectives through a fixed pipeline. Each stage has a type, assigned agent, status, input/output contract, and generated artifacts. Conduit reads that structure as a command layer so operators can understand the state of the workflow without digging through implementation details.
creator_objective
|
v
WaypointSDK Runtime Coordinator
|
+--> creator agents
+--> provider adapters
+--> local JSON persistence
+--> memory commits
|
v
Conduit Terminal Surface
|
+--> run status
+--> artifact review
+--> trace inspection
+--> next action:: pipeline stages
01. trend_discovery
02. strategy_planning
03. scriptwriting
04. media_generation
05. video_editing
06. remotion_render
07. platform_publish
08. community_engagement
09. analytics_review
10. optimization_loop
:: command examples
C:\CONDUIT> npm install
C:\CONDUIT> npm run waypoint -- run gaming
C:\CONDUIT> npm run waypoint -- inspect <runId>
C:\CONDUIT> npm run waypoint -- memory
C:\CONDUIT> conduit status --runtime waypoint
:: why the crossover matters
Conduit makes Waypoint visible. Waypoint makes Conduit operational. The crossover creates a clear product story: a terminal-first command experience for creator-agent systems, backed by a real TypeScript runtime that can coordinate agents, mock providers, persist artifacts, review analytics, and preserve memory across runs.