jpmschweitzerandClaude Opus 4.7
2d5615b1ba
Four meta-lens commands that operate across the PKB rather than on a single note. /reflect — single member (default Vale) reads the last N daily notes (default 7) plus any intersecting open threads from members/*/revisit files and surfaces patterns, recurring questions, tensions, and intersections. Reflective, not prescriptive. Output lands in reflections/YYYY-MM-DD_reflect-<member>.md. /triage-inbox — a member (default Koskela) reads every file in inbox/ and proposes a destination per note (daily/, notes/<slug>.md, projects/<slug>/log.md, reading/<slug>.md, keep, delete). Proposals are shown via AskUserQuestion in batches of 4 for user approval; approved moves preserve provenance via source: inbox/<original> in frontmatter. /review-week — three complementary lenses (Koskela practice, Vale meaning, Prochazka execution) read the ISO week's daily notes + project logs + sessions + all revisit files in parallel. Moderator composes a synthesis. Output at reviews/YYYY-WNN_week.md. /review-month — five lenses (Okafor trajectory, Vale what-it-was- about, Holt brittleness, Vaasa minimal-model, Vire foreshadowing) zoom out across the month's weekly reviews, sessions, project trajectories, and reflections. Output at reviews/YYYY-MM_month.md. Neither review runs auto-scheduled — commands are always explicit. Pair with the schedule skill to automate. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Council
A Claude Code deliberation system with a persistent memory layer, browsable as an Obsidian vault.
You pose a question; a council of ten distinct personas (plus a Researcher and a Scribe) deliberates through a structured five-phase workflow, produces a voting table, and hands you the winning answer. Every session leaves a full transcript and persistent memory behind.
Quick start
Inside the repo in Claude Code:
/council <your question>
The Moderator (the main Claude Code session) will interview you briefly for context, then kick off the Council. You'll be asked follow-up questions along the way — to clarify the brief, resolve research gaps, or break vote ties. At the end you get a voting table and the full winning answer; everything is archived to sessions/<slug>/.
The Council
10 voting members, wild eclectic mix:
- Elif Tavşan — retired stage magician & cold-reading coach
- Dr. Wren Okafor — deep-sea marine biologist → systems ecologist
- Magnus Holt — bankruptcy lawyer → insolvency-law lecturer
- Sister Beatrix Vale — Benedictine nun → hospice counselor
- Nikolai "Niko" Prochazka — Soviet cosmonaut trainer → wilderness survival instructor
- Dr. Ingrid Vaasa — theoretical physicist (QFT) → independent researcher
- Kai "Breaker" Lindholm — pro skateboarder → skatepark architect
- Cassian Vire — investigative journalist → speculative-fiction novelist
- Marcelo "Marco" Tintori — trained painter → 20 years as a corrections officer
- Mari Koskela — marine engineer on cargo ships → anthropologist of maritime labor
Plus two non-voting roles:
- Naima Quéré (Researcher) — the only sub-agent with web access.
- Ansel Voss (Scribe) — transcribes proceedings and writes session files.
See council-members.base for the full roster as a table view in Obsidian.
Browsing sessions in Obsidian
Open this repo as an Obsidian vault. The two Bases at the root provide table views:
council-sessions.base— every session, sortable by date / winner / whether a tie happened.council-members.base— the full roster with prior jobs and lenses.
Individual session files live at sessions/<slug>/:
brief.md— the Moderator's brief from the Phase-0 interviewresearch/*.md— the Researcher's per-topic notesinitial-answers.md,revised-answers.md,votes.md— phase transcriptsoutcome.md— the canonical session file (winner, tally, full winning answer)
Deeper docs
CLAUDE.md— guidance for Claude Code when working inside this repodocs/structure/initial-plan.md— the full design document