> For the complete documentation index, see [llms.txt](https://handbook.collettivoamigdala.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.collettivoamigdala.com/accordi-valori-metodi.-lhandbook-di-amigdala/agreements-values-methods-eng/how-we-organize-ourselves/digital-tools/archiving.md).
# Archiving
Contents of this page
* [Drive (shared archive)](#drive-archiviazione-condivisa)
* [Organizational structure](#organizational-structure)
* [How to use](#greater-than-discord-1)
* [Access and licensing](#access-and-licensing)
## Drive (shared archive)
### **Organizational Structure**
The shared archive is structured to reflect the organizational system of the working groups, facilitating day-to-day operations and ensuring coherence in content, access, and use.
Main folders include:
* **Administration** *(cross-functional group)*
* **Communication** *(cross-functional group)*
* **Coordination**
* **Artistic Creation** *(project-specific group)*
* **Space Management** *(cross-functional group)*
* **Childhood and Adolescence** *(project-specific group)*
* **Programming** *(project-specific group)*
* **Territorial Research** *(project-specific group)*
* **Vedetta**
A collective folder titled **"Programming"**, organized by year, is maintained. Within this folder, **shortcuts to each project folder** are added, allowing for an overview of all annual projects, which are often cross-group.
### **How to use**
Each group is free to organize its own folder based on operational needs, as long as a shared base structure is maintained. Each group folder should include at minimum:
* **Folder index** (to help with navigation, consultation, and planning)
* **Meeting's notes**
* **Project folder**, with subfolders for each project. Each project folder must include a shortcut to the general **"Projects"** folder located in the "Programming \[year]" folder, to ensure overall traceability of Amigdala's activities.
> ⚠️ **Cross-functional groups** (e.g., Administration, Communication) coordinate with **project-specific groups** to agree on how to manage shared folders.
### **Access and Licensing**
Each group appoints a person responsible for archive maintenance, with the following duties:
* Define the folder’s structure to ensure functionality and accessibility for all group members
* Keep the folder index up to date
* Verify document accessibility and manage any restrictions based on data sensitivity
* Create and maintain links to the "Programming \[year]" folder for each active project
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://handbook.collettivoamigdala.com/accordi-valori-metodi.-lhandbook-di-amigdala/agreements-values-methods-eng/how-we-organize-ourselves/digital-tools/archiving.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.