| Storytelling Policies: | | | | | | | |
| | | | | | | |
| Existing Policy: | | | | | | |
| Require all information to be easily publicly searchable with a simple URL link or decentralized file or info key, and automatically processed into other forms/platforms otherwise 0.25h policy tracking starting for the new half year. And data must be backupsble and stored on our own accessible storage (AWS, Google,or InMotion) NO barrier, NO log-in or pay wall to information. |
| | | | | | | |
| | | | | | | |
| New | Policy Propsal: TO require Notes Updates, so that all information from our notes is access for public searching on our note.updates.fqn.fun. | | | | | | |
| Everything that is presentable infromation is required to be posted directly in our note uptes. | | | | | | |
| | Real-Time | | | | | |
| | | | | | | |
| Policy Proposal: Every time we create a public doccument, it must be shared and publised on the web thorugh google. Exampe: Go to “file” menu and then “share” and then “Publish to web”. | | | | | | |
| | | | | | | |
| | | | | | | |
| new | Policy Proposal: TO requier decisions to be posted onto our decisions.fqn.fun site, within X amount of time, or policy tracking. | | | | | | |
| Details: | To start it is fine to first quickly post the decision on the decision schannels, but then eventuaully it needs to get on to the decisions site. | | | | | |
| Detail: | Decisions are required to link the verifiable information so that the deicison itself can always be verified into the future. | | | | | |
| | | | | | | |
| | | | | | | |
| new | Policy Propoal: Updating policies after decisions are made that effect policies is required on the policy.fqn.fun site, within X days or policy training time logged. | | | | | | |
| | | | | | | |
| | | | | | | |
| new | Proposal: TO require topic update summaries at the end of every topic or 0.25h policy traiing.. | | | | | | |
| | Real TIme | | | | | |
| | min 1 summary per topic (max is 2) | | | | | |
| | | | | | | |
| | | | | | | |
| new | Proposal: TO require session summaries and updates made within X hours of the end of each session???? | | | | | | |
| | Min one summary per session. (max is 2) | | | | | |
| | | | | | | |
| new | Proposal: To require daily summaries and updates from the team by the end of Sonic each day. | | | | | | |
| | Min 1 summary update per day, by the end of sonic. | | | | | |
| | max 2 per day, can do one during old world as well. | | | | | |
| | | | | | | |
| new | Proposal: To require the team to do a Weekly summary, after revieing the daily summaries, summaries the daily summaries, and then post minimumonce per week. | | | | | |
Leave a Reply