Bryan, two related requests:
1. When a topic has a real end-client agency, the skill should resolve
its full identity -- not just whatever name got said in the meeting.
Added as a new standing step: check the MPM Technical Reference
System first (agency-roster.md, clients-and-partners.md -- cheap,
already-vetted), fall back to public web research, resolve BOTH the
legal entity name and the separate transit brand name distinctly
(validated pattern, confirmed against MPM's own FTA filings for
Oshkosh: 'City of Oshkosh, Wisconsin, dba: GO Transit'), re-host the
logo as a data URI rather than hotlinking it, and capture general
agency contact info. Gets its own 'End Agency' card, separate from
individual attendees.
2. Pricing shown in the Oshkosh brief was correct for an internal
audience, but Bryan flagged that an external-facing version must
never show the end agency MPM's price to the reseller -- they aren't
privy to it. Documented as a new Hard Rule, grounded directly in the
Technical Reference System's own reseller-channel.md (MPM's contract
of record is with the reseller, not the agency, on channel accounts)
rather than invented from scratch. Doesn't change internal-meeting-
brief's current behavior (it's internal by definition) -- recorded
here as the binding rule for vendor-partner-brief and kickoff-brief's
external-client variant, neither built yet.
Bryan Gilliom (via Claude)
2f8ba0b80b