Working Surfaceissues

One note a day

Each morning's note, written by the morning job from the pieces it verified and kept here as written. 64 issues since 16 September 2026.

Issue · 5 linksWednesday 18 November 2026Five accounts from 14 to 17 November show teams whose AI agents and AI tools now produce steady work turning their attention to where that work stalls or must be checked. An engineering leader, an Intuit engineering manager, a Salesforce team, PostHog's designers and Figma's TJ Pitre each describe where people now stand in that flow.
Issue · 5 linksTuesday 17 November 2026AI agents now write the stories and specifications that coding agents build from, and staff outside engineering build their own software with AI. Four accounts place a person or a separate system where that output is checked, and a test by the research lab Concept finds agents weak at knowing their colleagues.
Issue · 3 linksMonday 16 November 2026In three pieces, people put their own judgement into AI work. They count which AI review comments led to code changes, correct the glossaries AI agents read, and record where work waits after AI speeds up coding. Each keeps a record that people can recount and revise, instead of trusting the volume of what AI produces.
Issue · 3 linksSunday 15 November 2026A GENDA developer, a former Meta engineering manager and three Amazon Web Services authors each describe how a team can check AI-written work without trusting the AI agent's own account. One locks an agent's predictions before tests run, one makes the person directing the agent answer for the result, and one has business owners approve the criteria.
Issue · 7 linksSaturday 14 November 2026Seven accounts describe how teams decide which AI-written work gets checked closely as its volume grows. They sort changes by risk, keep the checker separate from the builder, and measure what each added check costs and whether the work paid off.
Issue · 11 linksFriday 13 November 2026Eleven accounts show teams deciding how far AI agents may act alone, from Sentry's quick-look merges to Shopify's watched attacking agent and Zalando's design system prototypes. Across them, freedom for the agent follows limits on what it can reach, automated checks and a named person who answers for it.
Issue · 3 linksThursday 12 November 2026The day's three accounts come from engineers whose AI agents write most of the code, at Amazon Web Services, at Thoughtworks and on a Snowflake finance project. Each describes engineers putting their effort into tests, release checks and protected files that decide whether the agents' work is correct.
Issue · 3 linksWednesday 11 November 2026Engineering teams at Salesforce, Shopify and LITALICO describe what changed once AI agents wrote most of their code. Each team wrote its engineers' judgement into shared skills, review rules or testing policies that agents read before every task.
Issue · 4 linksTuesday 10 November 2026Salesforce, Spotify, the developer Simon Willison and the security trainer Andrea Scaduto each describe where a person's judgement sits once AI agents do much of the work. Each names one point that a person must own: approving a merge or release, vouching for a summary, or defining good output.
Issue · 5 linksMonday 9 November 2026Five pieces describe teams adding deliberate structure as AI agents speed up their work and act for users: owners and measures at Docusign, protected time for questions, written rules for an agent's workspace, and decisions about what an agent may do and how users come to trust it. Each treats speed as a reason to decide in advance who checks the work and how.
Issue · 4 linksSunday 8 November 2026Four accounts describe AI agents that hand people only the decisions they cannot settle, with the facts and evidence attached. People review those decisions and that evidence instead of reading everything the agent wrote.
Issue · 5 linksSaturday 7 November 2026The day's pieces show teams judging AI-assisted work by evidence they can check, from the records an AI agent left behind to a design system's current values. They also show who holds that judgement, from the product manager to design-system representatives in design and engineering.
Issue · 5 linksFriday 6 November 2026Shopify, Dropbox, Microsoft and Modus Create each describe one standard path that work by AI agents passes through before customers see it. The paths include one test file for two apps, a written plan before each delegated task, undo tied to a conversation, one owner for each language problem and an approved plan before any code.
Issue · 4 linksThursday 5 November 2026Three engineering teams and a designer describe giving AI agents the routine gathering, building and repair work. Each one keeps a person at the step where a mistake would be hard to undo or hard to notice.
Issue · 6 linksWednesday 4 November 2026Six accounts describe teams that answer each failure or correction in AI-assisted work by changing a check, a rule or a shared record, not only the single result. They come from an engineering leader, a founding engineer at a start-up, a tech lead at Google, a product designer who studies where AI agents fail, a designer at a studio and a design team at Cisco.
Issue · 5 linksTuesday 3 November 2026The day's five pieces move the human check on AI-assisted work to before an AI agent writes anything, by reviewing its plan, its instructions or its rules, or by naming who answers for the result. A development head reviews plans, Figma's product managers share one set of AI skills, and a design consultant proposes governing a design system's rules as an AI skill, while a firm's chief executive and an A.Team guide name a responsible person in advance.
Issue · 4 linksMonday 2 November 2026The day's four accounts show teams working out who must be able to explain work made with AI tools: a designer, an engineer or a product manager. A database report shows the cost when no one could, and a retailer's design team found that an AI-written specification did not help its engineers.
Issue · 6 linksSunday 1 November 2026Six accounts from 28 to 31 October show teams deciding where a person must make the final call on the work of AI agents, and what that asks of the person. A payments app, a wealth manager and Meta's testing system each set that line, while John Cutler asks whether one profession should set it alone. An Atlassian survey finds AI's time savings moving into code review, and Anthropic's research product team expects new hires to push back.
Issue · 6 linksSaturday 31 October 2026Six accounts from the week to 30 October ask where the checking of AI work should sit as agents produce more of it. Each keeps a person reviewing, and most give that person something concrete to check against.
Issue · 4 linksFriday 30 October 2026Four accounts from Thoughtworks, GitHub, Nordhealth and Microsoft show teams deciding on purpose what AI agents do and what people keep. Each keeps judgement, code review, cost tracking or measurement with people while agents take on more of the building.
Issue · 5 linksThursday 29 October 2026Five accounts describe how people change what they do when AI agents raise the volume of work to check. They cover fixed rules for build agents, design rules written where agents read them, small checked changes, a guide to reviewing AI-written code and design leaders who ship work again.
Issue · 3 linksWednesday 28 October 2026Three teams move the human check on code written by AI agents to before the code exists, through a short design brief, settled component behaviour or automated checks. Each keeps one point where a person takes responsibility for the changes hardest to undo, such as cross-service design, migrations and releases.
Issue · 5 linksTuesday 27 October 2026Four teams made AI output reliable by first writing down how their own product works, from Reddit's map of its components to Netflix's old diagnosis rules. Each then checked the AI's work against something the AI did not write. An investor's essay argues for the same arrangement across a company: let staff build with AI agents inside access rules and audits.
Issue · 3 linksMonday 26 October 2026Design system teams are testing what AI agents build with pass-or-fail checks, and keeping the decisions behind each rule with named people. A design lead applies the same discipline to AI features themselves, asking who needs one before it is built.
Issue · 4 linksSunday 25 October 2026Teams that let AI agents and people outside engineering change real products rely on groundwork laid earlier: shared templates, written rules and tools that give predictable results. People stay in the loop where judgement matters, as code owners, reviewers and the keepers of design-system rules.
Issue · 6 linksSaturday 24 October 2026Each of the day's links deals with who checks and maintains the work of AI tools, and when. The teams that fare best limit what an AI agent may do alone, name the actions that wait for a person's approval and name who owns what AI built.
Issue · 5 linksFriday 23 October 2026Four teams and a product leader set the rules for AI work before it started and kept the checks outside the AI agents. A person or ordinary code decides what counts as done, from agreed requirements and separate sign-offs on scope and usability to permitted pushes and screens that match the product.
Issue · 4 linksThursday 22 October 2026When AI agents make building cheap, the remaining work is choosing what to build and recording decisions where people and AI agents can read them. Managers and specialists move closer to the work, coaching experiments, writing rules for AI agents and making technical decisions again.
Issue · 6 linksWednesday 21 October 2026The day's links show AI tools raising the volume of code, documents, pull requests and prototypes at companies of every size. Each finds that the gain counts only where people can judge, review and keep track of what the tools produce.
Issue · 4 linksTuesday 20 October 2026AI agents now write code faster than teams can decide what that code should do. Four writers argue that the scarce work has moved to judgement about what to build, what to leave out, what to check and how teams stay aligned.
Issue · 2 linksMonday 19 October 2026Two pieces show organisations adjusting to AI tools that make documents and software cheap to produce. One argues that written documents no longer prove effort or understanding, and the other shows companies giving non-engineers their own tools to build internal apps.
Issue · 6 linksSunday 18 October 2026Imprint and the Claude Code team at Anthropic each wrote down which code changes a person must read, and let their build tools enforce it. Petros Bountis and Ravi Mehta ask for a written test before a roadmap item or a prototype gets more effort. Marty Cagan and Paul Boag show the cost of rewarding promised dates or setting rules far from the work.
Issue · 6 linksSaturday 17 October 2026Three of the day's pieces show AI output that looks plausible at first glance, and the missing detail came from a person who checked it against something real. Razorpay, a payments company, names who owns quality once designers write code, and LinearB's Andrew Zigler proposes that AI agents check the review queue before adding to it.
Issue · 3 linksFriday 16 October 2026Three pieces describe teams adjusting to AI agents that produce more code and more conversations than people can read one by one. Uber and Your360 AI move routine checks to machines and keep people for flagged or risky work, while Sarah Wells questions whether the evidence shows more shipped work.
Issue · 3 linksThursday 15 October 2026A platform company reviews plans instead of code, and a product manager pairs prototypes with written documents. A usability researcher sets out guidelines for AI agents with standing goals, and each piece puts the decision in writing where another person can challenge it.
Issue · 6 linksWednesday 14 October 2026Six write-ups describe how checking work changes when AI agents produce much of it. Teams move routine checks into automated tests, give agents rules they can install or query, and keep people for intent, contested rules and widening an agent's authority.
Issue · 3 linksTuesday 13 October 2026Three pieces from 12 October show the slow step in AI-assisted software work moving from writing code to checking, debugging and supervising it. A survey, a strategy essay and a consultancy's operations account each describe how teams measure or reorganise around that shift.
Issue · 1 linkMonday 12 October 2026One essay from 9 October notes that software apps are converging on chat interfaces faster than hardware products ever converged. This issue uses it to ask who writes down what a product is for before a team chooses its form.
Issue · 4 linksSunday 11 October 2026Four pieces from 9 and 10 October look at the written material AI agents work from and at who checks what those agents change. A study, a customer story, an essay and a proposal show files being written and changes reviewed, but rarely a named keeper for the files.
Issue · 5 linksSaturday 10 October 2026Five pieces describe who sets and enforces the rules for AI agents that act with little supervision. They give that duty to managers, to a renamed documentation team, to infrastructure, to design-system teams and to engineers who must learn to build agents.
Issue · 8 linksFriday 9 October 2026Eight pieces from 7 and 8 October show teams deciding in writing what a person still approves when AI agents take on routine work. They place the rules in approval steps, handoffs, named owners and files the agent reads, and one asks whether the approvers still understand the work.
Issue · 6 linksThursday 8 October 2026Six pieces from 5 to 7 October describe AI agents producing code and prototypes faster than people can check them. Each places a human check somewhere: in reading, in required reviews, in limits on agents, in more frequent design reviews or in written decisions.
Issue · 6 linksWednesday 7 October 2026Six pieces from 6 October describe what happens after AI agents start doing most of the making: checking and choosing become the slow steps. Engineers, designers and researchers each describe a way to decide where a person must look closely and what automated checks can stop first.
Issue · 4 linksTuesday 6 October 2026Teams handing work to AI agents are deciding where human judgement sits and how to keep it from thinning out. Meta, a Manchester engineering department, the makers of Intent and QuantumBlack write that judgement down, keep it beside the work, or make agent output easy to check.
Issue · 2 linksMonday 5 October 2026Two pieces from the past week say that the output of an AI agent is the easier part of the work. The harder part is the human judgement around it: an engineer who knows the path to a finished change, and a product that shows users each change the agent made.
Issue · 2 linksSunday 4 October 2026Two companies describe teams that build a working prototype before the written requirements and then produce the specification alongside it. Microsoft's Foundry Labs team kept its specification current by hand, while Salesforce's design pipeline drafts the specification and the reason for each decision for engineers.
Issue · 4 linksSaturday 3 October 2026Four pieces show that the instructions, prompts and design rules an AI agent reads now need an owner and a regular review, much like code. Stripe and the designer Luke Wroblewski show that material improving through use, and a Nielsen Norman Group study shows personal agent setups decaying without it.
Issue · 4 linksFriday 2 October 2026Three pieces describe where an AI agent stops and a person takes over, whether in product code, in a product's promises or in its tools for agents. Each one treats that limit as something to design and write down before anything fails. A fourth, a podcast on innovation, argues that a new solution is worth building only when it serves the customer better.
Issue · 3 linksThursday 1 October 2026Three pieces from the past four days place the risk of AI-assisted work at the moment a person must explain or judge what an AI agent produced. An engineering leader, a usability researcher and a summit of product leaders each argue that understanding and judgement do not grow with output and have to be checked on purpose.
Issue · 3 linksWednesday 30 September 2026Dropbox, Shopify and Figma describe what changes once AI agents make building cheap. Dropbox checks agent changes like a person's, Shopify rebuilds its apps natively with one shared test suite, and Figma's product lead says choosing a direction is now the hard part.
Issue · 11 linksTuesday 29 September 2026When AI tools do more of the drafting and building, some work that people did along the way stops happening. Six pieces name parts of it, from practising a skill to writing down why a rule exists, and suggest how a team can keep doing that work. Five engineering pieces from 29 September cover teams of coding agents, architecture, a developer survey, earlier approvals and how junior engineers build judgement.
Issue · 10 linksMonday 28 September 2026Five pieces from designers and engineers show which jobs people keep when AI agents do the building. They keep the design system and the first screen, the review of what agents make, the files agents read, and responsibility for the product as a whole. Five engineering pieces from 28 September cover reviewing AI-written code, agents that change live systems, agents that build agents, new AI models and tests written first.
Issue · 5 linksSunday 27 September 2026When AI writes part of a team's work, reviewers and users need to see what was made, by whom and from what. The pieces label sections by author, link summaries to sources, keep one document per feature, show users when a save happens, and ask for expert reviewers.
Issue · 7 linksSaturday 26 September 2026Six pieces describe how teams change their work once AI agents can finish whole tasks. They show the result before the tool, take workflows apart before automating them, set checks before release and make people responsible for managing agents. One engineering piece from the same day asks whether engineers still enjoy the work once their team codes with AI.
Issue · 5 linksFriday 25 September 2026Three pieces look at what shapes AI work before anyone chooses: the defaults a product ships, the options a team rejects, and the material an AI can reach. Each argues that these inputs should be kept in view, and one argues that each needs a named owner. Two engineering pieces from the same day look at how AI tools change an engineering manager's job and how a large embedded-software company plans to reorganise around AI agents.
Issue · 4 linksThursday 24 September 2026Four pieces from Anthropic, Stripe, Cursor and Evil Martians describe setting the rules for AI agents' work before the work starts. The rules go into automatic checks, review policies, monitoring plans and the components themselves, and people judge what falls outside them.
Issue · 4 linksWednesday 23 September 2026Four pieces argue that people can keep up with work made by AI agents only when it reaches them in small pieces that have already been checked. They also say that the judgment people bring has to be built first, by reading real cases and by working beside experienced colleagues.
Issue · 4 linksTuesday 22 September 2026Four accounts from Warp, Linear and Bolt show how software teams check work now that AI agents produce it faster than people can review it. Each company moves part of the checking into written criteria, into files the agents read, or into a review split by expertise.
Issue · 5 linksMonday 21 September 2026Five pieces look at the work left for people once AI agents build quickly. It lies in reviewing agent-built changes, answering for what is handed over, and deciding what an interface promises its users.
Issue · 2 linksSunday 20 September 2026Two pieces look at the standing instructions people give AI agents before a task begins. Heavy users of one agent keep written rules, including which actions need their approval, and one engineer has his agent question him about each plan.
Issue · 3 linksSaturday 19 September 2026Three pieces show that AI now produces working prototypes, whole apps and product comparisons in minutes. Each argues that the result is worth trusting only when something is settled first or can be checked: a written problem, fixed parts, or values with a source.
Issue · 3 linksFriday 18 September 2026Three pieces show that a person's review of an AI agent's work is only as good as the reference that person checks against. Without a reliable reference, a reviewer can add errors instead of catching them.
Issue · 4 linksThursday 17 September 2026Four pieces show that when AI agents do the building, people's judgment moves to either end of the work. People state the problem and write checks before the build, and review the running result before it reaches production.
Issue · 5 linksWednesday 16 September 2026Five pieces show that when AI helps produce work, a person still has to check it against a source before others rely on it. Where nobody inside the company does that checking, the users end up doing it themselves.