Nynch runs three engines in the background. The Authority engine builds your visibility profile across content and signals. The Pipeline engine keeps your deal records honest by checking for stale stages, missing evidence, and overdue next actions. The Admin engine handles imports, enrichment, and routine network maintenance.
For the first three weeks of Nynch, the engines were a black box. You set the schedule. You assumed the work was happening. Sometimes you’d notice the briefing pull in a new signal and infer the Authority engine had run. Mostly you trusted.
Trust without verification is a slow path to losing trust. Founding users started asking specific questions. “Did the Pipeline engine flag stale deals this week?” “What did the enrichment run actually update?” “Why hasn’t this contact’s profile refreshed?” The answer should have been one click away. It was three or four.
Each engine now opens as a 4-stage end-to-end view.
Inputs. What the engine is reading from your workspace. Specific record types, time windows, filter criteria. If you wonder why the engine isn’t touching a particular deal, you can see whether the deal even falls within the input set.
Processing. What the engine is doing right now, with timing. If it’s mid-run, you see progress. If it’s idle, you see the next scheduled run.
Outputs. What the engine produced on the last run. Linked back to the records it touched. The “what did this actually do” question becomes a scrollable list.
Schedule. What’s queued next, when, and why. If a run was skipped, the view tells you what condition prevented it.
If an engine is doing nothing useful, you can see it and tune the inputs. If an engine is doing a lot, you can see the impact and trust the schedule.
What changes for you. The engines stop being invisible work and become observable work. The “is this actually doing anything” question has a one-screen answer.
