Add visionary OSINT/INTOP political-intelligence AI capability program to FUTURE_*.md (to 2037)#2856
Merged
Merged
Conversation
…ability catalog + architecture, workflows and data structures Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>
…bility state machines Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>
…threat analysis and intelligence-integrity controls Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
pethers
May 31, 2026 19:25
View session
github-actions
Bot
added
documentation
Contributor
🏷️ Automatic Labeling SummaryThis PR has been automatically labeled based on the files changed and PR metadata. Applied Labels: documentation,security,isms,size-xl Label Categories
For more information, see |
Contributor
🔍 Lighthouse Performance Audit
📥 Download full Lighthouse report Budget Compliance: Performance budgets enforced via |
Contributor
There was a problem hiding this comment.
Pull request overview
This documentation-only PR adds a unified forward-looking OSINT/INTOP political-intelligence capability program through 2037, anchored by FUTURE_MINDMAP.md and propagated across the future architecture, workflow, data, process, state, SWOT, threat, and security documents.
Changes:
- Adds a master C1–C32 Political-Intelligence Capability Catalog and horizon roadmap.
- Maps the catalog into architecture, workflow, data-model, flowchart, and state-machine views.
- Adds threat, SWOT, and security-control coverage for counter-AI, FIMI, provenance, calibration, and neutrality risks.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
FUTURE_MINDMAP.md |
Adds the master C1–C32 capability catalog and maturity arc. |
FUTURE_ARCHITECTURE.md |
Adds the intelligence-specific architecture layer and AWS service mapping. |
FUTURE_WORKFLOWS.md |
Adds proposed intelligence-cycle workflows and maturity overlay. |
FUTURE_DATA_MODEL.md |
Adds future schema examples and ERD for intelligence entities. |
FUTURE_FLOWCHART.md |
Adds process flows for fusion, warning, calibration, FIMI, and counter-AI gates. |
FUTURE_STATEDIAGRAM.md |
Adds state machines for warning, calibration, FIMI, entity resolution, and publication. |
FUTURE_SWOT.md |
Adds capability SWOT and renumbers the table of contents. |
FUTURE_THREAT_MODEL.md |
Adds PI-T1…PI-T7 intelligence-integrity threat scenarios. |
FUTURE_SECURITY_ARCHITECTURE.md |
Adds II-1…II-9 intelligence-integrity and counter-AI controls. |
Comment on lines
+506
to
+514
| | Control | ISO 27001:2022 | NIST CSF 2.0 | OWASP LLM | | ||
| |---------|----------------|--------------|-----------| | ||
| | II-1 Evidence anchor | A.5.34 (PII), A.8.28 (secure coding) | PR.DS, GV.OC | LLM09 Overreliance | | ||
| | II-2 Provenance | A.8.24 (crypto), A.5.33 (records) | PR.DS-6 (integrity) | LLM08 | | ||
| | II-3 Injection defense | A.8.28, A.8.16 (monitoring) | DE.CM, PR.PS | LLM01 / LLM03 | | ||
| | II-4 Neutrality gate | A.5.1 (policies), A.8.29 (testing) | GV.OC, GV.RR | LLM09 | | ||
| | II-5 Calibration | A.8.16, A.5.36 (compliance) | ID.IM, DE.AE | LLM09 | | ||
| | II-7 FIMI ethics | A.5.34, A.18 (privacy) | GV.OC, ID.RA | — | | ||
| | II-8 Human-on-the-loop | A.5.4 (mgmt responsibilities) | GV.RR-1 | LLM08 Excessive Agency | |
Co-authored-by: pethers <1726836+pethers@users.noreply.github.com>
Contributor
🔍 Lighthouse Performance Audit
📥 Download full Lighthouse report Budget Compliance: Performance budgets enforced via |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The nine
FUTURE_*.mddocuments described a strong but single-source, build-time, document-centric intelligence operation. This expands them with a unified, forward-looking political-intelligence capability program spanning today → 2037, framed from a high-level intelligence-operative perspective with explicit benefit/why for each capability.Current-state review
The existing tradecraft (
analysis/methodologies/,analysis/templates/) is mature — F3EAD, ICD 203/206, ACH, Admiralty grading, PIR roll-forward, calibrated WEP forecasting, DISARM framing — but lacks runtime fusion, warning, continuous calibration and counter-AI defense. Those are the gaps this PR fills.Master catalog (the unifying spine)
FUTURE_MINDMAP.md— new Political-Intelligence Capability Catalog (C1–C32) organized along the intelligence cycle (Direction → Collection → Processing → Analysis → Production → Dissemination → Feedback): 5 pillar mindmaps + a capability→pillar→horizon→AI-method→benefit crosswalk + maturity timeline. All other docs cross-link here.Propagation into each doc's idiom
FUTURE_ARCHITECTURE.md— §4A capability architecture (collection/fusion, processing/provenance, analytic engine, dissemination, assurance) + I&W component view + AWS service mapping (Neptune, SageMaker, Bedrock Agents/Guardrails, EventBridge/Timestream, KMS/S3 Object Lock).FUTURE_WORKFLOWS.md— 18-workflow intelligence-cycle suite + maturity-model overlay.FUTURE_DATA_MODEL.md— §4.11 capability schemas (resolved-entity,fusion-edge,iw-indicator,forecast/calibration,fimi-signal,estimative,provenance— all@3.0, evidence-anchored) + ERD.FUTURE_FLOWCHART.md— §4A six process flows (master cycle, multi-INT fusion, I&W tripwire, calibration loop, FIMI early-warning, counter-AI gate).FUTURE_STATEDIAGRAM.md— §18 five state machines (I&W, calibration, FIMI, entity-resolution, estimative publication).FUTURE_SWOT.md— capability SWOT including the strategic cost of NOT building each capability.FUTURE_THREAT_MODEL.md— PI-T1…PI-T7 counter-AI / FIMI-targeting / analytic-integrity threats mapped to STRIDE / MITRE ATLAS / OWASP-LLM.FUTURE_SECURITY_ARCHITECTURE.md— §3.5 integrity-by-construction controls II-1…II-9 (evidence anchor, C2PA provenance, injection screening, neutrality CI-gate, calibration-as-release-metric, human-on-the-loop).Governing rails (preserved throughout)
Every capability stays evidence-anchored (
dok_id+ Admiralty grade), party-neutral, human-on-the-loop, aggregate/non-accusatory for FIMI, and bound to GDPR Art. 9 lawful bases (9(2)(e)/9(2)(g)) — augmenting accountability, never enabling surveillance or partisan influence.Notes for reviewers
FUTURE_WORKFLOWS.md:549, REST-API-endpoints diagram) is pre-existing and unrelated — left untouched.