Glaux
With Glaux I work on converting documents to Markdown and replacing identifying data with pseudonyms. I am still working on Lince, its review tool.
Security objective
A standard above ordinary market practice
The programme’s ambition is to develop a data-handling and confidentiality system that is more demanding than ordinary market practice. This is a design objective that must be demonstrated through technical, security, privacy and operational testing; it is not a quality claimed as proven today.
What the project is intended to solve
What the project is intended to solve
Glaux is not a language model and is not intended to make the professional decision. It is the local custody, processing and control zone placed before information is connected to an external AI service.
The central idea is to protect before connecting: originals, reidentification keys and correspondence maps remain local, while only task-bounded and approved context may move onwards.
Conceptual architecture
Conceptual architecture
Protected origin
Original documents, reidentification keys and sensitive organisational information are intended to remain within a local zone governed by defined roles and permissions.
Local processing
OCR, conversion into structured formats, detection of sensitive fields, pseudonymisation or anonymisation where appropriate, and quality control are intended to take place before any transfer.
Controlled exit
A task- and policy-based gate is intended to restrict each transfer to what is necessary and expressly authorised. External AI services should not receive originals or reidentification keys by default.
Local return
In the intended flow, results should return in pseudonymised form. Authorised rehydration is intended to take place locally, while source, version and processing history are retained for review.
Design principles
Design principles
- Process before connecting
- Conversion, detection and data protection are placed before any external transfer.
- Minimum necessary context
- Each task receives only the information and access required for its bounded purpose.
- Traceable and reversible processing
- Sources, versions and transformations are recorded; rehydration requires the authorised local map.
- Humans retain authority
- Releasing sensitive context and making decisions with external effects require appropriate human control.
Role in the wider system
Role in the wider system
Glaux is designed to be assembled with Alonides: Glaux is intended to protect and transform information, while Alonides is intended to manage context and orchestration. Membrain can build on that combination, but the projects remain separate and full integration should not be assumed.
Pseudonymisation reduces exposure, but it is not automatically equivalent to anonymisation. Its legal effect depends on the context and on the reasonable means available for reidentification.
Areas of work
Areas of work
- 01
Local document intake and offline processing
- 02
Detection, pseudonymisation and controlled restoration of sensitive information
- 03
Versioned organisation of sources, knowledge and working documents