How to turn site fixes into code changes your developers can review and merge
Nova writes each fix as an implementation brief or code change against your repository, and your team reviews and merges it. Nothing is merged by the crew.
Website Crew
When you need this
Your site is custom-built, fixes need a developer, and briefs from marketing usually arrive too vague to act on.
How the crew does it
Write the implementation brief
Website Crew
For each fix, Nova states the target URL, the problem, the evidence, the risk and the change needed. Vega's search fixes arrive in the same format.
Draft the code change
Website Crew
When a repository is connected, Nova proposes the change as code for your developers to review.
Review and merge
You
Your developers review the change and decide whether to merge. Merging code always waits for a person.
Verify after deploy
Website Crew
Nova re-crawls the affected pages after deploy to confirm the fix landed.
What waits for you
Every merge into your codebase.
Connect
Website access
Measured by
Fixes merged and confirmed on the next crawl, and time from finding to deployed fix.
Limits
Code changes stay as proposals until a repository is connected. Nova does not deploy, and write access to code stays separate from read-only crawl work.