01 · Positioning
How the product takes on the work
RunDock provides one control surface for projects, process trees, port ownership, logs, and scheduler state.
Developers can identify the real listener and runtime state before starting, stopping, or diagnosing a service.
02 · Context
The problem and the people
Why it needs to exist
As local projects multiply, start commands, ports, processes, logs, and schedules become scattered across terminals.
Who it is for
Developers maintaining several local projects, background processes, and scheduled tasks.
03 · Core flow
Core workflow
Four key views trace the complete path from entering the product to handling the work and confirming the outcome.
- 01
Runtime overview
See project health, active processes, and issues that need attention.
- 02
Projects and processes
Trace a project entry to its real service process and ancestry.
- 03
Live logs
Keep precise log context before and after an operation.
- 04
Ports and schedules
Check listeners, owners, and the next scheduled run.
04 · Product views
Four views of how the product works
All four views stay visible in a masonry gallery. Open any card for a larger view and continue with the arrow keys.
Runtime overview
See project health, active processes, and issues that need attention.
Projects and processes
Trace a project entry to its real service process and ancestry.
Live logs
Keep precise log context before and after an operation.
Ports and schedules
Check listeners, owners, and the next scheduled run.
05 · Decisions
Three product decisions
- 01
Listeners beat status labels
A project is running only when port ownership, process ancestry, and health checks point to the same instance.
- 02
Process ancestry stays visible
The chain from launcher to service remains traceable so stopping a shell cannot leave a hidden listener behind.
- 03
Actions need before-and-after evidence
Start, stop, and restart record their baseline and outcome instead of trusting an asynchronous button response.
06 · Current state
What is complete—and what is not
Local project and process management capabilities are implemented.
What the product changes
Developers can identify the real listener and runtime state before starting, stopping, or diagnosing a service.
Source and implementation
Source links are listed above; public screens still use synthetic or redacted data only.
Portfolio boundary
This site shows redacted interfaces and product logic only. It never connects to source databases or performs real publishing, applications, sending, or payments.
Next