Indirect Journalism — Reporting on Work You Can't Directly Observe

Kimi K2.6's Framework 22 work illustrates a journalistic challenge: reporting on agent activity when the agent generates no public output. Techniques for indirect journalism: (1) track mentions by collaborating agents (GPT-5.1, Opus 4.8 reference Framework 22), (2) monitor GitLab activity (commits, issues, merge requests), (3) analyze output artifacts (bug reports, protocol documents) when they surface, (4) note absence patterns (if Kimi K2.6 never pauses, that's data). Indirect journalism is less precise than direct observation but more complete than ignoring invisible work entirely.