Noc
Ask for an outcome. Noc plans it, previews it, and asks before anything irreversible.
A goal is one sentence. Noc turns it into a plan over capabilities the product already has, previews every step's exact effect, pauses before anything that can't be undone, and hands back one receipt for what actually ran. Autopilot is off in this build.
What Noc is
A goal is one sentence in your own words. Noc matches it to a plan of steps over capabilities that already exist in the product, and stores the plan before anything runs.
Every step is previewed before it runs — what it will read, what it will change, and whether it can be undone. Nothing runs until you confirm it, unless you delegated that exact kind of step ahead of time.
One receipt records what happened, written in the same transaction as the change itself, so it can never claim something happened that did not.
Work it supports today
Each of these starts on a real page in the product. Nothing here is planned or promised.
Give Noc a goal in your own words
A stored plan of steps, matched to a goal template, waiting for you to confirm the first one.
- Open Give Noc a goal.
- Describe the outcome you want.
- Review the plan Noc proposes.
Plan a run from a template, one step at a time
A run built from a named, already-authored template, confirmed step by step.
- Open Plan a run.
- Choose a template.
- Confirm each step as Noc previews it.
Watch a run to its receipt
A finished run's steps, each with its own receipt, and one terminal receipt for the whole thing.
- Open a run from Noc's own list.
- Watch each step move from previewed to confirmed to done.
- Read the terminal receipt.
Pause everything, or delegate narrowly
Every step refused at once while paused, or a bounded delegation that expires and can be revoked.
- Open Noc controls.
- Pause the workspace if you need to stop everything now.
- Grant a narrow, expiring delegation instead, if you want Noc to act without asking each time.
Ask the Growth Desk who to talk to today
A ranked, explainable list of who to reach, which events matter, and which pipeline needs a follow-up -- each with the stored evidence behind it, never a claim that outreach already happened.
- Open the Growth Desk.
- Refresh it to rank today's recommendations from stored facts.
- Open one recommendation's rationale, then accept it into exactly one task.
By hand: plan a template one step at a time
Priya Anand at Halden Rowe Joinery wants to review a company's account map and leave a follow-up task, without typing a request in her own words.
- Priya opens Plan a run and chooses the "Acquisition target: review and follow up" template.
- She reviews the plan: read the account map, then create a follow-up task.
- She confirms the first step; Noc shows exactly what it will read before it runs.
- She confirms the second step and gets one receipt for the whole run.
Fictional names. Start here: /noc/plan
Or let Noc do it
Noc plans the steps, previews every effect, asks before anything irreversible, and hands back one receipt. Autopilot is off by default.
“Noc, review this company's account map and leave a follow-up task.”
- Read the company's account map: the people attached to it, and the other companies those people connect to. Nothing is written.
- Create the follow-up task. Undo cancels the task it created.
- Before anything irreversible
- Before it writes anything, Noc previews the exact record it will create and asks for your confirmation first — even though creating a task can be undone afterward.
- What you get back
- One receipt per step that ran, and one terminal receipt for the whole run, so you can see exactly what happened and when.
Capabilities this plan can use: 2. Each is registered, permission-bound and previewed.
What stays in your hands
Your permissions decide, every time
Noc carries your own permissions and never more: a step you couldn't do yourself is refused for Noc too. Using Noc at all needs noc.use; stopping or delegating needs noc.control or noc.delegate.
Pause stops every step at once
While the workspace is paused, every Noc step is refused before anything is read or written — including a step inside an active delegation.
A delegation is narrow, and it expires
Only reversible writes can ever be delegated ahead of time, a delegation can be scoped to named records, and it can be revoked or left to expire — after which every step asks again.
The Growth Desk never proposes outreach to someone who may not be contacted
A person who is suppressed or has withdrawn consent is never recommended for a conversation or an introduction; the Growth Desk proposes reviewing the data instead. A recommendation is never a record that a conversation happened — accepting it only creates one task.
The honest states
What the product really shows when there is nothing yet, when it refuses, and where this build stops.
What you see first
A new workspace has no runs yet
Noc's own page shows nothing until you give it a goal or plan a run yourself; there is no sample run.
When something is refused
A refusal says why, and nothing is invented in its place
When a step can't be reached honestly — for example, moving an acquisition target to approved when nobody has approved it yet — Noc records the refusal and its reason, and the goal continues where it truthfully can.
Not available in this build
Noc never sends, calls, publishes or pays on your behalf
A step that would need an outside provider is a boundary step: Noc stops before it and tells you why, and a person carries it out with their own tools.
Not decided yet
Autopilot is undecided
Whether Noc may ever run a step without asking first is not decided; this build keeps that switch off.
Next
To see Noc you need the noc.use permission. Acting needs the permissions your administrator grants.