About

A project born from the reality of complex procedures and designed to make case files easier to understand.

ClariDroits aims to reduce administrative fatigue without oversimplifying human situations. Technology organises and explains; the person and professionals retain the decision.

Human English clarity reviewed — accessibility testing pending — ClariDroits is currently a project led by Patrick François Kahouadji, before the legal entity is established.

The page language is British English (en-GB), the reference country is France and the jurisdictional context described is French. These are separate: choosing English does not select UK law or activate any French right, procedure, deadline or public availability.

Review status: Human English clarity was reviewed on 30 July 2026. Patrick approved this informational English web release. Native British English review and human accessibility validation are not claimed; no accessibility-conformance claim is made.

Why the project exists

A lived difficulty that became a design requirement.

Patrick François Kahouadji leads ClariDroits on the basis of his own experience of disability and practical experience of medical and social procedures.

Difficult letters, medical certificates to prepare, scattered documents, deadlines, case files that had to be rebuilt and information that was sometimes misunderstood: the project starts from this everyday reality, not a theoretical use case.

ClariDroits aims to turn this complexity into understandable facts, connected documents, qualified evidence and cautious next actions.

Lived experience guides the product without replacing medical, social, educational, legal or administrative expertise.

Founder's words

I did not create ClariDroits to make one more application, but so that I could finally use the application I would have needed during my own experience of disability.

  • Patrick François Kahouadji
  • project lead for ClariDroits

Kyrelia Technologies

French technology designed around practical usefulness.

The name Kyrelia Technologies refers here to a project under development, not to an already incorporated company. ClariDroits combines lived experience, knowledge of procedures and software engineering. Reviews by disabled people and professionals are being sought; no human validation has been obtained at this stage.

Start with the real situation

Observe the actual difficulty before designing an interface or domain rule.

Document the results

Retain tests, limitations, issues and records rather than claiming absolute coverage.

Keep control

Reduce transfers of sensitive data and prioritise local processing where the version supports it.

Progressive development

Build, check and qualify before expanding.

The source describes five successive areas of work.

Understand

Gather situations, documents, accessibility needs and the risks of error.

Structure

Create domain capabilities, the orchestrator, graph, memory and checking components.

Test

Turn documented cases into repeatable tests with expected results and execution records that still need to be checked.

Qualify

Measure stability, performance, backup, restoration, accessibility and known limitations.

Seek field evaluation

Seek review and testing by willing individuals, carers and professionals before considering any wider distribution.

Evidence and transparency

Show what works, what still needs checking and what is blocked.

The project distinguishes observed evidence, product history, AI principles and verified wording.

Field evidence

Feedback, observed benefits, reservations and measurements still to be completed.

Public history

Major stages in the product, domain-specific AI and interfaces.

AI principles

Safeguards, human control, limitations and responsibility.

Material suitable for citation

Proposed wording that must be checked before it is used to present the project without exaggeration.

Partners and funders

Assess the project against evidence, a defined scope and explicit limitations.

ClariDroits aims to prepare possible future pilots with willing associations, professionals or medical and social organisations. No pilot, agreement or official partner is claimed at this stage.

An exploratory discussion is never presented as an official partnership, and no logo is displayed without written agreement.

Automated checks do not amount to human, accessibility, field or legal validation. Each form of evidence must be obtained and documented separately.

For a pilot participant

Any possible future controlled pilot would need a defined scope before use.

  • a clearly defined objective and audience
  • controlled test data
  • a shared feedback framework
  • visible known limitations
  • no implicit distribution

For a funder

The project is presented through its problem, architecture, evidence and realistic roadmap.

  • the practical problem and affected population
  • architecture and security
  • technical and domain evidence
  • impact indicators to be measured
  • a realistic roadmap

Continue

Understand the project before choosing the next step.

The source directs readers to the project lead, history, evidence or pilot resources according to their role.

  • project lead and team
  • project history
  • available evidence
  • pilot resources

Publication safeguards

Limits that remain visible in every language

  • ClariDroits aims to reduce administrative fatigue without oversimplifying human situations.
  • Technology organises and explains; the person and professionals retain the decision.
  • Lived experience guides the product without replacing medical, social, educational, legal or administrative expertise.
  • The project documents tests, limitations, issues and records rather than claiming absolute coverage.
  • Human English clarity is documented; no human product, field, accessibility or legal-compliance validation is claimed.
  • An exploratory discussion must not be presented as an official partnership.
  • No logo is displayed without written agreement.
  • No wider distribution is implied by a pilot.

Key facts

Clear answers about this page

Why was ClariDroits created?
It grew from Patrick François Kahouadji's own experience of disability and practical difficulties with medical and social procedures.
What does local-first development mean on this page?
The source describes reducing transfers of sensitive data and prioritising local processing where the version supports it.
How does ClariDroits describe its development method?
Understand, structure, test, qualify and seek field evaluation before considering wider distribution.
Does an exploratory discussion count as an official partnership?
No. The source explicitly says that an exploratory discussion is never presented as an official partnership.

Frequently asked questions

Questions about this page

Does lived experience replace professional expertise?

No. It guides the product without replacing medical, social, educational, legal or administrative expertise.

How does the project demonstrate transparency?

It documents tests, limitations, issues and records and distinguishes what works from what still needs checking or remains blocked.

Is field validation the same as automated testing?

No. Automated checks remain distinct from human, accessibility, field and legal validation, none of which is claimed here.

Are interested organisations automatically presented as partners?

No. An exploratory discussion is not presented as an official partnership, and no logo is displayed without written agreement.