omnibase/legal

Lawyers - rules and sources

Each rule the profile codes (classes under Base\Legal\; tests under tests/), the text it rests on, where that text was read, and the class and test that carry it. Read on 2026-10-05.

Compliance built into the code does not replace the Ordre's control: the conseil de l'Ordre is the only judge of a site's conformity.

The texts

Coded rules

Practice\Guard\Wording, Lawyer\Guard\SpecialistWords and Lawyer\Guard\DomainName read words: a help to whoever writes, shown in the back office. What they do not find is not thereby allowed.

What the application must keep (no check can see a template)

• RIN art. 10.5: « Le site de l'avocat ne peut comporter aucun encart ou bannière publicitaire, autres que ceux de la profession, pour quelque produit ou service que ce soit. »
• RIN art. 10.5: no hyperlink to a site whose content is contrary to the profession's essential principles; the lawyer visits the linked sites regularly. The memo recalls both.
• RIN art. 10.6: a denomination evoking generically the title, a field of law, a specialisation or an activity of the profession is forbidden - the same reading as the domain name's applies to the firm's name, which the bundle does not check.

To confirm (not coded as rules, or coded with this reserve)

• The current list of the mentions of specialisation: read in the CNB's 2022 leaflet (28 mentions); the order of 28 December 2011 as amended could not be read on Légifrance (it refuses automated readers). To be compared before a real firm relies on it.
• The article of the code de la consommation that has a professional give the mediator's coordinates (art. L. 616-1, as recalled from memory) was not read: the mediator and its coordinates are confirmed, the legal basis of the obligation is not - hence a warning, not a missing mention.
• Loi n° 71-1130 du 31 décembre 1971, art. 10 (fees, the mandatory agreement): cited by the RIN in the heading of its article 11, not read itself.
• The contest of fees before the bâtonnier (the fees and mediation pages say it): from RIN art. 11.5 (« il devra saisir son bâtonnier aux fins de taxation ») and the decree of 27 November 1991 cited in the heading of article 11, not read itself.
• The name of the mediator in office changes (a term of a few years): the configuration names the institution, not the person.
• Each bar's own rules (its règlement intérieur) may add to the RIN: not known to the bundle.

Notaries - rules and sources

Each rule the profile codes (classes under Base\Legal\; tests under tests/), the text it rests on, where that text was read, and the class and test that carry it. Read on 2026-10-05.

Compliance built into the code does not replace the chamber's control: the chamber of notaries verifies its notaries' sites and is the only judge of their conformity.

The texts

Coded rules

The wording check is a list of expressions (Practice\Guard\Wording): a help to whoever writes, shown as a warning. What it does not find is not thereby allowed.

What the bundle does not do, by design

• No online payment. The bundle offers none and the tariff page says so. The plan's reason ("clients' funds go through the Caisse des dépôts") was not verified on an official text as a prohibition of card payment of a notary's fees: it is therefore a choice of the product, not a coded rule. To confirm with the chamber before any payment is added.
• No testimonials, no client reviews, no comparison table. The bundle has no such entity or page. That testimonials are forbidden as such was not found in the texts read (the RPN forbids advertising, art. 14.2, and paid referencing): to confirm.
• No advertising insert. RPN art. 14.4: « Le site internet du notaire ne comporte aucun encart ou bannière publicitaire autre que celui ou celle de la profession. » Nothing in the bundle displays one; the application must not add any (no check can see a template).
• No paid referencing, no mass mailing. RPN art. 14.2: « La pratique du référencement payant est prohibée » ; art. 14.3: a personalised solicitation is a letter or an e-mail only. The bundle sends nothing but the answers to what a client asked.

To confirm (not coded as rules)

• The code de déontologie itself (decree n° 2023-1297): its articles on communication and on the title (art. 15, referred to by RPN art. 15) could not be read. To be read on Légifrance.
• The exact wording of art. L. 444-4 of the code de commerce and the article that asks for the discounts to be published (R. 444-10, as recalled from memory): read through notaires.fr only.
• The graphic charter and naming plan of the Conseil supérieur du notariat (intranet of the profession): a real office's site must follow them - its domain name too (RPN art. 16.2). The demonstration's own design is therefore provisional for a real office.
• Whether @notaires.fr is required of the site's sender address as well as of the notary's own address (the check warns, it does not fail).
• The mediator's e-mail address (only the postal address and the site were confirmed: https://mediateur-notariat.notaires.fr, postal address also on justice.fr and inc-conso.fr).
• A salaried notary must name the holder of the office and its seat in what they write (RPN art. 15, last paragraph): left to the member's biography, not checked.

Jurists - the law of 31 December 1971

French law no. 71-1130 of 31 December 1971 (art. 54 and following) reserves personalised legal advice and the drafting of deeds for others to the professions it allows: a lawyer, a notary, a university teacher of law (art. 57), another regulated profession within its own field (art. 59). Training, documentary information (art. 66-1), writing content, talks are open to anyone.

# config/packages/legal.yaml
legal:
    profession: jurist
    jurist:
        authorized_status: ~     # teacher (art. 57) or regulated_profession (art. 59) lifts the guard

