Orchestration
Thursday routes work between NITE DSP tools, handing a prepared document to the right verifier, or analysis output to the right reviewer, without you gluing steps together.
Internal Systems Family
The NITE DSP internal layer.
Orchestration · Planning · Verification
Every NITE DSP product does one job well. Thursday is the internal infrastructure layer that coordinates workflows between specialized components, plans multi-step jobs, and verifies results at every handoff. Thursday is internal infrastructure, not a public commercial product or consumer chatbot.
How It Works
Coordination with verification built in.
Workflows
Repeatable multi-step pipelines are defined once and reused. A submission-preparation workflow or a library-rescan workflow runs the same way every time.
Planning
Complex jobs are broken into ordered steps before execution, so each specialised component knows exactly what it receives and what it owes next.
Verification
Outputs are checked before handoff. Work moving through Thursday carries its evidence with it, and failed checks stop the pipeline rather than passing problems downstream.
What Thursday Is Not
Infrastructure, not conversation.
Not a chatbot
You don't converse with Thursday. It is infrastructure, it coordinates, it doesn't chat.
Not a cloud brain
Thursday coordinates local tools. Your creative material stays on your machine.
Not a product (yet)
Thursday is internal. It powers how NITE DSP products work together as the ecosystem grows.
The Ecosystem
One layer behind every tool.
As Submit, SLO, and KENN mature, Thursday is what lets them hand work to each other, safely, verifiably, locally.