Authority never lives in the model.
Nova can propose an action. Your configured rules decide whether it proceeds, waits for an approver or remains blocked.
It asks in words you can act on.
When approval is required, the request names the exact action and target, why it is needed, the supporting evidence and which rule caused the pause.
The request and outcome stay with the work in NovaCore, so reviewers see the same decision that Nova will follow rather than a second workflow layered on top.
Approval is scoped to that one action. It does not widen Nova’s authority or grant a reusable credential.
Publish the verified fix for review
- Action
- Publish branch nova/checkout-confirmations to acme/storefront.
- Why
- Jira PAY-2841. Nova reproduced the bug, added a regression test and all 214 tests pass.
- Evidence
- Unit suite passed. Browser check confirmed one confirmation email. Three files changed.
- Approval rule
- Ask. Publishing a new remote branch requires a checkout-team approver. Merge and deployment are out of scope.
Choose how often people are asked.
Manual, assisted and autonomous modes change how often people are asked. Explicit blocks, budgets and safety rules remain in force in every mode.
- 01 Manual
- 02 Assisted recommended starting point
- 03 Autonomous
NovaCore starts in assisted mode: routine work can move while actions outside the approved envelope stop for a person.
What you can put boundaries around.
Which repositories
It only ever sees the ones you connect.
Which kinds of work
Bug fixes but not schema changes. Test coverage but not deployments. Your call.
Which environments
Freer in development, tighter or blocked in production.
How much it may spend
A ceiling per ticket and per team, enforced rather than requested.
Who can approve what
By role and by team, so a production change needs the right person.
When to escalate
If it is stuck, over budget, or past a deadline, it comes and finds someone.
These are settings, not instructions written into a prompt and hoped for. Nova cannot talk its way past them, and it does not matter what it was asked to do.
Check the outcome before trying again.
Actions are specific
Nova keeps the exact action and target together so a retry does not quietly become a duplicate change.
Outcomes are recorded
Success or failure stays with the approval. If the outcome is unknown, Nova checks the connected service before proceeding.
You can steer or stop
Add direction while Nova works, pause the current job or stop it. The work history remains available.
Every change has a paper trail.
For anything consequential, you can answer the questions an auditor or an incident review will ask: what happened, when, who approved it, what evidence they had, and what the outcome was.
This is the history Nova used while doing the work, not a summary invented afterwards: the request, approval, connected action, outcome and verification evidence.
- · What was changed, and where
- · Who approved it, and what they were shown
- · What evidence supported it: tests, tickets, reviews
- · What Nova did on the way
- · Whether it worked after it shipped
- · What it cost
Bring us your approval process.
Describe the path a change takes through your organisation today, and we will show you where each step lands. That is a more useful hour than any feature tour.