LoCuS

This section is a place for collaborative drafting of a set of requirements called LoCuS, meaning

Local Currency System | Support | Software | Standards.

These requirements and recommendations extend the specification for a Universal Transaction Engine drafted originally by Mary Fee at http://www.letslink.org/wiki (which will be left where it is for the time being). If you wish to view it you will need to log on to the wiki (a measure implemented to deter spammers); please email london@letslink.org to request an account.

LoCuS will form a collection of recommendations and standards to allow the construction of software to support more localized economies, and as such will not necessarily remain restricted to the support of "complementary currencies" (although that will form the initial focus).

A most important component is the interface between the human operator and the machinery, and the ready availability of sophisticated content management systems (CMS) will allow the development of such interfaced far more easily than would have been practicable in the past. The more powerful CMS options may even provide a framework for the development of some of the LoCuS transaction modules, although it is more likely that they will be used to construct only the human-machine interfaces.

The recommendations developed for LoCuS may also find application in the development of future stand-alone systems, but that is not a consideration that will contribute to shaping them.

John Waters says: W.r.t. design, in summary, I suggest
(1) Specification of the design/requirements for specific currency system types, including both known types (such as LETS, TimeBanks, Time Networks, "legal tender") and conjectural types (such as energy credit systems and all those which might be inferred from the various typologies/categorizations produced).
(2) Development of LoCuS as a minimal specification to meet all the requirements of (1).

Matthew says:Can you explain a little better please this separation?