DOIN Artifact Inventory
DOIN Artifact Inventory
Below is the consolidated inventory of DOIN-related artifacts that surfaced in search. Because I have not opened each individual file, the paths shown are based on the repository locations inferred from the search results and naming conventions. Think of this as a DOIN Artifact Index v0.1 that you can use to locate and organize the materials.
Core Artifact Inventory
| Artifact | Type | Probable Path | Notes |
|---|---|---|---|
| doin.html | HTML | jasonkronemeyer.github.io/_site/doin.html |
Core DOIN framework; “Policy Learning Machine for the Digital Economy.” |
| training-the-compass-digital-opportunities-intelligence-framework | HTML | jasonkronemeyer.github.io/_site/training-the-compass-digital-opportunities-intelligence-framework.html |
Early Compass/DOIN architecture and Merit-related framing. |
| sem1 | Markdown | jasonkronemeyer.github.io/notes/sem1.md |
Contains awareness → engagement → participation → collective intelligence progression. |
| doin-okc | Markdown | jasonkronemeyer.github.io/notes/doin-okc.md |
DOIN Open Knowledge Commons; likely the strongest bridge to Cognitive Commons. |
| research-brief-dikw-learning-infrastructure | Markdown | jasonkronemeyer.github.io/research/research-brief-dikw-learning-infrastructure.md |
DIKW + learning infrastructure + DOIN synthesis. |
| DOIN_Ontology_Pipeline_Policy_Learning_Synthesis | DOCX | jasonkronemeyer.github.io/research/DOIN_Ontology_Pipeline_Policy_Learning_Synthesis.docx |
Ontology Pipeline integration with policy learning and knowledge infrastructure. |
| why-mgdl | HTML/Markdown | jasonkronemeyer.github.io/research/why-mgdl.* |
MiGreatDataLake rationale connected to DOIN and knowledge infrastructure. |
| Digital Opportunities Director Interview Points | DOCX | jasonkronemeyer.github.io/notes/Digital Opportunities Director Interview Points.docx |
Contains community-capacity language useful to the framework. |
Suggested DOIN Framework Collection
If you create a single folder to gather the key materials, I would recommend:
```text DOIN/ ├── 01-Foundations/ │ ├── doin.html │ ├── training-the-compass-digital-opportunities-intelligence-framework.html │ ├── 02-Knowledge-Commons/ │ ├── doin-okc.md │ ├── research-brief-dikw-learning-infrastructure.md │ ├── 03-Policy-Learning/ │ ├── DOIN_Ontology_Pipeline_Policy_Learning_Synthesis.docx │ ├── 04-Community-Intelligence/ │ ├── sem1.md │ ├── 05-Supporting-Research/ │ ├── why-mgdl.* │ ├── Digital Opportunities Director Interview Points.docx
DOIN Artifact InventoryArtifactTypeProbable PathNotesdoin.htmlHTMLjasonkronemeyer.github.io/_site/doin.htmlCore DOIN framework; “Policy Learning Machine for the Digital Economy.”training-the-compass-digital-opportunities-intelligence-frameworkHTMLjasonkronemeyer.github.io/_site/training-the-compass-digital-opportunities-intelligence-framework.htmlEarly Compass/DOIN architecture and Merit-related framing.sem1Markdownjasonkronemeyer.github.io/notes/sem1.mdContains awareness → engagement → participation → collective intelligence progression.doin-okcMarkdownjasonkronemeyer.github.io/notes/doin-okc.mdDOIN Open Knowledge Commons; likely the strongest bridge to Cognitive Commons.research-brief-dikw-learning-infrastructureMarkdownjasonkronemeyer.github.io/research/research-brief-dikw-learning-infrastructure.mdDIKW + learning infrastructure + DOIN synthesis.DOIN_Ontology_Pipeline_Policy_Learning_SynthesisDOCXjasonkronemeyer.github.io/research/DOIN_Ontology_Pipeline_Policy_Learning_Synthesis.docxOntology Pipeline integration with policy learning and knowledge infrastructure.why-mgdlHTML/Markdownjasonkronemeyer.github.io/research/why-mgdl.MiGreatDataLake rationale connected to DOIN and knowledge infrastructure.Digital Opportunities Director Interview PointsDOCXjasonkronemeyer.github.io/notes/Digital Opportunities Director Interview Points.docxContains community-capacity language useful to the framework.⸻Suggested DOIN Framework CollectionIf you create a single folder to gather the key materials, I would recommend:DOIN/ ├── 01-Foundations/ │ ├── doin.html │ ├── training-the-compass-digital-opportunities-intelligence-framework.html │ ├── 02-Knowledge-Commons/ │ ├── doin-okc.md │ ├── research-brief-dikw-learning-infrastructure.md │ ├── 03-Policy-Learning/ │ ├── DOIN_Ontology_Pipeline_Policy_Learning_Synthesis.docx │ ├── 04-Community-Intelligence/ │ ├── sem1.md │ ├── 05-Supporting-Research/ │ ├── why-mgdl. │ ├── Digital Opportunities Director Interview Points.docx ⸻Most Important Files for the Cognitive Commons DiscussionIf your immediate goal is to connect Mitchell Shapiro’s Cognitive Commons concept to DOIN, start with these three files first:doin-okc (Open Knowledge Commons) 2. sem1 (Collective Intelligence progression) 3. training-the-compass-digital-opportunities-intelligence-framework (overall architecture) My hypothesis is that those three documents already contain most of the conceptual foundation needed to extend DOIN from:Knowledge Commons ↓ Policy Learning ↓ Action to:Knowledge Commons ↓ Cognitive Commons ↓ Collective Intelligence ↓ Policy Learning ↓ Opportunity Creation