Campaign Library opens to partners

The Campaign Library is no longer staff-only: partners see what the campaign knows next to Asks & Approvals. Approvals now read as a dated timeline per checkpoint, and links to a drafted piece open on the first click.

A day spent on what partners can see. Two surfaces that had been ours alone opened up, and several pages stopped asking anyone to decode them.

For our partners

1. The Campaign Library renders for every user, under a Collaboration heading in the client sidebar. Notes & feedback has left the sidebar, and its old address lands on Historic Filings.
2. Approvals on a task read as one dated timeline per checkpoint, with who sent each ask and who made each decision.
3. Links to a drafted piece on a WordPress site open on the first click. Some of them were being refused; that is resolved, and the drafts already waiting were corrected.
4. A site edit now says how wide it lands: named pages, a shared template, or the whole site.
5. A link written into rewritten page copy renders as a link, with its destination shown on hover.

1. Campaign Library

The Library holds what a campaign knows: the notes that came in, what was filed from each one, and the outcome. Partners see their own side. Staff working as the partner see everything and keep the review.

Notes are intake now, handled the moment they land, so the old composer is retired and anything still pointing at it arrives at Historic Filings, where old notes live.

2. Approvals as a timeline

Each checkpoint gets its own headed section, written content and draft on the website, with a dated line per ask and per decision. An info tip on each line says who sent or decided it. On content tasks the card sits in the main column under the task rather than the rail.

Once a piece is approved, the content pages hold it read-only through drafting, review and publishing, so nothing can be marked published while a draft is still waiting on a partner.

4. How wide a site edit lands

A site edit could only name pages. A fix made once in a template that thirteen pages share, or once in something every page inherits, had to be written as a page list, which told the implementer nothing about the change. Tasks now carry a level: pages, templated pages (the layout named in words, with a couple of examples), or site-wide. The approval body reads the same way.

Behind the scenes

1. The Receptionist no longer writes a reply. What the sender gets back is composed from the items a person approved, and a question in a note is now an item with an answer of its own.
2. Planned content reaches the writing pipeline on one rule: the campaign’s writing mode and an approved plan decide, not who the row happens to be stamped to. Page expansions stay with a person until the workflow can draft them.
3. We can rehearse an agent locally, with its real instructions, tools and gates, without spending the platform’s own credit.

1. Composed outcomes

A note is not a chat, so nothing a written reply said could ever be answered, and it kept landing in the wrong tense: recorded before anything was recorded. A dozen rules in the prompt policed it and it still drifted. Now each applied item writes its own line and the outcome is a record of what happened.

We also tightened what counts as an event: something that had already happened when the note was written. A plan or an agreed fix is the work item and nothing else.

3. Rehearsing an agent

A rehearsal is a real run with the same gates, including the one that refuses a write until the agent has actually read and looked at the page. It is dry by default, so a task the agent decides to file is captured instead of created, and we can open that capture in the same task view a partner would see. An agent that is still switched off can only be rehearsed, never run live.