Merge pull request #145 from plebhash/2025-07-18-jd-clarifications

JD clarifications

Author: GitGab19

06-Job-Declaration-Protocol.md

@@ -16,8 +16,7 @@ It is responsible for:
 - Allocating tokens that JDC will use to declare Custom Jobs.
 - Acknowledging declaration of Custom Jobs associated with specific allocated tokens.
 - Maintaining an internal mempool (via RPCs (or similar) to a Bitcoin Node).
-- Requesting identification for transactions on some declared Custom Job.
-- Requesting missing transactions on some declared Custom Job.
+- Requesting missing transactions on some declared Custom Job (only under Full-Template mode).
 - Publishing valid block submissions received from JDC.
 
 ## 6.2 Job Declarator Client
@@ -41,7 +40,7 @@ Additionally, if:
 
 JDC is also responsible for switching to a new Pool+JDS (or solo mining as a last resort).
 
-This fallback strategy incentivizes honesty on Pool side, otherwise it will lose hashrate by rejecting Shares for a Custom Job that was already acknowledged to be valid.
+This fallback strategy incentivizes honesty on Pool side, otherwise it will lose hashrate by rejecting Shares for a Custom Job that was already acknowledged to be valid. It also allows the miner to never stop mining on their preferred templates.
 
 ## 6.3 Job Declaration Modes