SECURITY AND GOVERNANCE

How the factory stays under control.

What engineering leaders and security teams ask before NOCT touches a production codebase, answered precisely.

How changes are verified

Every change is checked in a separate stage from the agents that wrote it: two independent AI reviews, unit tests, mutation tests on money logic and end-to-end tests on a preview environment, each against the specification and its acceptance criteria. Verification reduces risk; it does not guarantee that a change is correct, which is why high-risk changes also need a person.

How approval gates work

A merge gate classifies each change by risk. Low-risk changes with every gate green may merge automatically. Changes to payments, refunds, financial calculations and other sensitive logic wait for a named approver. Customers set their own policy.

How NOCT works with your repositories and infrastructure

NOCT operates through your existing source control, ticketing and CI/CD. It opens branches and pull requests like an engineer would; deployment runs through your pipeline and stays under your control.

Auditability and traceability

Every specification, clarifying question and answer, model call, review, test result and approval is logged against the change it belongs to, from business intent to merge.

Controls around high-risk work

Agents cannot edit their own tests or gate configuration. Secrets are scanned and kept out of pull requests. Each run has a budget and a stop switch.

Separation of implementation and verification

Builders and checkers are different agents with different instructions, and a second model must agree before an AI decision stands.

FAQ

Questions engineering leaders ask first.

Is NOCT fully autonomous?

No. People state the intent, answer the questions NOCT cannot answer itself and approve high-risk changes. Everything in between runs on its own.

Is NOCT a wrapper around Cursor or Claude?

No. NOCT uses leading models and coding agents as building blocks and switches between them. What it adds is the system around them: specification, readiness, dispatch, independent verification and governed release.

Does it replace engineers?

It changes their work. Engineers set direction, own the architecture and make the consequential decisions while the factory carries more of the delivery volume.

What does NOCT need from us?

Access to your repositories, ticketing and CI/CD, and a business owner who can state what they want. Design partners are onboarded by the founding team.

How is success measured?

On lead time, throughput, change failure rate, human interventions per 100 changes and cost per delivered change, reported to you regularly.

Request early accessWatch the factory work