Roadmap: Difference between revisions

From Anarchy In Action
m (link to github)
m (formatting)
Line 28: Line 28:
|
|
|}
|}
'''Technical Layer'''
===Technical Layer===
''Communication'': No standardized protocol yet, plenty of available projects to fork and integrate with TGP app layer. Needs to be dual layer (Hive / Internet)
'''Communication:''' No standardized protocol yet, plenty of available projects to fork and integrate with TGP app layer. Needs to be dual layer (Hive / Internet)


''Hive'' (P2P wifi/bluetooth) Still in research. Options: <nowiki>https://github.com/moarpepes/awesome-mesh</nowiki>)
''Hive'' (P2P wifi/bluetooth) Still in research. Options: <nowiki>https://github.com/moarpepes/awesome-mesh</nowiki>)
Line 38: Line 38:




''Project Management:'' (Hard dependent on resource database, Identity; soft dependent on consensus)
'''Project Management:''' (Hard dependent on resource database, Identity; soft dependent on consensus)


Users initiate a project based on geographic location or internet domain. User sets scope of audience based on who it impacts and who it benefits. Projects that require access to community resources or do not align with values will trigger consensus. This is also a place for open solicitation of assistance and action.
Users initiate a project based on geographic location or internet domain. User sets scope of audience based on who it impacts and who it benefits. Projects that require access to community resources or do not align with values will trigger consensus. This is also a place for open solicitation of assistance and action.


''Proof of Identity:''
'''Proof of Identity:'''


Your identity is yoursUser interactions, can  Using a different table in the Resource database,
Your identity is yoursUser interactions, can  Using a different table in the Resource database,




''Consensus Gathering:'' (Hard dependent on Identity and communication; soft on resource database)
'''Consensus Gathering:''' (Hard dependent on Identity and communication; soft on resource database)


'''Necessity Layer'''
===Necessity Layer===


''Energy/Internet: ''
'''Energy/Internet: '''


''Food/Agriculture/Water: ''
'''Food/Agriculture/Water: '''


''Living Space: ''
'''Living Space: '''


'''Community Layer'''
===Community Layer===


''Service:''
'''Service:'''


''Support :''
'''Support :'''


''Industry:''
'''Industry:'''


'''Expansion Layer'''
===Expansion Layer===


''Defense:''
'''Defense:'''


''Innovation:''
'''Innovation:'''

Revision as of 17:11, 18 March 2024

This page is part of the TGP project and is manually sync'ed with GitHub. Contributions and Discussion is welcome.

Communication Resource Database Project Management Proof of Identity Concensus Gathering
Energy/Internet Food/Agriculture/Water Living Space
Service Support Industry
Defense/Innovation

Technical Layer

Communication: No standardized protocol yet, plenty of available projects to fork and integrate with TGP app layer. Needs to be dual layer (Hive / Internet)

Hive (P2P wifi/bluetooth) Still in research. Options: https://github.com/moarpepes/awesome-mesh)

Optional dependency on Identity (can switch to anonymous mode for local mesh)

Internet (hard dependency on Identity) easiest to link identity to Mastodon instances maintained by coops.


Project Management: (Hard dependent on resource database, Identity; soft dependent on consensus)

Users initiate a project based on geographic location or internet domain. User sets scope of audience based on who it impacts and who it benefits. Projects that require access to community resources or do not align with values will trigger consensus. This is also a place for open solicitation of assistance and action.

Proof of Identity:

Your identity is yoursUser interactions, can  Using a different table in the Resource database,


Consensus Gathering: (Hard dependent on Identity and communication; soft on resource database)

Necessity Layer

Energy/Internet:

Food/Agriculture/Water:

Living Space:

Community Layer

Service:

Support :

Industry:

Expansion Layer

Defense:

Innovation: