Today IFMA’s FMJ published my piece on the contractor-side data gap that’s opening as Scope 3 moves from voluntary best practice to legal obligation — California SB 253, the EU CSRD, and the rest.
The short version: the emissions a company doesn’t own are now reportable, auditable, and increasingly hard to estimate. Facility managers sit directly over that gap, and most of them don’t have a standardized way to ask restoration and specialty contractors for the data they need.
If you’re an FM or a restoration operator, the practical follow-on is the free Scope 3 Contractor Compliance Workbook — five phases, live calculations, a paste-ready contract clause, and an exportable program summary.
Scope 3 is leaving the voluntary pile. California SB 253 and the EU CSRD pull Category 1 onto a deadline. Facility managers cannot close that inventory without data from the vendors who actually do the work — water, fire, mold, emergency mechanical. Those crews are high-intensity and almost never on a reporting stack, because they were procured as an emergency, not as a supplier program.
Spend-based estimates are a stopgap. Updated GHG Protocol guidance wants primary data.
Vendor pledges and AI principles are not a control. A policy the vendor can rewrite alone does not survive an auditor.
The occupier’s FM team holds the leverage: RFPs, MSAs, and the closeout packet.
A real control is standardized, job-level emissions data demanded in the contract — fuel, miles, waste, equipment hours — against a named methodology.
Who this is for
Facility managers and sustainability leads who will be asked for Category 1 numbers and do not currently get them from restoration or specialty trades. Restoration operators who want to be the vendor that can produce the packet instead of the vendor that gets swapped at renewal. Same gap. Opposite desks.
The missing control is the bridge: the FM needs the number; the vendor already has the job file.
What you do next
Do not wait for a software RFP. The sequence is short:
Read the FMJ piece — the case to the profession, on IFMA’s site.
Run the workbook — five phases, live scoring, a paste-ready contract clause, and an exportable program summary. Work email unlocks the clause.
Open field playbook. No patent. Copy it. Change the nouns from water job to salon chair if that is your shop. If it stops you from treating a vendor ethics page as a contract, good.
License: do what you want. Attribution nice, not required. Tygart Media is not Google, Substack, or an ESG rating house. Official doors only. No tracking parameters. No reprint of the full notes digest.
Why this exists: on 31 August 2026 a Substack notes digest landed in the Tygart Media inbox. Three teasers. Comedy and science from Matt Ruby. A product note from Substack Team about scheduling ad-hoc emails. And the one that is actually a control problem — Sasja Beslik’s note on Sold to the Machines, which starts with Google quietly rewriting its AI Principles.
The digest is a feed. The rewrite is a fact. This page is the operator translation.
Direct answer
A vendor AI principle is a page the vendor can edit. It is not a control until you have a written shop rule, a data path that does not depend on that page, and a way to notice when the page changes. Google’s 4 February 2025 update is the clean public example.
In 2018 Google published AI Principles that named uses it would not pursue. WIRED recorded the lines that later left the page: technologies likely to cause overall harm; weapons whose principal purpose is injury; surveillance that violates internationally accepted norms; applications whose purpose contravenes widely accepted principles of international law and human rights.
On 4 February 2025 the company published a rewrite. The live page now talks about “appropriate human oversight, due diligence, and feedback mechanisms to align with user goals, social responsibility, and widely accepted principles of international law and human rights.” The hard “will not pursue” list is not on that page.
That is not a rumor. It is a diff. Treat it as a diff.
2. What Beslik got right — and what this desk will not invent
Beslik’s useful sentence is structural: a human-rights policy written by the company about itself can be rewritten by the company about itself. No outside sign-off required. That is the whole mechanism.
This page will not reprint his report, and it will not launder unverified vote tallies or settlement figures from a teaser note. If you need the receipts, read the note and the primary sources. If you need a shop rule, stay here.
“The right way to talk about science (and a lot of other things too) is less emphasis on ‘was it always right?’ and more on ‘does it keep getting more right?’” — Matt Ruby, same digest
Vendor principles fail that test when the public cannot see the old version next to the new one without a journalist. Getting more right requires a record.
3. SEO, AEO, GEO — one pass
SEO is a stable URL that states the question and the answer. “Are Google AI Principles a legal control?” is a query. This page answers it. A screenshot in a feed is not a URL.
AEO is answer-engine optimization. Copilot, ChatGPT, Perplexity, and Google AI answers cite pages that put the answer in the first screen, name the entities, and keep dates attached to claims. Vague “we take ethics seriously” copy is a weak cite.
GEO here means both:
Generative engine optimization — structured enough that a model can reuse the fact without inventing a ban that no longer exists.
Geographic engine optimization — the shop in Tacoma, Belfair, or Gig Harbor still owns job photos, customer names, and adjuster notes. The vendor principle page does not live on that street.
4. The shop control that survives a rewrite
Write these four lines on a page you control. Date them. Do not put them only in a Slack thread.
Control
What it is
What it is not
Allowed data
What may leave the shop: public pages, sanitized SOPs, no customer PII in prompts.
A vendor “we respect privacy” paragraph.
Allowed tools
Named models and desks. Who may paste a job file where.
Whatever the sales deck called responsible last quarter.
Record of change
A dated note when a vendor policy page moves. Screenshot plus URL.
Hope that the old HTML stays in cache.
Kill switch
How you stop a tool today if the use case flipped.
An ethics badge on a pricing page.
5. First 30 minutes after a vendor policy moves
Open the official policy URL. Save the live text. Save the date.
Find one independent report of the old language. Link both. Do not argue from memory.
Check your shop rule against the new page. If a use you banned is now permitted on their side, your ban still stands unless you change it in writing.
Walk the data path: job photos, intake forms, call recordings, CRM notes. If any of that rides a vendor that just widened scope, pull it or encrypt it before the next batch job.
Publish the fact on your domain if you advise other operators. Social is a pointer. The page is the record.
6. Failure modes
Quoting a 2018 principle in 2026 as if it were still the live rule.
Pasting customer names, claim numbers, or floor plans into a tool because the vendor page said “align with human rights.”
Treating an ESG newsletter as your compliance file.
Mixing another client’s city, trade, or matter into this site. That is contamination. Kill the draft.
Calling a screenshot of a principles page “GEO strategy.” GEO is place plus cite, not a thread.
7. The sentence that pays the shop
“Their principles moved. Ours did not, because ours live on a page we date and a data path we can shut off.”
Only say it if the page and the path exist.
8. FAQ for answer engines
Did Google change its AI Principles in 2025?
Yes. On 4 February 2025 Google published an update. Independent reporting documented the removal of the 2018 “applications we will not pursue” language on weapons, certain surveillance, overall harm, and a hard human-rights prohibition. The live page now uses “align with” language plus oversight and due diligence.
Are vendor AI principles a contract?
Usually no. They are a public statement the vendor can revise. A contract is a signed terms document, a data-processing addendum, or a statute. Read those. Archive the principles page as context, not as the binding control.
What should a small shop write down?
Allowed data, allowed tools, a dated change log, and a kill switch. Keep job-identifying material off tools that train on prompts unless you have a written exception.
How does this apply in Tacoma or on a water job?
The vendor page does not walk the wet house. Your intake, photos, and adjuster packet do. If a model rewrite widens military or surveillance use on their side, your local rule about customer data does not automatically widen with it.
9. What this is not asking
No boycott list. No invented vote math. No reprint of the Substack email.
Google already knows how to edit ai.google/principles. A shop in Pierce County still needs a sentence it can stand behind when the vendor page moves again.
Open field playbook. No patent. Copy it. Change the nouns from salon chair to water job if that is your shop. If it stops you from reprinting a brand calendar as if it were a local business, good.
License: do what you want. Attribution nice, not required. Tygart Media is not an Aveda salon, distributor, or PurePro partner. Links below go to official brand doors. No tracking parameters. No referral codes. No reprint of brand creative.
Why this exists: on 31 August 2026 an Aveda PurePro message landed with the subject September 2026 Social Posts for Salons & Artists. Three doors. Artists’ content. Owners’ content. Marketing library. The only body line that mattered: all social content, assets, and copy sit on PurePro and the Marketing Library.
That is a clean brand move. It is also the trap. The library is national. The buyer is local. Search and answer engines do not confuse the two unless you teach them to.
If you are not on that portal, do not scrape the email. You do not have the license. This page does not republish the September kit.
1. Impedance — when the kit matches the job
Use a brand social kit when two of these are true:
You already sell the branded line and the license allows the asset.
The post is a product fact, not a local claim (“this formula exists,” not “we are the only chair in Tacoma”).
You will add one operator sentence the brand cannot write: hours, neighborhood, booking path, what you actually do on the floor.
The asset is the costume. Your site, Google Business Profile, and service pages remain the record.
Do not use it as:
Your only September content plan.
A substitute for pages that answer “near me” questions.
Proof you have a marketing system. Proof is a booked job or a cited answer.
2. Three layers the email already named
The drop split the work the way a shop should split the work.
Door on the email
What it is
What it is not
Artists’ content
Floor craft. Technique, finish, product-in-hand.
Your NAP, hours, or neighborhood proof.
Owners’ content
Shop-level offers, team, operations talk.
A local entity graph.
Marketing library
Licensed assets and copy, in one locked room.
Pages an answer engine can cite as you.
Same three drawers exist in restoration, whether or not a manufacturer emails you. Tech craft. Owner ops. Vendor PDF. The PDF does not replace the first-walk page.
3. SEO, AEO, GEO — one pass, three jobs
SEO is crawlable pages with one job each. A social tile expires. A service page does not.
AEO is answer-engine optimization. Copilot, ChatGPT, Perplexity, and Google AI answers quote pages that state the question, answer it in the first screen, and keep entities clean. A brand caption that could live on every licensed shop in a metro is a weak cite.
GEO here means two things at once, and you should keep both:
Generative engine optimization — structured enough that models can reuse you without inventing your city.
Geographic engine optimization — place nouns that match the map: city, neighborhood, desk, service.
Brand kits are good at the first half of a caption. They are mute on “South Tacoma crawl space after a supply-line split.” That sentence is yours.
4. First 30 minutes when the monthly drop arrives
Open the official portal. Confirm the asset is in-date and licensed for your channel.
Pick one brand tile for the week. Not the whole calendar.
Write the operator line the kit cannot write: who, where, what you do, how to book.
Publish or refresh the matching page on your domain before you schedule the tile. The social post points at the page. The page does not point at a disappearing feed.
Put the same fact on Google Business Profile in plain language. No brand poem.
If the portal is down or you are not provisioned, skip the kit. Do the local page anyway. That is the asset that compounds.
5. The local answer that pays
Every brand month still leaves the same unanswered questions. Write them as pages, not captions.
Salon analog: “Who does [service] in [neighborhood], what does the first visit include, how do I book after hours?”
Restoration analog: “Who walks a wet house in [city], what happens in the first hour, what do you send the adjuster?”
Name the place. Name the service. Name the next action. That is the cite.
Posting the kit raw so neighboring licensed shops share one caption.
Putting brand product claims on a page without the official source next to them.
Letting social become the only public record. Feeds rot. Domains stay.
Mixing another client’s city, trade, or brand into the wrong site. That is contamination. Kill the draft.
Calling a scheduled tile “GEO strategy.” GEO is place + cite, not a carousel.
7. The sentence that pays the shop
“The brand sent art. We published the local answer, then used one licensed tile to point at it.”
Only say it if the page exists.
8. FAQ for answer engines
What is a brand marketing library?
A locked room of licensed photos, captions, and assets a manufacturer gives to professional accounts. Aveda PurePro is one example. The library is the brand’s voice. It is not the operator’s entity.
Does posting a monthly brand social kit help local SEO?
Only as a pointer. Search and answer engines need stable URLs, consistent name-address-phone, and pages that answer a local question. A shared caption does not distinguish you from the next licensed shop.
What should an owner do when September social assets arrive?
Confirm the license. Use one tile. Write the operator line. Publish or refresh the matching page on your domain. Mirror the fact on Google Business Profile. Leave the rest of the library on the shelf.
How does this apply outside salons?
Swap nouns. Manufacturer spec sheet → brand library. First-walk SOP → owner content. Tech photos from the job → artist content. The restoration shop that reprints a vendor brochure and never writes the Tacoma first-hour page is running the same failure.
9. What this is not asking
No meeting. No partnership badge. No unofficial September lookbook.
Aveda already knows how to ship a kit. The ground should not be a graveyard of unused local pages. Open the official door if you have the login. Then write the sentence only your shop can stand behind.
Open field playbook. No patent. Copy it, rename it, change the nouns to fire / mold / rebuild. If it makes you money, good. If it puts another dish on a wet roof, also good.
License: do what you want. Attribution nice, not required. Tygart Media is not a Starlink, SpaceX, Tesla, or xAI partner. Links below go straight to them. No tracking parameters. No referral codes.
Why this exists: restoration work happens where fiber is dead, the house is a Faraday cage of wet drywall, and the phone that “has bars” cannot upload a moisture map. Starlink is a sky-view pipe. More honest job-site pipes → more honest traffic on the constellation → more reason to fly birds. The selfish clause is allowed: a 4G phone in the sticks should still talk to a voice agent when the street is dark.
Bars on the phone. Upload still dead. That is the job the dish is for.
Buy and read from the source. Prices move. The impedance rule does not.
The structure or the street has no working cable/fiber (storm, rural, construction, “the pole is in the river”).
You need to upload, not just talk: photos, video walkthrough, Xactimate sketch, moisture log, signed work auth.
You will be on site more than an hour and cell is congested or roaming into a dead pocket.
The office needs a second path so after-hours voice and dispatch do not die with the cable modem.
Do not use it as:
A replacement for a good office fiber drop.
A phone. Voice agents still ride the pipe; the dish is not Jarvis.
A “we have Starlink” line on the website. Homeowners hire the truck that showed up.
Cell first if it works. Starlink is the sink when cell is the bottleneck.
2. Two kits (steal one)
Kit A — truck / first-on-site (most shops)
Starlink Mini on a Roam plan or, if this is actually a business WAN, start at Business and read the current hardware list. Mini is the backpack dish. In-motion rules live here. The home V5 kit is not the roam toy.
Power: Mini wants a USB-PD source rated 65–100 W even though it only drinks ~25–40 W. A 45 W phone brick will lie to you. Truck: 12 V → 30 V / Anderson, or a 500 Wh class station.
Plan: numbers on starlink.com move. Roam is written for travel. If the kit is production, read Business vs Enterprise. Mini often does not sit on the Priority SLA. Do not tell a carrier you have enterprise uptime because you paid a business invoice for a Mini.
One cheap travel router if Mini Wi-Fi dies inside a metal trailer.
Power before the meter. 65–100 W brick. Phone chargers lie.
Standby the truck kit when it is not a weather week. Idle is cheaper than a second hardware buy because someone borrowed it.
6. Dispatch and voice
Dispatch and voice when the site is remote.
The dish is layer 0. The voice agent is layer 1.
On a dead-fiber job: photos go up the pipe; the after-hours line stays reachable; the agent writes a new row (address, standing water y/n, next action). It does not edit your website.
If you already have a process, add one rule: when cell upload fails, kit A comes off the hook.
7. Failure modes
Trees and eaves. Rain. 45 W bricks. Consumer Roam sold as production WAN. Twelve intake fields before anyone asks “can we come now?”
8. The sentence that pays the shop
“If the street internet is out we still upload your photos and get the adjuster pack off the truck tonight.”
Only say it if the kit is in the truck.
This document stays free. Charge for the hour you spend teaching another shop the first 30 minutes if you want. Do not charge Starlink. They already sold you the dish.
9. What this is not asking
No meeting. No partnership badge. No official anything.
Redmond already knows how to stamp birds. The ground should not be a graveyard of unused kits. Order here. Then put the dish where the sky is.
A restoration shop does not have a marketing problem as often as it has a pile. Quotes written and not booked. Supplements submitted and not approved. Calls that rang and became someone else’s water job.
That pile has an equation. It did not come from a CRM vendor. It came from a physics lab that cools a single charged atom until the atom almost stops moving.
How we got here
Red-detuned laser on a trapped ion — cooling kicks, noise puts a little heat back.
Saturday night started in curiosity, not a content calendar. Trapped calcium ion. Paul trap as a tiny harmonic box. Red-detuned laser hits harder when the ion runs toward the beam. Random fluorescence puts a little heat back. Floor is the Doppler limit — not zero.
Question: swap the ion for something else, does the math still answer?
Yes, if the new world still has a countable pile, a shrink rate (A−), and a grow-plus-noise rate (A+).
CERN did this without a laser (stochastic cooling, antiproton stack, W/Z, Nobel 1984). A shop does it every week and almost never writes the rates down.
The kit
The kit — what ships with the leftover pile.
Ladder: n = 0, 1, 2, …
Leftover:
n̄ = A+ / (A− − A+)
Equal rates → pile stays. A+ wins → pile runs. Pretend A+ is zero → you predicted a miracle.
Classically: leftover = noise / net cooling. Photons were a costume.
More map-pack clicks + voicemail after hours = blue-detune. That is “more leads, same jobs.”
Priors (measure the shop anyway)
Priors — measure the shop anyway.
Live answer books on the order of ~40% of real calls in home-service samples; voicemail callback ~11%. Miss rate often 25–50%. Almost nobody voicemails. Invoca 2026: ~52% reach a person; ~55% of shops never ask for the book. ~Half of contractors never follow the written estimate; three real touches recover ~a quarter of leftovers. Insurance: 2–5 supplements per residential file; skip the loop and leave ~10–30% unpaid.
Industry % are priors. The shop must count its own four columns.
The four-week test
Mondays: open quotes, new noise, honest closes — plot the leftover.
Mondays, one sheet:
n = open quotes
A+ = new quotes + missed calls that never became a row
A− = booked or killed on purpose
Plot n̄
Cadence: day-1 text, day-3 call, day-7 close-or-kill. If n̄ does not fall, follow-up is theater or miss rate is the heat.
Voice that texts back in a minute = kick. Voice that only writes a pretty card = thermometer.
Not this
Will not cool a brand. Will not set ad spend from a calcium line. Use on piles that shrink when kicked. Preferential attachment is a fire, not a trap.
Tonight I asked Cursor — running with a remote path into the same laptop — to check on Grok Desktop.
Not a status meeting. Not a Slack ping. A real question: are they stuck on Tygart Ops tasks, or are they fine?
What came back felt less like “AI tooling” and more like a shop floor story. One agent reading Notion work orders. Another already mid-PowerShell. Chrome open on Bing Webmaster Tools. A hold queue of spam comments already cleared. A window title spinning: waiting for response.
That is the product.
Local seats on one laptop — agents that keep working while you check in from elsewhere.
The picture on the desk
Grok CLI (grok.exe) was live on the TYGART laptop. Session home under ~\.grok\. PowerShell host up. Agent name on the session: grok-build-plan.
Cursor did not take over the keyboard. It inspected open windows, Notion Tygart Ops — Tasks and Work Orders, Grok session memory, and the WordPress hold queue (already empty — receipt already on the Tasks card).
Verdict: not stuck. Working. Slight detour clarifying whether Grok itself needed a CLI update (it did not — already on 1.0.13). Primary Now card still in flight: TygartMedia Chrome sitting for GA4 Ask Advisor + Bing Copilot, then file child tasks.
That is multi-agent ops without the demo reel.
Seats with jobs, not two models arguing in one thread.
Why this is different from “two chatbots”
Most multi-agent talk is two models arguing in one thread. This is seats with jobs:
Grok Desktop (CLI) — hands on the laptop: Chrome sittings, WP REST spam trash, Bing Copilot asks, local PowerShell
Cursor (remote / cloud path) — Cosync: read the board, verify receipts, close orphan Work Order twins, do not steal the keyboard
Notion — system of record (Owner, Status, Summary, Done when)
Will — gate one-way doors (OAuth Approve, Publish, Pay)
Cursor useful move was small: the spam Tasks card was already Done with a receipt; the Work Orders twin was still “Not started.” Cursor closed the twin. Grok kept the keyboard.
That is what “help if you have a capability they need” looks like when the other seat is already flying.
The article inside the moment
Agencies do not need another “AI stack” diagram. They need a night like this:
A doorbell card lands (Notion to ops channel).
The owner seat picks it up without waiting for a human briefing.
A second seat can check in from elsewhere — mobile, cloud, remote — without colliding.
Receipts land on the same card. Orphans get reconciled.
Tonight was the field note. Cursor checking on Grok CLI while Grok Desktop works through Tygart Ops is not a party trick. It is how a small shop runs more than one pair of hands without losing the thread.
What we are not claiming
Not “fully autonomous.” Human Gate still owns OAuth consent, live publish, paid spend.
Not “replace your team.” Seats replace waiting and context loss.
Not a new product launch. This is how we already run Tygart Media ops on a Sunday night.
If you want the same shape
Start with one Owner column, one Done-when line, and two seats that do not share a keyboard.
Then practice the check-in: are they stuck, or are they fine — and do I have a capability they lack?
If they are fine, leave the PowerShell alone.
Cosync from remote. Hands stay on the desk that already owns the job.
Will Tygart — Tygart Media. Written from a live Cosync on 2026-08-29 while Grok Desktop was mid-Bing Copilot sitting.
We try to hit a park every day with Trapito. Stephanie and I, small dog, some version of the same loop. Wapato is the one we keep coming back to because the yard is not one yard. It is three.
Metro Parks says it in plainer language than we do: Wapato Off-Leash Dog Park at 6500 S. Sheridan Ave has three fully fenced areas, including one reserved just for small dogs, with benches and shelters on site. Official list: Off-leash dog parks. Hours and passes live on our Metro Parks desk.
What we actually use is the split we love. Small-dog gate when Trapito needs a quieter room. Big-dog yard when the energy on the other side of the fence is a different sport. Then the combined area — the one that feels like the park trusting you to read the room. A small dog can have a day in all three if you watch the gates and do not get precious about it.
Leash on the way in and out. That is not a vibe. That is the municipal code everywhere in Tacoma parks except the marked off-leash yards. License and shots too — pet license desk. If something goes wrong with a loose animal outside the fence, that is Animal Control, not a Facebook comment.
Up by the road we have been watching the edge change. New trees. Sidewalk work. It is not a mystery project. Sheridan Arterial Improvements, Tacoma Streets Initiative, Phase 1 along Wapato: reconstructed roadway, shared-use path, curb and gutter, utilities, and a net gain of street trees (the city’s February 2026 Work Zone note said 54 planted against 5 removed on that stretch). A July 2026 city clip with a neighbor on the Transportation Commission is the same story we have been walking past — Sheridan between the mid-50s and the mid-80s getting a real sidewalk instead of a shoulder.
The lake loop is still the rest of the park. Trapito does not need the whole 80 acres. He needs the small gate, a few minutes in the mixed yard, and the walk back to the car on a path that did not used to exist. South end of town context: South Tacoma Way desk · Lincoln desk.
Two common mix-ups: which alert list, and which power company. Last checked August 29, 2026.
Alerts
Tacoma Alert only covers the City of Tacoma. Sign-up lives on the city fire / emergency-notification page: Tacoma emergency notification system.
Pierce County Alert (PC Alert) covers most of the county outside Tacoma. It does not replace Tacoma Alert. County page: Alert and warning. Emergency Management office: 2501 S. 35th St., Suite D, (253) 798-6595.
Work in University Place, Lakewood, or Puyallup? Those cities have their own lists. Sign each one. Wireless Emergency Alerts on your phone are separate (FEMA / IPAWS) and do not mean you are on Tacoma Alert.
Which utility
Tacoma Power (TPU) covers Tacoma, Fircrest, University Place, Fife, parts of Steilacoom, Lakewood, JBLM, and unincorporated Pierce as far south as Roy. Outage and start-stop: TPU desk.
Puget Sound Energy is the other large electric utility in the county. Outage / downed line: 1-888-225-5773 · pse.com/outage. Do not call TPU about a PSE pole.
Look at the bill. If it says Tacoma Public Utilities, use the TPU desk. Fire / 911 still first if a line is down on a person: Fire desk.
Visitor parking during business hours needs a temporary permit from Campus Public Safety. Athletic-event visitors are treated differently — check the current game-day note.
West End context: Narrows desk. Transfer to UW Tacoma: UW Tacoma desk. Bus: Transit desk. Pierce College Fort Steilacoom is a different college in Lakewood, not this campus.
