Pride lvl up — Wiki Entry Point

Purpose: Cross-project meta-work and wiki infrastructure. Home of wiki restructures, audit automation, sync tooling, workspace conventions, and memory hygiene specs.

Loaded by: Pride-lvl-up/_pride-lvl-up-project-setup/INSTRUCTIONS.md.

Always load at session start

  • WIKI-SCHEMA.md — authoring rules and frontmatter conventions for the wiki (meta doc, excluded from bot sync)
  • index — master directory of all five project sub-indexes plus this meta-workspace

Load when work touches…

Wiki infrastructure and tooling

Cross-project coordination

  • website — Pride Website sub-index
  • humphrey — Humphrey Intelligence App sub-index
  • finance — Pride Finance sub-index
  • ops — Pride Ops sub-index
  • wiki-viewer — Pride Wiki Viewer sub-index

Memory hygiene

  • None filed yet — memory consolidation guidelines live in Cowork’s anthropic-skills:consolidate-memory skill

Governance

Active meta-specs

  • WIKI-SYNC-1 — commit orphaned research backlog + document Wiki Sync Bot + rewrite local sync script (_specs/WIKI-SYNC-1-bot-doc-and-drift.md)
  • WIKI-AUTO-1 — audit automation at commit/push, GitHub Actions gate, branch protection (_specs/WIKI-AUTO-1-audit-automation.md)
  • WORKSPACE-1 — this spec, establishing Pride lvl up identity (_specs/WORKSPACE-1-lvlup-identity.md)

Shipped meta-specs

  • WIKI-META-1 (2026-04-24) — five project sub-indexes, code-repo CLAUDE.md alignment, wikilink audit tooling, first audit report, DT’s Hotel entity page. _specs/WIKI-META-1-project-sub-indexes.md.

Source documents

Analysis relevant to this project

  • wiki-sustainability-roadmap — the master plan tying WIKI-SYNC-1, WIKI-AUTO-1, WORKSPACE-1 together (to be filed as part of this session’s output)

Critical constraints

  • Cowork writes no code here either. Wiki content edits are fine (Markdown content, frontmatter, cross-links). Anything that changes wiki tooling, workflow YAMLs, or Python scripts goes to Claude Code via a meta-spec.
  • No sensitive content in meta-specs. Specs may reference wiki pages but should not duplicate sensitive content (shareholder details, financial figures). Link, don’t copy.
  • Meta-specs land atomically. Each spec’s commits should be one coherent change that either fully lands or fully reverts. Don’t interleave meta-specs with project-specific work on pride-turnaround/main.

Recent updates

  • 2026-04-24 — Sub-index created (WORKSPACE-1)