Brian Marick's exploration of "New Hampshire Style", "Software evolution inspired by ecological and embodied cognition" site 
- does FedWiki's evolution reflect some of these principles? Do these principles, followed more consciously, help FedWiki to preserve important properties of flexibility and adaptability?
Consensus-forming cascades - when do people commit to a decision or strategy? Early adoption and late adoption; who do you vote for, and why? Who do you look to for evidence? ("social proof"). Manipulation of consensus-forming processes. Emotional narratives, anchoring decisions in emotional narratives. Thompson Morrison on "show your tender self" related to telling your authentic truth as an author, contrasting with Wikipedia's "cite and summarize supporting sources" approach.
Authenticity and faking authenticity, confidence tricks and street crime hacking into people's trust model.
Diagram showing enabling connections among early features and decisions in FedWiki (first two years, up to Assets, in blue) and recent features and decisions (latest two years; Frame Scripting, etc., in green). Are there patterns we see here in the novel mechanisms and concepts which mostly don't disturb established ones, patterns which preserve flexibility and adaptability?
FedWiki as a community of interacting knowledge sites, whose approach is broadly in dialogue / in parallel with other communities which point directly to FedWiki as an inspiration (MASVF Wiki etc.).
Seeding a consensus-forming cascade as a way of telling the story of bringing Design Patterns from vernacular architecture into software development, and the first Patterns conference, within a year and a half.
Paul's demonstration of popping up the "cc-by" detail window outside the browser pane as a new browser window.
Troubleshooting a wiki install and developing custom plugins on a Windows platform for Robert Best.