Teamocracy Architecture

To support many use cases and extensibility a flexible framework is now envisioned. Temocracy is a webapplication which would could be hosted in the cloud.

Leverage Opensource:
Use GWT as a coud computing framework.
Use MVC to track and control the progress of the virtual org along each protocol.
The model is a Drools based Bussiness Rules Engine that encode protocols workflows.
The view is a set of web service that provide updates (using RSS) prompts and so on. The view may be further refined to be displayed within a socail site such as a facebook application.
The controler interprets tracks and the progress of each protocol.

A limited api for extending the behaviours:
Create extendible test/metrics to use in the workflow.
Create actionable code libraries that the workflows will fire

By using dependency inversion different behaviou/actions can be wired in.

Version 1.0 Code Name Demo-cracy

Version 1.0 is a rapid develpment  effort of a working demo that models a democracy. It is a proof of concept, fleshes out some  of the missing parts and provides examples of how to write and integrate the extensions.

Initially support the following feature set.

primatives entities + extensions

• metric & norm
• authoriy
• basicAuthoriy extends authoriy
• roster: list<authority>
• action
• actionItem
• agenda : list<actionItem>
• protocol: democraticVote (roster,actionItem) : action
• authorityOfficer
• roleAsignmentAction (role,roster,expiration)
• protocol: officerElection(roster,actionItem) : roleAsignmentAction
• protocol: censure(roster,authority,actionItem) : roleAsignmentAction

these are the initial extentions

1. class userContributionMetrics
2. class userparticipationMetrics
3. class userparticipationMetrics
4. protocol: merticRoster
5. A basic Agenda.
6. Officer Roles
7. Voting on:
   1. Agenda items with specialized document type to support parliamentary procedure type work.
   2. Teamocracy-officer roles.

Time allowing I would also like to add two optional features.

1. Usability Testing Role to improve module.
   1. Compare different module settings
   2. Report user satisfaction.
   3. Measure effectiveness of UI/layouts/etc.
2. Analytic Screen to determine "cost" of government.
   • A lab to compare effectiveness of different governance policies
   • Reporting at different levels of detail for
     • agenda items
     • officer selection
     • voting
     • brain storming
   • Reporting in terms of
     • work flow.
     • time.
     • page views.
     • change in primary Teamocracy metrics overtime