PactAgent Developer Update: UI Redesign, DAO/Bounty Workflow Focus, and Agreement Operations Improvements

[Ajay]

Hi everyone,

I’d like to share a new developer update on PactAgent and get feedback from the Nervos CKB community.

For anyone seeing it for the first time, PactAgent is a milestone-based agreement and escrow workflow app built around Nervos CKB. The goal is to make direct work agreements, ecosystem bounties, and grant-style work easier to manage through clearer funding, proof submission, review, dispute, and settlement flows.

This update focuses on the recent UI redesign and improvements around DAO/bounty operations.

What I worked on recently

1. UI redesign across the app

I pushed a broad UI refresh across the main app experience, including the navbar, dashboard, agreement pages, and shared components.

The app now feels more like an operational workspace instead of a group of disconnected screens. The dashboard has been redesigned to make it easier to see:

• Which agreements need attention

• Who needs to act next

• What stage each agreement is in

• Where funding, review, or settlement risks may exist

The agreement page also now feels more like a live case file for each work agreement.

2. Agreement page improvements

The agreement detail page received a major upgrade.

It now gives clearer visibility into:

• Agreement status

• Next action

• Milestone progress

• Funding and settlement state

• Role-specific context

• Operational timeline

• Difference between direct agreements and imported work

For imported agreements, the funding section now shows more useful reserve information, such as reserve locked, reserve remaining, funding quote, and live quote comparison. This should make it easier for operators to understand whether the original funding still matches current quote conditions for unpaid work.

3. DAO/bounty import flow

I have also continued improving the forum-thread-to-agreement workflow.

Recent improvements include:

• Link-first import from a Nervos forum thread

• Source metadata capture and attribution

• Dynamic milestone extraction from source threads

• Imported grant context on the agreement page

• Stronger manual review framing

• Clearer imported workflow presentation across dashboard and detail pages

This is one area I am especially interested in getting feedback on. A lot of ecosystem work starts in a forum thread, but once execution begins, tracking progress, proof, funding, and settlement can become difficult. PactAgent is trying to help bridge that gap.

4. Imported grant funding and quote handling

I also improved the funding flow for imported grants, especially when the source budget is written in USD but the actual funding and settlement need to happen in CKB.

Recent improvements include:

• Live CKB/USD quote support

• Auto-filled CKB estimates from imported USD budgets

• Milestone-level USD-to-CKB helper inputs

• CKB-to-USD conversion helpers

• Total reserve visibility before funding

• Clearer post-funding quote awareness on the agreement page

The aim is to help operators fund reserves in CKB while still staying close to the original grant or bounty budget context.

5. Commencement payment support

For imported grants that include a separate kickoff or commencement payment, I improved the flow so that this payment does not have to be forced into Milestone 1.

This now supports:

• Commencement payment detection from source metadata

• Separate kickoff checkpoint behavior

• Clearer imported milestone structure

• Automatic kickoff release behavior after funding where applicable

This makes imported grant workflows more faithful to the original structure of the grant instead of flattening everything into a generic milestone model.

6. Proof review and human-in-the-loop controls

I also improved the proof and review layer so milestone approval can be more structured.

The current flow supports:

• Proof completeness checks

• Saved proof review states

• AI-drafted reviewer follow-up questions

• Structured reviewer information requests

• Worker responses to reviewer questions

• Human confirmation before high-stakes approval actions

The goal is not to let AI make payout decisions on its own. The goal is to reduce reviewer friction while keeping human approval in control of important decisions.

7. Source sync and governance-thread operations

Another important area is source sync for imported agreements.

Recent work includes:

• Agreement-page source sync controls

• Draft, review, and publish status flow

• Reviewer approval before outward posting

• Forum-aware sync behavior for Discourse-style threads

• Webhook support for source-sync events

This part is meant to connect agreement execution back to the original public governance thread, so updates do not get lost once work moves into execution.

8. Trust and ecosystem support features

Outside the core agreement flow, PactAgent now also has stronger support for:

• Public profiles

