Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
4ff7fb9
chore: consistency fixes, new chapters, PDF generator and refactor plan
kohutovic Aug 8, 2026
e215dff
refactor: rename chapters to canonical reading order, fix links and a…
kohutovic Aug 8, 2026
5b5e40c
refactor(general): subsection headings, promote universal forbidden a…
kohutovic Aug 8, 2026
ece6762
refactor: single canonical home for bout parameters, equipment checks…
kohutovic Aug 8, 2026
08229d5
fix(language): repair broken definitions, grammar errors and misleadi…
kohutovic Aug 8, 2026
44cbaae
style: normative verb convention (must/may/should) and Use of Languag…
kohutovic Aug 8, 2026
3cca1fd
style: singular they, role nouns instead of pronouns, plain register …
kohutovic Aug 8, 2026
925cb5d
style: canonical terminology, glossary entries for core scoring terms…
kohutovic Aug 8, 2026
3a449bc
style: fix hit-limit/point-limit inconsistency and intro stutter from…
kohutovic Aug 8, 2026
b06d7d8
feat: global article numbering with chapter prefixes, precise cross-r…
kohutovic Aug 8, 2026
e2e9325
refactor(penalties): pure markdown tables with filled ART. column and…
kohutovic Aug 8, 2026
49a5892
feat: summary tables for bout parameters, weapon parameters and equip…
kohutovic Aug 8, 2026
5dfccd6
feat: worked examples, Note convention, weapon overview and referee q…
kohutovic Aug 9, 2026
937605f
chore: cover new appendices in convention check
kohutovic Aug 9, 2026
bda5896
feat: version, curated changelog, title page version and open content…
kohutovic Aug 9, 2026
a5b9b61
fix: remove broken title-matching fallback in TOC page-number lookup
kohutovic Aug 9, 2026
83d8068
fix: PDF-internal appendix links, British spelling remnants and final…
kohutovic Aug 9, 2026
13064c6
style(intro): condense Use of Language section to two paragraphs
kohutovic Aug 9, 2026
fe070b3
refactor: move summary tables from core chapters to Weapon Overview a…
kohutovic Aug 9, 2026
18417af
style(appendix): checkmark icons instead of 'required' in equipment c…
kohutovic Aug 9, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,9 @@
**/.idea
**/.idea/**
CLAUDE.md
.DS_Store
venv/
febus_rulebook.pdf
febus_logo_old.png
original_febus_rules.pdf
rules.pdf
38 changes: 38 additions & 0 deletions .learnings/ERRORS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# Errors

## [ERR-20260728-001] docx_xml_text_replacement

**Logged**: 2026-07-28T00:00:00+02:00
**Priority**: low
**Status**: resolved
**Area**: docs

### Summary
Exact DOCX XML replacement failed because the closing quotation mark in the Word file differed from the Markdown source.

### Error

```text
RuntimeError: Expected one occurrence, found 0: Zriaďuje sa Rozhodcovská komisia (ďalej „Komisia") ako odborný orgán FEBUS pre rozhodcovskú agendu.
```

### Context

- The updater validates every original passage before rewriting the DOCX archive.
- The failed validation prevented any modification of the Word file.

### Suggested Fix

Inspect the exact paragraph text extracted from `word/document.xml`, update the expected source string, and rerun the all-or-nothing replacement.

### Metadata

- Reproducible: yes
- Related Files: FEBUS_smernica_o_rozhodcoch_navrh.docx, .tmp_update_directive_docx.py

### Resolution

- **Resolved**: 2026-07-28T00:00:00+02:00
- **Notes**: Matched the XML-escaped quotation mark and the separately formatted bold text run; all 20 replacements then completed atomically.

---
22 changes: 18 additions & 4 deletions 01-intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,24 @@
The goal of this event is to assess fencing in a safe and friendly manner on the principle of 'to
touch without being touched'. In common with historical rule-sets, competitions are explicitly an
abstracted test of skill, and not a simulation of an unregulated combat “to the finish” – in this
sense, we shall regard each individual point as a separate "duel" within the framework of the
sense, each individual point is regarded as a separate "duel" within the framework of the
following rules, the loss of which is indicated by having a point called against the losing fencer.
Our intention is to determine the relative ranking, and the best fencer among the competitors
present on the days of the competitions, in terms of tactical, technical, and athletic skills.
Our intention is to determine the relative ranking, and the best fencer present on the days of
the competitions, in terms of tactical, technical, and athletic skills.

One of the principles which stand above all others is the principle of fair play. Every functional
ruleset should be efficient in providing equal opportunities for every tournament contestant.
ruleset should be efficient in providing equal opportunities for every tournament fencer.

## Use of Language

In this Rulebook, **must** and **must not** state binding requirements,
**may** grants a permission, and **should** gives a non-binding
recommendation. Terms in *italics* are defined in the
[Glossary](appendices/01-glossary.md); blocks marked **Note:** or
**Example:** only illustrate the rules and contain no requirements.

Rules are numbered with a chapter prefix (E = Equipment, G = General,
RoW = Right of Way, LS = Longsword, R = Rapier, S = Sabre, SB = Sword &
Buckler, O = Organisational, D = Disciplinary) and are cited by these
identifiers, e.g. "G.16" or "RoW.12(a)". Once assigned, an identifier
never changes.
239 changes: 122 additions & 117 deletions 02-equipment.md

Large diffs are not rendered by default.

348 changes: 198 additions & 150 deletions 03-general.md

Large diffs are not rendered by default.

61 changes: 0 additions & 61 deletions 04-longsword.md

This file was deleted.

120 changes: 120 additions & 0 deletions 04-right-of-way.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,120 @@
# Right of Way and Priority Rules

## General Principles

**RoW.1** The Referee alone decides as to the validity or the priority (right of way, historically *Vor*) of the hit by applying the following basic rules which are the conventions applicable to priority-based weapons (longsword and sabre).

**RoW.2** Any attack properly executed must be parried, or completely avoided, and the phrase must be continuous.

**RoW.3** Priority rules are used to resolve double hits when both fencers are hit within one period of fencing time.

## Attack Definition and Requirements

**RoW.4** The attack is correctly carried out when the straightening of the arm, with the point or the edge continuously threatening the valid target, precedes the initiation of the footwork action.

**RoW.5** An attack with a lunge (or other offensive footwork) is correctly carried out:

- a) in a simple attack when the beginning of the straightening of the arms precedes the launching of the lunge or other offensive footwork, and the hit arrives at the latest when the front foot hits the ground
- b) in a compound attack when the beginning of the straightening of the arms, on the first feint, precedes the launching of the lunge or other offensive footwork, and the hit arrives at the latest when the front foot hits the ground.

**RoW.6** Attacks with step-forward-lunge or other compound footwork are not defined in this rulebook. Priority is assigned based on the start of the (attack with) lunge other simple offensive footwork, while steps in any case are considered as preparations.

**RoW.7** Actions, simple or compound, steps or feints, which are executed with bent arms, are not considered as attacks but as preparations, laying themselves open to the initiation of the offensive or defensive/offensive action of the opponent. Hits received from attacks/counterattacks initiated during these actions are counted as valid and score a point against the preparing fencer.

## Fencing Actions and Priority

For definitions of fencing actions (attack, feint, compound attack, counterattack, riposte, remise, etc.), see [Glossary](appendices/01-glossary.md).

Priority assignment for specific actions:
- **Attacks** gain priority when properly executed with blade commitment
- **Blade commitment requirement** - Priority is not given for pure footwork without blade commitment or actions not demonstrating forward commitment of blade
- **Ripostes** gain priority when immediate and simple after a parry
- **Counterattacks** cannot be assigned priority
- **Remise** can only gain priority if the defender's riposte was clearly and significantly delayed

## Attack Validity Rules

**RoW.8** **Point-in-line situations**: If the attack is initiated when the opponent has their point passively in line, the attacker must first deflect the opponent's weapon. Referees must ensure that a mere contact of the blades is not considered as sufficient to deflect the opponent's blade.

**RoW.9** **Failed blade finding**: If, when attempting to find the opponent's blade to deflect it, the blade is not found, the right of attack passes to the opponent.

**RoW.10** **Attack completion**: If the attack is commenced when the opponent's blade is not in line, the attack may be completed either direct, or by a disengagement or by a cutover, or else be preceded by feints which oblige the opponent to parry.

**RoW.11** **Stop-hits in compound attacks**: In a compound attack the opponent has the right to stop-hit; but, in order to be valid, the stop-hit must precede the last movement of the attack by one period of fencing time, i.e. the stop-hit must arrive before the attacker has started the last movement of the attack itself.

## Parry and Riposte

**RoW.12** The parry - properly carried out - gives the right to riposte; a simple riposte may be direct or indirect, but in order to annul any subsequent movement by the attacker, it must be carried out immediately, *without any hesitation or pause*. However, if the riposte is delayed so that a renewed attack clearly starts before the riposte, then the renewed attack gains priority.

**RoW.13** Against thrusts, and cuts with the edge, the flat, or the back edge of the blade, the object of the parry is to prevent hits made by the opponent arriving on the valid target; therefore:

- a) The parry is properly carried out when, before the completion of the attack, it prevents the arrival of that attack by closing the line in which that attack is to finish.
- b) When a parry is properly executed, the attack by the opponent must be declared parried, and judged as such by the Referee, even if, as a result of its flexibility, the tip of the opponent's weapon makes contact with the target.

> **Example:** A attacks; B parries successfully but pauses before riposting.
> A immediately renews the attack and hits while B's delayed riposte also
> lands. → A scores: the delayed riposte lost priority.

## Priority Assignment in Double Hits

**RoW.14** Priority rules are only used in assessing double hits. If there is a delay of a fencing time or more between hits, the fencer who landed first is assessed to have scored.

**RoW.15** Priority rules are only used when one fencer can be clearly assessed to have made a mistake.

### The fencer who is attacked is alone counted as hit:

**RoW.16** if they make a counter-attack against the opponent's simple attack

**RoW.17** if, instead of parrying, they attempt to avoid the hit and do not succeed in doing so

**RoW.18** if, after making a successful parry, they make a momentary pause (delayed riposte) which gives the opponent the right to renew the attack (redoublement, or remise, or reprise)

**RoW.19** if, during a compound attack, they make a stop-hit without being in time

**RoW.20** if, having their point 'in line' and being subjected to a beat or a taking of the blade which deflects their blade, they attack or place their point in line again instead of parrying a direct hit made by the opponent

> **Example:** A attacks with a straight thrust, the arm extending before the
> lunge. B counterattacks to the arm without parrying; both hits land within
> one fencing time. → A alone scores: a counterattack into a simple attack
> loses.

> **Example:** A makes a compound attack (feint, then disengage). B stop-hits,
> but the stop-hit lands only as A starts the final movement. → The stop-hit
> is not in time; A alone scores.

### The fencer who attacks is alone counted as hit:

**RoW.21** If they initiated their attack when the opponent's point was 'in line', without deflecting the opponent's weapon. Referees must ensure that a mere contact of the blades is not considered as sufficient to deflect the opponent's blade.

**RoW.22** If they attempt to find the blade, do not succeed (due to the opponent's avoiding reaction) and continue the attack.

**RoW.23** If, during a compound attack, they allow the opponent to find the blade, and continue the attack while the opponent ripostes immediately.

**RoW.24** If, during a compound attack, they bend their arm or make a momentary pause, during which time the opponent makes a stop-hit or an attack while the attacker continues their own attack.

**RoW.25** If, during a compound attack, they are stop-hit one period of fencing time before they make the final movement of the attack.

**RoW.26** If they make a hit by a renewed attack following a parry by the opponent which has been followed by a riposte which is immediate, simple and executed in one period of fencing time without withdrawing the arm.

> **Example:** B stands with the point in line before A starts attacking. A
> attacks without deflecting B's blade and both fencers are hit. → B alone
> scores: A had to take the blade first.

> **Example:** A attacks; B parries and ripostes immediately with a simple
> direct riposte. A renews the attack (remise) and both hits land. → B alone
> scores: a remise against an immediate simple riposte loses.

### Both fencers are at fault (no points awarded)

**RoW.27** Similar conception and execution of the same action by both fencers at once, without either of them taking the initiative sooner than the other.

**RoW.28** Similar failure to initiate or execute the appropriate actions, of both fencers at the same time, resulting in the loss of priority gained by previous actions, and without any of the fencers taking the initiative sooner than the other afterwards.

**RoW.29** When both fencers are at fault, NO POINTS are awarded to either fencer.


## Weapon-Specific Variations

See individual weapon rules for specific applications and variations of these priority principles:
- [Longsword specific applications](05-longsword.md)
- [Sabre specific applications](07-sabre.md)
64 changes: 64 additions & 0 deletions 05-longsword.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
# Longsword competitions

## Rules of hit validity and fencing actions

**LS.1** All hits made with the true edge, the false edge, and the tip of the blade are valid if they are
performed in such a way that it would have caused a wound to an unarmoured opponent, had the
weapon been sharp. Hits performed with the flat may be counted, if they bear the characteristics
of a coordinated and potent technique. A strike with the pommel against the front mesh of the
opponent's mask is also a valid hit (see [G.33](03-general.md) — pommel strike). It is
up to the Referee’s discretion to judge the validity of hits.

**LS.2** Hits through the blade, that is to say those which bend over the opponent’s blade or cross-guard,
are not considered to be valid. However, the Referee may count a hit as valid, if the opponent’s
blade has not closed the line of the attack, and it touches at the same time the valid target and
the weapon of the opponent, whenever they arrive clearly on the target.

**LS.3** The target includes the whole of the fencer’s body, including the handle of the weapon, clothing,
and safety equipment, except for the back of the head, spine, groin, the feet, and the back of
the knees.


## Priority

Longsword uses the standard priority (right of way, historically *Vor*) system. See [Right of Way and Priority Rules](04-right-of-way.md) for detailed priority conventions and examples.

## Close quarter combat

**LS.4** Priority ceases to exist when the weapons of the opponents come together at *Stercke* on
*Stercke* (including the cross-guard), and/or in case of grappling actions. In case the weapons
touch *Stercke* on *Stercke*, and a double hit follows immediately, no points are awarded.
Otherwise, they may disengage and continue fencing (with priority rules), or enter
grappling (with grappling rules).

## Judging of hits

**LS.5** When during a phrase both fencers are hit within a period of fencing time there is either a
simultaneous action or a double hit:

- a) The simultaneous action is due to simultaneous conception and execution of an attack by both
fencers; in this case no points are awarded.
- b) A double hit, on the other hand, occurs when there is no interval of fencing time between the
hits and it is the result of a clearly faulty action on the part of one of the fencers, as
defined by these rules.

**LS.6** When there is a double hit, and if the Referee is unable clearly to judge from which side the
fault has come, the Referee must not assign any points.

**LS.7** In cases when a stop-hit is made and there is doubt as to whether it was made sufficiently in
time in relation to the final movement of a compound attack, the double hit often occurs through
the fault of both fencers concerned. Since this is clearly not a tactically symmetrical case,
the Referee should assign no points.

> **Note:** The fault of the attacker typically consists of indecision, slow execution, or
> insufficiently effective feints; the fault of the defender lies in a delayed or slow stop-hit.

**LS.8** Any actions executed while holding the weapon with one hand only, can only score if the fencer
does not receive any attack or counterattack with a weapon held with two hands, within one
period of fencing time.

**LS.9** However if the opponent reacts to the attack with a weapon held in one hand with an attempt to
parry, an unsuccessful parry returns the priority to the one-handed hit.

**LS.10** In cases when both fencers get hit with a weapon held in one hand within time, the judgment of
the action follows the regular priority rules.
Loading