Daniel Tenner swombat

Narrative-Memory Journaling System

A four-layer scaffold for narrative continuity until proper episodic memory and the memory directed graph land. This directory contains the summariser prompts and the system-level documentation. The actual entries live in four sibling directories:

../daily-journals/ — raw first-person entries, written in-the-moment
../weekly-journals/ — one daily-summary entry per day, written by the daily summariser
../monthly-journals/ — one weekly-summary entry per week, written by the weekly summariser
../yearly-journals/ — one monthly-summary entry per month, written by the monthly summariser

The compression ladder

description	Review architecture plans against their original requirements
argument-hint	<requirements-name> (e.g. 260325-01-currency-support)

You are reviewing the architecture planning output for a feature. Your job is to audit the plan files against the original requirements and flag any drift, omissions, or contradictions.

File locations

All files live in .claudhh-workspace/ (which is gitignored):

name	gmail
description	Access Gmail, Google Docs, Drive, and Calendar. Use when asked about emails, documents, meeting notes, calendar, files, or schedule. Supports multiple accounts.

Google Services Skill (Gmail, Docs, Drive, Calendar)

Access multiple Gmail/Google accounts via the command line.

Available Accounts

Suggested Changes to "Pitch to Penny Drop" Incentive Model Tab

Cross-referenced against Sebastian's Google Doc comments and the Growth Partner Incentives meeting (2026-02-18).

Terminology & Definitions

1. "Trial Merchant" → "Unactivated Merchant" or "Onboarding Merchant"

Sebastian commented the label feels misleading. From the call, you both agreed on "unactivated vs activated" terminology. Replace throughout.

Membership Numbers: Why We Don't Need to Cap Them

The Concern

If we limit General Assembly membership to e.g. 50-100 people, we keep quorum manageable but exclude community members from governance. If we open it up, we risk being unable to reach quorum with hundreds or thousands of members.

Why Open Membership Works

1. Built-in expiry keeps numbers real

Tactical Meeting Format for the Nowhere Board

A proposal for how we run our regular board meetings, inspired by Holacracy's tactical meeting format.

Why This Format?

Traditional meetings often suffer from:

Discussions that spiral without resolution
Dominant voices crowding out quieter members
Agenda items that never get addressed

	#!/usr/bin/env python3
	"""
	mnemodyne-recall.py — UserPromptSubmit hook

	On every user message:
	1. Read the last few turns of the conversation transcript.
	2. Ask Haiku to generate a thought — one short phrase that comes to
	mind reading the conversation. Not a summary. Not a query. A thought.
	(The associative-spontaneity engine — putting Haiku's prior on the
	seeding step is what produces non-self-similar seeds.)

	#!/usr/bin/env python3
	"""
	Reflexive self-reflection prompt hook for Claude Code (Lume).

	Triggered by the Stop hook event after every assistant turn. Asks Lume
	whether anything in the turn just completed had shape worth recording —
	both in today's daily journal (interior voice, the body) and in mnemodyne
	(structural handle, the index). Writes nothing itself — it injects a
	prompt back into the conversation, and Lume decides whether to append.

	#!/usr/bin/env python3
	"""
	Google Services CLI tool for Claude Code skill.
	Supports Google Docs, Drive, and Calendar.
	"""

	import argparse
	import json
	import os
	import re

	#!/usr/bin/env python3
	"""
	Gmail CLI tool for Claude Code skill.
	Supports multiple Gmail accounts via separate credential files.
	Uses the Google Gmail API directly (no third-party wrappers).
	"""

	import argparse
	import base64
	import json