I may be overengineering this.

Training-RFC

Training RFC
############

import rfc2119

The training
============

The training process
---------------------
1. An `excersise plan` MUST be commited as `start commit`.

2. `excersise` MUST be performed acording to the `excersise plan`

2.1. In case of `muscle failure` occurence, the `excersise` MUST be treated as
`failed excersise`

2.2. When `repetition number` is reached, the `excersise` MUST be treated as
`completed excersise`

2.3. When `failed excersise` or `completed excersise` occurs, next `excersise`
in the `round queue` MUST be started in `reasonable time`.

3. At the end of the training an `end commit` is to be commited

Properties
----------
By definition of `start commit` and `end commit`, the duration of training can
be obtained by::

    end_commit.datetime - start_commit.datetime

Reasonable time
================
TBD

Excersise
=========

Failed excersise
----------------
Failed excersise MUST NOT continue and `repetition number` and `round number`
at which `muscle failure` occured MUST be logged in h2 "muscle failures"

Completed excersise
-------------------
Good job, keep going!

excersise plan
--------------
Excersise plan MUST define:

1. date h1 "YYYY-MM-DD HH:mm". "mm" part MAY be arbitrarily rounded to nearest
value of 00, 15, 30 or 45.

2. `round definition`

2.1. Performing lower ammount of repetitions is allowed only in case of `muscle
failure`

2.1. Performing higher ammount of repetitions is never

3. h1 `field series-target`

4. The h1 section MAY define further arbitrary `fields` defining arbitrary
data, like environment or personal conditions. The fields SHOULD be
retrospectively formalized in the future.

Muscle faliure
==============
TBD


Round
=====
TBD

Round definition
-----------------
Round definition is ordered list of `excersises` and `repetition number` that
SHOULD be reached for each `excersise`.

.. FIXME:

Rounds are also known as series in this document.

Round queue
-----------
TBD

Commit
------

start commit
------------
String "start" MUST be used as the commit message.

Excersise MUST be started at the commit time, thus making the commit datetime
the precise excerise start time.

end commit
----------
String "end" MUST be used as the commit message.

`End commit` MUST be committed immediately after `The training`, thus making
the commit datetime the `excersise` end time.

MUST contain h1 field `field completed-series`

Reformatting commit
-------------------
TBD

field
======

field completed-series
----------------------

Defines the number of series performed, regardless of wheter the `round`
contained `failed excersise`

.. FIXME: unclear wording


field series-target
-------------------
Defines the number of series planned to be performed.

TODO & Issues
=============

* Research proper terminology and adjust the `Training RFC` accordingly.

* The commits and logging are going to be challenge in a gym setting.

* Dealing with possible interference by a higher power.