docs/english #1

Merged
administrator merged 3 commits from docs/english into main 2026-10-27 18:21:48 +00:00
No description provided.
README.md, CONVENTION.md and CHANGELOG.md. A reader who cannot read French
cannot reuse this kit, which is the argument the kit itself makes about comments
and had not applied to itself.

HISTORY IS NOT REWRITTEN. The three tagged releases stay as they were written:
one does not rewrite three published versions to change their language. The rule
applies from here on, and the translation is a commit.

NOTHING OF SUBSTANCE CHANGED, deliberately, so that this reads as a translation
and nothing else. Every measured figure, every limit and every admission is kept
as it stood. Three things are wrong in the text and stay wrong here, to be fixed
where they belong:

  - the clone URL says dataseeds/infra-conventions; the repository lives at
    shared/infra-conventions
  - the Getting started section explains how to publish the kit, which is done
  - CONVENTION.md section 12 says an agent proposes and Nico approves, which
    names a person where a role belongs, and points at a handle the forge does
    not resolve: GET /api/v1/users/nico answers 404

WHAT IS DELIBERATELY NOT TOUCHED: MAPPING.md and
modules/naming/tests/cases.tftest.hcl are GENERATED, and make check runs their
generator then git diff --exit-code. Translating either by hand turns a green
check red. Their French lives in registry/capabilities.yaml and in
tools/naming.py, and it travels with a regeneration.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
registry/capabilities.yaml and the strings of tools/naming.py that build
MAPPING.md from it. The generated file follows, regenerated rather than edited:
make check runs the generator then refuses a diff, so a hand-translated
MAPPING.md would have turned that check red.

ONLY THE VALUES WERE TOUCHED, never a key, a slug or a capability id. The 165
strings were extracted, translated and reinjected by a script on the three
fields that carry prose - category, label, notes - so the structure could not be
damaged in transcription. 97 capabilities before, 97 after, and the YAML still
parses.

THE reuse VALUES MOVED TOO, and they are the one place where a translation
reaches data. jamais, 37 jours, 30 jours, 7 jours become never, 37 days and so
on. They are NOT part of the naming grammar - no name carries them - so this
changes no name and owes no major version; but they are read in three places
that had to move together: the registry, reuse_text in tools/naming.py, and the
policy test that asserts the warning mentions them.

What still speaks French and is deliberately left for its own commit: the
messages of policy/naming.rego, the registry comments, the adoption guides and
the module.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
fix: the reuse values had two more readers than the sweep found
Some checks failed
ci / check (pull_request) Has been cancelled
4ae9213915
make check went red twice after the previous commit, and both times it named a
reader that a grep had missed.

A SECOND POLICY ASSERTION cited a different value. The sweep had looked for
"jamais" and corrected the one assertion that used it; another case asserted
the warning mentions "7 jours", and no search for the first word would ever
have reached it.

AND AN EXPECTED FIXTURE CARRIED THE WHOLE MESSAGE.
policy/fixtures/plan_gcp_violations.expected.yaml holds the policy's output
verbatim, interpolated value included, and it is compared byte for byte.

Neither was visible in the diff, and neither would have been found by reading.
They were found by running the kit's own suite, which became possible on this
machine today - the devcontainer had no python3, so the previous rounds of this
translation could only be done blind.

make check is green end to end: 66 module tests, 48 policy tests, 11 reference
plans, and the two generated files regenerated from their source and identical
to what is committed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
administrator deleted branch docs/english 2026-10-27 18:21:48 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
shared/infra-conventions!1
No description provided.