Directory pages the platform creates now file their own link

Listing pages built for a location now come back with the public address attached, and a recheck no longer turns a listing we hold into an unclaimed one. Underneath, the agent that reads a support conversation learned when to write the reply itself.

Most of today went into listings: making the automated runs finish the job they say they finished, and making a recheck read ownership correctly. The rest went into the tools we use to answer partners.

For our partners

1. When the platform creates a directory page for a location, the public address of that page is now saved on the location.
2. A recheck no longer turns a listing we hold the login for into an unclaimed one, and the location summary counts only what is really unclaimed.
3. When a directory will not let a run finish, it stops with the reason and the next step instead of carrying on.

1. Pages come back with their link

The agent that builds listings now takes the address the directory itself offers for the client’s town rather than typing one in, and once the page exists it reads the page’s own public address back and attaches it to the location. That holds whether the run completed the claim or made the page and handed the last verification step to the client. Before, a page could exist with nothing on the location pointing at it.

2. Ownership through a recheck

A few partners saw pages we hold flip to unclaimed after a recheck. That is resolved. Some directories keep showing a claim prompt on a page until the client confirms it, and a read of that prompt now only changes ownership on a listing nobody holds. A listing that is ours, the client’s, or held through a listings provider keeps its ownership, and anything a person set by hand still wins.

3. Stopping on purpose

Two new stops: the directory rejecting the address, and the page not opening after it is created. Both come back to us with what happened and how to finish by hand. A run that stops this way attaches nothing, so a location never shows a link to a page that was never made.

Behind the scenes

1. The agent that reads a support conversation now drafts the reply itself when nothing has to happen before it goes out.
2. A to-do on a conversation is only for work that comes after the reply; anything the reply can settle goes out as a link or a fact.
3. The workspace where we grade agent work now covers the agents that answer send-backs on tasks, content and plans.

1 and 2. What the reply is for

The read used to hold its draft until the proposed work was done, on the reasoning that nobody should write a promise ahead of the thing. The cost showed up the first time a partner asked after something that had already been delivered: the agent confirmed it had gone out, proposed two to-dos, and wrote no words. Now it checks whether any proposed line needs a person’s hands first. If none do, the reply is written and saved as a draft at read time, with links to whatever already exists on the platform.

3. Grading the agents

Every read an agent produces opens in one place, with the thing it was handed, the thing it wrote, a grade, and a flag for filing a misbehaviour against the run. That now includes the agents that reply when a partner sends work back, so the sharpest feedback we get is the feedback we can measure against.