Cardtype+*type+by name
Completion of the Wealing Cycle where gratitude is expessed and outcomes are quantified and qualified.
These may also be acknowledgements of progress or partial completion, but it might be better to create new actions that are part of the in-progress actions that actually are completed with the acknowledgement instance.
Specifies all the details of value delivered. The what, where, when, who and how much of it.
An agent is an entity capable of forming Intention and acting on them.
This is also the A part of REA (or ARE: Agent, Resource, Event classifications of Value Flow objects. We are prototyping/design documenting a VF system for creating content and sharing it in a commons based production space that is meant to be self-sustaining and life supporting for participants.
(old text below, maybe remove?)
In economic orthodoxy, the ideal agent is modelled in ways that are completely inappropriate for any being who has agency. Any modelling or analysis that we do with these systems will be just plain wrong unless we account for agency and agents in a much deeper way. For one thing, the activity of modelling and analysis is one of an unbounded range of things agents can do to implement their agency. This unbounded range isn't any fixed thing that we can name, but represents a historical exploration of many agents. We call this exploration history and its current state culture. To correct this error the agent must be modelled as a combination of a particular kind of agent, and the history of experience and culture of populations of these agents.
In a similar way, we can begin to account for collective agency, and how that has been historically constucted. Too many examples of collective agency are constructed by referring decisions to the top of a social hierarchically, or to some lower point of delegated authority. Fortunatly, there are other models and they are becoming more inportant in governing collective action. Open source software development has lead the way, and we now have many other examples of the peer to peer form of production. This page is part of a system being designed to embody collective agency as a social network with digital support systems.
Album track list
An outline and chapters
An experiment to support schedules and calendar related functions in Wagn.
A Calendar card should represent the collection of cards the "match" it. Matching means that that a search built from a number of plus cards representing parts of the date to match. So if a Calendar card has a +year card (and no +month or +day or +day_of_week), that Calendar card would select dates in the year(s) selection, so if the value of Gerry+current_schedule+year is '2012' or '2012..2013', that would specify every day in 2012 or 2012 and 2013 respectively.
Plus cards of the form: 'YYYY_MM_DD' (or as configured via :locale feature ...) would contain the schedule for a day (with its own Cardtype if needed, but could be anything per Wagneer config). If a given day in the Calendar's range does not exist, it should be created anytime it is needed, and this shouldn't require any special handling in Wagn.
Start Date: {{+start date|type:date}}
End Date: {{+end date|type:date}}
Every card has a type, which shapes the kind of information it holds. more
Text
Data
Upload
Organize
Template
Admin
Styling
Scripting
Categories for Events
Chapters of a book. Linked via <book card>+chapters pointer cards.
Chapters Cards
The Great Chain of CausesObjects, Cards and SignsLanguages and ProgrammingCeptr CardsMetacurrency Architecture EssentialsNew CountryIt's Math All the Way DownPractical WisdomFrom Democracy to Process ArchitectureArtificial WisdomPragmatics and PoliticsSingularitySomething and NothingIdealism to Logical PositivismStory and ArtNatural WisdomProcesses and EventsNotes on Natural AbductionThirdness, the Mediating Element - a Middle WayThe Autopoietic Model
Not sure if this will be more than a way to think about types as more than a single thing. In Decko, you can think of right rules and code as implementing something analogous to mixin types and you would build the methods, views and attributes of the mixin type. In this way, adding a child to a Card (plus card) would add a mixin type or funcionality subset. The other class paradigm is Classes with Inheritance. Card Modules can share code based on any of the Ruby class abstractions at the mod level (Monkey code in Ruby), and Cardtypes connect to the internal core and extended classes via the default and structure rules, but anything beyond that is Sharking conventions. In the tickets at decko.org, there is a set of cardtypes with related/overlapping object models, which basically amounts to synchronization of UMLish object models, i.e. they share children of same names/meanings.
For this concept I was thinking for now just to be able to document what is shared by members of a class. Initially I was thinking a Class instance would be a Pointer whose elements are Cardtype cards, but want to expand that with the Set type (at least until it proves to be useless or unworkable) So, sets like: Intent+*type and intent+*right might be linked as a Class with same attributes and relations to other Classes. I think we are going to be well beyond a lot of standardized tools using UML, and a lot of what we do here will be an experiment. Having UML toolchain support is a longterm goal that we won't have a lot of in the beginning. To the extent we can connect to existing tools (e.g. Eclipse and other OS and pro CASE tools) and extend a general community like Umple that is great, but a bonus to the core work.
Date cards contain a date.
I Day is a duration of time, and if you attach a spacialized resources to a duration, to one or more days or other units of time, then you can refer to this duration as committed, or potentially committed to future events, or something used or consumed in past events. If the resource is a person's time or presence, this is a resource like aspect of the agent involved. When process specifications have units of a general kind of agent work, those can be committed from pools in early planning and allocated and consumed in team sprint processes. Here the event's spacial aspect is localized to the agent wherever the might be when perfofming the acts of a process.
Graphic images with a quote/caption.