Skip to content

LLM ready

/en/services/ai-governance.md

Title:
AI governance

Your team already codes with AI. Now prove the code works.

With your team, I define what agents handle alone, what needs review, and which checks block faulty work. I use specifications and tests.

Works with the agents your team already uses: Claude Code, Codex, Cursor, GitHub Copilot, Grok, Agy.

Using AI is not the same as having an AI process

Without agreed rules, everyone drives the agent their own way and nobody can prove what shipped.

AI without rules

  • Everyone configures the agent their own way
  • The agent changes the test until it passes
  • Large changes land without review
  • Nobody knows what the agent read or changed
  • Secrets and sensitive data end up in the prompt

AI with governance

  • Repository rules apply to every agent
  • An existing test is never loosened
  • Review is required at the agreed points
  • Every delivery carries evidence of what was done
  • Secrets kept out of the agents’ reach

What usually goes wrong when a team codes with agents

This is what the rules and checks must stop.

  • Exposed secrets (Critical): Keys and customer data copied into the agent’s context.
  • Loosened tests (Critical): The agent deletes or relaxes a test so the delivery passes.
  • Unreviewed changes (High): Large changes land directly, with nobody reading them.
  • Unaudited dependencies (High): The agent installs libraries nobody has assessed.
  • Uneven usage (Medium): Everyone has their own way, and the result depends on who asked.
  • No evidence (Medium): The team cannot show what was checked in each delivery.

What the agent does alone, what needs review and what is blocked

An example of how the rules look. In the immersion, the team sets its own limits.

Runs alone

  • Read the code and propose a plan
  • Write new tests
  • Fix lint and formatting
  • Run the test suite

Needs review

  • Change business rules
  • Alter the database schema
  • Add dependencies
  • Touch authentication and permissions

Blocked

  • Delete or loosen an existing test
  • Read secrets and environment variables
  • Deploy to production
  • Rewrite git history

From immersion to rules in the repository

Three phases. The rules are written with the team, not handed down.

  1. Discovery: We understand the workflow and agree on rules with the team.
    • Map of the current workflow
    • Proposed rules
  2. Repository rollout: If commissioned, I add the rules and checks to the repository.
    • Agent rules
    • Delivery checks
  3. Follow-up: The team gets instructions for applying the method.
    • Rules document
    • Review checklist

How it starts

You know what will be assessed in the team’s workflow before you approve the immersion.

  1. First conversation: Tell me how the team uses AI today.
    • 30 minutes, at no cost.
  2. Discovery: We review the workflow and which steps need checks.
    • Map of the current workflow
    • Proposed rules
  3. Workshop: The team practices the method.
    • Practice with the proposed rules
    • Examples of tests and evidence
  4. Delivery: I hand over the method and implement it in the repository if commissioned.
    • Rules document
    • Review checklist
    • Repository rollout if commissioned

What you get

  • Workflow with specifications and tests
  • Rules and limits for agents
  • Shared memory and context
  • Independent review before delivery
  • Rules document and checklist
  • Instructions for proving each delivery

See the potential before you invest

Discovery helps the team agree on how to review and verify agents’ work.

  • Free first conversation: Show me where reviews fall short today.
  • Shared rules: The team agrees on which tasks agents can handle.
  • Evidence for each delivery: The team records what it checked before delivery.

What governance excludes

  • Tool licenses: Your team handles AI tool licenses.
  • Model training: The work covers how the team uses its agents.
  • Security audit: A product security audit is a separate service.

Who handles the work

I lead discovery and the workshop. I use specifications, tests and independent review to record how each delivery was verified.

Agents in my workflow: Claude Code, Codex, Grok, Agy, Cursor.

If one of these sounds familiar, it is time to agree on the rules

  • “Every developer drives the agent differently.”
  • “The agent made the test pass, but the bug is still there.”
  • “Nobody reviewed that giant pull request.”
  • “I have no idea what the agent read from our code.”
  • “We need to show the client how we guarantee quality.”

Frequently asked questions

Will we need to switch tools?

We start with the tools and workflow your team already uses.

Is rollout included?

You can commission it after discovery.

What happens during discovery?

We align on risks, review rules and the checks the team will use.

Does the team help set it up?

Yes. The workshop helps the team practice and refine the rules.

