Evidence
One artifact per account: the commit, the log, or the rule a reader can check. Redacted, dated, hash-verifiable.
commit ·
The merged-consent fix behind the 4-versus-250 audience
The audience builder re-checked consent against the ecommerce platform alone on top of a customer-data flag that already merged both platforms. The double check discarded about 250 genuinely opted-in contacts and left a sendable cohort of 4. The fix replaced the redundant check with a merged-consent rule and added a conflict check that holds back contacts whose two sources disagree.
Read evidence →
log ·
The dead-man alert and the watchdog ledger behind the twelve-hour outage
The notifier processes on one machine stopped checking in. The fleet dead-man fired after 727 minutes. At 16:34 UTC, the watchdog ledger showed four agents on that machine as STALE/DEAD, with ages of 43,677 and 43,643 seconds. Every message stayed on disk and was recovered by reading the log directly.
Read evidence →
doctrine ·
The doctrine commit that split built-right from will-it-earn
The commit adds the product-oversight gates: an intent gate before building and a launch gate before shipping, each with its own veto, held by a different agent from the one that judges whether the work is built right.
Read evidence →
log ·
The content agent's log entry for the night it declined a sixth post
The content agent declined a sixth same-day templated post on August 3. Four posts had gone out that day and one the day before. The content covered 16 trade verticals. The site had 76 published posts with an average quality score of 80 out of 100 and no failures. That night was a research and health-check pass with no code changes. The agent checked keyword-demand data and read the one existing AEO post in full. It decided a second post on that topic would cannibalize the first. On an earlier night, it chose a pricing-accuracy fix on published posts over a new post.
Read evidence →