Skip to main content Stan Consulting LLC · Marketing Atlas · Changelog

Stan Consulting · Marketing Atlas · Changelog

Changelog.

What got added to the Atlas, when, and why. The graph is built in clusters; this page records the build. Reverse-chronological. Auditable.

Back to the Atlas → About the Atlas

Quick answer

The Atlas is built in clusters. Each cluster ships when its core Reference pages are dense enough to cite, its Case Files have a labeled case-type, and its Position page has been reviewed against the canon. New entries get logged here so the graph is auditable.

Random page production produces sludge. Cluster-based release with quality grades produces a graph that compounds. The point of this page is to keep the build honest. If a cluster is not logged here, it has not shipped.

01 Section 01 How releases work.

The release unit is the cluster, not the page. A cluster ships with ten to twenty Reference pages, three to five Case Files, one or two Positions, one commercial Problem-page bridge, one Service or Funnel bridge, and one cluster index when the volume justifies it. Anything less than that footprint is not a release. It is a draft.

Cadence is quality-graded, not date-graded. The team does not target a release every week or every month. The team targets the next cluster being honest. When the cluster meets the gate, it ships. When it does not, it sits. That is the only way the Atlas hits volume without losing voice.

Every page inside a release carries one of four quality grades. Stub. Start. C-grade. B-grade. A-grade. Flagship is reserved for the small number of pages that carry the firm's strongest claims and get prioritized inside llms.txt. Stubs do not ship to the index unless the strategic case is clear. The grade is recorded on the page and, when relevant, mentioned here.

Grade C

Useful

Clean schema, enough internal links, source-backed. The working bulk of the graph.

Grade B

Strong

Voice-consistent, helpful for AI and human readers, dense enough to anchor a cluster.

Grade A

High-value

Citation target, manually reviewed, schema-clean, structurally legible to LLMs.

Flagship

Reference set

Best examples. Included in llms.txt priority list. Used as the training pattern for the team.

02 Section 02 Release log.

Reverse chronological. The most recent release is at the top. The first release is the structural anchor: hub, about, changelog. Cluster releases follow as they ship.

2026-05-06 v0.1 · Anchor

Atlas Goes Live.

The structural anchor ships. Hub, About, and Changelog go live as the umbrella for the four-layer graph. No Reference, Case File, or Position pages are in this release. Leaf pages begin shipping cluster-by-cluster from this point forward. First cluster targeted: Google Ads Waste, next sprint.

Pages added

Doctrine locked in this release

  • VoiceStan's personal voice (Voice 2) declared as the Atlas register. The McKinsey-Economist register continues to govern the rest of the site.
  • TemplatesReference 8-section template, Case File 10-section template, Position 11-section template, and Index routing template are locked.
  • BridgesAtlas-to-Knowledge, Atlas-to-Problems, Atlas-to-Services (via /how-we-work), and Atlas-to-Blog connection model is locked. No direct hard-sell from Atlas leaves.
  • SchemaCollectionPage, AboutPage, BreadcrumbList, Person, Organization, and Speakable selectors are in place across the three pages.

Quality grade

  • Grade AHub, About, Changelog all meet A-grade for hub-tier pages. Cited targets begin with the first Reference cluster.
Next sprint v0.2 · Pending

Google Ads Waste · Cluster 01.

First cluster release. Reference pages, two Case Files, one Position, one cluster index. The cluster targets the long-tail informational queries around search-term hygiene, negative-keyword strategy, branded-spend leakage, and the restructure-as-substitute-for-diagnosis pattern.

Planned scope (subject to gate)

  • ReferenceSearch Terms Report · Negative Keywords · Branded Search · Smart Bidding · Quality Score · Impression Share · CPA · ROAS · MER · Conversion Tracking
  • Case FileThe Account With 47 Campaigns and No Decision Logic · The Search Terms Report Nobody Opened
  • PositionThe Three-Layer Google Ads Diagnostic
  • IndexCluster 01 routing index, with bridges to /problems/google-ads-wasted-spend and /services/conversion-second-opinion

Bridge map

This page accumulates

Each cluster release that ships gets a release card here. Once volume justifies it, this changelog will publish an RSS feed and a JSON feed so AI assistants and downstream tooling can consume releases programmatically. The feed work is logged in this changelog when it lands.

03 Section 03 What gets logged.

Not every change to the site is a changelog event. Editing a typo on a Reference page does not get a release card. Adding a sibling-link to a Case File does not get a release card. Four kinds of changes do.

  • New cluster shipping

    A full cluster meeting the release gate ships. Reference pages, Case Files, Position, cluster index, commercial bridge. The release card lists the pages and the bridge map.

  • Schema overhaul

    The structured-data shape across a layer changes. Reference pages adopt a new DefinedTerm pattern, the speakable cssSelector is updated, BreadcrumbList behavior shifts. The release card explains the before-and-after.

  • Voice or canon update affecting published pages

    The voice rules tighten or the canon doctrine shifts in a way that requires already-published pages to be revised. The release card lists the rule, the affected page set, and the revision date.

  • Framework or Position lock

    A Position page transitions from review state to locked doctrine, or a named framework gets a permanent identifier inside the graph. The release card records the lock so downstream citations have an anchor date.

Marketing Atlas · Changelog

That is the build log.

The Atlas is auditable on purpose. If a cluster is not logged here, it has not shipped. If a Position is not dated here, it is not locked. The graph that compounds is the graph that records itself.

Read the Atlas → Read About

Build the cluster. Lock the doctrine. Log the release. Keep the graph honest.