If you are curious here is a quick live example. As part of an automated hunt for quotes on something there is a process that tries public contact methods. To avoid spam people use contact forms on websites and try to detect bots but we also scrape their page for contact information. In this case the system failed to detect the form AND incorrectly scraped an example from an email text-box on the form. This is a first pass proposal. It doesn't mention all the routine tests like unit tests on the code and remediating automated checks because I don't want it cluttering up the proposal. But note it proposes both a sandboxed model test for the logic as well as the final production test.
The last bit an estimated token cost to make the change. If the numbers supported it he'd split it into multiple units of work and smartly manage subagents to execute eligible pieces in parallel that are estimated to be big enough to justify it while being small enough to fall within the 'smart window' context size [LLMs seem to get... dumber... beyond a certain fill threshold in their context window]. Company name changed to protect the innocent.
It will take longer for me to write this reply than this proposal to be executed, including building the sandboxed test.
"
PROPOSAL #834 and #833: Someone of Harrisburg's quote form (Ted, 2026-10-29)
What I found (read-only): the sub's website on record is the franchise page someone.com/harrisburg-il. The form search never opens that page, because it tries /contact, /quote and the home page at the root of the domain. Those pages belong to the national brand, so a form found there would reach corporate, not the Harrisburg owner. The franchise page does carry the quote form. It is built on the Neighborly platform: fields marked data-nbly, labelled but with no name attributes, sent by script. The form detector does not recognize it, which is why resolve returned form=-. The same form's email box has the placeholder "ex. johnsmith@gmail.com", and the resolver harvested that as the sub's email (#833).
Plan, one ticket under #834 with #833 folded in:
1. Form search: open the recorded website page itself first, with tracking parameters stripped. A form on the company's own page beats one on the brand's national pages.
2. Detection: recognize the Neighborly form and fill it through the browser path by its labels. Add an offline replay test built from the saved page.
3. #833: the resolver never takes an email from an input's placeholder or value. Add a test, and clear sub 1767's stored email through the stage's re-run, not by hand.
4. Re-run resolve for sub 1767 to confirm the form is recorded. Then reset-form so the contact stage sends the form and the text, as Shaitan said.
Estimate about 120k.
If you approve it, send "execute 834".