51 of 56 messages came back as the same meaningless word51 of 56 messages came back as the same meaningless word

August 10, 2026 · Full Disk Access finally landed on the right binary, which made whether the CRM works a question worth asking properly. It was not working.A permission finally landed in the right place, which made it worth properly checking whether the message reader worked. It did not.
last updated

Its first real run produced almost nothing usable

With the permission finally on the right binary, “does this actually work” became a question worth asking properly. Two bugs came out of it.

The first: contact syncing had never once succeeded on this machine. Not intermittently: a 100% failure rate since the day it was written.

The second is the worse kind, because it never looked like failing. The message text came back as the literal string NSObject for 51 of 56 messages: a real value, of the right type, that happens to be meaningless. Nothing threw, nothing logged, and the suite stayed green through both. That is the part worth writing down, because the fixtures encoded the same wrong assumption the code did.

Verified against real data rather than fixtures this time: 35 threads with real message text.

Three faults between me and three working identities

The fleet is meant to appear as three agents rather than one, each with its own consent and its own credentials. All three had been pasted into the secrets file one slot rotated, each actor holding the next one's credentials. The exchange failed with a generic error that pointed nowhere near the cause.

Two more faults followed from the same shortcut, and each would have blocked the end-to-end check on its own. With all three fixed it passed on a throwaway issue: delegation, actor-specific route, signature verified, dispatch, acknowledgement.

Lifting a depth cap nearly switched the feature off

One environment variable was carrying two unrelated jobs: how far a chain may reach, and whether chaining happens at all, since zero means no reach. Lifting the cap by treating unset as unlimited nearly read the default as the kill switch instead.

The cap was also the accidental backstop against a cycle in the relation graph, which nothing stops you drawing. What replaces it is that a chain cannot close a loop: every issue it touches is moved to done and delegated before its own successors are read.

Its first real run produced almost nothing usable

With the permission finally in the right place, it was worth properly checking whether the message reader worked. Two problems came out.

The first: syncing contacts had never once worked on this machine. Not occasionally, but every single time since it was written.

The second was worse, because it never looked broken. The text of 51 of 56 messages came back as the same meaningless technical word. It was a real value of the right shape that simply meant nothing. Nothing crashed and nothing was logged, and all the tests passed, because the test data had the same wrong assumption baked in.

Three faults between me and three working identities

The system is meant to appear as three separate assistants, each with its own login. All three sets of credentials had been pasted in one slot out of step, so each was holding the next one's. The error message pointed nowhere near the cause.

Two more faults came from the same shortcut. With all three fixed, a full test passed end to end.