ColivingLiguria

S.r.l. — Startup Innovativa
Apply Now

3 min read

TODOAI: Deployment of Collaboration System & Legal Framework

🎯 Mission Objective

Create a seamless, high-security, and user-friendly environment for non-programmer collaborators. You must implement the backend scripts, the frontend documentation, and update the legal contracts to regulate this interaction.

🛠️ CLAUDEHELP: BACKEND DEVELOPMENT (/adminCL/)

The following requires system setup and security scripting:

  • cl-setup.sh: Automates brew install gh, auth login, and shell aliases.
  • cl-sync.sh: Pull logic, BureauRegister validation, and automated commits.
  • cl-wipe.sh (CRITICAL): Secure corporate data deletion with metadata searching and safety confirmations.

📄 Phase 2: Frontend Implementation (Quartz/TSX)

Generate a high-fidelity, bilingual guide: /content/System/Collaborator-Onboarding.tsx.

  • Guidelines: Use <Bilingual /> components. Follow the minimalist, dark-mode “World-Class” UI.
  • Content:
  • Visual Stepper: 1. Install → 2. Authenticate → 3. Sync → 4. Wipe.
  • Terminal Code Blocks: Provide the one-liner installation command.
  • Safety Warnings: Highlight that the system is only for corporate data and that personal data must be backed up elsewhere.
  • Link to Legal: Direct link to the digital version of Allegato G.

Update the contract to include the digital platform regulations.

  • Clause: Technical Interaction: Define the obligation to use the provided cl-sync and cl-wipe tools.

  • Clause: Mandatory Cleanup: Explicitly state that upon termination, the user MUST run cl-wipe.

  • Clause: Limitation of Liability:

  • Italian: “La Società non si assume alcuna responsabilità per la perdita di dati personali del Firmatario derivante dall’installazione, dall’uso o dalla procedura di cancellazione dei tool aziendali. È onere del Firmatario eseguire backup preventivi.”

  • English: “The Company assumes no liability for the loss of the Signatory’s personal data resulting from the installation, use, or deletion procedure of the corporate tools. It is the Signatory’s responsibility to perform preventive backups.”

  • Disclaimer: State that malfunctioning of the scripts does not shift liability to Coliving Liguria.

📋 Compliance & Constraints

  1. Frontend: Adhere to Style_palette.tex for colors and TSX-Components.md for layout.
  2. Backend: Use set -e traps for safety, but include the “Rollback” logic we defined to prevent directory pilling.
  3. LaTeX: Maintain the bilingual sentence-by-sentence structure. Ensure the document ID matches the BureauRegister.
  4. Information Gathering: If you cannot find the current index.tex or the BureauRegister SQL schema, STOP and ask the user to provide the file content before proceeding.

🤖 Final Directive for the Agent

  1. Analyze: Review the existing adminCL folder (if any) and the LaTeX_CL structure.
  2. Execute: Write the 3 Bash scripts, the TSX page, and the LaTeX updates.
  3. Validate: Check that the cl-wipe command does not accidentally target root directories.
  4. Report: Provide a summary of all new paths and a “Ready to Sync” status.

What I can do next for you:

Would you like me to draft the specific logic for the cl-wipe command right now to ensure it is “extra safe” and doesn’t delete anything outside of the designated Coliving Liguria folders?

Graph View