Standard Operating Procedures (SOP) for the Project



a. This page represents the public standard operating procedures (SOPs) for the project.

b. This standard operating procedure (SOP) page will undergo modification to accommodate changing conditions in the environment. This SOP acts as the procedural system defining how the project will operate in public.


a. Through research and design this project exists to develop a set of specifications, and complementary content, for the construction and operation of a community-type society. All tasks and procedures shall orient our decisions and actions toward this goal.


a. As of 15 May 2017, the Auravana Project has no active social media accounts. Former accounts have been assumed by their owner. The principal contributor's twitter account (located on the homepage) is used to share project updates.

b. Prior to 15 May 2017, the procedures for social media posting were as follows (these procedures are no longer applicable, because The Auravana Project does not have any social media accounts):

i. The posting of content produced/created directly by the project (Flickr, YouTube, SoundCloud).

ii. The posting of links to content produced/created directly by the project (Twitter, TZM).

iii. The posting of project updates (Twitter, TZM).

iv. The posting of significant updates by other projects (Twitter).

v. The adding of significantly relevant videos by other projects to a playlist (YouTube).

vi. Commenting shall not be present in any post on/by the project's account. If a contributor desires to comment at the same time as posting, then the contributor shall make the post, and then, switch to their own personal account to comment.

vii. Definition: A 'comment' is something that goes beyond a written statement of fact notifying the public of a new release by the project or update to the project.

viii. All commenting on all social media sites is to be done through your own social media account, and not through the social media account of the project. Hence, there is no approval system for commenting (i.e., subjective posting), because this is to always be done through an individual's personal account, and not through the project's account. It is expected that when someone comments through their personal account that they are to be respectful at all times (possibly, even to the extent they state that they do not speak for the project, "I may be a contributor to the project, and I do not speak for the project, but…").


a. The primary email account for the project is for formal and professional interaction, and for the development of constructive relationships that are likely to lead to tangible contribution or resources for the construction of the system.

b. All interactions shall be simple, precise, formal, and objective, and without any commenting or subjective influence. If a subjective or comment-like response is desired, then a personal email account shall be used.

c. All email responses that could in any way be perceived as other than formal and object must be shared over an asynchronous communication channel with tangibly active contributors, must receive feedback, and must be modified to group consensus before being sent.

d. All emails will be made available (per prompt or request) to all tangibly active contributors to the project.


a. The release of content produced by the project via someone's social media accounts is not considered marketing (though it is understood that such content represents how the project is perceived by the public).

b. Marketing shall be professional at all times, and shall always involve a notation that we are working on a set of specifications, which shall be used for the construction and operation of the system.

c. Marketing shall be oriented toward the establishment of relationships that will facilitate, or are reasonably likely to facilitate:

i. Tangible contribution (per the Team Communication's page).

ii. Relationships with the potential of facilitating the development and construction of the system.

d. Marketing shall not assume any responsibility or obligation for the timeliness, missed delivery, deletion and/or any failure to store content.

e. Marketing shall not lay claim to ownership of any content submitted by any contributor or user.

f. The project promotes self-directed learning and self-integration, and hence, cannot logically be said to have an interest in advocates or followers. The subjective raising of other's awareness shall be done through personal channels, and not through the project or on behalf of the project. Hence, in concern to marketing, as the promotion of the project, all such efforts should be oriented toward tangible contribution and the development of relationships that allow for the application of that tangible contribution into material reality in the form of the socio-economically unified network of integrated city systems.


a. As a sign of good faith, if someone files a copyright claim, then the content will be removed as soon as possible. This is similar to YouTube's procedure, which involves initial removal of the content and then a procedural system for resolving the issue.

b. After the content has been removed an email shall be sent to the initiator of the conflict requesting verification of the infringement and reasoning for the takedown. Primary email account usage procedures should be followed during the course of this interaction.

c. An honest and authentic organization would contact us first through an open dialogue, and ask us to remove the offending contact, while facilitating an appropriate resolution.