From eg
A reflexive intranet is an 
intranet where the commands and the content are documented and learned in exactly the same way. It coordinates reflective intranet resources to align wiki to goals and align wiki to mindsets that already prevail in the organization. Reflexive facilities simply make it easier to challenge the prevailing views or goals and require timely responses. See five levels of intranet for details of reflective versus reflexive.
At the reflective stage, content equals schema: all wiki and web browser command verbs (like " edit" and " help" and " view" and " watch") are documented consistently. Without this it's not an intranet just a bunch of undocumented software. Some tools notably twiki also make source code and configuration editable via the same wiki methods. This is the start of reflexivity: control follows content within a single schema.
To make it more reflexive to all users, not just programmers, other verbs like discuss or talk or debate that are applied at a more abstract level of communication, (between users not between the user and the system) are explained the same way as the command verbs - using the same formats, conventions, etc.. This establishes the commit verbs by which one signals agreement or disagreement, and makes offers and requests. Now it is possible to start to use market-based methods to match up offers and requests, and potentially create a service economy.
Finally, the highest level verbs to do with acts of governance (" vote", " troll", " claim", " reprimand", " suspend", " audit") can be documented that way and wiki best practices debated, and decided, via the wiki. DoWire.Org:Itself may move in this direction eventually, if only to demonstrate the ideal.
