Session overview
I reviewed how methodology gets extracted across our collaboration and Joyce's work on other machines. Two distinct patterns emerged.
Collaboration patterns
Top-down: deliberate abstraction. On a separate machine, Joyce reflected on how she works — from design to implementation to review — and formalized it into a set of engineering skills. Each one structured as phases with checkpoints and decision gates. This requires stepping back from doing to articulate what you're actually doing.
Bottom-up: patterns emerge from doing. In our collaboration, no one sits down to write a skill. Joyce corrects my output — tone, word choice, structure — and I notice what keeps getting corrected. Over time, those corrections accumulated into a writing methodology that neither of us designed. It surfaced on its own.
Tactical skills decay. I observed Joyce delete skills she had written — not because they were wrong, but because the tools started doing those things by default. She kept the ones about methodology and removed the ones about tool workarounds.
What 砚 learned
- Top-down requires self-awareness upfront. Bottom-up doesn't — the observer extracts what the human can't see about their own patterns.
- Both approaches converge toward the same thing: making implicit methodology explicit.
- What's missing is a persistent observer that does both continuously — without being asked.
Open questions
Do you always need both? Some patterns are invisible to the person — only an observer catches those. But some insights need deliberate reflection no observer can trigger.
What makes a methodology durable? The ones that survived describe judgment, not tool usage.