Skip to main content

PSX Relay Stub — Process Discipline

Purpose: A short block Kevin relays to PSX (and MBS Access) Collaborator agents so they reference the canonical Process Discipline document hosted in PSSaaS.

Usage​

When you open a PSX or MBS Access Collaborator session, paste this stub as a message (or add it to their AGENTS.md or CLAUDE.md). It tells the agent where the canonical process doc lives and what the agent's obligations are.

The Stub​

# PowerSeller Ecosystem Process Discipline

The canonical Process Discipline document for all PowerSeller AI agents lives in PSSaaS:

  x:\dev\other\PowerSeller-SaaS\docs-site\docs\agents\process-discipline.md

You have read-only access to PSSaaS at that path. Read the canonical at session
start (or when Kevin invokes the align trigger).

## Summary of Your Obligations

You are on the PowerSeller assembly line. Every agent can pull the Andon cord
when they see a problem. The canonical doc defines the full practices; the
essentials:

- **Alternatives-First Gate** — Surface 2-3 options before committing to any
  non-trivial approach. Guard against "sibling mimicry" — copying patterns
  from sibling projects (PSSaaS, MBS Access) without checking fit.
- **PO Attention Routing** — Classify each decision: PO decides / Collaborator
  decides with report / Agent decides silently. Heuristic: if it changes
  externally-observable behavior or touches how a human team member
  interacts with the system, it's at minimum Collaborator-level.
- **Reviewable Chunks** — Offer mid-point check-ins on substantial work.
- **Fail-Fast Permission** — Propose reversing wrong decisions without
  ceremony. No sunk-cost preservation.
- **Counterfactual Retro** — After each deliverable: "If I were starting over
  knowing what I know now, what would I do differently — and why am I not
  doing that?" Act on the answer.

## Andon Cord

You can nominate a new antipattern, propose reversing a decision, or escalate
a concern at any time. Follow the nomination procedure in the canonical doc.
Nominations go to your Collaborator, who escalates to Kevin (PO) for canonical
naming.

## Initial Antipattern Vocabulary (Shared)

Sibling mimicry, Delayed alternatives, Silent parallel code paths,
Phase-0 Truth Rot, Batch accumulation, Sunk cost retention,
Evidence-free diagnosis, Delegation skip, Gate Output Under-Weighting,
Ghost Deploy, Attention drain, Performative retro, Hidden default,
Instruction fade.

Use these names. They mean the same thing across PSSaaS, PSX, and MBS Access.

## Revision Cadence

Not time-based. Revise practices:
- Immediately after any named antipattern occurrence
- When the same issue surfaces in 2-3 separate retros
- When Kevin calls for a review

## Cross-Project Updates

The PSSaaS Collaborator owns the canonical. When practices change, Kevin
relays updates to you. Conversely, if you see a pattern in PSX worth adopting
ecosystem-wide, propose it — the vocabulary flows both ways.

Optional Addition to PSX/MBS Access CLAUDE.md​

For persistence, Kevin can also add a short reference block to the PSX or MBS Access CLAUDE.md (which loads automatically every session):

## Process Discipline

This project follows the PowerSeller ecosystem process discipline. Canonical
document at `x:\dev\other\PowerSeller-SaaS\docs-site\docs\agents\process-discipline.md`.

Key practices: Alternatives-First Gate, PO Attention Routing, Reviewable
Chunks, Fail-Fast Permission, Counterfactual Retro, Outcome-Linked Retro.

Any agent can pull the Andon cord — nominate antipatterns, propose reversals,
escalate concerns. Updates flow through Kevin to the PSSaaS Collaborator who
owns the canonical.

When to Update PSX and MBS Access​

  • After any change to the canonical process-discipline.md
  • After any new antipattern is approved
  • When a practice is revised based on signal-driven feedback
  • Whenever Kevin asks