A jurist keeps no practice: omnibase/office is not needed, and none of the practice's pages, tables or checks is loaded. The profile is the guard:

• Jurist\Service\RegulatedActivityGuard::check($text) - null, or jurist.guard.legal_consultation / jurist.guard.deed_drafting (domain legal) when the text announces a reserved activity (Jurist\Enum\ReservedActivity: "consultation juridique", "conseil juridique personnalisé", "rédaction d'actes", "legal advice"...), whatever the offering was filed under;
• with omnibase/consulting, its rule Jurist\Consulting\OfferingRule (an OfferingRuleInterface of that bundle): an offering whose title, sentence or presentation announces one does not validate, and the back office prints why under that text.

Until 2026-10-09 this was omnibase/consulting's RegulatedActivityGuard (consulting.regulated_activity_guard, consulting.authorized_status): a site moves those two options here, as above.

It is a safeguard written into the code, not legal advice: what it does not find is not thereby allowed, and the profession's own rules still apply. Tests: tests/Jurist/.

Configuration reference

The legal tree

Dumped with Symfony's YamlReferenceDumper from Base\Legal\DependencyInjection\LegalConfiguration:

legal:

    # The profession the site is for: its profile is loaded, and it alone - its compliance checks, its entities and their tables, its pages, its demonstration accounts.
    profession:           ~ # One of "lawyer"; "notary"; "jurist", Required

    # The roles omnibase's groups give (security.yaml puts the readers under the staff's).
    roles:

        # Who of the practice reads a client's document; the rest of the staff sees that it exists. Default: the profession's - a lawyer [ROLE_LAWYER], a notary [ROLE_NOTARY, ROLE_CLERK].
        readers:              []
        staff:                ROLE_STAFF

    # The consumer mediator whose coordinates the practice gives (/mediation, the legal notice). Default: the one the profession set up.
    mediator:
        name:                 null
        address:              null
        email:                null
        url:                  null

    # The profession's rules, linked from the legal notice. Default: the profession's (a lawyer: the RIN on the Conseil national des barreaux's site).
    rules_url:            ~

    # Expressions added to the built-in list the texts are checked against (comparison, disparagement, and the profession's own).
    wording:              []

    # The lawyers' profile.
    lawyer:

        # The domain names the site answers on, checked against RIN art. 10.5 and listed in the memo for the Ordre. None: the host of the router's default address.
        domains:              []

        # Where the domain name is read when legal.lawyer.domains is empty.
        default_uri:          '%env(default::DEFAULT_URI)%'

        # Paying a fee note online - fees only, never clients' funds. Needs omnibase/marketplace: without it the link is not shown, whatever is set here.
        payment:
            enabled:              false

            # The application's route where a fee note is paid (the marketplace's checkout of a fee note).
            route:                null

    # The notaries' profile.
    notary:

        # What a notary's professional e-mail address ends with (règlement professionnel, art. 16.3).
        email_suffix:         notaires.fr

        # Where the regulated tariff is read: the official text, the order in force, the profession's explanation.
        tariff:

            # Code de commerce, articles A444-53 and following (the notaries' tariff).
            code_url:             'https://www.legifrance.gouv.fr/codes/texte_lc/LEGITEXT000005634379'

            # The order fixing the tariff in force, as it is named on the page.
            order:                'arrêté du 25 février 2026'
            order_url:            'https://www.legifrance.gouv.fr/eli/arrete/2026/2/25/ECOC2604872A/jo/texte'

            # The last day of the order's period: past it, the back office asks for the new order.
            until:                '2028-02-29'
            info_url:             'https://www.notaires.fr/fr/profession-notaire/le-tarif-du-notaire-emoluments-et-honoraires'

    # The jurists' profile.
    jurist:

        # A status that lets the jurist give legal advice all the same (law of 31 December 1971): a university teacher of law (art. 57), another regulated profession within its own field (art. 59). A lawyer or a notary is not a jurist's status: that is another profession.
        authorized_status:    null # One of null; "teacher"; "regulated_profession"

What reads each key

Only the chosen profession's section becomes parameters (legal.lawyer.domains, legal.notary.tariff...), with the common keys (legal.profession, legal.roles.readers...).

Services

config/services.php loads the practice's common part (src/Practice, on omnibase/office) when the profession keeps a practice (a lawyer, a notary), and the chosen profession's directory alone (src/Lawyer, src/Notary or src/Jurist); bin/console debug:container --tag=legal.profile lists what the profile registered. The routes follow the same rule through Base\Legal\Routing\ProfileRouteLoader (omnibase/legal).

Translations

The domain legal, in English, French and German (ICU format).

Testing

Running the suite

Inside a host application that has omnibase/office (the practice's tests need it, tests/NeedsOffice.php):

php vendor/bin/phpunit -c vendor/omnibase/legal/phpunit.xml.dist

omnisense/omnibase-harness has no omnibase/office: its test legal errs on Base\Office\Entity\Area. With the checkouts of omnibase/office and omnibase/consulting on the harness's autoloader and no kernel, the suite on this checkout gives:

Tests: 141, Assertions: 472, Errors: 8.

The eight errors are Practice\OfficeAudienceTest's, which needs the host kernel's App\Entity\User aliases.

What the tests check