---
title: AI governance
url: https://nandomoreira.dev/en/services/ai-governance
---

# Your team already codes with AI. Now prove the code works.

With your team, I define what agents handle alone, what needs review, and which checks block faulty work. I use specifications and tests.

Works with the agents your team already uses: Claude Code, Codex, Cursor, GitHub Copilot, Grok, Agy.

## Using AI is not the same as having an AI process

Without agreed rules, everyone drives the agent their own way and nobody can prove what shipped.

### AI without rules

- Everyone configures the agent their own way
- The agent changes the test until it passes
- Large changes land without review
- Nobody knows what the agent read or changed
- Secrets and sensitive data end up in the prompt

### AI with governance

- Repository rules apply to every agent
- An existing test is never loosened
- Review is required at the agreed points
- Every delivery carries evidence of what was done
- Secrets kept out of the agents’ reach

## What usually goes wrong when a team codes with agents

This is what the rules and checks must stop.

- **Exposed secrets** (Critical): Keys and customer data copied into the agent’s context.
- **Loosened tests** (Critical): The agent deletes or relaxes a test so the delivery passes.
- **Unreviewed changes** (High): Large changes land directly, with nobody reading them.
- **Unaudited dependencies** (High): The agent installs libraries nobody has assessed.
- **Uneven usage** (Medium): Everyone has their own way, and the result depends on who asked.
- **No evidence** (Medium): The team cannot show what was checked in each delivery.

## What the agent does alone, what needs review and what is blocked

An example of how the rules look. In the immersion, the team sets its own limits.

### Runs alone

- Read the code and propose a plan
- Write new tests
- Fix lint and formatting
- Run the test suite

### Needs review

- Change business rules
- Alter the database schema
- Add dependencies
- Touch authentication and permissions

### Blocked

- Delete or loosen an existing test
- Read secrets and environment variables
- Deploy to production
- Rewrite git history


## From immersion to rules in the repository

Three phases. The rules are written with the team, not handed down.

1. **Discovery:** We understand the workflow and agree on rules with the team.
   - Map of the current workflow
   - Proposed rules
2. **Repository rollout:** If commissioned, I add the rules and checks to the repository.
   - Agent rules
   - Delivery checks
3. **Follow-up:** The team gets instructions for applying the method.
   - Rules document
   - Review checklist

## How it starts

You know what will be assessed in the team’s workflow before you approve the immersion.

1. **First conversation:** Tell me how the team uses AI today.
   - 30 minutes, at no cost.
2. **Discovery:** We review the workflow and which steps need checks.
   - Map of the current workflow
   - Proposed rules
3. **Workshop:** The team practices the method.
   - Practice with the proposed rules
   - Examples of tests and evidence
4. **Delivery:** I hand over the method and implement it in the repository if commissioned.
   - Rules document
   - Review checklist
   - Repository rollout if commissioned

## What you get

- Workflow with specifications and tests
- Rules and limits for agents
- Shared memory and context
- Independent review before delivery
- Rules document and checklist
- Instructions for proving each delivery

## See the potential before you invest

Discovery helps the team agree on how to review and verify agents’ work.

- **Free first conversation:** Show me where reviews fall short today.
- **Shared rules:** The team agrees on which tasks agents can handle.
- **Evidence for each delivery:** The team records what it checked before delivery.

## What governance excludes

- **Tool licenses:** Your team handles AI tool licenses.
- **Model training:** The work covers how the team uses its agents.
- **Security audit:** A product security audit is a separate service.

## Who handles the work

I lead discovery and the workshop. I use specifications, tests and independent review to record how each delivery was verified.

Agents in my workflow: Claude Code, Codex, Grok, Agy, Cursor.

## If one of these sounds familiar, it is time to agree on the rules

- “Every developer drives the agent differently.”
- “The agent made the test pass, but the bug is still there.”
- “Nobody reviewed that giant pull request.”
- “I have no idea what the agent read from our code.”
- “We need to show the client how we guarantee quality.”

## Frequently asked questions

### Will we need to switch tools?

We start with the tools and workflow your team already uses.

### Is rollout included?

You can commission it after discovery.

### What happens during discovery?

We align on risks, review rules and the checks the team will use.

### Does the team help set it up?

Yes. The workshop helps the team practice and refine the rules.

Ready to share.