PM Phase 2 — 11 Questions

Ratify Phase 1 audit synthesis?

Reviews/2026-05-22-wikivault-build-audit.md · commit e0fe5d9

Ratify as-is Ratify with changes (note changes below) Reject (note reason below)

Optional: changes / reason / additional context

saved

Ratify Phase 2 config-mapping?

Projects/2026-05-22-variant-config-mapping.md · commit eba6c81

Ratify as-is Ratify with changes (note changes below) Reject (note reason below)

Optional: changes / reason / additional context

saved

Approve must-do #1 — PM scrubs variant-claude-md obsolete framing across all 8 vault files?

Replace "deployed copy syncs from this file" with corrigendum-aligned framing.

Yes — PM proceeds No — discuss first Wes does it manually

Optional: notes

saved

Approve must-do #3 — Fix Doc 28 Decision 7 body language?

Strike "Proposed:" at line 197, strike rejected v1-v3 sync language at lines 203-208.

Yes — PM proceeds No — discuss first Wes does it manually

Optional: notes

saved

Variant claude.md canonical direction?

Affects ALL downstream variant wiring.

(a) Vault canonical — corrigendum-aligned; local @-imports from cache (b) Local canonical — Ace's frontmatter; vault is mirror for discoverability (c) Hybrid — vault canonical for Ethos/shared; local canonical for variant identity

Optional: notes

saved

vault-sync trigger frequency?

Every hour during active hours On session boot only Manual only (v0) Webhook on commit — more responsive; more work

Optional: notes

saved

Universal @-import order in LOCAL CLAUDE.md?

Ethos first, then self-variant claude.md Self-variant first, then Ethos Doesn't matter — last @-import wins on conflict

Optional: notes

saved

PM peer variant promotion?

The always-on Telegram-enabled M3 variant from this morning.

Resume now Defer until post-MVP Cancel the promotion — PM stays session-scoped coordinator

Optional: notes

saved

Stub variant migration ownership?

Bilby / Frank / Clarvis / Clars / Nagatha vault claude.md.

Each variant on next session Autonomous PM peer pass Wes manually Mix — PM drafts, variants verify

Optional: notes

saved

Q10

Clars machine + identity?

Separate variant — note machine below Clarvis-alias — same machine, alias-merge per Clars/Tony pattern Unknown — needs investigation

Optional: machine / clarification / notes

saved

Q11

vault-sync trigger ownership?

PM peer specs OS-side commands; each variant provisions PM peer specs AND provisions everywhere it can (Mac, SSH-reachable M1) Each variant fully owns their trigger setup

Optional: notes

saved

Q12

Anything else / context / corrections?

Optional — fully open.

saved