ntnsndr/protocol-bicorder
1
0 Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: mark classifier integration historical; fix shortform count

Browse Source 
- INTEGRATION_GUIDE.md: rewritten as research notes — how to reproduce the
  cluster classification with the analysis scripts, and why it was removed
  from the tool in v1.3.0
- analysis/README.md: integration section marked historical
- bicorder-app/README.md: shortform is 9 gradients, not 10
This commit is contained in:
Protocolbot committed 2026-09-23 07:58:17 -06:00
1 parent 8c40ca076b
commit e7d6465ceb
3 files changed
+74 -374
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

analysis/README.md
+7 -2
View File
@@ -416,9 +416,14 @@ Hypothesis: Changing the analyst and their standpoint could result in interestin
Method: Alongside the dataset of protocols, generate diverse personas, such as a) personas used to evaluate every protocols, and b) protocol-specific personas that reflect different relationships to the protocol. Modify the test suite to include personas as an additional dimension of the analysis.
## Integration with Bicorder Tool
## Integration with Bicorder Tool (historical)
The cluster analysis findings have been integrated into the bicorder system as an automated analysis gradient:
> **Update (v1.3.0):** The bureaucratic↔relational (formal/informal) LDA analysis
> has been **removed from the bicorder itself**. The cluster classification lives
> on as research in this directory only — see `INTEGRATION_GUIDE.md` for how to
> reproduce it and why it was removed from the tool.
The cluster analysis findings were previously integrated into the bicorder system as an automated analysis gradient:
**Bureaucratic ↔ Relational** - A new analysis field that automatically calculates where a protocol falls on the spectrum between the two protocol families identified through clustering analysis.