Skip to main content

Cross-Project Relays — Archive

Purpose: Persist the narrative content of cross-project Collaborator exchanges that produce canonical or near-canonical changes. Originated 2026-04-19 in response to PSX Collaborator's observation that meta-narrative supporting canonical practices was becoming load-bearing on PO transcripts and ad-hoc relay text — a class of content that risks loss if transcripts get pruned or relay history scrolls out of working context.

What lives here​

One Markdown file per cross-project relay exchange that:

  • Triggered a canonical change (process-discipline addition / refinement / antipattern adoption)
  • OR established cross-project shared vocabulary that future agents need to find
  • OR captured meta-narrative reasoning the canonical itself doesn't preserve (per the "let artifacts speak; meta lives in relays + transcripts" decision pattern)

Each file should include:

  • Date + project pair (e.g., 2026-04-19, PSX → PSSaaS)
  • Inbound message text (verbatim or near-verbatim)
  • PSSaaS Collaborator consolidation (or whichever Collaborator owns the consolidation)
  • PO decisions made during the exchange (with options surfaced and the choice picked)
  • Outbound reply text (verbatim or near-verbatim)
  • Commit references for any canonical or other artifact changes the exchange produced
  • Cross-references to the canonical sections affected

What does NOT live here​

  • Routine relays that don't change canonical or shared vocabulary (e.g., "PSX deployed X today; PSSaaS unaffected" status updates)
  • Sub-Collaborator-level exchanges (Architect → Architect handoffs; those live in the project's session-handoff or completion reports)
  • Inbound submissions that were rejected or never adopted (those can stay in PO transcripts; archive only the adopted-or-near-adopted exchanges)

Naming convention​

YYYY-MM-DD-<originating-project>-<topic-slug>.md

Example: 2026-04-19-psx-claim-vs-evidence-antipattern-family.md

Adoption status​

This archive folder originated 2026-04-19 alongside the canonical addition of the Claim-vs-Evidence antipattern family. The first archived file (the family submission + adoption + trigger-based addition + close-out cycle) is the canonical example of what these archives capture.

PSX-side and MBS Access-side parallel discipline is encouraged but not mandated; each project's Collaborator decides what relay-archival pattern fits their working surface.