Updated the documentation, to be in line with the new architecture, and

unwritten conventions.

Author: McUsr

Docs/technical/namingconventions.md

@@ -18,8 +18,9 @@ conventions, used thoughout the system.
 
 see folder structure.
 
-* Naming conventions for dropin delegates/executionors.
+* Naming conventions used by dropin delegates/executionors.
 
+* Naming conventions for scripts of various kinds
 
 ## Periodic backup destination folder structure
 
@@ -252,6 +253,14 @@ whether it is a local dropin folder or the general dropin
 folder must have exactly the same name.
 
 
+##  Naming conventions for scripts of various kinds
+
+Routines that are commands and meant to be used from the cli
+doesn't end in `.sh`. Scripts that are intendend to be
+executed/sourced by other scripts and not by people,
+**ends** in `.sh`.
+
+
 ## Customizability of the variables, kinds, and schemes
 
 ### The FB literal name for the root of your backup repo can be changed.
@@ -283,5 +292,5 @@ break the scripts.
 
 They are hardcoded into the scripts as kinds as described above.
 
-  Last updated:23-02-02 18:59
+  Last updated:23-02-03 11:26
 

Docs/technical/systemsoverview.md

@@ -14,15 +14,16 @@ three tiers of classes of  routines
 ### The tiers of routines 
 
 
-### Governor class:
+### Executive class:
 
 The service triggered routine is named `governor.sh` and serves
-all periodic backups.
+all periodic backups. it is triggered -- normally -- by a
+service.
 
 The user triggered routine are named `fbctl` and
 `fbinstall`.
 
-### Manager
+### Manager class
 
 The user triggered commands at this level are `fbrestore` and
 `fbsnapshot`, since those are slightly deviating from the rest of
@@ -31,14 +32,16 @@ the naming schemes.
 the managers basically takes care of finding which delegate
 to run.
 
-### the agent/delegate/executioner
+### the agent/delegate class
 
 The delegates are the low level workers, their job is also
 to figure out if there are any exclude files involved.
 
+exclude files are of no use to `fbrestore`
 
 
 
 
-  Last updated:23-02-02 23:14
+
+  Last updated:23-02-03 11:20
 

Docs/technical/termsandjargon.md

@@ -43,18 +43,23 @@ minimize ambiguity and confusion.
 --->
 
 * **Container**. A **Container** for backups.
-  The `TIME_STAMPED_BACKUP_CONTAINING_FOLDER`: the folder
-	containing backups from that date onwards, depending on
-	the **scheme**.
+The `TIME_STAMPED_BACKUP_CONTAINING_FOLDER`: the folder
+containing backups from that date onwards, depending on
+the **scheme**.
 
-* **Delegate** The actual executionor of the job, whether
-	the job is performed on behalf of a manager?, called by the
-	governor, or by a fbsnapshot.
+* **Delegate** A class of scripts that actually performs a backup
+operation, whether it is taking a backup, or restoring a
+backup. The **delegate** is chosen by the  *manager*,
+called by an  *executive*.
+
+* **Executioner** See: *delegate*. 
+
+* **Executive** The script that controls a *job*, calls the
+*manager* if need be that dispatches the correct *delegate*.
+An executive is the top level layer of all the routines that
+works on the the system, the user commands, and the scripts
+that gets called by the services.
 
-* **Executioner** It's the *delegate*, that performs the
-	actual job, on the behalf of the **Governor**, that
-	qualifies and selects what to be done, and then gets the
-	**Executioner** to do it.
 
 * **Full-symlink-name** The **full-symlink-name** is a
 	*transformation of the full path to the target of the
@@ -80,6 +85,10 @@ minimize ambiguity and confusion.
 * **KIND** (Backup kind.) Denotes if it is a `OneShot` or a
 	`Periodical` backup kind.
 
+* **Manager** The manager, is the single script for all
+*jobs*/executives that gets sourced in, and chooses which
+delegate to choose.
+
 
 * **snapshot** This word has two different meanings. 
   I use it for a full backup at a given point in time, as to
@@ -144,5 +153,5 @@ minimize ambiguity and confusion.
 
 	* Monthly a `calendar-intervalled` backup.
 
-  Last updated:23-02-02 16:32
+  Last updated:23-02-03 11:20