Can it audit pages behind a login?

No. The worker uses the open web search connection for public pages and the Instagram connection for the social grid. Anything requiring authentication is listed as unreachable rather than skipped quietly, so the coverage of the audit is always explicit.

Design

Four versions of the logo are live and nobody signed off on three

A quarterly pass over your public surfaces, checked against the rules your brand doc states.

What the worker does

A brand consistency audit by an AI worker compares your public surfaces against your brand document. Using open web search and the Instagram connection, the worker reads the pages and posts you name, checks logo usage, typography and colour against the rules the document states, and lists every departure with a link to the instance and the rule it breaks. Vague rules produce vague findings, which the report says plainly.

Runs: Quarterly
Connections: Web search, Instagram, Google Drive
Output: Departures, each with a link

Brand drift happens where nobody is looking

The website is fine because the design team touches it. The drift is on the careers page a recruiter built, the partner microsite from a campaign two years ago, the deck template circulating in sales, and the twelve most recent posts on the social grid where the type sizes have crept.

Each of those was made by somebody doing their job with the assets they could find. The result is four logo lockups in the wild, and the only way to know is to look at all of it at once.

What gets checked, and against what

Surface	Connection	What the rule usually is
Public web pages you name	Web search	Logo lockup, clear space, approved type
The Instagram grid	Instagram	Colour palette, type treatment, template use
Shared decks and templates	Google Drive	Cover slide, type scale, approved colours
The brand document itself	Google Drive or Notion	The source of every rule the audit applies

How to make the report actionable

One row per instance, not per problem
Three pages using the old logo is three rows with three links. A summary saying the old logo is still in use gets read and not fixed.
Cite the rule
Each finding names the section of the brand document it comes from, which stops the audit becoming an argument about taste.
Separate what is behind a login
The worker only sees public surfaces. Anything it could not reach is listed explicitly, so nobody assumes the product interface was covered.
Turn severity-one rows into tasks
A wrong logo on a live pricing page is a task with an owner and a date. The rest can sit in the report until the next quarterly pass.

The boundary

Checkable

Which logo file is in use on which page
Whether the colours match the stated palette
Whether the typeface is one of the approved ones
Whether templates were used or bypassed

Not checkable

Whether the photography feels like the brand
Whether the tone of voice is right
Whether an exception was a good exception
Whether the brand itself still fits the company

Questions people ask

+How does it know our palette?

From the brand document you point it at, through the Google Drive or Notion connection. The rules in that document are the entire basis of the audit, and the worker cites the section it applied for each finding.

+Is quarterly the right cadence?

For most teams, yes, because fixing findings takes longer than finding them and a monthly report would repeat itself. Teams mid-rebrand often run it monthly for two quarters and then drop back.

+What about the product interface?

That is better served by the design system drift audit, which compares the component library against its documentation and against the implemented code. Brand audits cover public marketing surfaces, where the drift is caused by people outside the design team.

Design work an AI teammate can take, and the part it cannot

Five jobs around the work, none of them the work itself. Taste stays where it belongs.

The component was renamed and the documentation was not

A weekly drift report between the component library and the documentation that describes it.

Competitor monitoring that actually happens every week

Everyone agrees competitor tracking matters and nobody has done it since the last time a deal was lost over it.

Connect Instagram to Polaris

Engagement data is the only honest input to a content calendar, and it is the input most calendars are written without.

Web search in Polaris

Nothing to authorize, nothing to store, and every query a worker runs appears in the activity feed while it works.

Hire an AI social media manager

A month of posts planned, written and filed by Tuesday, so the only decision left is which ones you actually publish.

Polaris for design studios

Nobody has ever put a line item for asset renaming on an invoice, and every studio pays for it anyway.