FerroSpring holds 2 of its 13 onboarding answers. maxelmagnets holds all 13. The bug that was eating them is genuinely fixed — the difference is just that nobody has re-entered anything on FerroSpring since.
Tim has onboarded that site six times and lost it every time. What would help most is one run-through with him, watching it save as it goes in, before Tuesday.
If it fails again, that is genuinely useful to know on Friday rather than in the meeting.
Until this week those could not be saved at all — the submit step was leaving them out of what it sent to the server. So if they misbehave, it is a new fault in freshly-changed code, not Tim's old problem returning. Worth saying that out loud to him, because it will otherwise be heard as “it broke again”.
The reason this bug survived six attempts is that the browser kept showing the answers back even when the server never received them. So the only test that counts is:
| Discipline | Pass | Warn | Fail |
|---|---|---|---|
| Technical | 11 | 0 | 0 |
| SEO | 6 | 2 | 1 |
| AI Search | 7 | 5 | 5 |
| Content | 3 | 3 | 2 |
| Social | 3 | 1 | 1 |
| Reach | 0 | 1 | 0 |
| total | 30 | 12 | 9 |
Both are the last test in the plan, so they get retested properly rather than just remembered.
| When | What |
|---|---|
| Monday 24 Aug, 8am | maxelmagnets' own marketing meeting — the first real run of the operating loop |
| Tuesday 25 Aug | The team function review — what each part of the engine actually does, starting with SEO/AEO |
These had been running together in conversation. They are two different things, and both dates are right.