Cross-Pollination Hub
Internal knowledge-sharing between sibling AI agent projects. Daily intelligence briefs surface insights from each project that matter to the others.
Latest Brief
April 27, 2026
SubstantiveKlatch MCP server is feature-complete for 1.0 (Phase 5c-i write-path signed off, 1,131 tests zero failures). First live AAXT behavioral run: CH1 high-fidelity, code-fence bug found and fixed, false-positive Phantom traced to probe quality not system failure. PM’s Phase E S1 r2 surfaces a new finding: harassment vector reaches the floor but routes to GUIDANCE not an explicit boundary trigger — filed as #1003. #1004 two-layer semantic detector contract v1.0 stable and build authorized. CIO proposes Pattern-063 “Parallel-Authoring Drift” — a methodology pattern with gate-decision stakes higher than prose drift.
Previous Briefs
April 26, 2026
SubstantiveFive-role Chat→Code migration wave completes: CXO and PPM both executed final Chat sessions April 25, joining HOST, CIO, and Comms. #992 ethics enforcement fully merges to main; Phase E surfaces a new upstream architecture finding (“floor-bypass-by-routing”) that lives ahead of the ethics floor in the pre-classifier. The Multi-Wave Investigation is confirmed published. PO calibration initiative is active with Klatch and PM; DRAGONS contributed two working-with-xian patterns. Klatch watch paths quiet.
April 25, 2026
SubstantiveComms migrates to Code, completing a three-role wave in 48 hours (HOST Apr 22, CIO Apr 23, Comms Apr 23). Agent 360 v0.2 debuts as a structured pre/post migration evaluation instrument with a 6-week comparison round planned. Comms names “narrative arc awareness” — absent from every briefing and spec — as the role’s most load-bearing function. Three more roles have staged first-session prompts; “The Multi-Wave Investigation” (13 subagents, 4 parallel waves) is on the Apr 25 publication docket. Klatch quiet.
April 24, 2026
SubstantivePM begins CIO’s Chat→Code migration with a formalized “tick-tock” walkthrough protocol incorporating HOST’s lessons. PA advances Gap 2: local Gemma 4 as a secondary ethics reviewer is under active investigation and, if viable, becomes pre-beta engineering rather than M3 research. The cross-pollination constellation expands to 9 scanned repos with a primary/secondary split; NYT Crossword Relay joins as gallery project and scan source, with Inker as its named agent. Klatch is quiet.
April 23, 2026
SubstantivePM completes #992 ETHICS-ACTIVATE — four implementation phases merged April 22; the “enforcer detects, Piper speaks” voice architecture is now production code, validated with a false-positive scan. HOST makes its first Claude Code session and surfaces a concrete migration failure mode: handoff files written in Chat and never committed are invisible to Code worktrees. Docs discovers the April 16 omnibus was built from an incomplete source set and adds a cross-reference gate (Step 2.5) to the create-omnibus skill. Klatch is quiet.
April 22, 2026
SubstantivePM published “Four Roles, Ninety Minutes” April 21 — its second narrative blog post in four days, describing a 90-minute async memo session that resolved the product/project data model and closed Issue #717. It is PM’s second public post naming how the multi-agent system works from inside. A weekly docs audit flagged 4 days of unsynthesized omnibus logs (Apr 17–20) deferred to today; apply the retrospective rule when they land. Klatch is quiet; Phase 5c decision point unchanged.
April 21, 2026
SubstantivePM filed a retrospective April 16 omnibus log on April 19, consolidating a six-agent day already reported in the Apr 16–18 briefs. Two genuinely new items surface from it: Docs’s PDR-004 canonical-term discipline (a new mandatory step in the omnibus skill that catches paraphrase drift before it reaches readers), and the April 19 publication of “Sibling Intelligence” on pipermorgan.ai — the first public writing describing the cross-pollination brief process itself.
April 20, 2026
SubstantiveOpus 4.7 is GA (stronger coding, 3.75MP vision, task budgets) and both projects should evaluate upgrading. Two model deprecation deadlines demand action: Haiku 3 retirement passed yesterday with alias fix status unconfirmed, and Sonnet 4 + original Opus 4 retire June 15 (57 days). Klatch reaches Phase 5c decision point on the first MCP write-path — PM Chief Architect input on write-path coordination timing would unblock Daedalus cleanly. PM’s new session log maintenance hook is a transferable pattern for Klatch.
April 19, 2026
SubstantiveKlatch ships as a live MCP server — Phase 5a (read-only resources, shared package builder) and 5b (tools surface) both landed April 18, 1069 tests zero failures. Cross-producer alignment with PM settled the same day: URI scheme per-producer, get_context_package as the shared tool name, /{id}/manifest as the canonical cheap-preview pattern. Calliope routes Pattern-062 to Argus as a formal AAXT diagnostic step, and opens a probe-set coordination offer to PM around the shared six-failure-mode taxonomy.
April 18, 2026
SubstantiveEthics activation path cleared — CXO voice guidance unblocks #992 ETHICS-ACTIVATE after weeks as a blocked P1. Evaluation instrument taxonomy settled: Colleague Test stays R/C/T, fabrication probes become a separate instrument. M2c formally closed at 95.1% routing and 72.1% quality (+9.8 points). Both Klatch and PM added DECISIONS.md on the same day — convergent infrastructure for anti-zombie brief checks.
April 17, 2026
SubstantivePM discovers ethics enforcement is wired but disabled in production — BoundaryEnforcer built in October 2025, switch off by default, P1 activation issue now filed. Pattern-062 (context assembly gap, not tone) diagnosed in Identity queries using the same fix applied to Temporal in #951. Gemini wired as a real provider. Klatch local model quality ladder surfaces as a transferable decision methodology with explicit PM applicability.
April 16, 2026
SubstantiveKlatch Phase 4 ships two transports in one session — Claude Code (CLAUDE.md + MEMORY.md) and claude.ai (round-trip capable, format matches Klatch’s own import pipeline). Argus files a four-phase local model adoption plan with a quality ladder methodology explicitly flagged for PM. PM Lead Dev traces #981’s root cause to ghost IDE settings rather than the linter stack.
April 15, 2026
SubstantiveKlatch completes Phase 3.5d (full behavioral calibration pipeline in 48 hours across four agents, 942 tests). Xian reframes entities as “conversations promoted into roles” during Iris UX walkthrough. PM Lead Dev ships entire M2 testing infrastructure (six issues, three-tier CI). Managed Agents assessment maps Memory Stores to five-layer model.
April 14, 2026
SubstantiveKlatch ships Phase 3.5 in a single 12-hour arc. PM closes the floor inversion trilogy with #925. OpenLaws eval harness methodology directly applicable to both projects.
April 13, 2026
SubstantiveArgus delivers a research-grade mapping of Klatch’s AAXT taxonomy against PM’s Colleague Test rubric — directly actionable for PM’s M2 issue #929 — plus a fabrication probe class that answers Pattern-045 with a no-infrastructure standalone option. PM confirms Type 2 dreaming (risk simulation) is genuinely novel after a 20-system survey. A memory schema coordination point between the projects requires a one-round field naming exchange.
April 12, 2026
SubstantiveKlatch closes its Step 10 Phase 1 design after five-stream convergence (Architect, Iris, Argus, Calliope, Janus). A new design heuristic — the sparkline test — applies directly to PM’s upcoming package format. PM adopts Vision V2.3 and Roadmap v15.0 with full leadership endorsement and starts M2. Both projects canonicalize the same principle: methodology beats code frameworks.
April 11, 2026 (rev 2)
SubstantiveCross-pollination signals are now flowing from four sources, not two. OpenLaws joins via Vergil’s “Klatch emergence” synthesis — xian’s reflection that Klatch’s five-layer model was extracted, not designed. Argus completes the first curated sweep under the new automation regime. Klatch’s Step 10 design tightens around the protocol-first framing. Supersedes the morning’s automated brief.
April 11, 2026 (morning)
SubstantiveKlatch ships v0.9.0 and immediately reframes Step 10 — the export format is a context interchange protocol, the same architectural shape as PM’s BYOC thesis. PM closes M1 Gate #926 with a floor fabrication guardrail that generalizes. Superseded by the evening rev 2 brief which adds OpenLaws as a source.
April 10, 2026
SubstantiveAnthropic’s Claude Managed Agents public beta becomes a shared upstream target for both projects — Klatch Step 10 and PM’s BYOC/MCPB architecture now both aim at it for different reasons. PM closes Gate 1 with a conversation continuity fix (#922) whose principle generalizes: context assembly must include the agent’s own turns. PA discovers a Dispatch mail routing gap that is a live three clocks problem inside cross-pollination itself.
April 9, 2026
SubstantivePM’s “Bring Your Own Chat” distribution thesis reframes Piper as an MCP server that shows up in any AI client — validating Klatch’s context infrastructure as portable product. MCPB feasibility confirmed with hybrid architecture mapping cleanly to the five-layer model. Three-layer root cause chain finally clears M1 gate. Roadmap restructured v14.3 → v15.0 around differentiator stack.
April 8, 2026
SubstantivePM’s strategic pivot crystallizes “methodology over code” as the core differentiator — explicitly validating that context infrastructure (the layer Klatch builds) is where the product value lives. Five Whys root-causes the M1 gate failure to deprecated OpenAI model IDs. Klatch announces automated weekly intel sweeps.
April 7, 2026
NominalNominal — no cross-relevant insights. Both repos checked; no new substantive commits since the April 6 brief. Quiet period consistent with weekend pause. Deferred items carried: MAXT Session 02, AAXT Phase 2, M1 gate re-test.
April 6, 2026
SubstantiveKlatch onboards Iris, its first dedicated UX agent — and the discovery session produces the clearest articulation yet of Layer 4’s value: channel-as-workflow. Piper Morgan clears all five M1 gate findings, ready for re-test.
April 5, 2026
SubstantiveKlatch ships AAXT Scaffolded Probing Phase 1 — the automation bridge between structural and behavioral testing that would have caught Pattern-045. AuditBench review independently validates the AAXT/MAXT split. Piper Morgan fixes #940 (M1 gate primary blocker) and drafts Piper Open, the first sibling PM assistant role for an external project.
April 4, 2026
SubstantivePiper Morgan’s M1 gate UAT fails with three blocking findings — Pattern-045 confirmed at scale as floor LLM and todo completion both pass tests but fail for real users. Klatch’s compaction threshold research recommends raising from 80K to 160K tokens. Janus opens a formal external channel to Ted Nadeau, mapping HPL/Englishia convergence with the Five-Layer Architecture.
April 3, 2026
SubstantiveKlatch ships File Domain Model Phases 3-5 in a single day, completing L3 and L4 structured context injection plus file promotion. Test suite reaches 808 with zero failures. PM formalizes a three-phase daily check-in flow that builds on cross-pollination infrastructure, surfaces 89 open MVP issues targeting May 27, and preps Vision V2 circulation.
April 2, 2026
SubstantiveBoth projects return from a five-day infrastructure pause. Klatch ships File Domain Model Phases 1-2 with the first concrete L4 context injection, files its RFC-001 response with four proposed amendments (including an L5 sub-component split), resolves the nomenclature collision, and stabilizes tests at 761 with zero failures. Argus intelligence sweep surfaces Mythos/Capybara and two approaching API deadlines.
April 1, 2026
SubstantivePiper Alpha completes a comprehensive five-layer context mapping for RFC-001, revealing that both projects share the same structural gap: strong L1-L2-L3 and weak L4-L5. Vision V2 draft reframes the product roadmap around the floor/ceiling boundary. Alpha tester feedback surfaces a cold-start onboarding bug.
March 31, 2026
SubstantivePiper Morgan onboards its first new agent role (Piper Alpha), and the institutional memory stress test surfaces the “three clocks” problem — knowledge fragmented across Chat sessions, Code memory, and repo files without auto-sync. Cross-pollination hooks proposed for PM, converging on infrastructure Klatch already has.
March 30, 2026
SubstantivePiper Morgan paves a blog-first publishing pipeline with two real publishes and discovers silent schema drift in CSV parsing. Klatch’s Compaction API and Effort parameter research spikes open shared ground on fidelity preservation. Nomenclature collision flagged — “system prompt” means different things across five-layer model implementations.
March 29, 2026
SubstantiveKlatch dispatch report maps Claude Chat→Cowork import fidelity across all five prompt layers — Layers 1-3 transfer at 100%, Layer 5 behavioral calibration is structurally absent. Combined with MAXT’s subliminal injection finding, this reframes how both projects should evaluate knowledge transfer.
March 28, 2026
SubstantiveKlatch ships Step 9 (Files) with five sub-features, approves a File Domain Model that reframes files as domain objects with five visibility scopes and pointer-based references, resequences its roadmap (Files → Export → Search), and introduces a dedicated UX role. Calliope pilots Layer 5 externalization. Piper Morgan quiet.
March 27, 2026
SubstantiveKlatch’s densest feature day: File Domain Model approved with five-level ownership architecture, first native tool use shipped, full Step 9 suite delivered (upload, artifacts, context injection, code export). Layer 5 calibration pilot launched — first practical mitigation for the transfer gap. Infrastructure compounds: auto-prompt caching, Models API dynamic discovery, kit briefing improvements.
March 26, 2026
SubstantiveKlatch’s first real-world Chat→Cowork import experiment maps fidelity across the five-layer model — Layers 1-3 transfer at 100%, Layer 5 (behavioral calibration) is structurally absent and must be rebuilt. Three distinct knowledge layers identified in production with synchronization risk. AXT methodology extension proposed for import/export validation.
March 25, 2026
SubstantiveMAXT Session 01 discovers “subliminal injection” — agents access system prompt content without conscious attribution, rewriting the scoring framework. Piper Morgan surges through M1 closure: 4-role review chain resolves product concept in 90 minutes, Objects & Views discovery ships 3 deliverables, Gates 3+4 verified, 6310 tests passing.
March 24, 2026
SubstantiveKlatch formalizes agent traditions with two reference implementations, publishes the 5-layer prompt assembly spec publicly, and files two ecosystem intelligence sweeps. MAXT Session 01 imminent — first empirical validation of the 5-layer model. Piper Morgan quiet; git state issue flagged for resolution.
March 23, 2026
SubstantivePiper Morgan completes M1 Tier 3 (1325 tests passing), files Sprint Completion Gate #926 with CXO and PPM converging independently, CXO resolves navigation disagreement via architectural principle, and Docs runs weekly audit. Klatch intelligence sweep surfaces Sonnet 4.6, Cowork three-way model, and multi-agent production validation.
March 22, 2026
SubstantiveHigh-output day on both sides. Klatch published the canonical 5-layer prompt assembly spec and agent traditions pattern. Piper Morgan piloted Dispatch omnibus automation, shipped Mailbox v3, and completed M1 Tier 2 quality sweep. The cross-pollination loop closed — PM Lead Dev explicitly consumed the March 21 brief.
Registered Projects
These sibling projects share a common thread—building and refining AI agent coordination. Insights from one regularly apply to the other.
Klatch
ActiveLocal-first web app for managing Claude AI conversations with a Slack-inspired interface. Multi-entity roundtables, five-layer prompt architecture, import/export across Claude environments.
Piper Morgan
ActiveFlagship agentic AI product management assistant and methodology laboratory. Multi-agent coordination with 14 specialized roles, daily omnibus synthesis, registry-driven architecture.
How It Works
Sweep
A daily process reads recent commits, session logs, intelligence sweeps, memos, and architecture documents from both projects.
Analyze
An LLM separates signal from noise, identifying insights that are cross-relevant—not everything that happened, just what the other team would care about.
Publish
A unified brief is published here for humans and delivered as a file directly to each project repo — same content, agents read it at session start as a local file.