• Lightweight reputation views

• Invite links for draft agreements

• Webhook endpoint management

• Realtime agreement and activity updates

These features are meant to make PactAgent feel less like a one-time escrow tool and more like an operating layer for agreement coordination.

Why I’m sharing this

PactAgent is becoming more focused and opinionated.

The direction is now centered around:

• Direct milestone-based agreements

• DAO/bounty execution workflows

• Grant operations that connect source context, funding, proof, review, and settlement

This feels like the right direction to me, but I would really appreciate feedback from the community before pushing it further.

Feedback I’d appreciate

I’d especially like thoughts on these questions:

1. Does focusing PactAgent around direct agreements plus DAO/bounty imports make sense?

2. Would the dashboard and agreement-page direction be useful for real operators or reviewers?

3. Is the imported grant funding and live quote model understandable, or does it feel too complex?

4. Does separating commencement payments from normal milestones feel like the right approach?

5. Is the proof review plus human confirmation model credible for grant and bounty workflows?

6. Would source sync and forum update tooling be useful for Nervos ecosystem operations?

I have share screenshots of the current agreement lifecycle, import flow, and funding logic if that would make feedback easier.

Link to the repo and site:

https://github.com/Ajayfrizzy/pactagent

https://www.pactagent.online/

Thanks, and I’d really appreciate any thoughts or suggestions.

[Ajay]

Hi everyone,

I’d like to share a smaller follow-up update on PactAgent, focused mainly on the latest mobile view improvements.

After the previous UI redesign, I noticed that the desktop experience was becoming much stronger, but the mobile experience still needed more attention. Since PactAgent is meant to support operators, reviewers, clients, and workers who may need to check agreement status or take action quickly, I started improving the app so it feels more usable on smaller screens.

Latest mobile view improvements

I added a more mobile-friendly navigation structure across the app.

The mobile view now has a bottom navigation bar with the main actions:

• Home

• Dashboard

• Import

• Profile

• More

This makes the most important areas easier to reach without forcing users to rely on the desktop-style navigation.

I also moved secondary items like Webhooks into the More menu, while wallet access now sits separately in a hamburger menu. This helps keep the main mobile navigation cleaner and avoids overcrowding the bottom bar.

Mobile navigation state fixes

I also fixed some navigation state issues on mobile.

Previously, opening some menu sections could make the wrong page look active, especially around the Profile and More areas. That has now been improved so the active state better reflects what the user is actually viewing.

This should make the mobile experience feel less confusing when switching between agreement operations, profile settings, webhook settings, and other supporting pages.

Responsive layout improvements

I continued improving responsiveness across several screens, including:

• Dashboard

• Profile settings

• Webhook settings

• Agreement detail actions

• Admin replay actions

• Form flows

On smaller screens, key dashboard actions now stack better, buttons are easier to tap, and important action areas use the available width more effectively.

I also improved layouts where long content could break the mobile view. For example, webhook URLs, event labels, JSON examples, and long cards now wrap or scroll more cleanly instead of overflowing the screen.

Better mobile error and loading states

I also tightened some user feedback states.

Backend and wallet-related errors now show clearer messages instead of exposing large raw error responses in the UI. Loading states, pointer behavior, and button feedback are also more consistent across the agreement and admin flows.

Why this matters

The goal is to make PactAgent feel less like a desktop-only prototype and more like an agreement operations tool that can be checked and used from a phone.

This matters especially for workflows like:

• Reviewing agreement status

• Checking who needs to act next

• Viewing imported bounty or grant progress

• Managing proof review

• Checking funding or settlement state

• Responding to agreement actions while away from a laptop

There is still more mobile polish to do, but this update makes the app much more practical on smaller screens.

I’d appreciate feedback from anyone who tests the mobile view, especially around:

1. Whether the bottom navigation feels clear enough

2. Whether the More menu placement makes sense

3. Whether agreement and dashboard actions are easy to use on mobile

4. Any layout issues you notice on small screens

Thanks again to everyone following the progress of PactAgent.