| 001 |
French & Indian War |
1753 Ohio Country mission — diagnostic frame Washington journal / French and Indian War materials |
French and Indian War reconnaissance |
Washington’s mission to the French in the Ohio Country as reconnaissance, diplomacy, and route intelligence. Layer: Frame the case as a decision problem rather than a story. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the 1753 Ohio Country mission problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS02 · Intelligence consumer triage |
| 002 |
French & Indian War |
1753 Ohio Country mission — source-quality pass Washington journal / French and Indian War materials |
French and Indian War reconnaissance |
Washington’s mission to the French in the Ohio Country as reconnaissance, diplomacy, and route intelligence. Layer: Separate access, motive, freshness, and corroboration. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the 1753 Ohio Country mission report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 003 |
French & Indian War |
1753 Ohio Country mission — routing and authority pass Washington journal / French and Indian War materials |
French and Indian War reconnaissance |
Washington’s mission to the French in the Ohio Country as reconnaissance, diplomacy, and route intelligence. Layer: Identify who should receive, authorize, or constrain the next step. |
- What habits survived into Revolutionary command?
- What terrain and route knowledge did the young officer need?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the 1753 Ohio Country mission information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 004 |
French & Indian War |
1753 Ohio Country mission — risk and failure-mode pass Washington journal / French and Indian War materials |
French and Indian War reconnaissance |
Washington’s mission to the French in the Ohio Country as reconnaissance, diplomacy, and route intelligence. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the 1753 Ohio Country mission case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 005 |
French & Indian War |
1753 Ohio Country mission — artifact and legacy pass Washington journal / French and Indian War materials |
French and Indian War reconnaissance |
Washington’s mission to the French in the Ohio Country as reconnaissance, diplomacy, and route intelligence. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the 1753 Ohio Country mission episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 006 |
French & Indian War |
Frontier road and river observations — diagnostic frame Mount Vernon / Washington early military record |
French and Indian War reconnaissance |
Roads, rivers, forts, weather, and distance as an early intelligence vocabulary. Layer: Frame the case as a decision problem rather than a story. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Frontier road and river observations problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS02 · Intelligence consumer triage |
| 007 |
French & Indian War |
Frontier road and river observations — source-quality pass Mount Vernon / Washington early military record |
French and Indian War reconnaissance |
Roads, rivers, forts, weather, and distance as an early intelligence vocabulary. Layer: Separate access, motive, freshness, and corroboration. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Frontier road and river observations report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 008 |
French & Indian War |
Frontier road and river observations — routing and authority pass Mount Vernon / Washington early military record |
French and Indian War reconnaissance |
Roads, rivers, forts, weather, and distance as an early intelligence vocabulary. Layer: Identify who should receive, authorize, or constrain the next step. |
- What habits survived into Revolutionary command?
- What terrain and route knowledge did the young officer need?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Frontier road and river observations information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 009 |
French & Indian War |
Frontier road and river observations — risk and failure-mode pass Mount Vernon / Washington early military record |
French and Indian War reconnaissance |
Roads, rivers, forts, weather, and distance as an early intelligence vocabulary. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Frontier road and river observations case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 010 |
French & Indian War |
Frontier road and river observations — artifact and legacy pass Mount Vernon / Washington early military record |
French and Indian War reconnaissance |
Roads, rivers, forts, weather, and distance as an early intelligence vocabulary. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Frontier road and river observations episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 011 |
French & Indian War |
Fort Necessity information fragility — diagnostic frame French and Indian War case literature |
French and Indian War reconnaissance |
The cost of imperfect terrain knowledge, adversary intention estimates, and coalition misunderstanding. Layer: Frame the case as a decision problem rather than a story. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Fort Necessity information fragility problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS02 · Intelligence consumer triage |
| 012 |
French & Indian War |
Fort Necessity information fragility — source-quality pass French and Indian War case literature |
French and Indian War reconnaissance |
The cost of imperfect terrain knowledge, adversary intention estimates, and coalition misunderstanding. Layer: Separate access, motive, freshness, and corroboration. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Fort Necessity information fragility report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 013 |
French & Indian War |
Fort Necessity information fragility — routing and authority pass French and Indian War case literature |
French and Indian War reconnaissance |
The cost of imperfect terrain knowledge, adversary intention estimates, and coalition misunderstanding. Layer: Identify who should receive, authorize, or constrain the next step. |
- What habits survived into Revolutionary command?
- What terrain and route knowledge did the young officer need?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Fort Necessity information fragility information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 014 |
French & Indian War |
Fort Necessity information fragility — risk and failure-mode pass French and Indian War case literature |
French and Indian War reconnaissance |
The cost of imperfect terrain knowledge, adversary intention estimates, and coalition misunderstanding. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Fort Necessity information fragility case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 015 |
French & Indian War |
Fort Necessity information fragility — artifact and legacy pass French and Indian War case literature |
French and Indian War reconnaissance |
The cost of imperfect terrain knowledge, adversary intention estimates, and coalition misunderstanding. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Fort Necessity information fragility episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 016 |
French & Indian War |
Braddock campaign terrain lesson — diagnostic frame campaign history / Washington papers |
French and Indian War reconnaissance |
How conventional confidence can fail when terrain and local warning are underweighted. Layer: Frame the case as a decision problem rather than a story. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Braddock campaign terrain lesson problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS02 · Intelligence consumer triage |
| 017 |
French & Indian War |
Braddock campaign terrain lesson — source-quality pass campaign history / Washington papers |
French and Indian War reconnaissance |
How conventional confidence can fail when terrain and local warning are underweighted. Layer: Separate access, motive, freshness, and corroboration. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Braddock campaign terrain lesson report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 018 |
French & Indian War |
Braddock campaign terrain lesson — routing and authority pass campaign history / Washington papers |
French and Indian War reconnaissance |
How conventional confidence can fail when terrain and local warning are underweighted. Layer: Identify who should receive, authorize, or constrain the next step. |
- What habits survived into Revolutionary command?
- What terrain and route knowledge did the young officer need?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Braddock campaign terrain lesson information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 019 |
French & Indian War |
Braddock campaign terrain lesson — risk and failure-mode pass campaign history / Washington papers |
French and Indian War reconnaissance |
How conventional confidence can fail when terrain and local warning are underweighted. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Braddock campaign terrain lesson case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 020 |
French & Indian War |
Braddock campaign terrain lesson — artifact and legacy pass campaign history / Washington papers |
French and Indian War reconnaissance |
How conventional confidence can fail when terrain and local warning are underweighted. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Braddock campaign terrain lesson episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 021 |
French & Indian War |
Frontier militia warning networks — diagnostic frame Washington military correspondence |
French and Indian War reconnaissance |
Local warning, settlement vulnerability, and reporting routes during frontier command. Layer: Frame the case as a decision problem rather than a story. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Frontier militia warning networks problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS02 · Intelligence consumer triage |
| 022 |
French & Indian War |
Frontier militia warning networks — source-quality pass Washington military correspondence |
French and Indian War reconnaissance |
Local warning, settlement vulnerability, and reporting routes during frontier command. Layer: Separate access, motive, freshness, and corroboration. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Frontier militia warning networks report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 023 |
French & Indian War |
Frontier militia warning networks — routing and authority pass Washington military correspondence |
French and Indian War reconnaissance |
Local warning, settlement vulnerability, and reporting routes during frontier command. Layer: Identify who should receive, authorize, or constrain the next step. |
- What habits survived into Revolutionary command?
- What terrain and route knowledge did the young officer need?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Frontier militia warning networks information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 024 |
French & Indian War |
Frontier militia warning networks — risk and failure-mode pass Washington military correspondence |
French and Indian War reconnaissance |
Local warning, settlement vulnerability, and reporting routes during frontier command. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What terrain and route knowledge did the young officer need?
- Which observation could be converted into military intelligence?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Frontier militia warning networks case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 025 |
French & Indian War |
Frontier militia warning networks — artifact and legacy pass Washington military correspondence |
French and Indian War reconnaissance |
Local warning, settlement vulnerability, and reporting routes during frontier command. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which observation could be converted into military intelligence?
- What habits survived into Revolutionary command?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Frontier militia warning networks episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS03 · Map-terrain correspondenceS04 · Local knowledge integrationS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 026 |
French & Indian War |
Early cipher and correspondence habit — diagnostic frame Mount Vernon espionage tactics |
Secret funds, rewards, and correspondence |
Washington’s early exposure to coded correspondence and the need to protect wartime letters. Layer: Frame the case as a decision problem rather than a story. |
- What payment or letter was necessary?
- How could secrecy and accounting coexist?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Early cipher and correspondence habit problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 027 |
French & Indian War |
Early cipher and correspondence habit — source-quality pass Mount Vernon espionage tactics |
Secret funds, rewards, and correspondence |
Washington’s early exposure to coded correspondence and the need to protect wartime letters. Layer: Separate access, motive, freshness, and corroboration. |
- How could secrecy and accounting coexist?
- What would later reconstruction require?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Early cipher and correspondence habit report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 028 |
French & Indian War |
Early cipher and correspondence habit — routing and authority pass Mount Vernon espionage tactics |
Secret funds, rewards, and correspondence |
Washington’s early exposure to coded correspondence and the need to protect wartime letters. Layer: Identify who should receive, authorize, or constrain the next step. |
- What would later reconstruction require?
- What payment or letter was necessary?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Early cipher and correspondence habit information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 029 |
French & Indian War |
Early cipher and correspondence habit — risk and failure-mode pass Mount Vernon espionage tactics |
Secret funds, rewards, and correspondence |
Washington’s early exposure to coded correspondence and the need to protect wartime letters. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What payment or letter was necessary?
- How could secrecy and accounting coexist?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Early cipher and correspondence habit case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 030 |
French & Indian War |
Early cipher and correspondence habit — artifact and legacy pass Mount Vernon espionage tactics |
Secret funds, rewards, and correspondence |
Washington’s early exposure to coded correspondence and the need to protect wartime letters. Layer: Convert the case into a record, checklist, or institutional lesson. |
- How could secrecy and accounting coexist?
- What would later reconstruction require?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Early cipher and correspondence habit episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 031 |
Revolutionary War |
Boston siege disposition reports — diagnostic frame Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
The first commander-in-chief problem: understand enemy positions around Boston under scarcity. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Boston siege disposition reports problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 032 |
Revolutionary War |
Boston siege disposition reports — source-quality pass Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
The first commander-in-chief problem: understand enemy positions around Boston under scarcity. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Boston siege disposition reports report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 033 |
Revolutionary War |
Boston siege disposition reports — routing and authority pass Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
The first commander-in-chief problem: understand enemy positions around Boston under scarcity. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Boston siege disposition reports information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 034 |
Revolutionary War |
Boston siege disposition reports — risk and failure-mode pass Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
The first commander-in-chief problem: understand enemy positions around Boston under scarcity. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Boston siege disposition reports case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 035 |
Revolutionary War |
Boston siege disposition reports — artifact and legacy pass Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
The first commander-in-chief problem: understand enemy positions around Boston under scarcity. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Boston siege disposition reports episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 036 |
Revolutionary War |
Cambridge headquarters report triage — diagnostic frame Library of Congress Washington Papers |
Continental Army strategic intelligence |
Headquarters as a filter for militia reports, civilian warnings, and strategic uncertainty. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Cambridge headquarters report triage problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 037 |
Revolutionary War |
Cambridge headquarters report triage — source-quality pass Library of Congress Washington Papers |
Continental Army strategic intelligence |
Headquarters as a filter for militia reports, civilian warnings, and strategic uncertainty. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Cambridge headquarters report triage report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 038 |
Revolutionary War |
Cambridge headquarters report triage — routing and authority pass Library of Congress Washington Papers |
Continental Army strategic intelligence |
Headquarters as a filter for militia reports, civilian warnings, and strategic uncertainty. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Cambridge headquarters report triage information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 039 |
Revolutionary War |
Cambridge headquarters report triage — risk and failure-mode pass Library of Congress Washington Papers |
Continental Army strategic intelligence |
Headquarters as a filter for militia reports, civilian warnings, and strategic uncertainty. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Cambridge headquarters report triage case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 040 |
Revolutionary War |
Cambridge headquarters report triage — artifact and legacy pass Library of Congress Washington Papers |
Continental Army strategic intelligence |
Headquarters as a filter for militia reports, civilian warnings, and strategic uncertainty. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Cambridge headquarters report triage episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 041 |
Revolutionary War |
Congressional confidentiality loop — diagnostic frame Washington Papers / Continental Congress context |
Civil-military governance and legitimacy |
Keeping Congress informed while protecting sensitive movements and sources. Layer: Frame the case as a decision problem rather than a story. |
- What authority bounded the action?
- Which civilians or states were affected?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Congressional confidentiality loop problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S20 · Diplomatic-military reporting loopS27 · Civilian-risk legitimacy auditS29 · Accountability and record disciplineS30 · Confidentiality versus republican legitimacyS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 042 |
Revolutionary War |
Congressional confidentiality loop — source-quality pass Washington Papers / Continental Congress context |
Civil-military governance and legitimacy |
Keeping Congress informed while protecting sensitive movements and sources. Layer: Separate access, motive, freshness, and corroboration. |
- Which civilians or states were affected?
- What record preserved legitimacy?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Congressional confidentiality loop report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S20 · Diplomatic-military reporting loopS27 · Civilian-risk legitimacy auditS29 · Accountability and record disciplineS30 · Confidentiality versus republican legitimacyS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 043 |
Revolutionary War |
Congressional confidentiality loop — routing and authority pass Washington Papers / Continental Congress context |
Civil-military governance and legitimacy |
Keeping Congress informed while protecting sensitive movements and sources. Layer: Identify who should receive, authorize, or constrain the next step. |
- What record preserved legitimacy?
- What authority bounded the action?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Congressional confidentiality loop information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S20 · Diplomatic-military reporting loopS27 · Civilian-risk legitimacy auditS29 · Accountability and record disciplineS30 · Confidentiality versus republican legitimacy |
| 044 |
Revolutionary War |
Congressional confidentiality loop — risk and failure-mode pass Washington Papers / Continental Congress context |
Civil-military governance and legitimacy |
Keeping Congress informed while protecting sensitive movements and sources. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What authority bounded the action?
- Which civilians or states were affected?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Congressional confidentiality loop case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S20 · Diplomatic-military reporting loopS27 · Civilian-risk legitimacy auditS29 · Accountability and record disciplineS30 · Confidentiality versus republican legitimacyS16 · Double-agent and legend caution |
| 045 |
Revolutionary War |
Congressional confidentiality loop — artifact and legacy pass Washington Papers / Continental Congress context |
Civil-military governance and legitimacy |
Keeping Congress informed while protecting sensitive movements and sources. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which civilians or states were affected?
- What record preserved legitimacy?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Congressional confidentiality loop episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S20 · Diplomatic-military reporting loopS27 · Civilian-risk legitimacy auditS29 · Accountability and record disciplineS30 · Confidentiality versus republican legitimacyS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 046 |
Revolutionary War |
New York defense intelligence gap — diagnostic frame Revolutionary War campaign histories |
Continental Army strategic intelligence |
The difficulty of defending New York without sufficient enemy intention and landing intelligence. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the New York defense intelligence gap problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 047 |
Revolutionary War |
New York defense intelligence gap — source-quality pass Revolutionary War campaign histories |
Continental Army strategic intelligence |
The difficulty of defending New York without sufficient enemy intention and landing intelligence. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the New York defense intelligence gap report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 048 |
Revolutionary War |
New York defense intelligence gap — routing and authority pass Revolutionary War campaign histories |
Continental Army strategic intelligence |
The difficulty of defending New York without sufficient enemy intention and landing intelligence. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the New York defense intelligence gap information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 049 |
Revolutionary War |
New York defense intelligence gap — risk and failure-mode pass Revolutionary War campaign histories |
Continental Army strategic intelligence |
The difficulty of defending New York without sufficient enemy intention and landing intelligence. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the New York defense intelligence gap case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 050 |
Revolutionary War |
New York defense intelligence gap — artifact and legacy pass Revolutionary War campaign histories |
Continental Army strategic intelligence |
The difficulty of defending New York without sufficient enemy intention and landing intelligence. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the New York defense intelligence gap episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 051 |
Revolutionary War |
Long Island under-scouting lesson — diagnostic frame Long Island campaign histories |
Continental Army strategic intelligence |
A failure-mode case: routes, flanking movement, and the danger of incomplete reconnaissance. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Long Island under-scouting lesson problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 052 |
Revolutionary War |
Long Island under-scouting lesson — source-quality pass Long Island campaign histories |
Continental Army strategic intelligence |
A failure-mode case: routes, flanking movement, and the danger of incomplete reconnaissance. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Long Island under-scouting lesson report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 053 |
Revolutionary War |
Long Island under-scouting lesson — routing and authority pass Long Island campaign histories |
Continental Army strategic intelligence |
A failure-mode case: routes, flanking movement, and the danger of incomplete reconnaissance. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Long Island under-scouting lesson information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 054 |
Revolutionary War |
Long Island under-scouting lesson — risk and failure-mode pass Long Island campaign histories |
Continental Army strategic intelligence |
A failure-mode case: routes, flanking movement, and the danger of incomplete reconnaissance. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Long Island under-scouting lesson case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 055 |
Revolutionary War |
Long Island under-scouting lesson — artifact and legacy pass Long Island campaign histories |
Continental Army strategic intelligence |
A failure-mode case: routes, flanking movement, and the danger of incomplete reconnaissance. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Long Island under-scouting lesson episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 056 |
Revolutionary War |
Nathan Hale failure as caution — diagnostic frame Mount Vernon American spies of the Revolution |
Counterintelligence and betrayal |
Hale’s death as a caution about access, cover, route, and command expectations. Layer: Frame the case as a decision problem rather than a story. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Nathan Hale failure as caution problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 057 |
Revolutionary War |
Nathan Hale failure as caution — source-quality pass Mount Vernon American spies of the Revolution |
Counterintelligence and betrayal |
Hale’s death as a caution about access, cover, route, and command expectations. Layer: Separate access, motive, freshness, and corroboration. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Nathan Hale failure as caution report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS10 · Enemy disposition requirement |
| 058 |
Revolutionary War |
Nathan Hale failure as caution — routing and authority pass Mount Vernon American spies of the Revolution |
Counterintelligence and betrayal |
Hale’s death as a caution about access, cover, route, and command expectations. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should damage be contained?
- Who might be compromised?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Nathan Hale failure as caution information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 059 |
Revolutionary War |
Nathan Hale failure as caution — risk and failure-mode pass Mount Vernon American spies of the Revolution |
Counterintelligence and betrayal |
Hale’s death as a caution about access, cover, route, and command expectations. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Nathan Hale failure as caution case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS27 · Civilian-risk legitimacy audit |
| 060 |
Revolutionary War |
Nathan Hale failure as caution — artifact and legacy pass Mount Vernon American spies of the Revolution |
Counterintelligence and betrayal |
Hale’s death as a caution about access, cover, route, and command expectations. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Nathan Hale failure as caution episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 061 |
Revolutionary War |
Harlem Heights confidence recovery — diagnostic frame Washington campaign correspondence |
Continental Army strategic intelligence |
Using limited tactical intelligence and morale cues after a strategic retreat. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Harlem Heights confidence recovery problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 062 |
Revolutionary War |
Harlem Heights confidence recovery — source-quality pass Washington campaign correspondence |
Continental Army strategic intelligence |
Using limited tactical intelligence and morale cues after a strategic retreat. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Harlem Heights confidence recovery report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 063 |
Revolutionary War |
Harlem Heights confidence recovery — routing and authority pass Washington campaign correspondence |
Continental Army strategic intelligence |
Using limited tactical intelligence and morale cues after a strategic retreat. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Harlem Heights confidence recovery information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 064 |
Revolutionary War |
Harlem Heights confidence recovery — risk and failure-mode pass Washington campaign correspondence |
Continental Army strategic intelligence |
Using limited tactical intelligence and morale cues after a strategic retreat. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Harlem Heights confidence recovery case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 065 |
Revolutionary War |
Harlem Heights confidence recovery — artifact and legacy pass Washington campaign correspondence |
Continental Army strategic intelligence |
Using limited tactical intelligence and morale cues after a strategic retreat. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Harlem Heights confidence recovery episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 066 |
Revolutionary War |
Trenton strike threshold — diagnostic frame Washington Papers / Trenton campaign |
Strategic deception and surprise |
A case in acting under uncertainty when surprise, timing, weather, and enemy posture align. Layer: Frame the case as a decision problem rather than a story. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Trenton strike threshold problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 067 |
Revolutionary War |
Trenton strike threshold — source-quality pass Washington Papers / Trenton campaign |
Strategic deception and surprise |
A case in acting under uncertainty when surprise, timing, weather, and enemy posture align. Layer: Separate access, motive, freshness, and corroboration. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Trenton strike threshold report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 068 |
Revolutionary War |
Trenton strike threshold — routing and authority pass Washington Papers / Trenton campaign |
Strategic deception and surprise |
A case in acting under uncertainty when surprise, timing, weather, and enemy posture align. Layer: Identify who should receive, authorize, or constrain the next step. |
- Which timing window mattered?
- What did the enemy believe?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Trenton strike threshold information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 069 |
Revolutionary War |
Trenton strike threshold — risk and failure-mode pass Washington Papers / Trenton campaign |
Strategic deception and surprise |
A case in acting under uncertainty when surprise, timing, weather, and enemy posture align. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Trenton strike threshold case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 070 |
Revolutionary War |
Trenton strike threshold — artifact and legacy pass Washington Papers / Trenton campaign |
Strategic deception and surprise |
A case in acting under uncertainty when surprise, timing, weather, and enemy posture align. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Trenton strike threshold episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 071 |
Revolutionary War |
Princeton movement concealment — diagnostic frame campaign history / Washington correspondence |
Strategic deception and surprise |
Movement after Trenton as a case in enemy expectation management. Layer: Frame the case as a decision problem rather than a story. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Princeton movement concealment problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 072 |
Revolutionary War |
Princeton movement concealment — source-quality pass campaign history / Washington correspondence |
Strategic deception and surprise |
Movement after Trenton as a case in enemy expectation management. Layer: Separate access, motive, freshness, and corroboration. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Princeton movement concealment report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 073 |
Revolutionary War |
Princeton movement concealment — routing and authority pass campaign history / Washington correspondence |
Strategic deception and surprise |
Movement after Trenton as a case in enemy expectation management. Layer: Identify who should receive, authorize, or constrain the next step. |
- Which timing window mattered?
- What did the enemy believe?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Princeton movement concealment information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 074 |
Revolutionary War |
Princeton movement concealment — risk and failure-mode pass campaign history / Washington correspondence |
Strategic deception and surprise |
Movement after Trenton as a case in enemy expectation management. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Princeton movement concealment case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 075 |
Revolutionary War |
Princeton movement concealment — artifact and legacy pass campaign history / Washington correspondence |
Strategic deception and surprise |
Movement after Trenton as a case in enemy expectation management. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Princeton movement concealment episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 076 |
Revolutionary War |
Forage War local reporting — diagnostic frame New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Forage, patrols, militia knowledge, and local reporting as strategic pressure indicators. Layer: Frame the case as a decision problem rather than a story. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Forage War local reporting problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 077 |
Revolutionary War |
Forage War local reporting — source-quality pass New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Forage, patrols, militia knowledge, and local reporting as strategic pressure indicators. Layer: Separate access, motive, freshness, and corroboration. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Forage War local reporting report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 078 |
Revolutionary War |
Forage War local reporting — routing and authority pass New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Forage, patrols, militia knowledge, and local reporting as strategic pressure indicators. Layer: Identify who should receive, authorize, or constrain the next step. |
- What indicator was time-sensitive?
- Which ship, road, tide, or supply movement mattered?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Forage War local reporting information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 079 |
Revolutionary War |
Forage War local reporting — risk and failure-mode pass New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Forage, patrols, militia knowledge, and local reporting as strategic pressure indicators. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Forage War local reporting case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 080 |
Revolutionary War |
Forage War local reporting — artifact and legacy pass New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Forage, patrols, militia knowledge, and local reporting as strategic pressure indicators. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Forage War local reporting episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 081 |
Revolutionary War |
Philadelphia campaign scouting — diagnostic frame Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
Scout reporting and strategic ambiguity during the British move toward Philadelphia. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Philadelphia campaign scouting problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 082 |
Revolutionary War |
Philadelphia campaign scouting — source-quality pass Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
Scout reporting and strategic ambiguity during the British move toward Philadelphia. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Philadelphia campaign scouting report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 083 |
Revolutionary War |
Philadelphia campaign scouting — routing and authority pass Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
Scout reporting and strategic ambiguity during the British move toward Philadelphia. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Philadelphia campaign scouting information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 084 |
Revolutionary War |
Philadelphia campaign scouting — risk and failure-mode pass Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
Scout reporting and strategic ambiguity during the British move toward Philadelphia. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Philadelphia campaign scouting case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 085 |
Revolutionary War |
Philadelphia campaign scouting — artifact and legacy pass Washington Revolutionary War correspondence |
Continental Army strategic intelligence |
Scout reporting and strategic ambiguity during the British move toward Philadelphia. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Philadelphia campaign scouting episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 086 |
Revolutionary War |
Brandywine flank warning — diagnostic frame campaign histories / Washington papers |
Continental Army strategic intelligence |
A failure-mode case in interpreting contradictory flank reports. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Brandywine flank warning problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 087 |
Revolutionary War |
Brandywine flank warning — source-quality pass campaign histories / Washington papers |
Continental Army strategic intelligence |
A failure-mode case in interpreting contradictory flank reports. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Brandywine flank warning report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 088 |
Revolutionary War |
Brandywine flank warning — routing and authority pass campaign histories / Washington papers |
Continental Army strategic intelligence |
A failure-mode case in interpreting contradictory flank reports. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Brandywine flank warning information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 089 |
Revolutionary War |
Brandywine flank warning — risk and failure-mode pass campaign histories / Washington papers |
Continental Army strategic intelligence |
A failure-mode case in interpreting contradictory flank reports. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Brandywine flank warning case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 090 |
Revolutionary War |
Brandywine flank warning — artifact and legacy pass campaign histories / Washington papers |
Continental Army strategic intelligence |
A failure-mode case in interpreting contradictory flank reports. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Brandywine flank warning episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 091 |
Revolutionary War |
Germantown fog and friction — diagnostic frame campaign histories |
Strategic deception and surprise |
Battlefield uncertainty, visibility, and intelligence limits in a complex attack. Layer: Frame the case as a decision problem rather than a story. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Germantown fog and friction problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 092 |
Revolutionary War |
Germantown fog and friction — source-quality pass campaign histories |
Strategic deception and surprise |
Battlefield uncertainty, visibility, and intelligence limits in a complex attack. Layer: Separate access, motive, freshness, and corroboration. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Germantown fog and friction report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 093 |
Revolutionary War |
Germantown fog and friction — routing and authority pass campaign histories |
Strategic deception and surprise |
Battlefield uncertainty, visibility, and intelligence limits in a complex attack. Layer: Identify who should receive, authorize, or constrain the next step. |
- Which timing window mattered?
- What did the enemy believe?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Germantown fog and friction information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 094 |
Revolutionary War |
Germantown fog and friction — risk and failure-mode pass campaign histories |
Strategic deception and surprise |
Battlefield uncertainty, visibility, and intelligence limits in a complex attack. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Germantown fog and friction case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 095 |
Revolutionary War |
Germantown fog and friction — artifact and legacy pass campaign histories |
Strategic deception and surprise |
Battlefield uncertainty, visibility, and intelligence limits in a complex attack. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Germantown fog and friction episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 096 |
Revolutionary War |
Valley Forge winter intelligence — diagnostic frame Washington Papers / winter quarters |
Maritime, coastal, and logistics indicators |
Even in winter hardship, patrol, supply, and British movement reports remained essential. Layer: Frame the case as a decision problem rather than a story. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Valley Forge winter intelligence problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 097 |
Revolutionary War |
Valley Forge winter intelligence — source-quality pass Washington Papers / winter quarters |
Maritime, coastal, and logistics indicators |
Even in winter hardship, patrol, supply, and British movement reports remained essential. Layer: Separate access, motive, freshness, and corroboration. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Valley Forge winter intelligence report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 098 |
Revolutionary War |
Valley Forge winter intelligence — routing and authority pass Washington Papers / winter quarters |
Maritime, coastal, and logistics indicators |
Even in winter hardship, patrol, supply, and British movement reports remained essential. Layer: Identify who should receive, authorize, or constrain the next step. |
- What indicator was time-sensitive?
- Which ship, road, tide, or supply movement mattered?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Valley Forge winter intelligence information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 099 |
Revolutionary War |
Valley Forge winter intelligence — risk and failure-mode pass Washington Papers / winter quarters |
Maritime, coastal, and logistics indicators |
Even in winter hardship, patrol, supply, and British movement reports remained essential. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Valley Forge winter intelligence case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 100 |
Revolutionary War |
Valley Forge winter intelligence — artifact and legacy pass Washington Papers / winter quarters |
Maritime, coastal, and logistics indicators |
Even in winter hardship, patrol, supply, and British movement reports remained essential. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Valley Forge winter intelligence episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 101 |
Revolutionary War |
Monmouth enemy-movement cueing — diagnostic frame Washington correspondence / Monmouth campaign |
Continental Army strategic intelligence |
Using movement reports to decide pursuit and engagement after British evacuation. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Monmouth enemy-movement cueing problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 102 |
Revolutionary War |
Monmouth enemy-movement cueing — source-quality pass Washington correspondence / Monmouth campaign |
Continental Army strategic intelligence |
Using movement reports to decide pursuit and engagement after British evacuation. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Monmouth enemy-movement cueing report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 103 |
Revolutionary War |
Monmouth enemy-movement cueing — routing and authority pass Washington correspondence / Monmouth campaign |
Continental Army strategic intelligence |
Using movement reports to decide pursuit and engagement after British evacuation. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Monmouth enemy-movement cueing information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 104 |
Revolutionary War |
Monmouth enemy-movement cueing — risk and failure-mode pass Washington correspondence / Monmouth campaign |
Continental Army strategic intelligence |
Using movement reports to decide pursuit and engagement after British evacuation. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Monmouth enemy-movement cueing case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 105 |
Revolutionary War |
Monmouth enemy-movement cueing — artifact and legacy pass Washington correspondence / Monmouth campaign |
Continental Army strategic intelligence |
Using movement reports to decide pursuit and engagement after British evacuation. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Monmouth enemy-movement cueing episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 106 |
Revolutionary War |
British-occupied New York as target — diagnostic frame Mount Vernon Culper Ring |
British-occupied city networks |
New York as British headquarters and the central problem for persistent reporting. Layer: Frame the case as a decision problem rather than a story. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the British-occupied New York as target problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 107 |
Revolutionary War |
British-occupied New York as target — source-quality pass Mount Vernon Culper Ring |
British-occupied city networks |
New York as British headquarters and the central problem for persistent reporting. Layer: Separate access, motive, freshness, and corroboration. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the British-occupied New York as target report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticism |
| 108 |
Revolutionary War |
British-occupied New York as target — routing and authority pass Mount Vernon Culper Ring |
British-occupied city networks |
New York as British headquarters and the central problem for persistent reporting. Layer: Identify who should receive, authorize, or constrain the next step. |
- How could reports reach headquarters?
- What could only be learned from an occupied urban environment?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the British-occupied New York as target information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 109 |
Revolutionary War |
British-occupied New York as target — risk and failure-mode pass Mount Vernon Culper Ring |
British-occupied city networks |
New York as British headquarters and the central problem for persistent reporting. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the British-occupied New York as target case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 110 |
Revolutionary War |
British-occupied New York as target — artifact and legacy pass Mount Vernon Culper Ring |
British-occupied city networks |
New York as British headquarters and the central problem for persistent reporting. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the British-occupied New York as target episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 111 |
Culper / New York |
Tallmadge appointment — diagnostic frame Mount Vernon Spying and Espionage |
Culper and managed spy-ring reporting |
Washington’s appointment of Benjamin Tallmadge to organize New York intelligence. Layer: Frame the case as a decision problem rather than a story. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Tallmadge appointment problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 112 |
Culper / New York |
Tallmadge appointment — source-quality pass Mount Vernon Spying and Espionage |
Culper and managed spy-ring reporting |
Washington’s appointment of Benjamin Tallmadge to organize New York intelligence. Layer: Separate access, motive, freshness, and corroboration. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Tallmadge appointment report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 113 |
Culper / New York |
Tallmadge appointment — routing and authority pass Mount Vernon Spying and Espionage |
Culper and managed spy-ring reporting |
Washington’s appointment of Benjamin Tallmadge to organize New York intelligence. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should headquarters validate the stream?
- What requirement justified a standing network?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Tallmadge appointment information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 114 |
Culper / New York |
Tallmadge appointment — risk and failure-mode pass Mount Vernon Spying and Espionage |
Culper and managed spy-ring reporting |
Washington’s appointment of Benjamin Tallmadge to organize New York intelligence. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Tallmadge appointment case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 115 |
Culper / New York |
Tallmadge appointment — artifact and legacy pass Mount Vernon Spying and Espionage |
Culper and managed spy-ring reporting |
Washington’s appointment of Benjamin Tallmadge to organize New York intelligence. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Tallmadge appointment episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 116 |
Culper / New York |
Culper alias governance — diagnostic frame Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
Aliases and numbered references as identity-protection governance. Layer: Frame the case as a decision problem rather than a story. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Culper alias governance problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 117 |
Culper / New York |
Culper alias governance — source-quality pass Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
Aliases and numbered references as identity-protection governance. Layer: Separate access, motive, freshness, and corroboration. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Culper alias governance report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 118 |
Culper / New York |
Culper alias governance — routing and authority pass Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
Aliases and numbered references as identity-protection governance. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should headquarters validate the stream?
- What requirement justified a standing network?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Culper alias governance information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 119 |
Culper / New York |
Culper alias governance — risk and failure-mode pass Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
Aliases and numbered references as identity-protection governance. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Culper alias governance case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 120 |
Culper / New York |
Culper alias governance — artifact and legacy pass Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
Aliases and numbered references as identity-protection governance. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Culper alias governance episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 121 |
Culper / New York |
Culper codebook discipline — diagnostic frame Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
The codebook as a record of structured secrecy rather than improvisation. Layer: Frame the case as a decision problem rather than a story. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Culper codebook discipline problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 122 |
Culper / New York |
Culper codebook discipline — source-quality pass Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
The codebook as a record of structured secrecy rather than improvisation. Layer: Separate access, motive, freshness, and corroboration. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Culper codebook discipline report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 123 |
Culper / New York |
Culper codebook discipline — routing and authority pass Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
The codebook as a record of structured secrecy rather than improvisation. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should headquarters validate the stream?
- What requirement justified a standing network?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Culper codebook discipline information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 124 |
Culper / New York |
Culper codebook discipline — risk and failure-mode pass Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
The codebook as a record of structured secrecy rather than improvisation. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Culper codebook discipline case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 125 |
Culper / New York |
Culper codebook discipline — artifact and legacy pass Mount Vernon Culper Code Book |
Culper and managed spy-ring reporting |
The codebook as a record of structured secrecy rather than improvisation. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Culper codebook discipline episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 126 |
Culper / New York |
Abraham Woodhull reliability strain — diagnostic frame Culper histories / Washington correspondence |
Culper and managed spy-ring reporting |
Risk, fatigue, access, and report quality in a standing human network. Layer: Frame the case as a decision problem rather than a story. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Abraham Woodhull reliability strain problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 127 |
Culper / New York |
Abraham Woodhull reliability strain — source-quality pass Culper histories / Washington correspondence |
Culper and managed spy-ring reporting |
Risk, fatigue, access, and report quality in a standing human network. Layer: Separate access, motive, freshness, and corroboration. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Abraham Woodhull reliability strain report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 128 |
Culper / New York |
Abraham Woodhull reliability strain — routing and authority pass Culper histories / Washington correspondence |
Culper and managed spy-ring reporting |
Risk, fatigue, access, and report quality in a standing human network. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should headquarters validate the stream?
- What requirement justified a standing network?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Abraham Woodhull reliability strain information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 129 |
Culper / New York |
Abraham Woodhull reliability strain — risk and failure-mode pass Culper histories / Washington correspondence |
Culper and managed spy-ring reporting |
Risk, fatigue, access, and report quality in a standing human network. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Abraham Woodhull reliability strain case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 130 |
Culper / New York |
Abraham Woodhull reliability strain — artifact and legacy pass Culper histories / Washington correspondence |
Culper and managed spy-ring reporting |
Risk, fatigue, access, and report quality in a standing human network. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Abraham Woodhull reliability strain episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 131 |
Culper / New York |
Robert Townsend Manhattan access — diagnostic frame Mount Vernon / Culper histories |
British-occupied city networks |
Using commercial and social access to read British-occupied Manhattan. Layer: Frame the case as a decision problem rather than a story. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Robert Townsend Manhattan access problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 132 |
Culper / New York |
Robert Townsend Manhattan access — source-quality pass Mount Vernon / Culper histories |
British-occupied city networks |
Using commercial and social access to read British-occupied Manhattan. Layer: Separate access, motive, freshness, and corroboration. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Robert Townsend Manhattan access report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticism |
| 133 |
Culper / New York |
Robert Townsend Manhattan access — routing and authority pass Mount Vernon / Culper histories |
British-occupied city networks |
Using commercial and social access to read British-occupied Manhattan. Layer: Identify who should receive, authorize, or constrain the next step. |
- How could reports reach headquarters?
- What could only be learned from an occupied urban environment?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Robert Townsend Manhattan access information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 134 |
Culper / New York |
Robert Townsend Manhattan access — risk and failure-mode pass Mount Vernon / Culper histories |
British-occupied city networks |
Using commercial and social access to read British-occupied Manhattan. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Robert Townsend Manhattan access case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 135 |
Culper / New York |
Robert Townsend Manhattan access — artifact and legacy pass Mount Vernon / Culper histories |
British-occupied city networks |
Using commercial and social access to read British-occupied Manhattan. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Robert Townsend Manhattan access episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 136 |
Culper / New York |
Austin Roe courier route — diagnostic frame Culper histories |
Culper and managed spy-ring reporting |
Courier movement as both lifeline and vulnerability. Layer: Frame the case as a decision problem rather than a story. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Austin Roe courier route problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 137 |
Culper / New York |
Austin Roe courier route — source-quality pass Culper histories |
Culper and managed spy-ring reporting |
Courier movement as both lifeline and vulnerability. Layer: Separate access, motive, freshness, and corroboration. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Austin Roe courier route report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 138 |
Culper / New York |
Austin Roe courier route — routing and authority pass Culper histories |
Culper and managed spy-ring reporting |
Courier movement as both lifeline and vulnerability. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should headquarters validate the stream?
- What requirement justified a standing network?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Austin Roe courier route information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 139 |
Culper / New York |
Austin Roe courier route — risk and failure-mode pass Culper histories |
Culper and managed spy-ring reporting |
Courier movement as both lifeline and vulnerability. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Austin Roe courier route case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 140 |
Culper / New York |
Austin Roe courier route — artifact and legacy pass Culper histories |
Culper and managed spy-ring reporting |
Courier movement as both lifeline and vulnerability. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Austin Roe courier route episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 141 |
Culper / New York |
Caleb Brewster maritime link — diagnostic frame Culper histories / coastal reporting |
Maritime, coastal, and logistics indicators |
Boat movement and coastal passage as part of the intelligence chain. Layer: Frame the case as a decision problem rather than a story. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Caleb Brewster maritime link problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 142 |
Culper / New York |
Caleb Brewster maritime link — source-quality pass Culper histories / coastal reporting |
Maritime, coastal, and logistics indicators |
Boat movement and coastal passage as part of the intelligence chain. Layer: Separate access, motive, freshness, and corroboration. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Caleb Brewster maritime link report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 143 |
Culper / New York |
Caleb Brewster maritime link — routing and authority pass Culper histories / coastal reporting |
Maritime, coastal, and logistics indicators |
Boat movement and coastal passage as part of the intelligence chain. Layer: Identify who should receive, authorize, or constrain the next step. |
- What indicator was time-sensitive?
- Which ship, road, tide, or supply movement mattered?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Caleb Brewster maritime link information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 144 |
Culper / New York |
Caleb Brewster maritime link — risk and failure-mode pass Culper histories / coastal reporting |
Maritime, coastal, and logistics indicators |
Boat movement and coastal passage as part of the intelligence chain. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Caleb Brewster maritime link case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 145 |
Culper / New York |
Caleb Brewster maritime link — artifact and legacy pass Culper histories / coastal reporting |
Maritime, coastal, and logistics indicators |
Boat movement and coastal passage as part of the intelligence chain. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Caleb Brewster maritime link episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 146 |
Culper / New York |
British troop movement stream — diagnostic frame Mount Vernon Culper Ring |
Culper and managed spy-ring reporting |
Regular reporting on British troop movement as the network’s core deliverable. Layer: Frame the case as a decision problem rather than a story. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the British troop movement stream problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 147 |
Culper / New York |
British troop movement stream — source-quality pass Mount Vernon Culper Ring |
Culper and managed spy-ring reporting |
Regular reporting on British troop movement as the network’s core deliverable. Layer: Separate access, motive, freshness, and corroboration. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the British troop movement stream report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 148 |
Culper / New York |
British troop movement stream — routing and authority pass Mount Vernon Culper Ring |
Culper and managed spy-ring reporting |
Regular reporting on British troop movement as the network’s core deliverable. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should headquarters validate the stream?
- What requirement justified a standing network?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the British troop movement stream information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 149 |
Culper / New York |
British troop movement stream — risk and failure-mode pass Mount Vernon Culper Ring |
Culper and managed spy-ring reporting |
Regular reporting on British troop movement as the network’s core deliverable. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the British troop movement stream case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 150 |
Culper / New York |
British troop movement stream — artifact and legacy pass Mount Vernon Culper Ring |
Culper and managed spy-ring reporting |
Regular reporting on British troop movement as the network’s core deliverable. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the British troop movement stream episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 151 |
Revolutionary War |
British naval movement stream — diagnostic frame Culper / Revolutionary maritime sources |
Maritime, coastal, and logistics indicators |
Naval signals, embarkation rumors, and harbor activity as campaign indicators. Layer: Frame the case as a decision problem rather than a story. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the British naval movement stream problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 152 |
Revolutionary War |
British naval movement stream — source-quality pass Culper / Revolutionary maritime sources |
Maritime, coastal, and logistics indicators |
Naval signals, embarkation rumors, and harbor activity as campaign indicators. Layer: Separate access, motive, freshness, and corroboration. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the British naval movement stream report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 153 |
Revolutionary War |
British naval movement stream — routing and authority pass Culper / Revolutionary maritime sources |
Maritime, coastal, and logistics indicators |
Naval signals, embarkation rumors, and harbor activity as campaign indicators. Layer: Identify who should receive, authorize, or constrain the next step. |
- What indicator was time-sensitive?
- Which ship, road, tide, or supply movement mattered?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the British naval movement stream information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 154 |
Revolutionary War |
British naval movement stream — risk and failure-mode pass Culper / Revolutionary maritime sources |
Maritime, coastal, and logistics indicators |
Naval signals, embarkation rumors, and harbor activity as campaign indicators. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the British naval movement stream case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 155 |
Revolutionary War |
British naval movement stream — artifact and legacy pass Culper / Revolutionary maritime sources |
Maritime, coastal, and logistics indicators |
Naval signals, embarkation rumors, and harbor activity as campaign indicators. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the British naval movement stream episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 156 |
Revolutionary War |
Loyalist social network mapping — diagnostic frame New York occupation histories |
British-occupied city networks |
Loyalist ties, clubs, shops, officers, and merchants as the city’s intelligence topology. Layer: Frame the case as a decision problem rather than a story. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Loyalist social network mapping problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 157 |
Revolutionary War |
Loyalist social network mapping — source-quality pass New York occupation histories |
British-occupied city networks |
Loyalist ties, clubs, shops, officers, and merchants as the city’s intelligence topology. Layer: Separate access, motive, freshness, and corroboration. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Loyalist social network mapping report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticism |
| 158 |
Revolutionary War |
Loyalist social network mapping — routing and authority pass New York occupation histories |
British-occupied city networks |
Loyalist ties, clubs, shops, officers, and merchants as the city’s intelligence topology. Layer: Identify who should receive, authorize, or constrain the next step. |
- How could reports reach headquarters?
- What could only be learned from an occupied urban environment?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Loyalist social network mapping information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 159 |
Revolutionary War |
Loyalist social network mapping — risk and failure-mode pass New York occupation histories |
British-occupied city networks |
Loyalist ties, clubs, shops, officers, and merchants as the city’s intelligence topology. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Loyalist social network mapping case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 160 |
Revolutionary War |
Loyalist social network mapping — artifact and legacy pass New York occupation histories |
British-occupied city networks |
Loyalist ties, clubs, shops, officers, and merchants as the city’s intelligence topology. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Loyalist social network mapping episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 161 |
Revolutionary War |
Mersereau network comparison — diagnostic frame DIA Washington letters / regional spy networks |
British-occupied city networks |
Comparing parallel networks to avoid single-stream dependence. Layer: Frame the case as a decision problem rather than a story. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Mersereau network comparison problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 162 |
Revolutionary War |
Mersereau network comparison — source-quality pass DIA Washington letters / regional spy networks |
British-occupied city networks |
Comparing parallel networks to avoid single-stream dependence. Layer: Separate access, motive, freshness, and corroboration. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Mersereau network comparison report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticism |
| 163 |
Revolutionary War |
Mersereau network comparison — routing and authority pass DIA Washington letters / regional spy networks |
British-occupied city networks |
Comparing parallel networks to avoid single-stream dependence. Layer: Identify who should receive, authorize, or constrain the next step. |
- How could reports reach headquarters?
- What could only be learned from an occupied urban environment?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Mersereau network comparison information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 164 |
Revolutionary War |
Mersereau network comparison — risk and failure-mode pass DIA Washington letters / regional spy networks |
British-occupied city networks |
Comparing parallel networks to avoid single-stream dependence. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Mersereau network comparison case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 165 |
Revolutionary War |
Mersereau network comparison — artifact and legacy pass DIA Washington letters / regional spy networks |
British-occupied city networks |
Comparing parallel networks to avoid single-stream dependence. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Mersereau network comparison episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 166 |
Revolutionary War |
Cross-Hudson scouting lane — diagnostic frame Washington letters / regional campaigns |
Maritime, coastal, and logistics indicators |
Scouting and local observation across the Hudson corridor. Layer: Frame the case as a decision problem rather than a story. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Cross-Hudson scouting lane problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 167 |
Revolutionary War |
Cross-Hudson scouting lane — source-quality pass Washington letters / regional campaigns |
Maritime, coastal, and logistics indicators |
Scouting and local observation across the Hudson corridor. Layer: Separate access, motive, freshness, and corroboration. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Cross-Hudson scouting lane report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 168 |
Revolutionary War |
Cross-Hudson scouting lane — routing and authority pass Washington letters / regional campaigns |
Maritime, coastal, and logistics indicators |
Scouting and local observation across the Hudson corridor. Layer: Identify who should receive, authorize, or constrain the next step. |
- What indicator was time-sensitive?
- Which ship, road, tide, or supply movement mattered?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Cross-Hudson scouting lane information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 169 |
Revolutionary War |
Cross-Hudson scouting lane — risk and failure-mode pass Washington letters / regional campaigns |
Maritime, coastal, and logistics indicators |
Scouting and local observation across the Hudson corridor. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Cross-Hudson scouting lane case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 170 |
Revolutionary War |
Cross-Hudson scouting lane — artifact and legacy pass Washington letters / regional campaigns |
Maritime, coastal, and logistics indicators |
Scouting and local observation across the Hudson corridor. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Cross-Hudson scouting lane episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 171 |
Revolutionary War |
James Jay invisible-ink governance — diagnostic frame Mount Vernon spy techniques |
Secret funds, rewards, and correspondence |
Use of secret writing as a correspondence-protection problem, not a technical recipe. Layer: Frame the case as a decision problem rather than a story. |
- What payment or letter was necessary?
- How could secrecy and accounting coexist?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the James Jay invisible-ink governance problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 172 |
Revolutionary War |
James Jay invisible-ink governance — source-quality pass Mount Vernon spy techniques |
Secret funds, rewards, and correspondence |
Use of secret writing as a correspondence-protection problem, not a technical recipe. Layer: Separate access, motive, freshness, and corroboration. |
- How could secrecy and accounting coexist?
- What would later reconstruction require?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the James Jay invisible-ink governance report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 173 |
Revolutionary War |
James Jay invisible-ink governance — routing and authority pass Mount Vernon spy techniques |
Secret funds, rewards, and correspondence |
Use of secret writing as a correspondence-protection problem, not a technical recipe. Layer: Identify who should receive, authorize, or constrain the next step. |
- What would later reconstruction require?
- What payment or letter was necessary?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the James Jay invisible-ink governance information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 174 |
Revolutionary War |
James Jay invisible-ink governance — risk and failure-mode pass Mount Vernon spy techniques |
Secret funds, rewards, and correspondence |
Use of secret writing as a correspondence-protection problem, not a technical recipe. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What payment or letter was necessary?
- How could secrecy and accounting coexist?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the James Jay invisible-ink governance case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 175 |
Revolutionary War |
James Jay invisible-ink governance — artifact and legacy pass Mount Vernon spy techniques |
Secret funds, rewards, and correspondence |
Use of secret writing as a correspondence-protection problem, not a technical recipe. Layer: Convert the case into a record, checklist, or institutional lesson. |
- How could secrecy and accounting coexist?
- What would later reconstruction require?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the James Jay invisible-ink governance episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 176 |
Revolutionary War |
Letter interception risk — diagnostic frame Washington correspondence context |
Secret funds, rewards, and correspondence |
Captured letters as a source-protection, deception, and counterintelligence problem. Layer: Frame the case as a decision problem rather than a story. |
- What payment or letter was necessary?
- How could secrecy and accounting coexist?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Letter interception risk problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 177 |
Revolutionary War |
Letter interception risk — source-quality pass Washington correspondence context |
Secret funds, rewards, and correspondence |
Captured letters as a source-protection, deception, and counterintelligence problem. Layer: Separate access, motive, freshness, and corroboration. |
- How could secrecy and accounting coexist?
- What would later reconstruction require?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Letter interception risk report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 178 |
Revolutionary War |
Letter interception risk — routing and authority pass Washington correspondence context |
Secret funds, rewards, and correspondence |
Captured letters as a source-protection, deception, and counterintelligence problem. Layer: Identify who should receive, authorize, or constrain the next step. |
- What would later reconstruction require?
- What payment or letter was necessary?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Letter interception risk information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 179 |
Revolutionary War |
Letter interception risk — risk and failure-mode pass Washington correspondence context |
Secret funds, rewards, and correspondence |
Captured letters as a source-protection, deception, and counterintelligence problem. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What payment or letter was necessary?
- How could secrecy and accounting coexist?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Letter interception risk case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 180 |
Revolutionary War |
Letter interception risk — artifact and legacy pass Washington correspondence context |
Secret funds, rewards, and correspondence |
Captured letters as a source-protection, deception, and counterintelligence problem. Layer: Convert the case into a record, checklist, or institutional lesson. |
- How could secrecy and accounting coexist?
- What would later reconstruction require?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Letter interception risk episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 181 |
Culper / New York |
Courier delay and obsolescence — diagnostic frame Culper correspondence context |
Culper and managed spy-ring reporting |
Freshness and delivery time as decisive intelligence-quality variables. Layer: Frame the case as a decision problem rather than a story. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Courier delay and obsolescence problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 182 |
Culper / New York |
Courier delay and obsolescence — source-quality pass Culper correspondence context |
Culper and managed spy-ring reporting |
Freshness and delivery time as decisive intelligence-quality variables. Layer: Separate access, motive, freshness, and corroboration. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Courier delay and obsolescence report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 183 |
Culper / New York |
Courier delay and obsolescence — routing and authority pass Culper correspondence context |
Culper and managed spy-ring reporting |
Freshness and delivery time as decisive intelligence-quality variables. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should headquarters validate the stream?
- What requirement justified a standing network?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Courier delay and obsolescence information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 184 |
Culper / New York |
Courier delay and obsolescence — risk and failure-mode pass Culper correspondence context |
Culper and managed spy-ring reporting |
Freshness and delivery time as decisive intelligence-quality variables. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What requirement justified a standing network?
- Which identity or route required protection?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Courier delay and obsolescence case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 185 |
Culper / New York |
Courier delay and obsolescence — artifact and legacy pass Culper correspondence context |
Culper and managed spy-ring reporting |
Freshness and delivery time as decisive intelligence-quality variables. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which identity or route required protection?
- How should headquarters validate the stream?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Courier delay and obsolescence episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS06 · Trusted intermediary selectionS07 · Compartmented correspondence governanceS08 · Patron-protector postureS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 186 |
Revolutionary War |
Headquarters report fusion — diagnostic frame Washington Papers |
Continental Army strategic intelligence |
Transforming reports from scouts, spies, officers, and civilians into commander judgment. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Headquarters report fusion problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 187 |
Revolutionary War |
Headquarters report fusion — source-quality pass Washington Papers |
Continental Army strategic intelligence |
Transforming reports from scouts, spies, officers, and civilians into commander judgment. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Headquarters report fusion report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 188 |
Revolutionary War |
Headquarters report fusion — routing and authority pass Washington Papers |
Continental Army strategic intelligence |
Transforming reports from scouts, spies, officers, and civilians into commander judgment. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Headquarters report fusion information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 189 |
Revolutionary War |
Headquarters report fusion — risk and failure-mode pass Washington Papers |
Continental Army strategic intelligence |
Transforming reports from scouts, spies, officers, and civilians into commander judgment. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Headquarters report fusion case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 190 |
Revolutionary War |
Headquarters report fusion — artifact and legacy pass Washington Papers |
Continental Army strategic intelligence |
Transforming reports from scouts, spies, officers, and civilians into commander judgment. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Headquarters report fusion episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 191 |
CI / betrayal |
Benedict Arnold warning signs — diagnostic frame Revolutionary War counterintelligence histories |
Counterintelligence and betrayal |
Ambition, grievance, command access, and British contact as a betrayal-risk study. Layer: Frame the case as a decision problem rather than a story. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Benedict Arnold warning signs problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 192 |
CI / betrayal |
Benedict Arnold warning signs — source-quality pass Revolutionary War counterintelligence histories |
Counterintelligence and betrayal |
Ambition, grievance, command access, and British contact as a betrayal-risk study. Layer: Separate access, motive, freshness, and corroboration. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Benedict Arnold warning signs report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS10 · Enemy disposition requirement |
| 193 |
CI / betrayal |
Benedict Arnold warning signs — routing and authority pass Revolutionary War counterintelligence histories |
Counterintelligence and betrayal |
Ambition, grievance, command access, and British contact as a betrayal-risk study. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should damage be contained?
- Who might be compromised?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Benedict Arnold warning signs information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 194 |
CI / betrayal |
Benedict Arnold warning signs — risk and failure-mode pass Revolutionary War counterintelligence histories |
Counterintelligence and betrayal |
Ambition, grievance, command access, and British contact as a betrayal-risk study. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Benedict Arnold warning signs case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS27 · Civilian-risk legitimacy audit |
| 195 |
CI / betrayal |
Benedict Arnold warning signs — artifact and legacy pass Revolutionary War counterintelligence histories |
Counterintelligence and betrayal |
Ambition, grievance, command access, and British contact as a betrayal-risk study. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Benedict Arnold warning signs episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 196 |
CI / betrayal |
Major André capture — diagnostic frame Arnold-André case histories |
Counterintelligence and betrayal |
A single capture revealing a larger compromise and forcing rapid damage control. Layer: Frame the case as a decision problem rather than a story. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Major André capture problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 197 |
CI / betrayal |
Major André capture — source-quality pass Arnold-André case histories |
Counterintelligence and betrayal |
A single capture revealing a larger compromise and forcing rapid damage control. Layer: Separate access, motive, freshness, and corroboration. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Major André capture report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS10 · Enemy disposition requirement |
| 198 |
CI / betrayal |
Major André capture — routing and authority pass Arnold-André case histories |
Counterintelligence and betrayal |
A single capture revealing a larger compromise and forcing rapid damage control. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should damage be contained?
- Who might be compromised?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Major André capture information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 199 |
CI / betrayal |
Major André capture — risk and failure-mode pass Arnold-André case histories |
Counterintelligence and betrayal |
A single capture revealing a larger compromise and forcing rapid damage control. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Major André capture case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS27 · Civilian-risk legitimacy audit |
| 200 |
CI / betrayal |
Major André capture — artifact and legacy pass Arnold-André case histories |
Counterintelligence and betrayal |
A single capture revealing a larger compromise and forcing rapid damage control. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Major André capture episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 201 |
CI / betrayal |
West Point vulnerability — diagnostic frame Arnold-André case histories |
Counterintelligence and betrayal |
A fortress as intelligence target, betrayal object, and strategic chokepoint. Layer: Frame the case as a decision problem rather than a story. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the West Point vulnerability problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 202 |
CI / betrayal |
West Point vulnerability — source-quality pass Arnold-André case histories |
Counterintelligence and betrayal |
A fortress as intelligence target, betrayal object, and strategic chokepoint. Layer: Separate access, motive, freshness, and corroboration. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the West Point vulnerability report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS10 · Enemy disposition requirement |
| 203 |
CI / betrayal |
West Point vulnerability — routing and authority pass Arnold-André case histories |
Counterintelligence and betrayal |
A fortress as intelligence target, betrayal object, and strategic chokepoint. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should damage be contained?
- Who might be compromised?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the West Point vulnerability information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 204 |
CI / betrayal |
West Point vulnerability — risk and failure-mode pass Arnold-André case histories |
Counterintelligence and betrayal |
A fortress as intelligence target, betrayal object, and strategic chokepoint. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the West Point vulnerability case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS27 · Civilian-risk legitimacy audit |
| 205 |
CI / betrayal |
West Point vulnerability — artifact and legacy pass Arnold-André case histories |
Counterintelligence and betrayal |
A fortress as intelligence target, betrayal object, and strategic chokepoint. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the West Point vulnerability episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 206 |
CI / betrayal |
Treason response and morale — diagnostic frame Washington correspondence / Arnold case |
Counterintelligence and betrayal |
Public justice, army morale, and institutional repair after betrayal. Layer: Frame the case as a decision problem rather than a story. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Treason response and morale problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 207 |
CI / betrayal |
Treason response and morale — source-quality pass Washington correspondence / Arnold case |
Counterintelligence and betrayal |
Public justice, army morale, and institutional repair after betrayal. Layer: Separate access, motive, freshness, and corroboration. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Treason response and morale report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS10 · Enemy disposition requirement |
| 208 |
CI / betrayal |
Treason response and morale — routing and authority pass Washington correspondence / Arnold case |
Counterintelligence and betrayal |
Public justice, army morale, and institutional repair after betrayal. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should damage be contained?
- Who might be compromised?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Treason response and morale information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 209 |
CI / betrayal |
Treason response and morale — risk and failure-mode pass Washington correspondence / Arnold case |
Counterintelligence and betrayal |
Public justice, army morale, and institutional repair after betrayal. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Treason response and morale case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS27 · Civilian-risk legitimacy audit |
| 210 |
CI / betrayal |
Treason response and morale — artifact and legacy pass Washington correspondence / Arnold case |
Counterintelligence and betrayal |
Public justice, army morale, and institutional repair after betrayal. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Treason response and morale episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 211 |
CI / betrayal |
Benjamin Church affair — diagnostic frame Revolutionary counterintelligence histories |
Counterintelligence and betrayal |
Early revolutionary counterintelligence: status, access, letters, and betrayal. Layer: Frame the case as a decision problem rather than a story. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Benjamin Church affair problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 212 |
CI / betrayal |
Benjamin Church affair — source-quality pass Revolutionary counterintelligence histories |
Counterintelligence and betrayal |
Early revolutionary counterintelligence: status, access, letters, and betrayal. Layer: Separate access, motive, freshness, and corroboration. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Benjamin Church affair report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS10 · Enemy disposition requirement |
| 213 |
CI / betrayal |
Benjamin Church affair — routing and authority pass Revolutionary counterintelligence histories |
Counterintelligence and betrayal |
Early revolutionary counterintelligence: status, access, letters, and betrayal. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should damage be contained?
- Who might be compromised?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Benjamin Church affair information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 214 |
CI / betrayal |
Benjamin Church affair — risk and failure-mode pass Revolutionary counterintelligence histories |
Counterintelligence and betrayal |
Early revolutionary counterintelligence: status, access, letters, and betrayal. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Benjamin Church affair case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS27 · Civilian-risk legitimacy audit |
| 215 |
CI / betrayal |
Benjamin Church affair — artifact and legacy pass Revolutionary counterintelligence histories |
Counterintelligence and betrayal |
Early revolutionary counterintelligence: status, access, letters, and betrayal. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Benjamin Church affair episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 216 |
CI / betrayal |
John Honeyman legend audit — diagnostic frame CIA Studies in Intelligence Honeyman article |
Presidential legacy and archival memory |
A cautionary case on invented or exaggerated spy legends around Trenton. Layer: Frame the case as a decision problem rather than a story. |
- What lesson moved from war to statecraft?
- Which record corrects mythology?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the John Honeyman legend audit problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 217 |
CI / betrayal |
John Honeyman legend audit — source-quality pass CIA Studies in Intelligence Honeyman article |
Presidential legacy and archival memory |
A cautionary case on invented or exaggerated spy legends around Trenton. Layer: Separate access, motive, freshness, and corroboration. |
- Which record corrects mythology?
- How should the public remember intelligence discipline?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the John Honeyman legend audit report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 218 |
CI / betrayal |
John Honeyman legend audit — routing and authority pass CIA Studies in Intelligence Honeyman article |
Presidential legacy and archival memory |
A cautionary case on invented or exaggerated spy legends around Trenton. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should the public remember intelligence discipline?
- What lesson moved from war to statecraft?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the John Honeyman legend audit information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 219 |
CI / betrayal |
John Honeyman legend audit — risk and failure-mode pass CIA Studies in Intelligence Honeyman article |
Presidential legacy and archival memory |
A cautionary case on invented or exaggerated spy legends around Trenton. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What lesson moved from war to statecraft?
- Which record corrects mythology?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the John Honeyman legend audit case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 220 |
CI / betrayal |
John Honeyman legend audit — artifact and legacy pass CIA Studies in Intelligence Honeyman article |
Presidential legacy and archival memory |
A cautionary case on invented or exaggerated spy legends around Trenton. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which record corrects mythology?
- How should the public remember intelligence discipline?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the John Honeyman legend audit episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacy |
| 221 |
Revolutionary War |
Prisoner debrief at headquarters — diagnostic frame Washington correspondence |
Prisoner, deserter, and traveler reports |
Using prisoners as information sources while controlling incentive and access bias. Layer: Frame the case as a decision problem rather than a story. |
- What did the speaker actually know?
- What incentive shaped the testimony?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Prisoner debrief at headquarters problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirementS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 222 |
Revolutionary War |
Prisoner debrief at headquarters — source-quality pass Washington correspondence |
Prisoner, deserter, and traveler reports |
Using prisoners as information sources while controlling incentive and access bias. Layer: Separate access, motive, freshness, and corroboration. |
- What incentive shaped the testimony?
- How could details be checked?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Prisoner debrief at headquarters report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirement |
| 223 |
Revolutionary War |
Prisoner debrief at headquarters — routing and authority pass Washington correspondence |
Prisoner, deserter, and traveler reports |
Using prisoners as information sources while controlling incentive and access bias. Layer: Identify who should receive, authorize, or constrain the next step. |
- How could details be checked?
- What did the speaker actually know?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Prisoner debrief at headquarters information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirementS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 224 |
Revolutionary War |
Prisoner debrief at headquarters — risk and failure-mode pass Washington correspondence |
Prisoner, deserter, and traveler reports |
Using prisoners as information sources while controlling incentive and access bias. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did the speaker actually know?
- What incentive shaped the testimony?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Prisoner debrief at headquarters case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirementS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 225 |
Revolutionary War |
Prisoner debrief at headquarters — artifact and legacy pass Washington correspondence |
Prisoner, deserter, and traveler reports |
Using prisoners as information sources while controlling incentive and access bias. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What incentive shaped the testimony?
- How could details be checked?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Prisoner debrief at headquarters episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirementS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 226 |
Revolutionary War |
Deserter claim validation — diagnostic frame Revolutionary War correspondence |
Prisoner, deserter, and traveler reports |
Deserter reports as potentially useful but bias-heavy information. Layer: Frame the case as a decision problem rather than a story. |
- What did the speaker actually know?
- What incentive shaped the testimony?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Deserter claim validation problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirementS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 227 |
Revolutionary War |
Deserter claim validation — source-quality pass Revolutionary War correspondence |
Prisoner, deserter, and traveler reports |
Deserter reports as potentially useful but bias-heavy information. Layer: Separate access, motive, freshness, and corroboration. |
- What incentive shaped the testimony?
- How could details be checked?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Deserter claim validation report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirement |
| 228 |
Revolutionary War |
Deserter claim validation — routing and authority pass Revolutionary War correspondence |
Prisoner, deserter, and traveler reports |
Deserter reports as potentially useful but bias-heavy information. Layer: Identify who should receive, authorize, or constrain the next step. |
- How could details be checked?
- What did the speaker actually know?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Deserter claim validation information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirementS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 229 |
Revolutionary War |
Deserter claim validation — risk and failure-mode pass Revolutionary War correspondence |
Prisoner, deserter, and traveler reports |
Deserter reports as potentially useful but bias-heavy information. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did the speaker actually know?
- What incentive shaped the testimony?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Deserter claim validation case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirementS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 230 |
Revolutionary War |
Deserter claim validation — artifact and legacy pass Revolutionary War correspondence |
Prisoner, deserter, and traveler reports |
Deserter reports as potentially useful but bias-heavy information. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What incentive shaped the testimony?
- How could details be checked?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Deserter claim validation episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S15 · Loyalty-screening skepticismS18 · Rumor-control and information hygieneS26 · Prisoner/deserter/debrief source critiqueS10 · Enemy disposition requirementS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 231 |
Revolutionary War |
Traveler and merchant reports — diagnostic frame Washington correspondence / occupation histories |
British-occupied city networks |
Travelers and merchants as carriers of both intelligence and rumor. Layer: Frame the case as a decision problem rather than a story. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Traveler and merchant reports problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 232 |
Revolutionary War |
Traveler and merchant reports — source-quality pass Washington correspondence / occupation histories |
British-occupied city networks |
Travelers and merchants as carriers of both intelligence and rumor. Layer: Separate access, motive, freshness, and corroboration. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Traveler and merchant reports report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticism |
| 233 |
Revolutionary War |
Traveler and merchant reports — routing and authority pass Washington correspondence / occupation histories |
British-occupied city networks |
Travelers and merchants as carriers of both intelligence and rumor. Layer: Identify who should receive, authorize, or constrain the next step. |
- How could reports reach headquarters?
- What could only be learned from an occupied urban environment?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Traveler and merchant reports information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 234 |
Revolutionary War |
Traveler and merchant reports — risk and failure-mode pass Washington correspondence / occupation histories |
British-occupied city networks |
Travelers and merchants as carriers of both intelligence and rumor. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What could only be learned from an occupied urban environment?
- Which social channel was closest to British movement?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Traveler and merchant reports case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 235 |
Revolutionary War |
Traveler and merchant reports — artifact and legacy pass Washington correspondence / occupation histories |
British-occupied city networks |
Travelers and merchants as carriers of both intelligence and rumor. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which social channel was closest to British movement?
- How could reports reach headquarters?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Traveler and merchant reports episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S05 · Delegated ring architectureS10 · Enemy disposition requirementS12 · Occupied-capital listening postS15 · Loyalty-screening skepticismS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 236 |
Revolutionary War |
Loyalist trading leakage — diagnostic frame Washington letters / New Jersey records |
Counterintelligence and betrayal |
Trade with British lines as an intelligence leak and governance problem. Layer: Frame the case as a decision problem rather than a story. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Loyalist trading leakage problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 237 |
Revolutionary War |
Loyalist trading leakage — source-quality pass Washington letters / New Jersey records |
Counterintelligence and betrayal |
Trade with British lines as an intelligence leak and governance problem. Layer: Separate access, motive, freshness, and corroboration. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Loyalist trading leakage report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS10 · Enemy disposition requirement |
| 238 |
Revolutionary War |
Loyalist trading leakage — routing and authority pass Washington letters / New Jersey records |
Counterintelligence and betrayal |
Trade with British lines as an intelligence leak and governance problem. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should damage be contained?
- Who might be compromised?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Loyalist trading leakage information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 239 |
Revolutionary War |
Loyalist trading leakage — risk and failure-mode pass Washington letters / New Jersey records |
Counterintelligence and betrayal |
Trade with British lines as an intelligence leak and governance problem. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Who might be compromised?
- What motive or access created risk?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Loyalist trading leakage case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS27 · Civilian-risk legitimacy audit |
| 240 |
Revolutionary War |
Loyalist trading leakage — artifact and legacy pass Washington letters / New Jersey records |
Counterintelligence and betrayal |
Trade with British lines as an intelligence leak and governance problem. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What motive or access created risk?
- How should damage be contained?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Loyalist trading leakage episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S15 · Loyalty-screening skepticismS16 · Double-agent and legend cautionS18 · Rumor-control and information hygieneS28 · Treason and betrayal responseS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 241 |
Revolutionary War |
Trenton deception posture — diagnostic frame Trenton campaign sources |
Strategic deception and surprise |
Managing enemy expectations before a surprise crossing and attack. Layer: Frame the case as a decision problem rather than a story. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Trenton deception posture problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 242 |
Revolutionary War |
Trenton deception posture — source-quality pass Trenton campaign sources |
Strategic deception and surprise |
Managing enemy expectations before a surprise crossing and attack. Layer: Separate access, motive, freshness, and corroboration. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Trenton deception posture report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 243 |
Revolutionary War |
Trenton deception posture — routing and authority pass Trenton campaign sources |
Strategic deception and surprise |
Managing enemy expectations before a surprise crossing and attack. Layer: Identify who should receive, authorize, or constrain the next step. |
- Which timing window mattered?
- What did the enemy believe?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Trenton deception posture information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 244 |
Revolutionary War |
Trenton deception posture — risk and failure-mode pass Trenton campaign sources |
Strategic deception and surprise |
Managing enemy expectations before a surprise crossing and attack. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Trenton deception posture case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 245 |
Revolutionary War |
Trenton deception posture — artifact and legacy pass Trenton campaign sources |
Strategic deception and surprise |
Managing enemy expectations before a surprise crossing and attack. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Trenton deception posture episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 246 |
Revolutionary War |
Winter raid warning — diagnostic frame Morristown / winter quarters correspondence |
Strategic deception and surprise |
Winter operations require warning even when armies appear static. Layer: Frame the case as a decision problem rather than a story. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Winter raid warning problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 247 |
Revolutionary War |
Winter raid warning — source-quality pass Morristown / winter quarters correspondence |
Strategic deception and surprise |
Winter operations require warning even when armies appear static. Layer: Separate access, motive, freshness, and corroboration. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Winter raid warning report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 248 |
Revolutionary War |
Winter raid warning — routing and authority pass Morristown / winter quarters correspondence |
Strategic deception and surprise |
Winter operations require warning even when armies appear static. Layer: Identify who should receive, authorize, or constrain the next step. |
- Which timing window mattered?
- What did the enemy believe?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Winter raid warning information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 249 |
Revolutionary War |
Winter raid warning — risk and failure-mode pass Morristown / winter quarters correspondence |
Strategic deception and surprise |
Winter operations require warning even when armies appear static. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did the enemy believe?
- What visible posture should be managed?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Winter raid warning case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 250 |
Revolutionary War |
Winter raid warning — artifact and legacy pass Morristown / winter quarters correspondence |
Strategic deception and surprise |
Winter operations require warning even when armies appear static. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What visible posture should be managed?
- Which timing window mattered?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Winter raid warning episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S17 · Strategic posture deceptionS22 · Strike intelligence thresholdS24 · Strategic surprise timingS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 251 |
Yorktown / Alliance |
Lafayette intelligence liaison — diagnostic frame Washington-Lafayette correspondence |
Alliance and French coordination |
Lafayette as a bridge of trust, reporting, and allied coordination. Layer: Frame the case as a decision problem rather than a story. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Lafayette intelligence liaison problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 252 |
Yorktown / Alliance |
Lafayette intelligence liaison — source-quality pass Washington-Lafayette correspondence |
Alliance and French coordination |
Lafayette as a bridge of trust, reporting, and allied coordination. Layer: Separate access, motive, freshness, and corroboration. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Lafayette intelligence liaison report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 253 |
Yorktown / Alliance |
Lafayette intelligence liaison — routing and authority pass Washington-Lafayette correspondence |
Alliance and French coordination |
Lafayette as a bridge of trust, reporting, and allied coordination. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should liaison reporting be caveated?
- What did allied forces know uniquely?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Lafayette intelligence liaison information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS29 · Accountability and record discipline |
| 254 |
Yorktown / Alliance |
Lafayette intelligence liaison — risk and failure-mode pass Washington-Lafayette correspondence |
Alliance and French coordination |
Lafayette as a bridge of trust, reporting, and allied coordination. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Lafayette intelligence liaison case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 255 |
Yorktown / Alliance |
Lafayette intelligence liaison — artifact and legacy pass Washington-Lafayette correspondence |
Alliance and French coordination |
Lafayette as a bridge of trust, reporting, and allied coordination. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Lafayette intelligence liaison episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 256 |
Yorktown / Alliance |
Rochambeau coordination — diagnostic frame Yorktown campaign histories |
Alliance and French coordination |
Joint army timing, road movement, and strategic secrecy with French partners. Layer: Frame the case as a decision problem rather than a story. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Rochambeau coordination problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 257 |
Yorktown / Alliance |
Rochambeau coordination — source-quality pass Yorktown campaign histories |
Alliance and French coordination |
Joint army timing, road movement, and strategic secrecy with French partners. Layer: Separate access, motive, freshness, and corroboration. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Rochambeau coordination report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 258 |
Yorktown / Alliance |
Rochambeau coordination — routing and authority pass Yorktown campaign histories |
Alliance and French coordination |
Joint army timing, road movement, and strategic secrecy with French partners. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should liaison reporting be caveated?
- What did allied forces know uniquely?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Rochambeau coordination information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS29 · Accountability and record discipline |
| 259 |
Yorktown / Alliance |
Rochambeau coordination — risk and failure-mode pass Yorktown campaign histories |
Alliance and French coordination |
Joint army timing, road movement, and strategic secrecy with French partners. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Rochambeau coordination case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 260 |
Yorktown / Alliance |
Rochambeau coordination — artifact and legacy pass Yorktown campaign histories |
Alliance and French coordination |
Joint army timing, road movement, and strategic secrecy with French partners. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Rochambeau coordination episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 261 |
Yorktown / Alliance |
De Grasse naval intelligence — diagnostic frame Yorktown campaign histories |
Alliance and French coordination |
French naval movement as the decisive intelligence-timing variable for Yorktown. Layer: Frame the case as a decision problem rather than a story. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the De Grasse naval intelligence problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 262 |
Yorktown / Alliance |
De Grasse naval intelligence — source-quality pass Yorktown campaign histories |
Alliance and French coordination |
French naval movement as the decisive intelligence-timing variable for Yorktown. Layer: Separate access, motive, freshness, and corroboration. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the De Grasse naval intelligence report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 263 |
Yorktown / Alliance |
De Grasse naval intelligence — routing and authority pass Yorktown campaign histories |
Alliance and French coordination |
French naval movement as the decisive intelligence-timing variable for Yorktown. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should liaison reporting be caveated?
- What did allied forces know uniquely?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the De Grasse naval intelligence information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS29 · Accountability and record discipline |
| 264 |
Yorktown / Alliance |
De Grasse naval intelligence — risk and failure-mode pass Yorktown campaign histories |
Alliance and French coordination |
French naval movement as the decisive intelligence-timing variable for Yorktown. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the De Grasse naval intelligence case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 265 |
Yorktown / Alliance |
De Grasse naval intelligence — artifact and legacy pass Yorktown campaign histories |
Alliance and French coordination |
French naval movement as the decisive intelligence-timing variable for Yorktown. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the De Grasse naval intelligence episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 266 |
Yorktown / Alliance |
Yorktown convergence — diagnostic frame Yorktown campaign histories |
Alliance and French coordination |
Land, naval, deception, and logistical intelligence fused into decisive campaign timing. Layer: Frame the case as a decision problem rather than a story. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Yorktown convergence problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 267 |
Yorktown / Alliance |
Yorktown convergence — source-quality pass Yorktown campaign histories |
Alliance and French coordination |
Land, naval, deception, and logistical intelligence fused into decisive campaign timing. Layer: Separate access, motive, freshness, and corroboration. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Yorktown convergence report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 268 |
Yorktown / Alliance |
Yorktown convergence — routing and authority pass Yorktown campaign histories |
Alliance and French coordination |
Land, naval, deception, and logistical intelligence fused into decisive campaign timing. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should liaison reporting be caveated?
- What did allied forces know uniquely?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Yorktown convergence information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS29 · Accountability and record discipline |
| 269 |
Yorktown / Alliance |
Yorktown convergence — risk and failure-mode pass Yorktown campaign histories |
Alliance and French coordination |
Land, naval, deception, and logistical intelligence fused into decisive campaign timing. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Yorktown convergence case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 270 |
Yorktown / Alliance |
Yorktown convergence — artifact and legacy pass Yorktown campaign histories |
Alliance and French coordination |
Land, naval, deception, and logistical intelligence fused into decisive campaign timing. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Yorktown convergence episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 271 |
Revolutionary War |
Southern theater report integration — diagnostic frame Southern campaign correspondence |
Continental Army strategic intelligence |
Integrating reports from Greene, militia networks, British movement, and local politics. Layer: Frame the case as a decision problem rather than a story. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Southern theater report integration problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculus |
| 272 |
Revolutionary War |
Southern theater report integration — source-quality pass Southern campaign correspondence |
Continental Army strategic intelligence |
Integrating reports from Greene, militia networks, British movement, and local politics. Layer: Separate access, motive, freshness, and corroboration. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Southern theater report integration report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS15 · Loyalty-screening skepticism |
| 273 |
Revolutionary War |
Southern theater report integration — routing and authority pass Southern campaign correspondence |
Continental Army strategic intelligence |
Integrating reports from Greene, militia networks, British movement, and local politics. Layer: Identify who should receive, authorize, or constrain the next step. |
- What was the cost of ignorance?
- What decision did headquarters need to make?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Southern theater report integration information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 274 |
Revolutionary War |
Southern theater report integration — risk and failure-mode pass Southern campaign correspondence |
Continental Army strategic intelligence |
Integrating reports from Greene, militia networks, British movement, and local politics. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What decision did headquarters need to make?
- Which report type could change deployment?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Southern theater report integration case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 275 |
Revolutionary War |
Southern theater report integration — artifact and legacy pass Southern campaign correspondence |
Continental Army strategic intelligence |
Integrating reports from Greene, militia networks, British movement, and local politics. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which report type could change deployment?
- What was the cost of ignorance?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Southern theater report integration episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S01 · Commander’s requirement disciplineS02 · Intelligence consumer triageS10 · Enemy disposition requirementS23 · Force-preservation calculusS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 276 |
Revolutionary War |
New Jersey militia intelligence — diagnostic frame New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Militia and local observers as persistent warning sensors near British lines. Layer: Frame the case as a decision problem rather than a story. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the New Jersey militia intelligence problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 277 |
Revolutionary War |
New Jersey militia intelligence — source-quality pass New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Militia and local observers as persistent warning sensors near British lines. Layer: Separate access, motive, freshness, and corroboration. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the New Jersey militia intelligence report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 278 |
Revolutionary War |
New Jersey militia intelligence — routing and authority pass New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Militia and local observers as persistent warning sensors near British lines. Layer: Identify who should receive, authorize, or constrain the next step. |
- What indicator was time-sensitive?
- Which ship, road, tide, or supply movement mattered?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the New Jersey militia intelligence information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 279 |
Revolutionary War |
New Jersey militia intelligence — risk and failure-mode pass New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Militia and local observers as persistent warning sensors near British lines. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- Which ship, road, tide, or supply movement mattered?
- What did logistics reveal about intention?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the New Jersey militia intelligence case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 280 |
Revolutionary War |
New Jersey militia intelligence — artifact and legacy pass New Jersey campaign sources |
Maritime, coastal, and logistics indicators |
Militia and local observers as persistent warning sensors near British lines. Layer: Convert the case into a record, checklist, or institutional lesson. |
- What did logistics reveal about intention?
- What indicator was time-sensitive?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the New Jersey militia intelligence episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S03 · Map-terrain correspondenceS11 · Movement and logistics indicatorsS13 · Courier and time-window disciplineS14 · Maritime and coastal reportingS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 281 |
Revolutionary administration |
Secret-service expenses — diagnostic frame Washington accounts / secret-service funds |
Secret funds, rewards, and correspondence |
Payments and support as necessary but accountable intelligence infrastructure. Layer: Frame the case as a decision problem rather than a story. |
- What payment or letter was necessary?
- How could secrecy and accounting coexist?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Secret-service expenses problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 282 |
Revolutionary administration |
Secret-service expenses — source-quality pass Washington accounts / secret-service funds |
Secret funds, rewards, and correspondence |
Payments and support as necessary but accountable intelligence infrastructure. Layer: Separate access, motive, freshness, and corroboration. |
- How could secrecy and accounting coexist?
- What would later reconstruction require?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Secret-service expenses report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 283 |
Revolutionary administration |
Secret-service expenses — routing and authority pass Washington accounts / secret-service funds |
Secret funds, rewards, and correspondence |
Payments and support as necessary but accountable intelligence infrastructure. Layer: Identify who should receive, authorize, or constrain the next step. |
- What would later reconstruction require?
- What payment or letter was necessary?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Secret-service expenses information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS20 · Diplomatic-military reporting loop |
| 284 |
Revolutionary administration |
Secret-service expenses — risk and failure-mode pass Washington accounts / secret-service funds |
Secret funds, rewards, and correspondence |
Payments and support as necessary but accountable intelligence infrastructure. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What payment or letter was necessary?
- How could secrecy and accounting coexist?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Secret-service expenses case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 285 |
Revolutionary administration |
Secret-service expenses — artifact and legacy pass Washington accounts / secret-service funds |
Secret funds, rewards, and correspondence |
Payments and support as necessary but accountable intelligence infrastructure. Layer: Convert the case into a record, checklist, or institutional lesson. |
- How could secrecy and accounting coexist?
- What would later reconstruction require?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Secret-service expenses episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S07 · Compartmented correspondence governanceS09 · Expense and reward controlS13 · Courier and time-window disciplineS29 · Accountability and record disciplineS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 286 |
Presidency |
Presidency confidential information — diagnostic frame Washington Papers / presidency records |
Presidential legacy and archival memory |
From commander to president: confidential information as executive responsibility. Layer: Frame the case as a decision problem rather than a story. |
- What lesson moved from war to statecraft?
- Which record corrects mythology?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Presidency confidential information problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 287 |
Presidency |
Presidency confidential information — source-quality pass Washington Papers / presidency records |
Presidential legacy and archival memory |
From commander to president: confidential information as executive responsibility. Layer: Separate access, motive, freshness, and corroboration. |
- Which record corrects mythology?
- How should the public remember intelligence discipline?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Presidency confidential information report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 288 |
Presidency |
Presidency confidential information — routing and authority pass Washington Papers / presidency records |
Presidential legacy and archival memory |
From commander to president: confidential information as executive responsibility. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should the public remember intelligence discipline?
- What lesson moved from war to statecraft?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Presidency confidential information information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 289 |
Presidency |
Presidency confidential information — risk and failure-mode pass Washington Papers / presidency records |
Presidential legacy and archival memory |
From commander to president: confidential information as executive responsibility. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What lesson moved from war to statecraft?
- Which record corrects mythology?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Presidency confidential information case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 290 |
Presidency |
Presidency confidential information — artifact and legacy pass Washington Papers / presidency records |
Presidential legacy and archival memory |
From commander to president: confidential information as executive responsibility. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which record corrects mythology?
- How should the public remember intelligence discipline?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Presidency confidential information episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacy |
| 291 |
Presidency |
Neutrality and foreign reporting — diagnostic frame Washington presidency correspondence |
Alliance and French coordination |
Presidential-era foreign reporting and neutrality as intelligence-consumer discipline. Layer: Frame the case as a decision problem rather than a story. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Neutrality and foreign reporting problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 292 |
Presidency |
Neutrality and foreign reporting — source-quality pass Washington presidency correspondence |
Alliance and French coordination |
Presidential-era foreign reporting and neutrality as intelligence-consumer discipline. Layer: Separate access, motive, freshness, and corroboration. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Neutrality and foreign reporting report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 293 |
Presidency |
Neutrality and foreign reporting — routing and authority pass Washington presidency correspondence |
Alliance and French coordination |
Presidential-era foreign reporting and neutrality as intelligence-consumer discipline. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should liaison reporting be caveated?
- What did allied forces know uniquely?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Neutrality and foreign reporting information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS29 · Accountability and record discipline |
| 294 |
Presidency |
Neutrality and foreign reporting — risk and failure-mode pass Washington presidency correspondence |
Alliance and French coordination |
Presidential-era foreign reporting and neutrality as intelligence-consumer discipline. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What did allied forces know uniquely?
- Which timing dependency controlled the plan?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Neutrality and foreign reporting case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 295 |
Presidency |
Neutrality and foreign reporting — artifact and legacy pass Washington presidency correspondence |
Alliance and French coordination |
Presidential-era foreign reporting and neutrality as intelligence-consumer discipline. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which timing dependency controlled the plan?
- How should liaison reporting be caveated?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Neutrality and foreign reporting episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S19 · French-alliance intelligence integrationS20 · Diplomatic-military reporting loopS21 · Liaison reliability comparisonS22 · Strike intelligence thresholdS31 · Intelligence lessons into statecraftS32 · Archival memory conversion |
| 296 |
Presidency |
Farewell-statecraft lesson — diagnostic frame Washington Farewell / presidential legacy |
Presidential legacy and archival memory |
The legacy of intelligence restraint, foreign caution, and republican legitimacy. Layer: Frame the case as a decision problem rather than a story. |
- What lesson moved from war to statecraft?
- Which record corrects mythology?
- What would Washington need to know before treating this as actionable in the diagnostic frame?
|
Define the Farewell-statecraft lesson problem as a commander’s intelligence requirement with a deadline, decision owner, and uncertainty statement. |
requirement card; decision deadline; priority note |
executive judgment; campaign sense; question design |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS01 · Commander’s requirement disciplineS02 · Intelligence consumer triage |
| 297 |
Presidency |
Farewell-statecraft lesson — source-quality pass Washington Farewell / presidential legacy |
Presidential legacy and archival memory |
The legacy of intelligence restraint, foreign caution, and republican legitimacy. Layer: Separate access, motive, freshness, and corroboration. |
- Which record corrects mythology?
- How should the public remember intelligence discipline?
- What would Washington need to know before treating this as actionable in the source-quality pass?
|
Evaluate the Farewell-statecraft lesson report stream by access, motive, freshness, corroboration, and contradiction before elevating it. |
source-quality matrix; corroboration log; freshness score |
source criticism; counterintelligence skepticism; evidence grading |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS10 · Enemy disposition requirementS15 · Loyalty-screening skepticism |
| 298 |
Presidency |
Farewell-statecraft lesson — routing and authority pass Washington Farewell / presidential legacy |
Presidential legacy and archival memory |
The legacy of intelligence restraint, foreign caution, and republican legitimacy. Layer: Identify who should receive, authorize, or constrain the next step. |
- How should the public remember intelligence discipline?
- What lesson moved from war to statecraft?
- What would Washington need to know before treating this as actionable in the routing and authority pass?
|
Route the Farewell-statecraft lesson information to the proper military, congressional, state, or allied channel while preserving necessary confidentiality. |
routing memo; authority note; controlled-distribution copy |
civil-military judgment; correspondence discipline; alliance awareness |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS20 · Diplomatic-military reporting loopS29 · Accountability and record discipline |
| 299 |
Presidency |
Farewell-statecraft lesson — risk and failure-mode pass Washington Farewell / presidential legacy |
Presidential legacy and archival memory |
The legacy of intelligence restraint, foreign caution, and republican legitimacy. Layer: Ask how the case fails if the report is wrong, late, captured, or politicized. |
- What lesson moved from war to statecraft?
- Which record corrects mythology?
- What would Washington need to know before treating this as actionable in the risk and failure-mode pass?
|
Stress-test the Farewell-statecraft lesson case for compromise, false confidence, rumor inflation, civilian harm, and strategic blowback. |
risk register; failure-mode note; legitimacy check |
premortem reasoning; legitimacy analysis; compromise control |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacyS16 · Double-agent and legend cautionS27 · Civilian-risk legitimacy audit |
| 300 |
Presidency |
Farewell-statecraft lesson — artifact and legacy pass Washington Farewell / presidential legacy |
Presidential legacy and archival memory |
The legacy of intelligence restraint, foreign caution, and republican legitimacy. Layer: Convert the case into a record, checklist, or institutional lesson. |
- Which record corrects mythology?
- How should the public remember intelligence discipline?
- What would Washington need to know before treating this as actionable in the artifact and legacy pass?
|
Convert the Farewell-statecraft lesson episode into a reusable record: lesson, ledger, case note, or archival warning. |
after-action lesson; archival trace; myth-correction note |
institutional memory; archival thinking; historical correction |
S31 · Intelligence lessons into statecraftS32 · Archival memory conversionS33 · Myth-correction disciplineS30 · Confidentiality versus republican legitimacy |