Checked changes, and a release only with a "yes"

How the AgentOps control panel runs the work on two real projects: a municipal platform and a building-permit SaaS.

Product
AgentOps
Projects
Municipal platform · building-permit SaaS
Data
19–20 October 2026
Design approval · e-mail track, 14:09waiting 22 min

Approve the order confirmation e-mail

The confirmation e-mail on desktop and phone, with the delivery time and the deposit paid. Until it is decided, this track is on hold.

If yesThe e-mail design is linked to the confirmation e-mailThe e-mail track is unblocked and work continues from the template
If noThe track stays on hold and the reason is passed on
ApproveRejectAskapproved on the desktop screen
Review and checksthe last 40 of 124 check runs

Reviewedone minor note, approved

Two projects, one way of working

Different clients and different stages, the same rules: checks before a merge, a person's "yes" before a release.

Municipal residents' platform

Resident card, transport, events and services

Items in the plan
78
6 phases: from design to the apps
Check runs
124
7 automatic checks each
Merged changes
46
each one after green checks
Criteria met
174
each with evidence in the log

Building-permit SaaS

Building permits and an order forecast for all of Lithuania

Items in the plan
53
7 phases: from the skeleton to growth
Parallel work lanes
5
started 20 October
Decisions for the owner
10
prices, domain, payments, e-mail…
Released without a "yes"
0
nothing is deployed without the owner

Every change goes through the checks

124 runs on the municipal platform: 114 passed, and 9 times a change was stopped and sent back to be fixed.

passed 114stopped 9running 119 October 12:54 → 20 October 07:44
  1. Types
  2. Routing engine
  3. Migrations
  4. Database
  5. Web
  6. Build
  7. Container image
A stopped change does not reach the main branch until all seven checks are green.
Review

Green is not yet accepted

Every green change is also reviewed by a second reviewer. A serious finding holds the change until it is fixed.

46approved20sent back2comments
Mira reported today: #11 reviewed – one minor note, approved; on hold – a design needs approval
Decisions

A release waits for a person

The card says what happens on "yes" and what happens on "no". The answer is recorded with the time and the channel – on screen or by voice through Mira.

  • Design directionmunicipal platform · approved 20 October
  • ?
    Plan pricesbuilding-permit SaaS
  • ?
    Domain and payment providerbuilding-permit SaaS
  • ?
    Production servernothing is deployed until the owner says so
Design approval · e-mail track, 14:09waiting 22 min

Approve the order confirmation e-mail

If yesThe e-mail design is linked to the confirmation e-mail
If noThe track stays on hold and the reason is passed on
ApproveRejectAsk
Progress

Progress from evidence, not from guesses

An item counts as done only when its criteria are confirmed by evidence: tests, the whole flow working in a browser, security, privacy, design. Nobody ticks boxes by hand.

  • Done3
  • Running1
  • Building12
  • Planned62

Criteria with evidence

Tests51The whole flow works25Security18Privacy7Legal requirements7
Municipal platform, 78 items, 19 October.

What this means for your team

If your team works with AI agents, AgentOps shows what is happening and leaves the decisions to people.

  • You see every itemwhat is in progress, what is stuck and why
  • Nothing is merged without checksa failed check sends the change back
  • A release only with a "yes"on screen or by voice through Mira

Does your team work with AI agents?

We will show you AgentOps on your project and tell you what it takes to start.

Write to us

No call needed: describe the task, attach a specification, and we reply in writing.

Write a message

info@afkzonagroup.lt·+370 603 92409

Book a call

A 30-minute video call. We work out the task and tell you the price range.

November