Problem
profile/README.md line 40 reads:
Enquiries: r.nash1@async-digital.com
The general-enquiries address used everywhere else on the company's public web
presence is info@async-digital.com. A reader who takes the address from this
README reaches a different inbox from every other public surface, and a personal
mailbox rather than a company one.
Two separate problems, worth naming separately because they have different fixes:
- It is the wrong address. Everything public points at the general
enquiries address. This one does not.
- It names an individual on a surface that is meant to be brand-only. The
organisation profile README is one of the surfaces that speaks as the
company rather than as a person, and a personal-looking local part
undercuts that.
Fix
-Enquiries: r.nash1@async-digital.com
+Enquiries: info@async-digital.com
Why this went unnoticed
The existing automated check on this file asserts the canonical positioning
sentence. It does not assert the contact address, so the address can drift
without anything going red. Worth extending that check to cover the contact
line, otherwise the same drift recurs and is found the same way: by eye,
eventually.
Adjacent, same file, not fixed by the above
Line 29 states that the public repositories here "are reference utilities and
supporting components, not the systems described above". That is accurate today.
It stops being accurate the first time a standalone end-user tool is published
under this organisation, so it needs revisiting at that point rather than being
left to quietly become false.
Problem
profile/README.mdline 40 reads:The general-enquiries address used everywhere else on the company's public web
presence is
info@async-digital.com. A reader who takes the address from thisREADME reaches a different inbox from every other public surface, and a personal
mailbox rather than a company one.
Two separate problems, worth naming separately because they have different fixes:
enquiries address. This one does not.
organisation profile README is one of the surfaces that speaks as the
company rather than as a person, and a personal-looking local part
undercuts that.
Fix
Why this went unnoticed
The existing automated check on this file asserts the canonical positioning
sentence. It does not assert the contact address, so the address can drift
without anything going red. Worth extending that check to cover the contact
line, otherwise the same drift recurs and is found the same way: by eye,
eventually.
Adjacent, same file, not fixed by the above
Line 29 states that the public repositories here "are reference utilities and
supporting components, not the systems described above". That is accurate today.
It stops being accurate the first time a standalone end-user tool is published
under this organisation, so it needs revisiting at that point rather than being
left to quietly become false.