# INITKOA CONTEXT PACK repository: Power_Dynamics source_commit: local-directory source_mode: directory working_tree_markdown: not-applicable working_tree_selected: not-applicable selection_mode: markdown wiki_source_commit: none wiki_working_tree_markdown: none policy_version: 2026-09-18.3 repo_files: 292 wiki_files: 0 source_files: 292 included_files: 292 excluded_files: 0 duplicate_files: 0 content_bytes: 771830 authority_counts: {"reference":292} content_role_counts: {"knowledge":292} generated_at: 2026-09-22T15:18:21-04:00 files: 292 content_sha256: 350afe473bb38e2c2ac9007b1f18c7fe636a9c40dba86e9401e9d2860549011f ================================================================================================ FILE INDEX ================================================================================================ 001. [reference] [knowledge] Power-Dynamics.wiki/_Footer.md | bytes=196 | sha256=199f5bb2d286946ccc1cbecb8c6b621c236cc82a9664321baafdd83bbcb6b177 002. [reference] [knowledge] Power-Dynamics.wiki/_Sidebar.md | bytes=5020 | sha256=ebe816913fbf50be40cb2c603de7b8cdaacc3e0eca547c5e1a597083b6bc66f1 003. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-01-Power-Dependence-and-Domination.md | bytes=9383 | sha256=3e351b0f6fe9e91ee383d80c0764790545e4225441f49ec1d9411eda0270ef13 004. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-02-Polycentric-Governance-and-Institutions.md | bytes=3212 | sha256=b429a77e2f9601fc935a3b52b97adecefe413307d14737958f5c1b4844c5efef 005. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-03-Modularity-Standards-and-Path-Dependence.md | bytes=4369 | sha256=850e73869f6ba3fb835a7afd848913ffd1f90b6c620f72ead1cc0780744f8138 006. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-04-Open-Source-Exit-Fork-and-Peer-Production.md | bytes=3239 | sha256=96e11aeb6525cfe79b2b628b3c2fd3ecb0ccce1150db5560d82ceb06cfe64abc 007. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-05-Network-Power-and-Social-Capital.md | bytes=3074 | sha256=ce2e4c419cc3350c26c86381216b0e7bf593b511439d2823f54cd65ae50f546b 008. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-06-Expertise-SmartVote-and-Collective-Judgment.md | bytes=6247 | sha256=6a68a1753cebd3945875a4323c3dbd5fa7aeb172c0ab3bd74bc3f565d7bed484 009. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-07-Metrics-Reputation-and-Gaming.md | bytes=2955 | sha256=415347b531d2f9fda225bec43bd87b589dd00e94dbe14d66491422cbbf3dfac6 010. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-08-Classification-Infrastructure-and-Code.md | bytes=2998 | sha256=23795e53fb8f3f0477dbcebb30f808841a0db3482e824e43bae2976444792d0f 011. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-09-Epistemic-Power-Provenance-and-Plurality.md | bytes=3574 | sha256=eb29d21427d7739e75a45f8fabdc76e736323f688f74a8cf03d43ea0309a721f 012. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-10-Systems-Cybernetics-and-Adaptation.md | bytes=2584 | sha256=469cefbc5cd52fe3b00b0fb3e4cdcc75f2c7f2722b9fdfaca3a437a9b8e9d009 013. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-11-Collective-Action-Mobilization-and-Diffusion.md | bytes=4190 | sha256=4da7f881dbc5f7263b75d568134d375dc7c60090296c2216b93d1fb9760f1bfd 014. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-12-Capabilities-Concerted-Power-and-Legibility.md | bytes=3278 | sha256=1a6325cf99020beea2ff4674d09973205506f637d99cf3a656a15455a9a154bc 015. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage-Bibliography.md | bytes=11340 | sha256=8c4812722387ad7056b8d757d784012562061c9ac0070ee22e5de39de7330670 016. [reference] [knowledge] Power-Dynamics.wiki/Academic-Lineage.md | bytes=7295 | sha256=7336284bc963a5dec5498754d308085f2cb8f3b377641f6dd4275d7b1a2b3e81 017. [reference] [knowledge] Power-Dynamics.wiki/Administrative-and-Operational-Power.md | bytes=1644 | sha256=348fa65d5603c05632768d6c5ac701501f2db1cc2131bfc043a01a3161185eb7 018. [reference] [knowledge] Power-Dynamics.wiki/AI-and-Cognitive-Puissance.md | bytes=711 | sha256=f6eee22ecbb03a08eac4c1bf2af3e977ee38755c4f5a5b31100e67f44bc82c46 019. [reference] [knowledge] Power-Dynamics.wiki/AI-Hidden-Sovereignty.md | bytes=585 | sha256=23af199c1f1b420b029043f1909717a4c9192c3278d721970352b04642bd90e3 020. [reference] [knowledge] Power-Dynamics.wiki/Authority-Architecture.md | bytes=1519 | sha256=02cb7f519eb1a1eb4b03c3ccf5a7236465f90d8a9a78555bd73fca35f4e78053 021. [reference] [knowledge] Power-Dynamics.wiki/Branch-Ecology.md | bytes=1417 | sha256=0fc2019186627fe63477de561d7e4a50313524ea13b996f51aa48c127bf7e644 022. [reference] [knowledge] Power-Dynamics.wiki/Branch-Mobility.md | bytes=627 | sha256=2e1f0ca832211835ae0da912cf425f5f3ccb6bf17c0ca605ae1ac6d98b282a1f 023. [reference] [knowledge] Power-Dynamics.wiki/Brand-Founder-and-Optionality.md | bytes=2501 | sha256=b2f8ec546671eac59a6bb69a61300f68d9b42e61df4d8dfd5ea0d428f7dbabe5 024. [reference] [knowledge] Power-Dynamics.wiki/Capability-Show-Profile.md | bytes=1995 | sha256=b9be02bbd8daa025dfc375ad7b0ca7de5d08f9d2b664c912f669ce6bcf48ba4b 025. [reference] [knowledge] Power-Dynamics.wiki/Capability-Spectrum.md | bytes=5032 | sha256=b57fc69714e1b7628007320f9630bcd2d4fac653f6216350949523f0888dcded 026. [reference] [knowledge] Power-Dynamics.wiki/Capsules-and-Federation.md | bytes=710 | sha256=062dd5b907b10824ccec3678ccb6d8aeaaddb3fb322f44420ca84a2088d7dcce 027. [reference] [knowledge] Power-Dynamics.wiki/Case-Studies.md | bytes=1747 | sha256=7f629009678347c49585325709cb0d7ed8aaac0f49b63fe25705de7f1828a633 028. [reference] [knowledge] Power-Dynamics.wiki/Cognitive-and-AI-Power.md | bytes=1608 | sha256=971494d51016289dd448ac9dd5accd9dea164277526b8d62f8b218e6f461df31 029. [reference] [knowledge] Power-Dynamics.wiki/Complementarity-Branches-and-Kristals.md | bytes=1851 | sha256=c9a5db5cae3c75c8f7b9ba6c589f97b3bd2e1ddbcd48a4b4e8c34dda550a358e 030. [reference] [knowledge] Power-Dynamics.wiki/Component-Power-Matrix.md | bytes=3169 | sha256=b37589f22bbc4f0bcd67d6a1c0d2840f8256a7bb40f117ff5dd42cc803ef5481 031. [reference] [knowledge] Power-Dynamics.wiki/Composition-Engine.md | bytes=2652 | sha256=2ce2748cb516d6f7cdff3158d8a31e07a7f86b8dd6c477e8751ec3206677488a 032. [reference] [knowledge] Power-Dynamics.wiki/Compounding-Engine.md | bytes=2185 | sha256=ffda61b1462a74d67fff7e2def60199341f6a87e35745b1ed6669049f391e54d 033. [reference] [knowledge] Power-Dynamics.wiki/Constitutional-Tests.md | bytes=715 | sha256=01a91622d1997fdd639daad991b332a90214184dd7206d5257a0bb67994224d1 034. [reference] [knowledge] Power-Dynamics.wiki/Conversion-Chains.md | bytes=2169 | sha256=3e813b6511f619763da0345afa7803a2a92c7b8c99a50787e5f3f816f25cbe25 035. [reference] [knowledge] Power-Dynamics.wiki/Core-Ontology.md | bytes=1506 | sha256=6214a334d91f7031f355a617e9ba433c2cb4e22bc0945082e3f8b5ebb12eebce 036. [reference] [knowledge] Power-Dynamics.wiki/Corpus-Map.md | bytes=6147 | sha256=26e52f23de4d1138fb79fdcd045635ad484ba7ca3a056f8491659330ffabac33 037. [reference] [knowledge] Power-Dynamics.wiki/Counterpower-and-Optionality.md | bytes=2223 | sha256=c4eef9b0b93cb8f1bd72e04bef205cac7f7a7873f7991ce00f45b5e01293c82c 038. [reference] [knowledge] Power-Dynamics.wiki/Counterpowers-and-Legibility.md | bytes=870 | sha256=b5f9b716ee49592a517f4df5bab229c18109b7217cad843a5238b115983f0b48 039. [reference] [knowledge] Power-Dynamics.wiki/Credibility-and-Reputation-Power.md | bytes=1672 | sha256=c2655b2c80f9458bb486ffa4f6aa9510478edb156087756fc29df94fd265733f 040. [reference] [knowledge] Power-Dynamics.wiki/Cross-Domain-Power-Conversion.md | bytes=3257 | sha256=7e5e2d2661767b711de9fbd7fbde62e2f2247d8e0199d7385b2f27ddbabc9927 041. [reference] [knowledge] Power-Dynamics.wiki/Desjardins-Power-Stacking.md | bytes=562 | sha256=8df61a15eef3d267133d6f8612d72b03830b2b6b4ee0209b24425bf8bb2b1376 042. [reference] [knowledge] Power-Dynamics.wiki/Dynamics.md | bytes=2990 | sha256=0e9f238054afc1bfa4655791ea4ca281c67ae554d7c2ea08f4ce01ed6b46dac5 043. [reference] [knowledge] Power-Dynamics.wiki/Economic-and-Allocation-Power.md | bytes=1970 | sha256=21f2b14b72837bd26d0e9d8ec19f2af00ee0c9b859c6f9b85125897ff299d58d 044. [reference] [knowledge] Power-Dynamics.wiki/Effective-Possibility.md | bytes=1187 | sha256=510eb816143c88b9b541bb755763ce9e713db0354ed0c1c2ebaf99b0712bd5dd 045. [reference] [knowledge] Power-Dynamics.wiki/Epistemic-and-Semantic-Power.md | bytes=1715 | sha256=cdcf3834f60e1e423398672d1c9693ce8ff3c7cf2e4345630e50683e15ebd85e 046. [reference] [knowledge] Power-Dynamics.wiki/Ethical-Fiction-as-Self-Binding.md | bytes=1822 | sha256=dcb95db3321ed79afa8cd96b78dff227fbb6d77143ff6fa6c0134f9d5850f4b6 047. [reference] [knowledge] Power-Dynamics.wiki/Evolutionary-and-Counterpower.md | bytes=1638 | sha256=aa179254b68062d1249858e022215866a14f441bf1a39cf6af5a1560f2314683 048. [reference] [knowledge] Power-Dynamics.wiki/Exit-Portability-and-Federation.md | bytes=1838 | sha256=53890451baefd1e4562314077dfad093cf6c75ca182c86c32729b33e8db3ed42 049. [reference] [knowledge] Power-Dynamics.wiki/FAQ.md | bytes=4574 | sha256=d6cfa2dc4f533cf75631e466b00499690cad4709ad9b6383073671a983efd71a 050. [reference] [knowledge] Power-Dynamics.wiki/Forms-of-Puissance.md | bytes=2486 | sha256=9cda341ea7f541fa7cc5071aec3a8b2d5fc4d73de1ebac10cb202436fc57ecd7 051. [reference] [knowledge] Power-Dynamics.wiki/Founder-Decentering.md | bytes=1068 | sha256=6708897ab75edad1166b6faa58686d0be9cb7830be9146d94c3fce8d9a14a99a 052. [reference] [knowledge] Power-Dynamics.wiki/From-Individual-to-Federation.md | bytes=1997 | sha256=d4e4067612642a414768df7b5c1d5fde1459391d9bcd3677c29d9e7a2a577220 053. [reference] [knowledge] Power-Dynamics.wiki/Getting-Started.md | bytes=3991 | sha256=99f3d673f142a512ff5dca8b2581ff2e029312db0bf169b13fe6abf26574a562 054. [reference] [knowledge] Power-Dynamics.wiki/Glossary.md | bytes=33154 | sha256=aab8c99db0c7d84d93ecb360b9e6b9482966a838214ddaa9fc29ed9847918424 055. [reference] [knowledge] Power-Dynamics.wiki/Governance-After-Capability.md | bytes=2915 | sha256=60898dd85795983c0c720b638be9f49bc53a8e754ac4dc4debf97b8ba96ebc9a 056. [reference] [knowledge] Power-Dynamics.wiki/Home.md | bytes=7980 | sha256=5ede6a4411c2d48db418840e2a452730f081613e8444047e9d658f1e39aef986 057. [reference] [knowledge] Power-Dynamics.wiki/Imperfection-and-Plurality.md | bytes=960 | sha256=3f5b3664206a08d650006eea324cd11f0a2e98923e922e397599d63aefc69011 058. [reference] [knowledge] Power-Dynamics.wiki/Improvement-Support-and-Dominance.md | bytes=906 | sha256=4f0da892465299087446ce1a3badea68fd75fb0c5e79da828d9e2b329dc80e3d 059. [reference] [knowledge] Power-Dynamics.wiki/Information-Attention-and-Media-Power.md | bytes=1662 | sha256=75e078094492a1d10305b2379a13cd513e2fec903e00b42e52b012dbf10574e2 060. [reference] [knowledge] Power-Dynamics.wiki/KingCoin-Legacy-Stress-Test.md | bytes=594 | sha256=fa3fd6df782c33438691a7906d8fe378afa6da3b8f81e0884140d6e25b9166d1 061. [reference] [knowledge] Power-Dynamics.wiki/Know-Choose-Act-Remember.md | bytes=805 | sha256=fb18f61f705fe60e385c528a99e0f88d363bdda094cfae94d3487d46ba473a24 062. [reference] [knowledge] Power-Dynamics.wiki/kOA-Propagation-and-Adoption.md | bytes=917 | sha256=872f13b38f69e3b154e9807522f5f6e5ef15c5cbc24f49b6925cd26b25d1f7ff 063. [reference] [knowledge] Power-Dynamics.wiki/kOA-Returns-and-Compounding.md | bytes=793 | sha256=326b6ec61537b0774158e4656461df114f7cef6904b3e677fe3620661658d07c 064. [reference] [knowledge] Power-Dynamics.wiki/kOA-System-Map.md | bytes=2738 | sha256=22fc562715e30b05757696f106a46448e9b167bd3a19d8592350a0d4058a566e 065. [reference] [knowledge] Power-Dynamics.wiki/Koali-and-EkoH.md | bytes=1166 | sha256=c6f1b186f5897114bcc51a91eda3a03e32223d39a97bca2a215b0b2c804ca6ce 066. [reference] [knowledge] Power-Dynamics.wiki/Koali-From-Property-to-Protocol.md | bytes=1813 | sha256=04287abab64c470bf3f8ffe6d6cdc1622023181a2be88f1224eef0c9f8e552e9 067. [reference] [knowledge] Power-Dynamics.wiki/Konnaxion.md | bytes=618 | sha256=82b8ed21f1286879196aeee77bb7b66850649916b5d9a807cd228979a62d6a55 068. [reference] [knowledge] Power-Dynamics.wiki/Kristal.md | bytes=902 | sha256=03d87ab461823b7ccf26125999ac05a9ff61cdffb62a116d60d38408724f05fa 069. [reference] [knowledge] Power-Dynamics.wiki/Limitations-and-Open-Questions.md | bytes=3931 | sha256=548328643ddd5c8858396d8c47e5be15e7021e43bc82aede97a7da8bf7f743e4 070. [reference] [knowledge] Power-Dynamics.wiki/Media-and-State.md | bytes=536 | sha256=7d6c9443afba4ca3e88b9ff4467c5b8f013af10e54ea91e86dcd392d6a8395e9 071. [reference] [knowledge] Power-Dynamics.wiki/Mnemonic-and-Temporal-Power.md | bytes=1682 | sha256=5d19ded0adc57a0ac423ae7c45b0a34e846408bafe15db3ac21833a948cb237b 072. [reference] [knowledge] Power-Dynamics.wiki/Monetary-Credit-and-Liquidity-Power.md | bytes=1992 | sha256=c177e811c1ba22cc8ffb9cd4f792fac6b5b99f4ad16968d11b3cc0463b713a3d 073. [reference] [knowledge] Power-Dynamics.wiki/Narrative-Symbolic-and-Brand-Power.md | bytes=1689 | sha256=f6a916d2ef6d4a6658bea649221bdaa7b781613b191d118440ed74bc5161da5b 074. [reference] [knowledge] Power-Dynamics.wiki/Network-and-Affiliation-Power.md | bytes=1637 | sha256=2585fd17e4ba7f1960cbfd0411eecbf5547fcc914abaea93ef534b8a7fea1159 075. [reference] [knowledge] Power-Dynamics.wiki/Non-Domination-and-Terminality.md | bytes=665 | sha256=453d3983a709656f67f502aebbac6d5291a1c4369d7cf2cae28b392fb123c973 076. [reference] [knowledge] Power-Dynamics.wiki/Orgo.md | bytes=688 | sha256=ceb8a68110165b27ac1a44ca4f6035fc52ad22349b3c6eee9546a9cd69e2f7a0 077. [reference] [knowledge] Power-Dynamics.wiki/Political-and-Constitutional-Power.md | bytes=1979 | sha256=2d3fe0bc515ef228f47c68728e9820aad32c34b7419e61f3058f855e8c411863 078. [reference] [knowledge] Power-Dynamics.wiki/Political-Economic-and-Monetary-Power.md | bytes=4191 | sha256=6f9d908ef0388dd0ab3dd477ca701cd03a9420289e55802ebf260f19469b0c60 079. [reference] [knowledge] Power-Dynamics.wiki/Power-Analysis-Method.md | bytes=1511 | sha256=652db9f68234dac98474312e4dcedc0ea528b3b50865fc167155e742b3babf3d 080. [reference] [knowledge] Power-Dynamics.wiki/Power-Balance-Sheet.md | bytes=757 | sha256=8bfd41d34daf8b82a78be92e9b23b0acdc4a51c47f44cb81b49d30e860b036d6 081. [reference] [knowledge] Power-Dynamics.wiki/Power-Constitution.md | bytes=3015 | sha256=b7cfad9bb022f7c0caa0f40fc231a58ba30109cca88e59f779017c4efbc5f72e 082. [reference] [knowledge] Power-Dynamics.wiki/Power-Conversion-and-Routing-Map.md | bytes=2555 | sha256=65815d209058641a50b2c9ab8ef1889ecd2d0820db2564a73f56c50eeb302286 083. [reference] [knowledge] Power-Dynamics.wiki/Power-Conversion-Firewalls.md | bytes=731 | sha256=ffd727f27fdfecc4b402ca256909d24e434800c00e46c6878508712122d92648 084. [reference] [knowledge] Power-Dynamics.wiki/Power-Domains.md | bytes=3882 | sha256=b4e73b871adef9907fa4ede8188efae403f783129b7f3c9e546e1c470b46a27b 085. [reference] [knowledge] Power-Dynamics.wiki/Power-Ecology.md | bytes=2530 | sha256=6bc86fca35d0080bd9cd9230b68f46b96d11b620f6bf4f133ee75f9930a2d5cd 086. [reference] [knowledge] Power-Dynamics.wiki/Power-Relations.md | bytes=2561 | sha256=f6cc2f0289a9abd194c8dab0c4950f5215267afdca8dfb4481887e07a360b1d3 087. [reference] [knowledge] Power-Dynamics.wiki/Power-Routing-and-Sharing.md | bytes=5554 | sha256=f8e2c9fdcf2edea86c61d6eee8bbcb9974ff97a63adc29a2d6e4b5036a4ccba8 088. [reference] [knowledge] Power-Dynamics.wiki/Power-Routing-Audit.md | bytes=1029 | sha256=d1fcebdcafc3eca148b9721221371fb24153445d98887a6f26fe94c3bb6122a8 089. [reference] [knowledge] Power-Dynamics.wiki/Power-Show.md | bytes=7756 | sha256=5913915f92e232032a091226aa9ca918b6e14c63728a786788047b3544a3b974 090. [reference] [knowledge] Power-Dynamics.wiki/Power-Surface-Audit.md | bytes=2386 | sha256=b3bff62c9c7c406088a5eeda3dbca7dbce7cd9387a36b1cb2b7877ada78f99ef 091. [reference] [knowledge] Power-Dynamics.wiki/Power-Surface.md | bytes=6310 | sha256=323f34a853aa8979a2ab63b09b2d908acfbf37a48a5615d6088eecab6b9aee61 092. [reference] [knowledge] Power-Dynamics.wiki/Pre-Political-Power.md | bytes=1817 | sha256=ea4a11df856cb01534ffaedab5da23bf293894a6af9b02bf8bbaba0068bfa2ba 093. [reference] [knowledge] Power-Dynamics.wiki/Principles.md | bytes=8079 | sha256=a8a6938f0be48bde6c9e2913408d5856ef8f4e1cab9923c421c115849e394a24 094. [reference] [knowledge] Power-Dynamics.wiki/Propagation-Engine.md | bytes=1475 | sha256=f89b9beae2077c138e843a5a061e590d1e3205da016203c5b00df4004ce45c1a 095. [reference] [knowledge] Power-Dynamics.wiki/Property-and-Territorial-Power.md | bytes=1732 | sha256=650cfde9595c0cdb552de627db7a07f3fa1746b2642e9bc2cf1713c866a5d4c0 096. [reference] [knowledge] Power-Dynamics.wiki/README-WIKI-SETUP.md | bytes=1502 | sha256=053b2930edaf5492bd875f8705947b555502cc6a9ed8e87c0d47f00d3e106d42 097. [reference] [knowledge] Power-Dynamics.wiki/Recognition-Loop.md | bytes=576 | sha256=68aeccb83e793e842a50513b400559b583fa12ef9af411d96a0618ff048f1a93 098. [reference] [knowledge] Power-Dynamics.wiki/Recombination-and-Replacement.md | bytes=494 | sha256=81bd7135521b7da6a53f0022dc819a8db5ad7e0541cedbdaa8558a12fb2aeb6e 099. [reference] [knowledge] Power-Dynamics.wiki/Repository-Map.md | bytes=2636 | sha256=65d427388768bf69af76d9ac4931d06fc2c599f42047c84156ef76bbd6794b2b 100. [reference] [knowledge] Power-Dynamics.wiki/Research-and-Literature.md | bytes=4895 | sha256=5d7a407a321ea613c2f6fd46ce2f399790c16c6ee0be1697594ffb16cfcf5283 101. [reference] [knowledge] Power-Dynamics.wiki/Resources-and-Stocks.md | bytes=3457 | sha256=c993f7ed3618872a19a08deb9324be16387bc8918b64e03761d49379457d7dde 102. [reference] [knowledge] Power-Dynamics.wiki/Semantic-Layer.md | bytes=1634 | sha256=19eb164e5a166db1f90fe85dc9c97b63ac76cd68f312b007419414efd62749ee 103. [reference] [knowledge] Power-Dynamics.wiki/SmartVote-Discoverability.md | bytes=587 | sha256=efeb6f086cc424b5a552eeb18f5a4541584e17a9bfe2c36d580aa2604d32de0c 104. [reference] [knowledge] Power-Dynamics.wiki/SmartVote.md | bytes=2809 | sha256=44fec491acf0bdb2cae5352e733e9f6aa58eb46118a795d8c3daae4096b378da 105. [reference] [knowledge] Power-Dynamics.wiki/Sources-and-Provenance.md | bytes=3247 | sha256=da796110e0b6cd9ab8f9355680310421358c73260df61ff199c9e85ba040549a 106. [reference] [knowledge] Power-Dynamics.wiki/System-Power-Profile.md | bytes=2370 | sha256=15a0ccb16641acd38190612f01fa5cc94836458919f54ccc1e86fe84891c4846 107. [reference] [knowledge] Power-Dynamics.wiki/Technical-and-Infrastructural-Power.md | bytes=1705 | sha256=68c742c801066e44f2ef3f4a7943f60579905f20598b1c3bffe1718d0c4cb293 108. [reference] [knowledge] Power-Dynamics.wiki/Technical-Evidence-Map.md | bytes=3098 | sha256=0648675fa47471ccb58d7633a76ca1b043cf9071743ed9a2437f26b72b70dffe 109. [reference] [knowledge] Power-Dynamics.wiki/Three-Axis-Model.md | bytes=1974 | sha256=f073a9aa992679ae128b7686e836b845ce669a0c6b1010849cae139a5ddcf8fc 110. [reference] [knowledge] Power-Dynamics.wiki/Unpublished-Corpus-as-Epistemic-Reservoir.md | bytes=691 | sha256=a03b370e4c6a51b6db768f64eae738865a65c2d2b8b432bb22bbb3a88ae8dece 111. [reference] [knowledge] Power-Dynamics.wiki/Why-kOA-Is-Immensely-Powerful.md | bytes=3060 | sha256=c6bc40bbf7ab1da161e2a945385d7bce0931f15493887b4e5ba5ce970a1d9bbe 112. [reference] [knowledge] Power-Dynamics.wiki/Why-kOA-Is-Not-Just-Software.md | bytes=1595 | sha256=e8f00d490f73579cfe049cfedf23fb3fc551da5a9b0bcf817fedc8198d9b91c2 113. [reference] [knowledge] Power-Dynamics.wiki/WIKI-LINK-VALIDATION.md | bytes=1387 | sha256=445b3beb3cb2fe253b7dd179878dc5bd415e41c50243f4a7350d7d6067c04492 114. [reference] [knowledge] Power-Dynamics.wiki/Zero-Skim-Philanthropy.md | bytes=476 | sha256=846dc14a100728ec22625dd9554c4b548e9a5dad502a38a709d64092d1b20be0 115. [reference] [knowledge] power_dynamics/.github/ISSUE_TEMPLATE/concept-proposal.md | bytes=434 | sha256=03e6fe6d91967c4399635cdedf59617110ab2e63d77684bb0069af40a682ef58 116. [reference] [knowledge] power_dynamics/.github/ISSUE_TEMPLATE/power-audit.md | bytes=950 | sha256=63733dcce29792606a818da10da35e03bf9cd698283bd7793a60ff43ed1f8704 117. [reference] [knowledge] power_dynamics/.github/ISSUE_TEMPLATE/power-surface-audit.md | bytes=1091 | sha256=17f37e8979ea432c539b1f4c1fc9c56dc2c2d49a1ec6c1efccbf2468dc10405e 118. [reference] [knowledge] power_dynamics/.github/PULL_REQUEST_TEMPLATE.md | bytes=930 | sha256=ef84dafed953cfa966a1307edd6938b5699b7875f5834ffaac5a3bcfc158e2fb 119. [reference] [knowledge] power_dynamics/Academic-Lineage/01-power-dependence-and-domination.md | bytes=9405 | sha256=ff2886c0a534321f1e21341cd6ac9de7ffaa2dc97b2f8e7748f8787725a336a0 120. [reference] [knowledge] power_dynamics/Academic-Lineage/02-polycentric-governance-and-institutions.md | bytes=3237 | sha256=6ef6c06e48518a2366ec87d4930d19d625bb8a70d2347697691ee2f7a1ed178b 121. [reference] [knowledge] power_dynamics/Academic-Lineage/03-modularity-standards-and-path-dependence.md | bytes=4403 | sha256=808472e1512519aab57db4d3d5db7360806c75fc6d226ae086ef4a94b90fd9e0 122. [reference] [knowledge] power_dynamics/Academic-Lineage/04-open-source-exit-fork-and-peer-production.md | bytes=3257 | sha256=2eae3ea0c2b2f51c8dcec9f3aa0136ccf7e1a48c0850430c53d16ee02961f80a 123. [reference] [knowledge] power_dynamics/Academic-Lineage/05-network-power-and-social-capital.md | bytes=3106 | sha256=6fdcfdb8851ce80d92b1536440fa467acdc4a1023f03299ca32ced819d85e259 124. [reference] [knowledge] power_dynamics/Academic-Lineage/06-expertise-smartvote-and-collective-judgment.md | bytes=6269 | sha256=08675a176587e3ffa36e12360cbde82cd2a851002e0663ef7c91f8510eb6d460 125. [reference] [knowledge] power_dynamics/Academic-Lineage/07-metrics-reputation-and-gaming.md | bytes=2973 | sha256=46592989636864b14db948eed85bdedea51b830f5a830386e1a5a7c121c28d12 126. [reference] [knowledge] power_dynamics/Academic-Lineage/08-classification-infrastructure-and-code.md | bytes=3034 | sha256=dfc55292723cc35868017533eb3f6aeb698058a1b02b643f95c1efb23d2687be 127. [reference] [knowledge] power_dynamics/Academic-Lineage/09-epistemic-power-provenance-and-plurality.md | bytes=3607 | sha256=2a4abe1fc51c046003f341d282475d38d45bf48632798cdf7bdc3e6fda74614b 128. [reference] [knowledge] power_dynamics/Academic-Lineage/10-systems-cybernetics-and-adaptation.md | bytes=2607 | sha256=b48b810452f61eee92085628d8df085266d117b930ae9ca4ec3eb72d6bb62dce 129. [reference] [knowledge] power_dynamics/Academic-Lineage/11-collective-action-mobilization-and-diffusion.md | bytes=4225 | sha256=c70e65da377d522ccb3bc647133f20ba5f4b24e7d99eb05979cff155d1c313f6 130. [reference] [knowledge] power_dynamics/Academic-Lineage/12-capabilities-concerted-power-and-legibility.md | bytes=3313 | sha256=05d70ea188ee47db5354d671c30ee931e162a8d28c96f65c8ffebd77292f40d4 131. [reference] [knowledge] power_dynamics/Academic-Lineage/BIBLIOGRAPHY.md | bytes=11346 | sha256=3ccd73b299cdefeed569d9c7f56a129356ace2754367d44b216d7b69628c6f90 132. [reference] [knowledge] power_dynamics/Academic-Lineage/README.md | bytes=7015 | sha256=03802af9de883e16c79cbcc960d438a9e19a611ef92e25ad689d71d95095cdf0 133. [reference] [knowledge] power_dynamics/assessment/analysis-method.md | bytes=1223 | sha256=53431cb746023eef7f52b7258a2d046a51f0482fd2801a44c8976990c472c4ff 134. [reference] [knowledge] power_dynamics/assessment/branch-comparison.md | bytes=552 | sha256=d68c6361610c6bcd2a1234e6db3d39cd07331148eb6f61ddb9730d89139bd658 135. [reference] [knowledge] power_dynamics/assessment/capability-show-profile.md | bytes=2462 | sha256=37dbf1afb6d53556886274f04a950a00346ebc9d4a3651f86c8ea0fdfad3bce4 136. [reference] [knowledge] power_dynamics/assessment/constitutional-tests.md | bytes=712 | sha256=900e662557b831ee9d0416c4d450465ae5e91267d15553feb952c3743ff0c60c 137. [reference] [knowledge] power_dynamics/assessment/dependency-exit-audit.md | bytes=532 | sha256=c5ca609903634a7adf2769fa0d089e7e1460932322fe51428eb74d1be162d691 138. [reference] [knowledge] power_dynamics/assessment/flow-conversion-capture-audit.md | bytes=1246 | sha256=80998ac936fad5e6ca00e43d5921712516a859c55e84f106c5f4e0dc8dd5d62f 139. [reference] [knowledge] power_dynamics/assessment/power-balance-sheet.md | bytes=754 | sha256=a93483759c7dbaa42e4b181e8947fb6cb98ad2f7985dded0a89a9e4c00dea7b6 140. [reference] [knowledge] power_dynamics/assessment/power-routing-audit.md | bytes=2119 | sha256=01d594c96fad05dad77a5847946d52126cf263f94c95a522fd92e55ff4815dce 141. [reference] [knowledge] power_dynamics/assessment/power-surface-audit.md | bytes=2301 | sha256=3b8ff9c56ceaeba651951393249cb21ce9f6a6db21312d9fe96b69982434f778 142. [reference] [knowledge] power_dynamics/assessment/propagation-audit.md | bytes=2268 | sha256=6f8ac614742bc652b31f9038b4b1282d8ed799313f7927fa7b96673be2bd6646 143. [reference] [knowledge] power_dynamics/assessment/README.md | bytes=1429 | sha256=70ff429cda2f510210f6a1d63683462dd5cd1c7a96d21dbdc40cf653f6d77929 144. [reference] [knowledge] power_dynamics/assessment/system-profile.md | bytes=535 | sha256=69cf0ff0c73e3ea15c355187836de1d392b4798961fdd51779bfe9a542f298ad 145. [reference] [knowledge] power_dynamics/assessment/temporal-evolution.md | bytes=641 | sha256=56241585fa5d2f89d05ccc59cdc6243b661c9327b522294dac1f218a082e8134 146. [reference] [knowledge] power_dynamics/branch-ecology/branch-mobility.md | bytes=670 | sha256=b3b359d471ed714cf8c501aea2db6242317f345a405ef4dd7e38c73c90988d32 147. [reference] [knowledge] power_dynamics/branch-ecology/complementarity-and-antidogma.md | bytes=957 | sha256=364d86ab0d9f63adbd67aadd4be67f645b16c9559cce0c4e704eb7a314d2e424 148. [reference] [knowledge] power_dynamics/branch-ecology/improvement-support-dominance.md | bytes=977 | sha256=34737a5c599919734bc46b6cad75bb8bde2a8453871e6e0e897a2ad6b30f4642 149. [reference] [knowledge] power_dynamics/branch-ecology/lineage-and-competing-kristals.md | bytes=1078 | sha256=a309402aa928d404161eab52b45b6014ff725acc4891fa89c8d14e94e5b9dfbc 150. [reference] [knowledge] power_dynamics/branch-ecology/README.md | bytes=1231 | sha256=6db9733893795e13e0dcddadc85b7ba77760fd093b4d5aae42eb59ea00417f5b 151. [reference] [knowledge] power_dynamics/branch-ecology/recombination-replacement.md | bytes=529 | sha256=a65575b7586c37ac1a267a73283dd320b44c79ac8f6a953cdf858be6a13d0818 152. [reference] [knowledge] power_dynamics/cases/ai-hidden-sovereignty.md | bytes=629 | sha256=536d76bfefa83626d31f2a09b10f8e7fad59fca5b4c733e297ad8955afbc0181 153. [reference] [knowledge] power_dynamics/cases/bootstrap-koa.md | bytes=621 | sha256=53aefc26c8c6f45a1d48e3eef31df8e525e0c851c52b8289ba44320853ff67f2 154. [reference] [knowledge] power_dynamics/cases/brand-merchandise-affiliation.md | bytes=627 | sha256=102267fbc80e6226cbbd950d3f8971399c070639fee2443e569be3af1e2277c0 155. [reference] [knowledge] power_dynamics/cases/competing-kristals.md | bytes=1443 | sha256=001e5b6baa2cc42a73c5047fab2a82f80b3183b53e63f4d2d49619d12696d164 156. [reference] [knowledge] power_dynamics/cases/desjardins-stacking.md | bytes=596 | sha256=76e3ade5e1a4b49c44a998e8efbfe3cdd2fce27220dfb928ebe4fa47b496b603 157. [reference] [knowledge] power_dynamics/cases/epistemic-authority-corruption.md | bytes=3003 | sha256=c37e3a3471782fd70600f183220fdef3e54cf7812573c29860abdcc677532cf8 158. [reference] [knowledge] power_dynamics/cases/ethical-fiction-self-binding.md | bytes=4082 | sha256=58c2c385d224e50c13e4551dc24be37323e236b964ab3b9b2755397fb5aded75 159. [reference] [knowledge] power_dynamics/cases/founder-identity-optionality.md | bytes=608 | sha256=4b1748556ec1095fe39d72aeda05ee5ced1f4d4d5cfd2c95bfdf1c7af7384fd4 160. [reference] [knowledge] power_dynamics/cases/founder-opposition-rehearsal.md | bytes=3504 | sha256=2538cf15f94117bc8a5ec260e5955a28e9dac094c0667be9fc53e735b48a5e38 161. [reference] [knowledge] power_dynamics/cases/kingcoin-legacy-stress-test.md | bytes=631 | sha256=a502d7c9f7dabc1dcb67d10a9cc2a5fb387410cb22f61f05df4edc1cb89684b4 162. [reference] [knowledge] power_dynamics/cases/media-and-state.md | bytes=599 | sha256=56c01c0cc89cb7e936f581b7486efc16b80376e5d8eda059ca068e04cd1fc87a 163. [reference] [knowledge] power_dynamics/cases/README.md | bytes=1545 | sha256=66fd280c3c57985372922ebbb6e2d70183b1d75dde69dbb0273d93afc2ee521f 164. [reference] [knowledge] power_dynamics/cases/recognition-loop.md | bytes=623 | sha256=44f23f4d8fb4394c934f391867e458eb99949325c148c88d5326d5f90b2263f2 165. [reference] [knowledge] power_dynamics/cases/smartvote-discoverability.md | bytes=637 | sha256=9bdd6ad3b071ef0e3e8ed54c9bf1f11497eb93e70cef75e3f287e880c62feb9f 166. [reference] [knowledge] power_dynamics/cases/unpublished-corpus-reservoir.md | bytes=747 | sha256=29e2369982ab4cf802e04f9b4b3893a8a6891b1826413c119296e2568f6cfe9e 167. [reference] [knowledge] power_dynamics/cases/zero-skim-philanthropy.md | bytes=500 | sha256=bd34206ab66cb54f3ee3027d75954af27e94b852000ae2c077d7fbe08f064d46 168. [reference] [knowledge] power_dynamics/CHANGELOG.md | bytes=9063 | sha256=ae88fd85dfa4c271bc14c50b1d9fe15ca95fbe5348664fd5db26c5e245f253ff 169. [reference] [knowledge] power_dynamics/constitution/authority-architecture.md | bytes=1619 | sha256=8ece80483108c18b85c47dd0ac5e187d7507d9f307f840bfb3388889117c0537 170. [reference] [knowledge] power_dynamics/constitution/branch-evolution.md | bytes=897 | sha256=cc34a964e51576812c86ec85c96a89a75ec7764c2028727392c5aac515321ca3 171. [reference] [knowledge] power_dynamics/constitution/conversion-firewalls.md | bytes=1107 | sha256=db2b9f09eaa7c670a2487f599cd451b5fca80b9edd2e4a385e468eb3fe7a9963 172. [reference] [knowledge] power_dynamics/constitution/counterpowers-and-legibility.md | bytes=1603 | sha256=0c7155f9450b6390afa531d175b60739029cee85fe3e542ded9c1f7d90027b48 173. [reference] [knowledge] power_dynamics/constitution/federation-subsidiarity.md | bytes=674 | sha256=527ad2d9212d6e84f140adc995c96fbb25757af8a740bc0201efe39121c081b8 174. [reference] [knowledge] power_dynamics/constitution/founder-decentering.md | bytes=2313 | sha256=9f115b3b0e38563eef5cd994452affab4eae4b415e7df75f4f889741ee330b75 175. [reference] [knowledge] power_dynamics/constitution/non-domination-terminality.md | bytes=714 | sha256=6fc05944ad5d1f849f7adce22019174e4adb06017ff746a855e1b308f5752214 176. [reference] [knowledge] power_dynamics/constitution/power-redirection-sharing.md | bytes=3801 | sha256=963a87598e4a453fc732dcff16690574e8a0f0643df792e496855e699b7559bb 177. [reference] [knowledge] power_dynamics/constitution/README.md | bytes=1853 | sha256=b44adc345ae62721a692ef674dfdd1606de87f8ed8b6ed31eac4160556cc84b2 178. [reference] [knowledge] power_dynamics/constitution/revocability-exit-portability.md | bytes=1066 | sha256=19eda7fbdb5358adfec997df0037428aea244453485b0c59728aaf923783d686 179. [reference] [knowledge] power_dynamics/CONTRIBUTING.md | bytes=2587 | sha256=e0f9a34ac5236e4df6d90c3e36e2141895234132ec3e0b324010f15fc58b8fe1 180. [reference] [knowledge] power_dynamics/domains/01-political-constitutional.md | bytes=1704 | sha256=3c7bb0cfb688fb062bd1a8af51dc7c3bcd4eecd7d79a9d707424bae5e3801879 181. [reference] [knowledge] power_dynamics/domains/02-economic-allocation.md | bytes=1461 | sha256=fb3077e0edb0bfaac4ffb72eb67f5862debc1f98d72135e584e559de7a77fe60 182. [reference] [knowledge] power_dynamics/domains/03-monetary-credit.md | bytes=1303 | sha256=42d2d44ce08b9173e8d8f091a3b0ccbf3e44298d0253b40d9a52d2bb41a2f895 183. [reference] [knowledge] power_dynamics/domains/04-epistemic-semantic.md | bytes=1480 | sha256=9525cb058fe7c0abf741e7d7f39cc4d98d105c7ad8558e0b11b51f6505d4e50a 184. [reference] [knowledge] power_dynamics/domains/05-information-attention-media.md | bytes=981 | sha256=4dd7f7dabfd647511f55881bf36c943f8d66940a73bc73d1c88d309a38e695ca 185. [reference] [knowledge] power_dynamics/domains/06-credibility-reputation.md | bytes=1863 | sha256=19fdba100531596dbb055a73f70192ffd03cd22a8259dba8e4e2ecb7cb9d65e0 186. [reference] [knowledge] power_dynamics/domains/07-network-affiliation.md | bytes=1006 | sha256=568aec0bae262b1d03069a02ac0b36bfd37d31562b0a7e6d8924e23ca025fdae 187. [reference] [knowledge] power_dynamics/domains/08-administrative-operational.md | bytes=972 | sha256=c71835c94f154835ee9d1bdabb694340854026e3f9ba3bee1fb45e801c6cb8e4 188. [reference] [knowledge] power_dynamics/domains/09-technical-infrastructural.md | bytes=1000 | sha256=7b6d00d9690ab770774eba0b8ce240360dae0b582fcf1e7571ccb78025a1b58f 189. [reference] [knowledge] power_dynamics/domains/10-narrative-symbolic-brand.md | bytes=1244 | sha256=05e1bbc7047ab8d87f954fad1ee80557f70f15665765091dfa790cbb7d1550e1 190. [reference] [knowledge] power_dynamics/domains/11-cognitive-ai.md | bytes=998 | sha256=ff5193c9011f452360b13cea360dfafa25993cb3f20038782e7bc9262d800003 191. [reference] [knowledge] power_dynamics/domains/12-mnemonic-temporal.md | bytes=1039 | sha256=03f313f6fdcc0c83e16c37620efd7735ad65ec81d9fb851fc62b3a0d055816e6 192. [reference] [knowledge] power_dynamics/domains/13-evolutionary-counterpower.md | bytes=1070 | sha256=a1264bbd73d7fb42e3eeeb812d8ac0f4c0000943b3b001244eb66d498ede37e3 193. [reference] [knowledge] power_dynamics/domains/14-property-territorial.md | bytes=1188 | sha256=8e8a26b5f79e46a11019a471afb7dd04ab5afa2496b50b7158281e57c2c22dda 194. [reference] [knowledge] power_dynamics/domains/README.md | bytes=3688 | sha256=1ddb0c150e52335bf55393a7f38b5bdfb801921ad1e72869481d192c018ed721 195. [reference] [knowledge] power_dynamics/dynamics/01-formation.md | bytes=860 | sha256=a61f69fc3f729ac0b0fd83ea0847e05c628d2fa9f92c4f6958f75fddbdf51317 196. [reference] [knowledge] power_dynamics/dynamics/02-mobilization.md | bytes=1275 | sha256=f94d268e3a4ad7117d2e0e79892a9fb239d1616f540729b8a89caab4b6c9a9c0 197. [reference] [knowledge] power_dynamics/dynamics/03-composition-generated-puissance.md | bytes=986 | sha256=cf4739b0f5ebb549a04fdaba4610b3f115d5c897a5f9d7c0acdf03c5323a310a 198. [reference] [knowledge] power_dynamics/dynamics/04-conversion-and-firewalls.md | bytes=1324 | sha256=c400a2ce7708722101609a0fa8a47307fc51e97935bfcd83c18c46a085a45b47 199. [reference] [knowledge] power_dynamics/dynamics/05-returns-reinvestment-compounding.md | bytes=1123 | sha256=8e10b507e845a6405d67fe9554448c5a68992ded63254ed0e47431fe7c0749e2 200. [reference] [knowledge] power_dynamics/dynamics/06-concentration-stacking-capture.md | bytes=1234 | sha256=d9167a5bd723ecc7b4e248b36748f21f15431934a517429d27874210573d4166 201. [reference] [knowledge] power_dynamics/dynamics/07-counterpower-contestation-exit.md | bytes=1671 | sha256=a0c76c6f518214e732985cd8889cedad7851663d50f0bc761bdb9e1d3e4ddcaa 202. [reference] [knowledge] power_dynamics/dynamics/08-diversification-and-evolution.md | bytes=1011 | sha256=958d7114aca1b0af225408f6e2393704395b9320ebb57812c683d2a6c140ed2f 203. [reference] [knowledge] power_dynamics/dynamics/09-decay-dissipation-and-loss.md | bytes=954 | sha256=e7da359c4b23f9007aa125f34f3d2f0f5b009a020194088b18802aae12b02956 204. [reference] [knowledge] power_dynamics/dynamics/10-transfer-succession-and-inheritance.md | bytes=981 | sha256=4a0b2158560933c5f61cd0ebaa7b5fd4138086bc6561b18253a0d8f07ab2b00e 205. [reference] [knowledge] power_dynamics/dynamics/11-externalities-and-scale.md | bytes=1173 | sha256=ab8e38798b3fe58b6afb1ccc37c728eebee4236027dd3937567b62d723f1c8d2 206. [reference] [knowledge] power_dynamics/dynamics/12-routing-sharing-and-devolution.md | bytes=2129 | sha256=5379152d1e96c65af324734bc2206646364699b2dc65d341bc4074a8ded68212 207. [reference] [knowledge] power_dynamics/dynamics/13-propagation-and-coupled-loops.md | bytes=1503 | sha256=ee4827f0a57bdcdf84e08b784be1001f9a9e660155680b58616c118ce2948609 208. [reference] [knowledge] power_dynamics/dynamics/README.md | bytes=2908 | sha256=b8a53758ff655ca3abcc77d9815fd21e124d124d911fbe562aae9ff0fb11abfa 209. [reference] [knowledge] power_dynamics/framework/00-field-definition.md | bytes=2984 | sha256=949eebb55338782bd723df4447fbce37a76cc92a2e2ba0615c0b4dbba99d0e74 210. [reference] [knowledge] power_dynamics/framework/01-core-ontology.md | bytes=1563 | sha256=9870cedcd7e56114d37d52ca5d514ef2fdd4491867c31965bb98e99bc275279b 211. [reference] [knowledge] power_dynamics/framework/02-effective-possibility.md | bytes=1220 | sha256=4fe40c6b06581229e61ff0d45eacfb14c0e7a5162bf3c792855b383fb3839186 212. [reference] [knowledge] power_dynamics/framework/03-three-axis-model.md | bytes=1124 | sha256=d98ab9f724a383157d84f1906ec4fc0990e1783d0ea032acabe0da5a05f81d06 213. [reference] [knowledge] power_dynamics/framework/04-power-ecology.md | bytes=2630 | sha256=c18ba690b0bd08794ea8fe9a63cc2d0fbd32a521c590b6acaaeaab0043b90665 214. [reference] [knowledge] power_dynamics/framework/05-pre-political-chain.md | bytes=1084 | sha256=137833c4bb9bee00cf252bdd3b9ecf7c8c6b3326d1978065691b18875ea68f30 215. [reference] [knowledge] power_dynamics/framework/06-stock-capacity-flow-return.md | bytes=1011 | sha256=d34c73c5ad6f1b07cd1c921b79bab3c0e2b6f42630966c05d966662e04f956ea 216. [reference] [knowledge] power_dynamics/framework/07-imperfection-and-plurality.md | bytes=1020 | sha256=90a7d912e0cca2dbdb137b1212102e8f3bf43435bc527e11230aaf44abd94e3e 217. [reference] [knowledge] power_dynamics/framework/08-constitutional-thesis.md | bytes=1631 | sha256=0b8841e37581d3ef849495e885e94c31c14ad0e342276d569a13e76502787ee7 218. [reference] [knowledge] power_dynamics/framework/09-power-routing-and-sharing.md | bytes=4893 | sha256=19fc6658b7ec0a37dffe5ad520f2cddf4061f1a750c20737395b8007bfc053da 219. [reference] [knowledge] power_dynamics/framework/10-cross-domain-power-conversion.md | bytes=3375 | sha256=22d6aeadbe8a2b6f82d5897adee1e56d79cb1c63144c7b9ca62099f5157399fa 220. [reference] [knowledge] power_dynamics/framework/README.md | bytes=1373 | sha256=ca75bfafa4e1975588bf8e8ce28cee259ad0f857ab5acff147213b5dc3d53654 221. [reference] [knowledge] power_dynamics/GLOSSARY.md | bytes=34710 | sha256=b56812c85cc4c07007f0957c38a9d5f62fcf0ab744d1b5d3b61ab90ff49afb0d 222. [reference] [knowledge] power_dynamics/history/central-correction-to-nondomination.md | bytes=893 | sha256=d26db69f5cafec0f5787cbf247a2275823049102b2e27f61c8686fcc5c7c77bf 223. [reference] [knowledge] power_dynamics/history/dependency-to-empowerment.md | bytes=830 | sha256=9659d2d8a4950bb49be56c7046a2a061003e4340803dd06d04a25e6f1ae6e7f6 224. [reference] [knowledge] power_dynamics/history/founder-to-protocol.md | bytes=583 | sha256=c57200716fcc6386bd319ecc87127be2a4a8ea87327b4fba420bf36beb28149b 225. [reference] [knowledge] power_dynamics/history/README.md | bytes=812 | sha256=c7d8393007d030196a56c8c56500ac34180cd16b8aefd5c09f301682be6cc647 226. [reference] [knowledge] power_dynamics/koa/ai.md | bytes=785 | sha256=ab870e24420c7cc24af7b03ff2fa7ce0e5c040092f10b9d365d47b0dc7689dfe 227. [reference] [knowledge] power_dynamics/koa/brand-narrative.md | bytes=2020 | sha256=4b6f0f38f63a2e5aba46b8cb8568aec777367a879946a2c53fedabe8e5f89934 228. [reference] [knowledge] power_dynamics/koa/capsules-federation.md | bytes=748 | sha256=5f7141814fdd72fb928797af1a01609474e4c9238dae5814f1b5d139160a6da8 229. [reference] [knowledge] power_dynamics/koa/founder-power.md | bytes=1704 | sha256=429a699d468fda6f72f3ae55cab9302a4cd07221040f89acae6d9c65365b6ec7 230. [reference] [knowledge] power_dynamics/koa/know-choose-act-remember.md | bytes=851 | sha256=19d458a56e5a45596e10a640842ecf2a6cdf0768d88cb7464326141ed86e8366 231. [reference] [knowledge] power_dynamics/koa/koali-ekoh.md | bytes=1264 | sha256=3b3a2be42815858d6a082e336531f8b45035da456a7943162ddebb273ccd3304 232. [reference] [knowledge] power_dynamics/koa/koali-protocolization.md | bytes=3208 | sha256=18bc122c87356df1b913e2398358bfffdb479f929d9efa2de24a351591a5201f 233. [reference] [knowledge] power_dynamics/koa/konnaxion.md | bytes=660 | sha256=8074805970509a45962d51579ceb2d1e28871ec215760bc161089881e9e7283f 234. [reference] [knowledge] power_dynamics/koa/kristal.md | bytes=1578 | sha256=13435ad31e387e5c3d62725fc271107d961833f0ced0f9ce537bb80a83df1acd 235. [reference] [knowledge] power_dynamics/koa/multilingualism.md | bytes=737 | sha256=0c4a5f1f643ef572ee43abc049aa8d300b760eca8a8e56132d1f317bdadb963a 236. [reference] [knowledge] power_dynamics/koa/orgo.md | bytes=730 | sha256=bc94b509262a72041622b41c58312043e208541f0d55c1680f525a8ac4de85ec 237. [reference] [knowledge] power_dynamics/koa/propagation-adoption.md | bytes=2690 | sha256=3374d9d890488aefb3529717d0e73ddb74bc0d10283440f5d258c4decd396201 238. [reference] [knowledge] power_dynamics/koa/README.md | bytes=2694 | sha256=44d066857b307ebfe64f3fe58ed41aa32688494fc604353fca05aa03f9a44f6d 239. [reference] [knowledge] power_dynamics/koa/returns-compounding.md | bytes=843 | sha256=097ef104342a19dfa62307c58c3117784f6a107c24c0cd930a12f6e59bcd560b 240. [reference] [knowledge] power_dynamics/koa/semantik-sentient.md | bytes=774 | sha256=f3c3247eac7a2b9a5882c346abd57a717981b6b2976cf582cf50c78bbedfed07 241. [reference] [knowledge] power_dynamics/koa/smartvote.md | bytes=1839 | sha256=f92a7961e46d6ce73fcde78b30d2540a15f63e919f2988ba71b1590cf5a76849 242. [reference] [knowledge] power_dynamics/koa/system-map.md | bytes=3032 | sha256=9c151ee921ca860734ab06a1d9cc39797bff7b360f0efb23b400dad378ca9392 243. [reference] [knowledge] power_dynamics/LICENSE.md | bytes=336 | sha256=266e240dcb7657e8290e0cea2f8115617834c7a20b8db11a61c033bf0a8a0ea7 244. [reference] [knowledge] power_dynamics/POWER-ROUTING.md | bytes=5814 | sha256=88caf4a93bbbdd6daedb0b46411ecd0c7fa9a23e49165acceabbd35eeb9e1a06 245. [reference] [knowledge] power_dynamics/POWER-SHOW.md | bytes=8643 | sha256=430ec4f29fab36df9d43d02f9d0c199b411226d4766c09c64bcf272d9c30d1d3 246. [reference] [knowledge] power_dynamics/POWER-SURFACE.md | bytes=6573 | sha256=1181145076011b3b1fcccf9ebfe7e44dc3862aa04451969be28540b80047491d 247. [reference] [knowledge] power_dynamics/PRINCIPLES.md | bytes=10732 | sha256=6533284462887d2515c96f69e764ce3bb7e4691bd231fc85a7d8b688517efa97 248. [reference] [knowledge] power_dynamics/PROPAGATION.md | bytes=9810 | sha256=70bac184193365bf8c050a6232c2dff1cd4467fcd3c3333681b30074e676f0b4 249. [reference] [knowledge] power_dynamics/propagation/00-field-definition.md | bytes=2117 | sha256=60293d166de5a94feeeb77e9d68d358d64fa33f13d75d51d8b3d847f07fb9bf7 250. [reference] [knowledge] power_dynamics/propagation/01-coupled-feedback-loops.md | bytes=2382 | sha256=ae4c5be6081bd065829b70b1d7445d1b7b0be9c949f02ab0df175fc619f0f6de 251. [reference] [knowledge] power_dynamics/propagation/02-adoption-stack.md | bytes=2082 | sha256=e1532570915cc74098ad544a6e636d5f75c5115441389e2fb4c701be6c72f237 252. [reference] [knowledge] power_dynamics/propagation/03-cross-branch-returns.md | bytes=2014 | sha256=7d9fec4487567b496cf3993b74449c4a751e4a1c87693be51cd668263245b974 253. [reference] [knowledge] power_dynamics/propagation/04-distribution-surfaces.md | bytes=2415 | sha256=43847c9dc78f08d43be3b8f9fcb86722af8dbbe99a4c3ed6ac8eefbf20ade510 254. [reference] [knowledge] power_dynamics/propagation/05-autonomy-and-founder-absence.md | bytes=1904 | sha256=75089851dbc09f16e85d7f64a2527f855a26aeb22c2fad07c1d11cf6d20ce269 255. [reference] [knowledge] power_dynamics/propagation/06-damping-and-runaway-prevention.md | bytes=2449 | sha256=1ae882df0d831935de3df2294a1cf2a0c6ded85f5442d9f83840499da80c5267 256. [reference] [knowledge] power_dynamics/propagation/07-metrics-and-falsification.md | bytes=2876 | sha256=6092320596edd86bfdb49bf450a9f098702f9750ade4370ce803c7c04b64807a 257. [reference] [knowledge] power_dynamics/propagation/08-koa-loop-catalog.md | bytes=3494 | sha256=640c5e590f57e1842a0ee5151823fa44b962c3b1ead52d6c62dba5e7e390d71d 258. [reference] [knowledge] power_dynamics/propagation/README.md | bytes=1748 | sha256=317384fb5a41ca692c33e37de7432d8feb0ee4485da5d8c6e0f3d7e027b427c8 259. [reference] [knowledge] power_dynamics/puissance/README.md | bytes=2425 | sha256=f5f93e33c679cb57cde5f24f1390492ed0c38e2c298bcaf1b6312a57c0846aee 260. [reference] [knowledge] power_dynamics/README.md | bytes=16514 | sha256=e571ff7aaf4cbdc39e5157d2dcae586d274755fabf4f62a10814b7fc8a26aeca 261. [reference] [knowledge] power_dynamics/relations/README.md | bytes=2479 | sha256=cc74e02ab75c34bb299cdbe65ec037f5a1404ddb8992fdf9b9bda95993833b7b 262. [reference] [knowledge] power_dynamics/research/disciplinary-map.md | bytes=1092 | sha256=e391e0dd2b7de8023a0122696574c11c3e394277e05bb981db1074a6693c5127 263. [reference] [knowledge] power_dynamics/research/literature-roadmap.md | bytes=2247 | sha256=14e86349571c627e90abee058a1226eb6a259a79f3d4ac9ccb63c9083334daa9 264. [reference] [knowledge] power_dynamics/research/README.md | bytes=812 | sha256=804a646584375d90c0244945e7e71d6570d343a99bd6ef37e41d153b52cfce5f 265. [reference] [knowledge] power_dynamics/resources/README.md | bytes=2348 | sha256=b37b3f776c012b5887ba1c8ab3e12304ba9c2d88619e4c8bba9090a7231767bf 266. [reference] [knowledge] power_dynamics/showcase/00-why-koa-is-immensely-powerful.md | bytes=3009 | sha256=0a1fccf6b937e23151c8aaea09bd8911006d7283d77784e0e0ffce55933e5d0f 267. [reference] [knowledge] power_dynamics/showcase/01-capability-spectrum.md | bytes=5041 | sha256=35b55929ff2b0c72fa186e621f04f28252d3ab6b7212764d60a24e567666c02e 268. [reference] [knowledge] power_dynamics/showcase/02-individual-to-federation.md | bytes=2040 | sha256=290c6243729f0a72c2aaa460f2ab40d650cfc1caffcb3b902665eaab4277289a 269. [reference] [knowledge] power_dynamics/showcase/03-composition-engine.md | bytes=2656 | sha256=21484ccca187161d98d85a37863b2e2f75a62727a5346f9edaa1ff5456c2360c 270. [reference] [knowledge] power_dynamics/showcase/04-compounding-engine.md | bytes=2187 | sha256=ad794216140bce451fdd6a6aa1097b07c72ec8b3beea0911cad5917f1413fad2 271. [reference] [knowledge] power_dynamics/showcase/05-conversion-chains.md | bytes=1962 | sha256=685e187411bf0031df6a2448c701da8bbbec180ba64abf73bc7a571151c64769 272. [reference] [knowledge] power_dynamics/showcase/06-pre-political-chain.md | bytes=1879 | sha256=79880e420eb4dad94ae0f356e33737d89bac6d0bf40a21fb79e85ac463faead4 273. [reference] [knowledge] power_dynamics/showcase/07-component-power-matrix.md | bytes=3864 | sha256=03f8ba9c591f24548dda658e517bd6c1f41101d2356bf824212eb509b7f41008 274. [reference] [knowledge] power_dynamics/showcase/08-governance-after-capability.md | bytes=3019 | sha256=ff1fc042f49f177f186981568bc76ffcb466e0cd2b4e84ad5c7c70ecf7b4ab4f 275. [reference] [knowledge] power_dynamics/showcase/09-why-this-is-not-just-software.md | bytes=1632 | sha256=6c0ee039801c0a22660b0434583316f625eae068a7cdc4a460e26f956fda1c39 276. [reference] [knowledge] power_dynamics/showcase/10-counterpower-and-optionality.md | bytes=2279 | sha256=8b0b9d1f41d7da968e241220d2ca8e23c20e76e2f9c56fe0d623f596fd476541 277. [reference] [knowledge] power_dynamics/showcase/11-power-routing-and-sharing.md | bytes=6924 | sha256=70a24e3ef1ff1216276eccec6fcae8cf62af4e5cf8115942ec8046348c9d1152 278. [reference] [knowledge] power_dynamics/showcase/12-cross-domain-power-surface.md | bytes=2753 | sha256=f547049898911bc48d4926ead1552d86a78cd86031b2086d28928f14110f9701 279. [reference] [knowledge] power_dynamics/showcase/13-political-economic-monetary-power.md | bytes=4044 | sha256=729a6d1736bf24e898c8fe6badbb9005c91d8cc54d8dcf64cccdfb950882a304 280. [reference] [knowledge] power_dynamics/showcase/14-power-conversion-and-routing-map.md | bytes=3572 | sha256=23b45d217d5ec37956edddffe04f707613e262cdae073260fbb81bd99a381bfd 281. [reference] [knowledge] power_dynamics/showcase/15-propagation-engine.md | bytes=1877 | sha256=542797cb657ea8785d4b15c3633537f06b5e649c2ea4e50d65b9682fb23bd332 282. [reference] [knowledge] power_dynamics/showcase/README.md | bytes=2496 | sha256=d0922f1c0084a093282f0cddc37714f525338e4abeebf3b6c8a48526ab9591fd 283. [reference] [knowledge] power_dynamics/sources/architect-confirmed-design-notes.md | bytes=4305 | sha256=1ffe789263ea505063407bd8d0586203a7611e99806f0137f45bd564ffac6301 284. [reference] [knowledge] power_dynamics/sources/concept-origin-map.md | bytes=4085 | sha256=10f8496b1e4bef109ddbb3e72239130eff4c883d5442a85d64459b4e75577a22 285. [reference] [knowledge] power_dynamics/sources/corpus-map.md | bytes=6276 | sha256=aba8e13c36dc5bb2eb34b31ff744fd4774b6b71777bda34d49e2ea34476b347f 286. [reference] [knowledge] power_dynamics/sources/epistemic-rules.md | bytes=1330 | sha256=5996d25b1b9a2a16439ca79d252937c7cd02f50191958e5554cf2725cb537a95 287. [reference] [knowledge] power_dynamics/sources/propagation-design-notes.md | bytes=4892 | sha256=a9bbe85f3df1f51870ab1d2562f7da4939e19f68be3b30ea9c83b3db429dcd6b 288. [reference] [knowledge] power_dynamics/sources/README.md | bytes=694 | sha256=201f82c96bf093f036c5fe3d1c6c169333099ad57745e67e3a51a3aaa32acea0 289. [reference] [knowledge] power_dynamics/sources/source-status.md | bytes=804 | sha256=b23eac9463b2ad1aaea717986127110ca02978e5aa4367916e8fe0b5e7427b38 290. [reference] [knowledge] power_dynamics/sources/technical-evidence-map.md | bytes=3056 | sha256=eee327112e5ff10c27eb4d204670b31e83f14b2994cd4148f3d5e56566da2b9f 291. [reference] [knowledge] power_dynamics/STATUS.md | bytes=5798 | sha256=c944106b9870c900b46757d4ac267f5557db0bd0216c5d14c0de49d4947e065a 292. [reference] [knowledge] power_dynamics/TREE.md | bytes=8828 | sha256=eb595d93a25a6fb4e94653359ae16f6a282b5e95aa94ed044d332ed3b32e4b74 ================================================================================================ FILE: Power-Dynamics.wiki/_Footer.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 199f5bb2d286946ccc1cbecb8c6b621c236cc82a9664321baafdd83bbcb6b177 CONTENT_BYTES: 196 ================================================================================================ **Power Dynamics v6.2** · [Power Surface](Power-Surface) · [Power Show](Power-Show) · [Power Routing](Power-Routing-and-Sharing) · [Academic Lineage](Academic-Lineage) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/_Sidebar.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ebe816913fbf50be40cb2c603de7b8cdaacc3e0eca547c5e1a597083b6bc66f1 CONTENT_BYTES: 5020 ================================================================================================ # Power Dynamics v6.3 **Start** - [Home](Home) - [Getting Started](Getting-Started) - [Why kOA Is Immensely Powerful](Why-kOA-Is-Immensely-Powerful) - [The kOA Power Show](Power-Show) **Power Surface** - [Power Surface Map](Power-Surface) - [Power Domains](Power-Domains) - [Political / Economic / Monetary](Political-Economic-and-Monetary-Power) - [Political & Constitutional](Political-and-Constitutional-Power) - [Economic & Allocation](Economic-and-Allocation-Power) - [Monetary / Credit / Liquidity](Monetary-Credit-and-Liquidity-Power) - [Cross-Domain Conversion](Cross-Domain-Power-Conversion) - [Conversion + Routing Map](Power-Conversion-and-Routing-Map) **Capability Engines** - [Capability Spectrum](Capability-Spectrum) - [Individual → Federation](From-Individual-to-Federation) - [Composition Engine](Composition-Engine) - [Compounding Engine](Compounding-Engine) - [Propagation Engine](Propagation-Engine) - [Conversion Chains](Conversion-Chains) - [Pre-Political Power](Pre-Political-Power) - [Component Power Matrix](Component-Power-Matrix) - [Why kOA Is Not Just Software](Why-kOA-Is-Not-Just-Software) **Routing & Constitution** - [Power Routing & Sharing](Power-Routing-and-Sharing) - [Ethical Fiction & Self-Binding](Ethical-Fiction-as-Self-Binding) - [Koali: Property → Protocol](Koali-From-Property-to-Protocol) - [Power Constitution](Power-Constitution) - [Authority Architecture](Authority-Architecture) - [Conversion Firewalls](Power-Conversion-Firewalls) - [Counterpowers & Legibility](Counterpowers-and-Legibility) - [Counterpower & Optionality](Counterpower-and-Optionality) - [Non-Domination & Terminality](Non-Domination-and-Terminality) - [Exit, Portability & Federation](Exit-Portability-and-Federation) - [Founder Decentering](Founder-Decentering) **Theory** - [Core Ontology](Core-Ontology) - [Effective Possibility](Effective-Possibility) - [Three-Axis Model](Three-Axis-Model) - [Power Ecology](Power-Ecology) - [Resources & Stocks](Resources-and-Stocks) - [Forms of Puissance](Forms-of-Puissance) - [Power Relations](Power-Relations) - [Dynamics](Dynamics) - [Imperfection & Plurality](Imperfection-and-Plurality) - [Principles](Principles) **Evolution** - [Branch Ecology](Branch-Ecology) - [Branch Mobility](Branch-Mobility) - [Complementarity & Kristals](Complementarity-Branches-and-Kristals) - [Improvement, Support & Dominance](Improvement-Support-and-Dominance) - [Recombination & Replacement](Recombination-and-Replacement) **kOA** - [kOA System Map](kOA-System-Map) - [Know → Choose → Act → Remember](Know-Choose-Act-Remember) - [Kristal](Kristal) - [Konnaxion](Konnaxion) - [Koali & EkoH](Koali-and-EkoH) - [SmartVote](SmartVote) - [Orgo](Orgo) - [Semantic Layer](Semantic-Layer) - [AI & Cognitive Puissance](AI-and-Cognitive-Puissance) - [Capsules & Federation](Capsules-and-Federation) - [Brand, Founder & Optionality](Brand-Founder-and-Optionality) - [Returns & Compounding](kOA-Returns-and-Compounding) - [Propagation & Adoption](kOA-Propagation-and-Adoption) **Audit** - [Power Surface Audit](Power-Surface-Audit) - [Power Routing Audit](Power-Routing-Audit) - [Capability Show Profile](Capability-Show-Profile) - [Power Analysis Method](Power-Analysis-Method) - [System Power Profile](System-Power-Profile) - [Power Balance Sheet](Power-Balance-Sheet) - [Constitutional Tests](Constitutional-Tests) **Cases & Evidence** - [Case Studies](Case-Studies) - [Zero-Skim](Zero-Skim-Philanthropy) - [KingCoin Stress Test](KingCoin-Legacy-Stress-Test) - [Desjardins Stacking](Desjardins-Power-Stacking) - [Sources & Provenance](Sources-and-Provenance) - [Corpus Map](Corpus-Map) - [Technical Evidence Map](Technical-Evidence-Map) - [Research & Literature](Research-and-Literature) **Academic Lineage** - [Overview](Academic-Lineage) - [Power & Dependence](Academic-Lineage-01-Power-Dependence-and-Domination) - [Polycentric Governance](Academic-Lineage-02-Polycentric-Governance-and-Institutions) - [Modularity & Standards](Academic-Lineage-03-Modularity-Standards-and-Path-Dependence) - [Exit, Fork & Peer Production](Academic-Lineage-04-Open-Source-Exit-Fork-and-Peer-Production) - [Network Power](Academic-Lineage-05-Network-Power-and-Social-Capital) - [Expertise & SmartVote](Academic-Lineage-06-Expertise-SmartVote-and-Collective-Judgment) - [Metrics & Gaming](Academic-Lineage-07-Metrics-Reputation-and-Gaming) - [Infrastructure & Code](Academic-Lineage-08-Classification-Infrastructure-and-Code) - [Epistemic Power](Academic-Lineage-09-Epistemic-Power-Provenance-and-Plurality) - [Systems & Cybernetics](Academic-Lineage-10-Systems-Cybernetics-and-Adaptation) - [Mobilization & Diffusion](Academic-Lineage-11-Collective-Action-Mobilization-and-Diffusion) - [Capabilities & Legibility](Academic-Lineage-12-Capabilities-Concerted-Power-and-Legibility) - [Bibliography](Academic-Lineage-Bibliography) **Reference** - [Glossary](Glossary) - [Limitations & Open Questions](Limitations-and-Open-Questions) - [Repository Map](Repository-Map) - [FAQ](FAQ) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-01-Power-Dependence-and-Domination.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 3e351b0f6fe9e91ee383d80c0764790545e4225441f49ec1d9411eda0270ef13 CONTENT_BYTES: 9383 ================================================================================================ # Power, Dependence, Domination, and Conversion This lineage is the closest academic neighbor to the repo's distinction between **capability** and **relational power**. ## Robert A. Dahl — relational power Dahl's 1957 formulation treats power as a relation in which A can affect B's behavior. This is a useful baseline for Power Dynamics because it rejects `power = possession` and directs attention toward **relations, scope, and effects**. **Correspondence:** `Resource → Potential → Capacity → Puissance → Power Relation → Effect`. **Limit:** Dahl's behavioral formulation is narrower than Power Dynamics' interest in agenda formation, infrastructures, dependency, and latent possibility. Reference: Robert A. Dahl, “The Concept of Power,” *Behavioral Science* 2(3), 1957. https://doi.org/10.1002/bs.3830020303 ## Bachrach & Baratz; Steven Lukes — visible decisions are not the whole power surface Bachrach and Baratz's “two faces” argument expands power analysis beyond observable decisions to **nondecision and agenda control**. Lukes' later three-dimensional account adds preference-shaping and forms of domination that may not present as open conflict. **Correspondence:** the **pre-political chain** in Power Dynamics: classification, discoverability, ranking, agenda formation, defaults, and legitimacy can shape outcomes before a formal vote occurs. **Design implication:** an audit that only inspects formal decision rights will miss important upstream power. References: - Peter Bachrach and Morton S. Baratz, “Two Faces of Power,” *American Political Science Review* 56(4), 1962. https://doi.org/10.2307/1952796 - Steven Lukes, *Power: A Radical View*, first published 1974; later editions expand the argument. https://www.bloomsbury.com/ca/power-9781350544758/ ## Richard M. Emerson — power-dependence relations Emerson's 1962 theory is exceptionally close to the repo's dependency logic: power emerges from a relation in which one actor depends on resources, services, or opportunities controlled by another, and dependence is reduced when meaningful alternatives exist. **Correspondence:** - `Strong capability. Weak sovereignty.` - `credible exit`; - substitutability; - alternative providers / branches; - dependency-exit audits; - founder decentering through reproducibility. **Design implication:** for each critical capability, ask not only *who can provide it?* but also *who becomes dependent on that provider, and what alternatives remain viable?* Reference: Richard M. Emerson, “Power-Dependence Relations,” *American Sociological Review* 27(1), 1962, pp. 31–41. https://www.jstor.org/stable/2089716 ## Cook, Emerson, Gillmore & Yamagishi — network structure changes power Cook et al. experimentally studied power in exchange networks and found that simple centrality measures can fail where dependency structure predicts power more accurately. **Correspondence:** Power Dynamics should not infer `most connected = most powerful`. Network power depends on **alternatives, scarcity, exchange structure, and dependency topology**. **Design implication:** network audits should combine centrality with dependency / substitutability measures. Reference: Karen S. Cook, Richard M. Emerson, Mary R. Gillmore, and Toshio Yamagishi, “The Distribution of Power in Exchange Networks,” *American Journal of Sociology* 89(2), 1983. https://doi.org/10.1086/227866 ## Pfeffer & Salancik — resource dependence Resource Dependence Theory studies how organizations become constrained by actors controlling critical external resources. **Correspondence:** DNS, hosting, registries, funding, compute, signing keys, maintainer knowledge, payment rails, distribution, trademarks, and scarce operators can all create hidden sovereignty even when governance documents appear decentralized. **Design implication:** extend the power audit from formal authority to **critical-resource dependency**. Reference: Jeffrey Pfeffer and Gerald R. Salancik, *The External Control of Organizations: A Resource Dependence Perspective*, 1978. https://www.gsb.stanford.edu/faculty-research/books/external-control-organizations-resource-dependence-perspective ## French & Raven — distinct bases of social power French and Raven distinguished bases of social influence such as legitimate, reward, coercive, expert, and referent power. **Correspondence:** Power Dynamics' separation of domains and conversion firewalls. Expertise, money, brand, technical administration, and political standing should not be treated as interchangeable permissions. **Design implication:** identify the **source** of leverage before deciding the legitimate **scope** of that leverage. Reference: John R. P. French Jr. and Bertram Raven, “The Bases of Social Power,” in *Studies in Social Power*, 1959. https://cdn.isr.umich.edu/pubFiles/historicPublications/studiesinsocialpower_1413_.pdf ## Pierre Bourdieu — multiple forms of capital and convertibility Bourdieu distinguishes economic, cultural, and social forms of capital and emphasizes that resources can be accumulated and converted across social fields. His broader work on symbolic power is especially relevant to cases where recognition and classification become consequential without direct coercion. **Correspondence:** Power Dynamics' cross-domain conversion model: money, network position, knowledge, credentials, reputation, and symbolic standing can become leverage in other domains. **Design implication:** conversion pathways need explicit firewalls because different resources do not remain in the domains where they were originally earned. Reference: Pierre Bourdieu, “The Forms of Capital,” in John G. Richardson (ed.), *Handbook of Theory and Research for the Sociology of Education*, Greenwood, 1986, pp. 241–258. ## Philip Pettit — non-domination Republican non-domination focuses not merely on actual interference, but on exposure to **arbitrary power**: another actor may possess uncontrolled capacity to interfere even if it is not presently exercised. **Correspondence:** `non-domination-terminality`, revocability, contestability, exit, and constitutional limits on successful functions becoming terminal sovereigns. **Design implication:** “the administrator is benevolent” is not a sufficient safeguard. The architecture should reduce arbitrary dependency itself. Reference: Philip Pettit, *Republicanism: A Theory of Freedom and Government*. Oxford University Press. https://doi.org/10.1093/0198296428.001.0001 ## Peter Morriss — power as ability Morriss' philosophical analysis is especially relevant to the repo's use of **puissance**. He argues that power is usefully understood as a form of **ability / capacity**, not only as successful influence over another actor. **Correspondence:** this is a close conceptual neighbor to the repo's insistence that `capacity / puissance` must be distinguished from an exercised `power relation`. **Limit:** similar vocabulary does not imply identity between Morriss' analysis and the Power Dynamics ontology. Reference: Peter Morriss, *Power: A Philosophical Analysis*, Manchester University Press, 1987. ## Michel Foucault — power relations revealed through resistance Foucault's “The Subject and Power” emphasizes studying concrete relations of power and using forms of resistance to locate their points of application. **Correspondence:** counterpower, contestation, founder-opposition rehearsals, and adversarial audits can be used diagnostically: resistance is not merely a threat to the system; it is evidence about where power actually sits. Reference: Michel Foucault, “The Subject and Power,” *Critical Inquiry* 8(4), 1982. https://doi.org/10.1086/448181 ## Crozier & Friedberg — zones of uncertainty Crozier and Friedberg's strategic analysis of organizations emphasizes how actors gain leverage through organizational **zones of uncertainty** — areas where rules do not fully determine outcomes and where some actors control information, expertise, external relations, or operational contingencies. **Correspondence:** hidden maintainer knowledge, undocumented exceptions, manual override paths, scarce operational expertise, and discretionary queues can create power even when formal permissions are symmetrical. **Design implication:** audit uncertainty control, not only explicit roles. Reference: Michel Crozier and Erhard Friedberg, *L'acteur et le système: les contraintes de l'action collective*, Seuil, 1977. ## Power conversion as the synthesis opportunity The literature above generally studies **particular relations or domains**. Power Dynamics adds a cross-domain question: > **How does legitimate capability in one domain convert into leverage in another?** Examples include: ```text expertise → credibility → agenda leverage brand → attention → affiliation → revenue money → infrastructure → dependency technical administration → defaults → governance leverage network brokerage → opportunity allocation ``` The academic lineage strengthens the need for **Power Conversion Firewalls**. It does not by itself establish that the current firewalls are sufficient. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-02-Polycentric-Governance-and-Institutions.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b429a77e2f9601fc935a3b52b97adecefe413307d14737958f5c1b4844c5efef CONTENT_BYTES: 3212 ================================================================================================ # Polycentric Governance and Institutional Grammar ## Elinor Ostrom — polycentric governance Ostrom's work rejects the assumption that complex collective-action problems must be solved either by a single state hierarchy or by simple privatization. Polycentric systems can contain multiple, partially autonomous centers of decision-making that interact, experiment, monitor, and learn. **Correspondence:** - federation and subsidiarity; - local autonomy; - independently governed branches; - multiple implementations sharing protocols; - `Founder-powered → Architecture-powered → Protocol-powered → Ecosystem-powered`. **Design implication:** decentralization is not merely “no center.” A viable polycentric ecology still needs rules for coordination, conflict, monitoring, nested levels, and cross-scale learning. References: - Elinor Ostrom, *Governing the Commons*, Cambridge University Press, 1990. - Elinor Ostrom, “Beyond Markets and States: Polycentric Governance of Complex Economic Systems,” Nobel Prize Lecture, 2009/2010. https://www.nobelprize.org/prizes/economic-sciences/2009/ostrom/lecture/ ## Crawford & Ostrom — a grammar of institutions Crawford and Ostrom proposed a structured grammar for analyzing institutional statements — rules, norms, and shared strategies. **Correspondence:** kOA's ambition to represent institutional structures as explicit, inspectable, versionable artifacts rather than leaving them as tacit custom or inaccessible legal prose. **Design implication:** common syntax can increase legibility without requiring identical institutions. This is a strong academic precedent for **shared grammar + local institutional variation**. Reference: Sue E. S. Crawford and Elinor Ostrom, “A Grammar of Institutions,” *American Political Science Review* 89(3), 1995. https://www.cambridge.org/core/journals/american-political-science-review/article/grammar-of-institutions/7D37CD3BC5ED2D9FD57D2EE292958F47 ## Institutional levels: operational, collective-choice, constitutional The Institutional Analysis and Development tradition distinguishes rules that govern day-to-day action from rules governing collective choice and higher-level constitutional rules that determine who can alter the system itself. **Correspondence:** Power Dynamics' authority architecture and the recurring question: > **Who can change the rules that determine who can change the rules?** **Design implication:** audits should classify authority by level, not merely by feature. A system can be democratic operationally while constitutional amendment remains concentrated. ## Polycentricity is not automatically non-dominating A federation can still contain: - a dominant reference implementation; - a registry everyone depends on; - an interface controlled by one maintainer group; - a financially dominant node; - a credibility system that becomes de facto mandatory. Therefore: > **Polycentric topology ≠ non-domination.** Power Dynamics adds dependency, conversion, and exit analysis to the polycentric frame. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-03-Modularity-Standards-and-Path-Dependence.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 850e73869f6ba3fb835a7afd848913ffd1f90b6c620f72ead1cc0780744f8138 CONTENT_BYTES: 4369 ================================================================================================ # Modularity, Standards, Compatibility, and Path Dependence This lineage is central to the repo's attempt to combine **local freedom** with a **common compatible substrate**. ## Herbert Simon — near decomposability Simon argued that complex systems often become tractable and evolvable when organized into subsystems with relatively strong internal interaction and weaker interaction across subsystem boundaries. **Correspondence:** capsules, replaceable services, bounded modules, and the ambition to let parts of kOA evolve without requiring total-system redesign. Reference: Herbert A. Simon, “The Architecture of Complexity,” *Proceedings of the American Philosophical Society* 106(6), 1962. ## Baldwin & Clark — modularity and visible design rules Baldwin and Clark formalize modular systems in which components can change independently while obeying shared **design rules** / interfaces. **Correspondence:** > **Freeze only what is necessary for interoperability; allow everything else to mutate.** This provides a strong academic parallel to kOA's intended combination of independent implementations, shared artifact contracts, and branch evolution. Reference: Carliss Y. Baldwin and Kim B. Clark, *Design Rules, Volume 1: The Power of Modularity*, MIT Press, 2000. https://doi.org/10.7551/mitpress/2366.001.0001 ## Interface power The same modularity that creates freedom can create a new concentration point: **the interface itself**. A party that controls the shared interface can shape all modules while appearing not to control them internally. Power Dynamics should therefore treat shared interfaces as **governance surfaces**: - Who can change the interface? - Who bears migration cost? - Can an older version remain viable? - Can adapters bridge divergent versions? - Can competing standards coexist? - Who certifies compatibility? ## Farrell & Saloner — excess inertia Farrell and Saloner analyze how the benefits of standardization can trap an industry in an inferior or obsolete standard under incomplete information — **excess inertia**. **Correspondence:** a successful kOA compatibility layer could become difficult to change precisely because compatibility is valuable. Reference: Joseph Farrell and Garth Saloner, “Standardization, Compatibility, and Innovation,” *RAND Journal of Economics* 16(1), 1985, pp. 70–83. https://doi.org/10.2307/2555589 ## Katz & Shapiro — network externalities and installed-base power Network goods become more valuable as more compatible users / complements exist. Adoption itself can therefore create structural advantage. **New Power Dynamics concept proposed:** **Installed-Base Power** — the ability of an adopted protocol, implementation, or standard to constrain future choice because participants depend on continued interoperability. Reference: Michael L. Katz and Carl Shapiro, “Network Externalities, Competition, and Compatibility,” *American Economic Review* 75(3), 1985, pp. 424–440. https://www.jstor.org/stable/1814809 ## Paul Pierson — path dependence and increasing returns Pierson describes how increasing returns can make timing and sequence matter, amplify initially small differences, and make established paths difficult to reverse. **Correspondence:** early defaults, registries, naming conventions, scoring systems, reference implementations, and trust roots can become constitutionally significant long after they were introduced as convenience choices. Reference: Paul Pierson, “Increasing Returns, Path Dependence, and the Study of Politics,” *American Political Science Review* 94(2), 2000, pp. 251–267. https://doi.org/10.2307/2586011 ## Proposed constitutional invariant > **Compatibility must not imply constitutional subordination.** Related audit propositions: - `Shared interface → explicit governance surface`; - `Installed base → migration obligation`; - `Compatibility benefit → ossification risk`; - `Forkability without bridges → fragmentation risk`; - `Version pluralism + adapters → evolutionary optionality`. The academic literature establishes the failure modes. It does not prove that a particular kOA versioning or federation scheme solves them. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-04-Open-Source-Exit-Fork-and-Peer-Production.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 96e11aeb6525cfe79b2b628b3c2fd3ecb0ccce1150db5560d82ceb06cfe64abc CONTENT_BYTES: 3239 ================================================================================================ # Exit, Voice, Forking, and Peer Production ## Albert O. Hirschman — exit and voice Hirschman's classic distinction asks how members respond when an organization deteriorates: they may **exit** or use **voice** to attempt repair. **Correspondence:** Power Dynamics deliberately combines contestation and credible exit rather than treating either as sufficient alone. **Design implication:** - voice without exit can leave participants captive; - exit without voice can cause unnecessary fragmentation; - formal exit without portable assets may be practically meaningless. Reference: Albert O. Hirschman, *Exit, Voice, and Loyalty*, Harvard University Press, 1970. ## Nyman & Lindman — forking as governance Nyman and Lindman explicitly analyze code forking as a governance and sustainability mechanism across software, community, and ecosystem levels. **Correspondence:** forkability, branch mobility, incumbent replacement, and the idea that the **possibility** of a fork can constrain maintainers before a fork occurs. Reference: Linus Nyman and Juho Lindman, “Code Forking, Governance, and Sustainability in Open Source Software,” *Technology Innovation Management Review*, January 2013. https://www.timreview.ca/article/644 ## O'Mahony & Ferraro — authority can emerge without conventional ownership Their study of an open-source community shows the development of formal authority combined with democratic mechanisms and evolving conceptions of legitimate leadership. **Correspondence:** a commons still needs governance; `open` does not mean `authority-free`. The relevant question is whether authority remains bounded, contestable, and revisable. Reference: Siobhán O'Mahony and Fabrizio Ferraro, “The Emergence of Governance in an Open Source Community,” *Academy of Management Journal* 50(5), 2007. https://doi.org/10.5465/amj.2007.27169153 ## Yochai Benkler — commons-based peer production Benkler's analysis of Linux and peer production demonstrates a mode of large-scale production that is neither simply firm hierarchy nor price-mediated market organization. **Correspondence:** independent contributors can take responsibility for branches, modules, documentation, institutions, or deployments without becoming employees of a central owner. Reference: Yochai Benkler, “Coase's Penguin, or, Linux and The Nature of the Firm,” *Yale Law Journal* 112, 2002. https://yalelawjournal.org/article/coases-penguin-or-linux-and-the-nature-of-the-firm ## Founder decentering as protocolization Power Dynamics goes beyond “the founder promises not to interfere.” It seeks conversion of founder-specific capability into: - explicit schemas; - reproducible builds; - documentation; - public interfaces; - branch rights; - independent maintenance capacity; - portable data and artifacts. The academic lineage above supports the importance of these mechanisms while also warning that informal reputation, scarce expertise, release keys, brand ownership, and installed-base dominance can preserve founder power after formal control has been removed. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-05-Network-Power-and-Social-Capital.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ce2e4c419cc3350c26c86381216b0e7bf593b511439d2823f54cd65ae50f546b CONTENT_BYTES: 3074 ================================================================================================ # Network Power, Brokerage, Diffusion, and Social Capital ## Linton Freeman — centrality is multidimensional Freeman clarified distinct concepts of centrality rather than treating “central” as one thing. **Correspondence:** network / affiliation power should be measured through several structural lenses rather than a single universal score. Reference: Linton C. Freeman, “Centrality in Social Networks: Conceptual Clarification,” *Social Networks* 1(3), 1978–79. https://doi.org/10.1016/0378-8733(78)90021-7 ## Phillip Bonacich — centrality is not automatically power Bonacich explicitly addresses cases in which network centrality and power diverge. **Correspondence:** Power Dynamics should resist `many connections = sovereignty`. Dependency structure and the positions of one's neighbors matter. Reference: Phillip Bonacich, “Power and Centrality: A Family of Measures,” *American Journal of Sociology* 92(5), 1987. https://doi.org/10.1086/228631 ## Mark Granovetter — weak ties and cross-cluster diffusion Weak ties can connect otherwise separated social clusters and play an outsized role in information diffusion, mobility, and community organization. **Correspondence:** mobilization capacity is not only a function of audience size or strong affiliation. **Bridging ties** can matter disproportionately for spreading initiatives across communities. Reference: Mark S. Granovetter, “The Strength of Weak Ties,” *American Journal of Sociology* 78(6), 1973. https://doi.org/10.1086/225469 ## Ronald Burt — structural holes and brokerage Burt's structural-hole theory treats gaps between otherwise disconnected actors as opportunities for brokerage, information access, and strategic advantage. **Correspondence:** identify actors or services whose brokerage position becomes a hidden allocation or gatekeeping surface. Reference: Ronald S. Burt, *Structural Holes: The Social Structure of Competition*, Harvard University Press, 1992. ## James Coleman — social capital as a resource for action Coleman describes obligations, expectations, information channels, and norms as forms of social capital that enable action. **Correspondence:** Power Dynamics' broad resource → capacity model can explicitly recognize network relations and trust structures as **resources that alter effective possibility**. Reference: James S. Coleman, “Social Capital in the Creation of Human Capital,” *American Journal of Sociology* 94, 1988. https://doi.org/10.1086/228943 ## Audit consequence A network power audit should inspect at least: - centrality; - dependency / substitutability; - brokerage; - bridge positions; - control of discovery / introductions; - access to high-trust clusters; - concentration of communication channels; - ability to route opportunities to others. Network maps show topology. They do **not** by themselves show legitimacy, authority, or domination. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-06-Expertise-SmartVote-and-Collective-Judgment.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6a68a1753cebd3945875a4323c3dbd5fa7aeb172c0ab3bd74bc3f565d7bed484 CONTENT_BYTES: 6247 ================================================================================================ # Expertise, SmartVote, and Collective Judgment This is the most direct academic lineage for the SmartVote principle: > **Expertise should be bounded by domain and used as an advisory reading rather than silently converted into universal political sovereignty.** ## Chi, Feltovich & Glaser — experts structure problems differently within a domain Their classic physics study found systematic differences between expert and novice representations: experts tended to organize problems around deeper domain principles rather than surface features. **Correspondence:** expert standing should be attached to a **domain / problem class**, not treated as a universal personal property. Reference: Michelene T. H. Chi, Paul J. Feltovich, and Robert Glaser, “Categorization and Representation of Physics Problems by Experts and Novices,” *Cognitive Science* 5(2), 1981. https://doi.org/10.1207/s15516709cog0502_2 ## Ericsson & Lehmann — expert performance is adapted to domain-specific constraints Their broad review emphasizes domain-specific cognitive, perceptual-motor, and physiological adaptations behind expert performance. **Correspondence:** a universal “expert score” would collapse heterogeneous competence into an invalid abstraction. EkoH / SmartVote credibility should be scoped to demonstrable domains and tasks. Reference: K. Anders Ericsson and Andreas C. Lehmann, “Expert and Exceptional Performance: Evidence of Maximal Adaptation to Task Constraints,” *Annual Review of Psychology* 47, 1996. https://doi.org/10.1146/annurev.psych.47.1.273 ## Alvin Goldman — the layperson's expert-selection problem Goldman analyzes how nonexperts can rationally decide which experts to trust when they cannot directly evaluate the technical subject matter. **Correspondence:** SmartVote should not merely expose an `expert` badge. It should make evidence of expertise, track record, relevant credentials / contribution, disagreement, and source relations legible. Reference: Alvin I. Goldman, “Experts: Which Ones Should You Trust?”, *Philosophy and Phenomenological Research* 63(1), 2001. https://doi.org/10.1111/j.1933-1592.2001.tb00093.x ## Roger Cooke — calibrated expert judgment Cooke develops methods for eliciting, evaluating, and weighting expert judgments, including performance-based calibration rather than reliance on status alone. **Correspondence:** `expertise → weighted advisory reading` can be grounded in observable performance and calibration rather than title-based authority. Reference: Roger M. Cooke, *Experts in Uncertainty: Opinion and Subjective Probability in Science*, Oxford University Press, 1991. https://doi.org/10.1093/oso/9780195064650.001.0001 ## Budescu & Chen — identify contributors who improve the crowd Budescu and Chen show that aggregation can be improved by identifying judges whose forecasts consistently make positive contributions relative to the group. **Correspondence:** reputation may be **performance-sensitive** and task-sensitive rather than merely social prestige. Reference: David V. Budescu and Eva Chen, “Identifying Expertise to Extract the Wisdom of Crowds,” *Management Science* 61(2), 2015. https://doi.org/10.1287/mnsc.2014.1909 ## Mannes, Soll & Larrick — select crowds Their work shows that in some estimation settings, averaging judgments from a carefully selected small group can be robust and accurate. **Correspondence:** Power Dynamics should allow multiple aggregation lenses rather than assuming either `all votes always equal epistemically` or `single best expert decides`. Reference: Albert E. Mannes, Jack B. Soll, and Richard P. Larrick, “The Wisdom of Select Crowds,” *Journal of Personality and Social Psychology* 107(2), 2014. https://doi.org/10.1037/a0036677 ## Hong & Page — diversity can outperform selection of individually strongest solvers Under their model's conditions, a diverse group of problem solvers can outperform a group selected only for individual ability. **Correspondence:** SmartVote should not turn expertise weighting into an anti-diversity filter. Diversity of representations and heuristics can itself be an epistemic resource. Reference: Lu Hong and Scott E. Page, “Groups of Diverse Problem Solvers Can Outperform Groups of High-Ability Problem Solvers,” *PNAS* 101(46), 2004. https://doi.org/10.1073/pnas.0403723101 ## Social choice: Arrow, Gibbard, and Satterthwaite Social choice theory supplies an important warning: there is no universal voting mechanism that simultaneously satisfies every attractive property under unrestricted conditions, and broad classes of voting systems are vulnerable to strategic manipulation. **Correspondence:** SmartVote should present itself as a **plural, inspectable set of readings and decision aids**, not as a mathematically perfect replacement for politics. References: - Kenneth J. Arrow, *Social Choice and Individual Values*, 1951/1963. - Allan Gibbard, “Manipulation of Voting Schemes: A General Result,” *Econometrica* 41(4), 1973. https://doi.org/10.2307/1914083 - Mark A. Satterthwaite, “Strategy-proofness and Arrow's Conditions,” *Journal of Economic Theory* 10(2), 1975. https://doi.org/10.1016/0022-0531(75)90050-2 ## SmartVote design implications The literature supports several strong constraints: 1. **Domain-bounded expertise** — no universal expert authority. 2. **Performance evidence** — title or prestige is not enough. 3. **Plural aggregation** — different lenses can answer different questions. 4. **Diversity preservation** — selecting only high-status experts can destroy useful heterogeneity. 5. **Political firewall** — epistemic weighting does not automatically purchase political sovereignty. 6. **Manipulation awareness** — every ranking / voting mechanism exposes gaming surfaces. 7. **Baseline visibility** — raw democratic readings should remain visible when advisory lenses are added. None of these references validates a particular SmartVote weighting formula. They provide **design constraints and testable failure modes**. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-07-Metrics-Reputation-and-Gaming.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 415347b531d2f9fda225bec43bd87b589dd00e94dbe14d66491422cbbf3dfac6 CONTENT_BYTES: 2955 ================================================================================================ # Metrics, Reputation, Prestige, and Gaming Any system that makes expertise, contribution, trust, or credibility legible creates a new power surface. ## Donald Campbell — indicators become corruption targets Campbell's work on social indicators is associated with a recurring warning: when quantitative indicators become important targets for decision-making, actors have incentives to corrupt or optimize the indicator rather than the underlying goal. **Correspondence:** EkoH, reputation, contribution metrics, moderation metrics, and SmartVote-derived standings must be treated as **adversarially optimizable surfaces**. Reference: Donald T. Campbell, “Assessing the Impact of Planned Social Change,” *Evaluation and Program Planning* 2(1), 1979. https://doi.org/10.1016/0149-7189(79)90048-X ## Robert K. Merton — the Matthew effect Merton analyzed cumulative advantage in science: recognition and resources can disproportionately accrue to already prominent actors. **Correspondence:** credibility systems can produce a positive feedback loop: ```text initial recognition → more visibility → more opportunities → more visible contribution → more recognition ``` **Design implication:** distinguish demonstrated contribution from **recognition compounding**, and monitor whether discoverability causes prestige to become self-validating. Reference: Robert K. Merton, “The Matthew Effect in Science,” *Science* 159(3810), 1968. https://doi.org/10.1126/science.159.3810.56 ## Prestige, reputation, and authority are not identical Power Dynamics should retain separate concepts for: - observed performance; - domain expertise; - social prestige; - contribution history; - institutional credential; - political standing; - moral / ethical trust; - brand affiliation. A reputation system becomes dangerous when one of these silently converts into all the others. ## Proposed audit questions For every score or ranking: 1. What exactly is being measured? 2. Is the construct domain-specific? 3. Can participants optimize the metric without improving the underlying objective? 4. Does early visibility create cumulative advantage? 5. Are negative evidence and uncertainty preserved? 6. Is the score portable, contestable, and versioned? 7. Can users inspect the weighting rule? 8. Does the score grant authority outside the domain it measures? 9. Can alternative scoring systems coexist? 10. What happens to newcomers with no historical data? ## Proposed invariant > **Legibility should increase informed choice without turning measurement into universal sovereignty.** The academic literature makes the gaming and cumulative-advantage risks difficult to dismiss. It does not determine the correct scoring architecture; that remains an engineering and governance question. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-08-Classification-Infrastructure-and-Code.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 23795e53fb8f3f0477dbcebb30f808841a0db3482e824e43bae2976444792d0f CONTENT_BYTES: 2998 ================================================================================================ # Classification, Infrastructure, Code, and Hidden Governance This lineage supports one of Power Dynamics' most important claims: > **Power can be embedded in technical and semantic architecture before any formal political decision occurs.** ## Langdon Winner — artifacts can embody politics Winner argues that technical artifacts and systems can embody or require particular distributions of power and authority. **Correspondence:** technical design choices belong on the Power Surface; they are not merely neutral implementation details. Reference: Langdon Winner, “Do Artifacts Have Politics?”, *Daedalus* 109(1), 1980. https://www.jstor.org/stable/20024652 ## Lawrence Lessig — code regulates Lessig's work on cyberspace argues that software and hardware architecture regulate behavior alongside law, norms, and markets. **Correspondence:** permissions, defaults, data models, ranking, reader policies, trust roots, update mechanisms, and interoperability rules are governance mechanisms. Reference: Lawrence Lessig, *Code and Other Laws of Cyberspace*, 1999; *Code: Version 2.0*, 2006. https://hls.harvard.edu/bibliography/code-and-other-laws-of-cyberspace-version-2-0/ ## Bowker & Star — classification has consequences Bowker and Star show that classification systems and standards organize worlds, distribute visibility, and can encode consequential social assumptions. **Correspondence:** SemantiK, Kristal schemas, ontologies, category systems, admissibility criteria, and metadata are forms of **semantic / classificatory power**. Reference: Geoffrey C. Bowker and Susan Leigh Star, *Sorting Things Out: Classification and Its Consequences*, MIT Press, 1999. https://doi.org/10.7551/mitpress/6352.001.0001 ## Star & Ruhleder — infrastructure is relational and becomes visible on breakdown Their infrastructure studies emphasize that infrastructure is not merely equipment; it is embedded in practices, communities, standards, learned conventions, and installed bases. **Correspondence:** kOA's technical layer should be audited in relation to actual users and institutions, not only against internal architectural elegance. Reference: Susan Leigh Star and Karen Ruhleder, “Steps Toward an Ecology of Infrastructure,” *Information Systems Research* 7(1), 1996. https://doi.org/10.1287/isre.7.1.111 ## Hidden-sovereignty audit A technically decentralized system may still concentrate power through: - default schemas; - canonical registries; - ranking algorithms; - update keys; - API compatibility requirements; - moderation queues; - model prompts / AI system instructions; - search and discovery; - identity providers; - documentation that defines the “normal” implementation. This literature strongly supports treating those mechanisms as constitutional surfaces rather than implementation trivia. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-09-Epistemic-Power-Provenance-and-Plurality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: eb29d21427d7739e75a45f8fabdc76e736323f688f74a8cf03d43ea0309a721f CONTENT_BYTES: 3574 ================================================================================================ # Epistemic Power, Provenance, Disagreement, and Plurality Kristal and Konnaxion operate in a space that social epistemology, argumentation theory, and belief-revision research have studied from different angles. ## Miranda Fricker — epistemic injustice Fricker distinguishes forms of injustice in which a speaker is given an unfair credibility deficit or lacks shared interpretive resources for making an experience intelligible. **Correspondence:** credibility systems, semantic categories, moderation, and expert-weighted discovery can either reduce or amplify epistemic exclusion. **Design implication:** a credibility system should inspect not only false positive authority, but also **systematic credibility deficits** and missing conceptual categories. Reference: Miranda Fricker, *Epistemic Injustice: Power and the Ethics of Knowing*, Oxford University Press, 2007. https://doi.org/10.1093/acprof:oso/9780198237907.001.0001 ## Alvin Goldman — social epistemology and expert trust Goldman's work treats knowledge practices as social systems that can be evaluated partly by how well they support truth-seeking and rational trust. **Correspondence:** provenance, source comparison, expert-selection evidence, and visible disagreement should support users' own epistemic judgment rather than simply replace it with authority. Reference: Alvin I. Goldman, “Experts: Which Ones Should You Trust?”, 2001. https://doi.org/10.1111/j.1933-1592.2001.tb00093.x ## AGM belief revision — changing a knowledge state should be explicit Alchourrón, Gärdenfors, and Makinson formalized belief revision as a problem of changing a knowledge / belief set while preserving rational structure. **Correspondence:** versioned Kristals, explicit revisions, lineage, conflict, supersession, and rollback are related to the general problem that **new information should alter a knowledge state without erasing how the change occurred**. Reference: Carlos E. Alchourrón, Peter Gärdenfors, and David Makinson, “On the Logic of Theory Change: Partial Meet Contraction and Revision Functions,” *Journal of Symbolic Logic* 50(2), 1985. https://doi.org/10.2307/2274239 ## Dung — argumentation frameworks and conflicting claims Dung's abstract argumentation framework models arguments and attack relations without requiring all participants to share a single consistent knowledge base. **Correspondence:** competing claims / Kristals can remain explicitly related through support, challenge, provenance, and evaluation rather than being collapsed into false consensus. Reference: Phan Minh Dung, “On the Acceptability of Arguments and Its Fundamental Role in Nonmonotonic Reasoning, Logic Programming and n-Person Games,” *Artificial Intelligence* 77(2), 1995. https://doi.org/10.1016/0004-3702(94)00041-X ## Epistemic design implications 1. **Cryptographic integrity ≠ truth.** 2. **Provenance ≠ authority.** 3. **Source multiplicity ≠ source independence.** 4. **Forkability ≠ epistemic equivalence.** 5. **Consensus ≠ absence of dissent.** 6. **Credibility ≠ infallibility.** 7. **Revision should preserve lineage.** 8. **Competing worldviews should remain comparable where possible.** The academic lineage reinforces the repo's adversarial epistemic tests. It also supplies a warning: making epistemic structure explicit does not eliminate disagreement; it makes disagreement more inspectable. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-10-Systems-Cybernetics-and-Adaptation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 469cefbc5cd52fe3b00b0fb3e4cdcc75f2c7f2722b9fdfaca3a437a9b8e9d009 CONTENT_BYTES: 2584 ================================================================================================ # Systems, Cybernetics, Feedback, and Adaptation Power Dynamics is not only a theory of authority. It is also a theory of **capability formation, feedback, memory, and evolutionary adaptation**. ## W. Ross Ashby — requisite variety Ashby's cybernetics is associated with the principle that effective regulation requires sufficient variety in the regulator to respond to the variety of disturbances in the system. **Correspondence:** centralized simplification can fail when local contexts vary more than the center can represent. Federation, local autonomy, plural branches, and specialized modules can preserve response variety. Reference: W. Ross Ashby, *An Introduction to Cybernetics*, 1956. ## Stafford Beer — viable systems and recursive autonomy Beer's Viable System Model studies how viable organizations combine operational autonomy with coordination, control, intelligence, and identity across recursive levels. **Correspondence:** kOA's local / federated architecture and the attempt to avoid both total centralization and incoherent fragmentation. Reference: Stafford Beer, *Brain of the Firm*, 1972; later editions. ## Donella Meadows — leverage points Meadows' systems work distinguishes interventions at different depths, from parameters to information flows, rules, system goals, and paradigms. **Correspondence:** Power Dynamics' cross-domain approach asks whether changing a UI parameter, a ranking rule, a constitutional permission, or an underlying paradigm produces radically different leverage. Reference: Donella H. Meadows, “Leverage Points: Places to Intervene in a System,” Sustainability Institute, 1999. ## Feedback and the kOA capability loop The canonical kOA cycle: > **Know → Choose → Act → Remember → Know better** can be interpreted as a feedback architecture: ```text state / evidence → interpretation → decision → action → result → memory → revised state / evidence ``` The key Power Dynamics addition is that **feedback channels themselves are power surfaces**. Whoever controls what gets measured, remembered, ranked, or ignored can influence future adaptation. ## Systems caution A system can be technically adaptive while politically dominating. Cybernetic viability is not identical to legitimacy, justice, or non-domination. Therefore the systems lineage should be paired with the constitutional lineage rather than used as a substitute for it. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-11-Collective-Action-Mobilization-and-Diffusion.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 4da7f881dbc5f7263b75d568134d375dc7c60090296c2216b93d1fb9760f1bfd CONTENT_BYTES: 4190 ================================================================================================ # Collective Action, Mobilization, Diffusion, and Thresholds Power Dynamics includes a mobilization layer: resources do not become social power merely because they exist. They must be **released, routed, coordinated, and adopted**. ## Mancur Olson — collective action is not automatic Olson's classic work shows why groups with shared interests may still fail to organize or contribute to collective goods because individual incentives and group outcomes can diverge. **Correspondence:** kOA cannot assume that a good common objective automatically produces participation. Roles, incentives, visibility of contribution, modular tasks, local ownership, and low-friction entry all affect whether latent capacity becomes mobilized capacity. Reference: Mancur Olson, *The Logic of Collective Action*, Harvard University Press, 1965. https://doi.org/10.4159/9780674041660 ## McCarthy & Zald — resource mobilization Resource Mobilization Theory shifts attention from grievances alone toward the resources, organizations, media relations, alliances, and structural conditions that make sustained collective action possible. **Correspondence:** Power Dynamics' `Reservoir → Release → Flow → Mediation` model and the distinction between possessing resources and actually mobilizing them. Reference: John D. McCarthy and Mayer N. Zald, “Resource Mobilization and Social Movements: A Partial Theory,” *American Journal of Sociology* 82(6), 1977. https://doi.org/10.1086/226464 ## Granovetter — threshold models of collective behavior Granovetter models individuals as having different participation thresholds: some act early, while others act only after enough others have acted first. Small differences in the distribution of thresholds can produce very different collective outcomes. **Correspondence:** a network can contain substantial **latent commitment** that becomes visible only after credibility, adoption, or social proof crosses thresholds. This directly supports analysis of: - delayed activation of previously contacted collaborators; - tipping dynamics; - adoption cascades; - why early visible participants can disproportionately affect later mobilization; - why aggregate inactivity does not prove absence of latent support. Reference: Mark Granovetter, “Threshold Models of Collective Behavior,” *American Journal of Sociology* 83(6), 1978. https://doi.org/10.1086/226707 ## Everett Rogers — diffusion of innovations Rogers' diffusion framework studies how innovations spread through communication channels over time and how uncertainty, social networks, and adopter categories affect uptake. **Correspondence:** cultural / narrative corridors, demonstrations, reference implementations, peer testimony, and local adoption can be treated as parts of a diffusion system rather than generic “marketing.” Reference: Everett M. Rogers, *Diffusion of Innovations*, 5th ed., Free Press, 2003. ## Damon Centola — complex contagion Centola's experimental work shows that behavioral adoption can differ from simple information diffusion: some behaviors benefit from **reinforcement through multiple social contacts** rather than one weak exposure. **Correspondence:** mobilization for costly participation may require redundant trust paths and local reinforcement, even when information itself can spread through weak ties. Reference: Damon Centola, “The Spread of Behavior in an Online Social Network Experiment,” *Science* 329(5996), 2010. https://doi.org/10.1126/science.1185231 ## Power Dynamics consequence Mobilization should be modeled as a conversion problem: ```text latent resource / willingness → visibility → credibility / social proof → threshold crossing → contribution → coordination → result → public evidence → lower thresholds for later participants ``` This creates a possible compounding loop, but also a capture risk: whoever controls visibility, endorsement, discovery, or narrative framing may control which latent resources ever become mobilized. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-12-Capabilities-Concerted-Power-and-Legibility.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 1a6325cf99020beea2ff4674d09973205506f637d99cf3a656a15455a9a154bc CONTENT_BYTES: 3278 ================================================================================================ # Capabilities, Concerted Power, and the Risks of Legibility Three academic traditions sharpen the normative stakes of Power Dynamics: **capabilities**, **collective agency**, and the dangers of making society legible through simplified administrative categories. ## Amartya Sen — capability and substantive freedom Sen's capability approach shifts attention from resources alone toward what people are **actually able to do and be**. Resources matter partly through the substantive freedoms they make possible. **Correspondence:** Power Dynamics' concept of **effective possibility** is structurally close to a capability-oriented question: possession is not enough; what matters is the real action space available under actual constraints. **Design implication:** a system should not measure empowerment only through nominal access. Ask whether participants can actually use, contest, exit, reproduce, and benefit from the capability. Reference: Amartya Sen, *Development as Freedom*, 1999/2000. https://www.penguinrandomhouse.com/books/163962/development-as-freedom-by-amartya-sen/ ## Hannah Arendt — power as acting in concert Arendt distinguishes power from simple coercion or violence and ties political power to a group's capacity to **act in concert**. **Correspondence:** this is a useful academic neighbor to **generated collective puissance**: composition can create a capacity at group scale that no isolated participant possesses. **Limit:** Arendt's political concept of power is normatively and philosophically distinct from the broader Power Dynamics ontology. Reference: Hannah Arendt, *On Violence*, 1970. ## James C. Scott — legibility can become domination Scott's *Seeing Like a State* studies failures of high-modernist schemes that simplified complex local realities into administratively legible categories and then governed through those abstractions. **Correspondence:** kOA deliberately increases legibility — schemas, classifications, provenance, metrics, workflows, registries, institutional grammar. That is a capability **and a danger**. **Design implication:** semantic clarity must not erase local knowledge or turn the reference model into compulsory reality. The anti-capture answer is not “avoid legibility,” but combine legibility with: - local override / interpretation; - plural schemas where necessary; - provenance and uncertainty; - reversible mappings; - branch alternatives; - explicit scope; - user-visible disagreement. Reference: James C. Scott, *Seeing Like a State: How Certain Schemes to Improve the Human Condition Have Failed*, Yale University Press, 1998/1999. https://yalebooks.yale.edu/book/9780300078152/seeing-like-a-state/ ## Synthesis These three traditions create a useful triangle: ```text Sen: What can people actually do? Arendt: What can people do together? Scott: What happens when institutions simplify people in order to coordinate them? ``` Power Dynamics can use that triangle as a normative test: > **Increase effective individual and collective capability without making the legibility infrastructure a new sovereign.** --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage-Bibliography.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 8c4812722387ad7056b8d757d784012562061c9ac0070ee22e5de39de7330670 CONTENT_BYTES: 11340 ================================================================================================ # Academic Lineage Bibliography This bibliography is intentionally **selective rather than exhaustive**. Entries are grouped by their strongest use in Power Dynamics. A work may belong to several groups. ## Power, dependency, domination - Bachrach, Peter, and Morton S. Baratz. “Two Faces of Power.” *American Political Science Review* 56(4), 1962. https://doi.org/10.2307/1952796 - Bourdieu, Pierre. “The Forms of Capital.” In John G. Richardson (ed.), *Handbook of Theory and Research for the Sociology of Education*, Greenwood, 1986: 241–258. - Dahl, Robert A. “The Concept of Power.” *Behavioral Science* 2(3), 1957: 201–215. https://doi.org/10.1002/bs.3830020303 - Emerson, Richard M. “Power-Dependence Relations.” *American Sociological Review* 27(1), 1962: 31–41. https://www.jstor.org/stable/2089716 - Cook, Karen S., Richard M. Emerson, Mary R. Gillmore, and Toshio Yamagishi. “The Distribution of Power in Exchange Networks: Theory and Experimental Results.” *American Journal of Sociology* 89(2), 1983: 275–305. https://doi.org/10.1086/227866 - French, John R. P. Jr., and Bertram Raven. “The Bases of Social Power.” In *Studies in Social Power*, 1959. https://cdn.isr.umich.edu/pubFiles/historicPublications/studiesinsocialpower_1413_.pdf - Lukes, Steven. *Power: A Radical View*. First published 1974; later editions. https://www.bloomsbury.com/ca/power-9781350544758/ - Pettit, Philip. *Republicanism: A Theory of Freedom and Government*. Oxford University Press. https://doi.org/10.1093/0198296428.001.0001 - Pfeffer, Jeffrey, and Gerald R. Salancik. *The External Control of Organizations: A Resource Dependence Perspective*. 1978. https://www.gsb.stanford.edu/faculty-research/books/external-control-organizations-resource-dependence-perspective - Morriss, Peter. *Power: A Philosophical Analysis*. Manchester University Press, 1987. - Foucault, Michel. “The Subject and Power.” *Critical Inquiry* 8(4), 1982: 777–795. https://doi.org/10.1086/448181 - Crozier, Michel, and Erhard Friedberg. *L'acteur et le système: les contraintes de l'action collective*. Seuil, 1977. ## Institutions, polycentric governance, commons - Crawford, Sue E. S., and Elinor Ostrom. “A Grammar of Institutions.” *American Political Science Review* 89(3), 1995. https://www.cambridge.org/core/journals/american-political-science-review/article/grammar-of-institutions/7D37CD3BC5ED2D9FD57D2EE292958F47 - Ostrom, Elinor. *Governing the Commons*. Cambridge University Press, 1990. - Ostrom, Elinor. “Beyond Markets and States: Polycentric Governance of Complex Economic Systems.” Nobel Prize Lecture, 2009/2010. https://www.nobelprize.org/prizes/economic-sciences/2009/ostrom/lecture/ ## Modularity, standards, path dependence - Baldwin, Carliss Y., and Kim B. Clark. *Design Rules, Volume 1: The Power of Modularity*. MIT Press, 2000. https://doi.org/10.7551/mitpress/2366.001.0001 - Farrell, Joseph, and Garth Saloner. “Standardization, Compatibility, and Innovation.” *RAND Journal of Economics* 16(1), 1985: 70–83. https://doi.org/10.2307/2555589 - Katz, Michael L., and Carl Shapiro. “Network Externalities, Competition, and Compatibility.” *American Economic Review* 75(3), 1985: 424–440. https://www.jstor.org/stable/1814809 - Pierson, Paul. “Increasing Returns, Path Dependence, and the Study of Politics.” *American Political Science Review* 94(2), 2000: 251–267. https://doi.org/10.2307/2586011 - Simon, Herbert A. “The Architecture of Complexity.” *Proceedings of the American Philosophical Society* 106(6), 1962: 467–482. ## Exit, forking, open source, peer production - Benkler, Yochai. “Coase's Penguin, or, Linux and The Nature of the Firm.” *Yale Law Journal* 112, 2002. https://yalelawjournal.org/article/coases-penguin-or-linux-and-the-nature-of-the-firm - Hirschman, Albert O. *Exit, Voice, and Loyalty*. Harvard University Press, 1970. - Nyman, Linus, and Juho Lindman. “Code Forking, Governance, and Sustainability in Open Source Software.” *Technology Innovation Management Review*, January 2013. https://www.timreview.ca/article/644 - O'Mahony, Siobhán, and Fabrizio Ferraro. “The Emergence of Governance in an Open Source Community.” *Academy of Management Journal* 50(5), 2007. https://doi.org/10.5465/amj.2007.27169153 ## Network power and social capital - Bonacich, Phillip. “Power and Centrality: A Family of Measures.” *American Journal of Sociology* 92(5), 1987. https://doi.org/10.1086/228631 - Burt, Ronald S. *Structural Holes: The Social Structure of Competition*. Harvard University Press, 1992. - Coleman, James S. “Social Capital in the Creation of Human Capital.” *American Journal of Sociology* 94, 1988. https://doi.org/10.1086/228943 - Freeman, Linton C. “Centrality in Social Networks: Conceptual Clarification.” *Social Networks* 1(3), 1978–79. https://doi.org/10.1016/0378-8733(78)90021-7 - Granovetter, Mark S. “The Strength of Weak Ties.” *American Journal of Sociology* 78(6), 1973. https://doi.org/10.1086/225469 ## Expertise and collective judgment - Budescu, David V., and Eva Chen. “Identifying Expertise to Extract the Wisdom of Crowds.” *Management Science* 61(2), 2015. https://doi.org/10.1287/mnsc.2014.1909 - Chi, Michelene T. H., Paul J. Feltovich, and Robert Glaser. “Categorization and Representation of Physics Problems by Experts and Novices.” *Cognitive Science* 5(2), 1981. https://doi.org/10.1207/s15516709cog0502_2 - Cooke, Roger M. *Experts in Uncertainty: Opinion and Subjective Probability in Science*. Oxford University Press, 1991. https://doi.org/10.1093/oso/9780195064650.001.0001 - Ericsson, K. Anders, and Andreas C. Lehmann. “Expert and Exceptional Performance: Evidence of Maximal Adaptation to Task Constraints.” *Annual Review of Psychology* 47, 1996. https://doi.org/10.1146/annurev.psych.47.1.273 - Goldman, Alvin I. “Experts: Which Ones Should You Trust?” *Philosophy and Phenomenological Research* 63(1), 2001. https://doi.org/10.1111/j.1933-1592.2001.tb00093.x - Hong, Lu, and Scott E. Page. “Groups of Diverse Problem Solvers Can Outperform Groups of High-Ability Problem Solvers.” *PNAS* 101(46), 2004. https://doi.org/10.1073/pnas.0403723101 - Mannes, Albert E., Jack B. Soll, and Richard P. Larrick. “The Wisdom of Select Crowds.” *Journal of Personality and Social Psychology* 107(2), 2014. https://doi.org/10.1037/a0036677 - Tetlock, Philip E. *Expert Political Judgment: How Good Is It? How Can We Know?* Princeton University Press, 2005. ## Social choice and strategic manipulation - Arrow, Kenneth J. *Social Choice and Individual Values*. 1951; 2nd ed. 1963. - Gibbard, Allan. “Manipulation of Voting Schemes: A General Result.” *Econometrica* 41(4), 1973: 587–601. https://doi.org/10.2307/1914083 - Satterthwaite, Mark Allen. “Strategy-proofness and Arrow's Conditions: Existence and Correspondence Theorems for Voting Procedures and Social Welfare Functions.” *Journal of Economic Theory* 10(2), 1975: 187–217. https://doi.org/10.1016/0022-0531(75)90050-2 ## Metrics, prestige, cumulative advantage - Campbell, Donald T. “Assessing the Impact of Planned Social Change.” *Evaluation and Program Planning* 2(1), 1979: 67–90. https://doi.org/10.1016/0149-7189(79)90048-X - Merton, Robert K. “The Matthew Effect in Science.” *Science* 159(3810), 1968: 56–63. https://doi.org/10.1126/science.159.3810.56 ## Infrastructure, classification, code - Bowker, Geoffrey C., and Susan Leigh Star. *Sorting Things Out: Classification and Its Consequences*. MIT Press, 1999. https://doi.org/10.7551/mitpress/6352.001.0001 - Lessig, Lawrence. *Code and Other Laws of Cyberspace*. 1999; *Code: Version 2.0*, 2006. https://hls.harvard.edu/bibliography/code-and-other-laws-of-cyberspace-version-2-0/ - Star, Susan Leigh, and Karen Ruhleder. “Steps Toward an Ecology of Infrastructure: Design and Access for Large Information Spaces.” *Information Systems Research* 7(1), 1996. https://doi.org/10.1287/isre.7.1.111 - Winner, Langdon. “Do Artifacts Have Politics?” *Daedalus* 109(1), 1980: 121–136. https://www.jstor.org/stable/20024652 ## Epistemic power, disagreement, revision - Alchourrón, Carlos E., Peter Gärdenfors, and David Makinson. “On the Logic of Theory Change: Partial Meet Contraction and Revision Functions.” *Journal of Symbolic Logic* 50(2), 1985. https://doi.org/10.2307/2274239 - Dung, Phan Minh. “On the Acceptability of Arguments and Its Fundamental Role in Nonmonotonic Reasoning, Logic Programming and n-Person Games.” *Artificial Intelligence* 77(2), 1995. https://doi.org/10.1016/0004-3702(94)00041-X - Fricker, Miranda. *Epistemic Injustice: Power and the Ethics of Knowing*. Oxford University Press, 2007. https://doi.org/10.1093/acprof:oso/9780198237907.001.0001 - Goldman, Alvin I. *Knowledge in a Social World*. Oxford University Press, 1999. ## Collective action, mobilization, diffusion - Centola, Damon. “The Spread of Behavior in an Online Social Network Experiment.” *Science* 329(5996), 2010. https://doi.org/10.1126/science.1185231 - Granovetter, Mark. “Threshold Models of Collective Behavior.” *American Journal of Sociology* 83(6), 1978. https://doi.org/10.1086/226707 - McCarthy, John D., and Mayer N. Zald. “Resource Mobilization and Social Movements: A Partial Theory.” *American Journal of Sociology* 82(6), 1977. https://doi.org/10.1086/226464 - Olson, Mancur. *The Logic of Collective Action*. Harvard University Press, 1965. https://doi.org/10.4159/9780674041660 - Rogers, Everett M. *Diffusion of Innovations*, 5th ed. Free Press, 2003. ## Capabilities, concerted action, legibility - Arendt, Hannah. *On Violence*. 1970. - Scott, James C. *Seeing Like a State: How Certain Schemes to Improve the Human Condition Have Failed*. Yale University Press, 1998/1999. https://yalebooks.yale.edu/book/9780300078152/seeing-like-a-state/ - Sen, Amartya. *Development as Freedom*. 1999/2000. https://www.penguinrandomhouse.com/books/163962/development-as-freedom-by-amartya-sen/ ## Systems and cybernetics - Ashby, W. Ross. *An Introduction to Cybernetics*. 1956. - Beer, Stafford. *Brain of the Firm*. 1972; later editions. - Meadows, Donella H. “Leverage Points: Places to Intervene in a System.” Sustainability Institute, 1999. ## Candidates for later expansion These are significant enough to deserve later treatment but are not yet integrated in detail: - Hannah Arendt — power as acting in concert, and distinction from violence; - Pierre Bourdieu — economic, cultural, social, and symbolic capital and conversion; - Michel Foucault — productive / dispersed power, normalization, and conduct; - Crozier & Friedberg — organizational power through zones of uncertainty; - mechanism design / incentive compatibility; - platform governance and recommender-system power; - algorithmic accountability and AI-mediated authority; - common-pool resource design principles in digital infrastructure; - standards governance and Internet protocol ossification; - epistemic democracy and deliberative systems; - institutional diversity and comparative constitutional design. --- [Academic Lineage](Academic-Lineage) · [Bibliography](Academic-Lineage-Bibliography) · [Research & Literature](Research-and-Literature) ================================================================================================ FILE: Power-Dynamics.wiki/Academic-Lineage.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 7336284bc963a5dec5498754d308085f2cb8f3b377641f6dd4275d7b1a2b3e81 CONTENT_BYTES: 7295 ================================================================================================ # Academic Lineage This wiki section situates **Power Dynamics** and selected kOA mechanisms beside established academic traditions that study the same classes of problems. > **This is a lineage of problems, concepts, and convergent mechanisms — not a claim of historical influence, endorsement, or proof.** A cited author may have identified a problem that Power Dynamics also identifies, formalized a mechanism that helps explain a Power Dynamics claim, or supplied a counterexample / impossibility result that a kOA mechanism must survive. None of that means the author endorsed kOA, and none of it validates a particular implementation. ## Why this layer exists Power Dynamics crosses fields that are usually separated: political theory, organizational sociology, institutional economics, social choice, network science, open-source governance, systems theory, science and technology studies, social epistemology, expertise research, and software architecture. The purpose of this section is therefore to make four things explicit for each major connection: 1. **Academic finding or problem** — what the literature actually established or argued. 2. **Power Dynamics correspondence** — which concept, audit surface, or kOA mechanism is structurally related. 3. **Design implication** — what should be tested, measured, separated, or protected. 4. **Limit of correspondence** — what the citation does **not** prove. ## High-level map | Academic lineage | Problem / insight | Power Dynamics correspondence | |---|---|---| | Dahl; Bachrach & Baratz; Lukes | power includes decisions, agenda control, and preference shaping | pre-political chain; discoverability; narrative / classification power | | Emerson; Cook et al.; Pfeffer & Salancik | power grows from dependency and scarce alternatives | effective possibility; dependency-exit audit; strong capability / weak sovereignty | | French & Raven; Bourdieu | power has multiple bases and convertible forms | power domains; cross-domain conversion; credibility ≠ authority | | Pettit | freedom requires protection against arbitrary domination | non-domination terminality; contestation; credible exit | | Ostrom; Crawford & Ostrom | polycentric governance and institutional rules can be analyzed at multiple levels | federation; subsidiarity; rules-about-rules; constitutional architecture | | Simon; Baldwin & Clark | complex systems can remain evolvable through modularity and explicit interfaces | capsules; protocolization; branch ecology; local variation + compatibility | | Farrell & Saloner; Katz & Shapiro; Pierson | compatibility can create lock-in, installed-base power, and path dependence | protocol power; ossification audits; migration paths; version pluralism | | Hirschman; Nyman & Lindman; O'Mahony & Ferraro; Benkler | exit, voice, forking, peer production, and open governance constrain hierarchy | forkability; branch mobility; founder decentering; capability commons | | Freeman; Bonacich; Granovetter; Burt; Coleman | network position, brokerage, weak ties, and social capital alter effective capacity | network / affiliation power; mobilization; brokerage and dependency audits | | Chi; Ericsson & Lehmann; Goldman | expertise is structured, domain-bounded, and difficult for nonexperts to evaluate | SmartVote domain scopes; EkoH context; expertise → advice, not sovereignty | | Cooke; Budescu & Chen; Mannes et al.; Hong & Page | calibrated weighting can help, but diversity and aggregation rules matter | plural lenses; measured contribution; diverse advisory readings | | Arrow; Gibbard; Satterthwaite | collective choice mechanisms face structural impossibility and manipulation limits | SmartVote transparency; baseline vs advisory lenses; no universal perfect voting rule | | Campbell; Merton | metrics and prestige can self-reinforce and be gamed | EkoH / reputation audits; Matthew effects; anti-Goodhart safeguards | | Winner; Lessig; Bowker & Star; Star & Ruhleder | artifacts, code, classifications, and infrastructure embed governance | power surface; semantic power; interface power; hidden sovereignty | | Fricker; Goldman; argumentation / belief-revision traditions | epistemic standing, testimony, disagreement, and revision are power-laden | Kristal provenance; competing Kristals; epistemic authority corruption tests | | Ashby; Beer; Meadows | viable systems require feedback, requisite variety, adaptation, and attention to leverage points | Know → Choose → Act → Remember; local autonomy; feedback; systemic audits | | Olson; McCarthy & Zald; Granovetter thresholds; Rogers; Centola | collective action requires mobilization, diffusion, threshold crossing, and sometimes social reinforcement | mobilization flow; latent resources; cultural corridors; adoption cascades | | Sen; Arendt; James C. Scott | real capability, concerted action, and dangers of administrative legibility | effective possibility; generated collective puissance; plural / contestable legibility | ## Reading order 1. [`01-power-dependence-and-domination.md`](Academic-Lineage-01-Power-Dependence-and-Domination) 2. [`02-polycentric-governance-and-institutions.md`](Academic-Lineage-02-Polycentric-Governance-and-Institutions) 3. [`03-modularity-standards-and-path-dependence.md`](Academic-Lineage-03-Modularity-Standards-and-Path-Dependence) 4. [`04-open-source-exit-fork-and-peer-production.md`](Academic-Lineage-04-Open-Source-Exit-Fork-and-Peer-Production) 5. [`05-network-power-and-social-capital.md`](Academic-Lineage-05-Network-Power-and-Social-Capital) 6. [`06-expertise-smartvote-and-collective-judgment.md`](Academic-Lineage-06-Expertise-SmartVote-and-Collective-Judgment) 7. [`07-metrics-reputation-and-gaming.md`](Academic-Lineage-07-Metrics-Reputation-and-Gaming) 8. [`08-classification-infrastructure-and-code.md`](Academic-Lineage-08-Classification-Infrastructure-and-Code) 9. [`09-epistemic-power-provenance-and-plurality.md`](Academic-Lineage-09-Epistemic-Power-Provenance-and-Plurality) 10. [`10-systems-cybernetics-and-adaptation.md`](Academic-Lineage-10-Systems-Cybernetics-and-Adaptation) 11. [`11-collective-action-mobilization-and-diffusion.md`](Academic-Lineage-11-Collective-Action-Mobilization-and-Diffusion) 12. [`12-capabilities-concerted-power-and-legibility.md`](Academic-Lineage-12-Capabilities-Concerted-Power-and-Legibility) 13. [`BIBLIOGRAPHY.md`](Academic-Lineage-Bibliography) ## Core caution Academic literature can support a **problem diagnosis**, a **mechanism**, an **impossibility constraint**, or a **design principle**. It does not automatically validate: - a specific SmartVote weighting formula; - an EkoH scoring implementation; - the security or decentralization of a current deployment; - a claim that kOA is optimal; - a claim that Power Dynamics is derived from these authors; - or a claim that any cited scholar endorses kOA. The strongest use of this literature is adversarial: **it gives the framework better names for failure modes and better tests for whether the architecture actually solves them.** > **Canonical repo source:** `Academic-Lineage/README.md` and the corresponding files under `Academic-Lineage/`. --- [Home](Home) · [Research & Literature](Research-and-Literature) · [Bibliography](Academic-Lineage-Bibliography) ================================================================================================ FILE: Power-Dynamics.wiki/Administrative-and-Operational-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 348fa65d5603c05632768d6c5ac701501f2db1cc2131bfc043a01a3161185eb7 CONTENT_BYTES: 1644 ================================================================================================ # Administrative & Operational Power > **Core question:** Who can route, assign, schedule, delay, approve, escalate, execute, record, or close work? ## Generated puissance Effective capability to **transform decisions into roles, tasks, ownership, routing, escalation, execution, closure, and operational memory**. ## Relational power that can emerge Timing power, workload power, approval power, escalation power, closure power, de facto policy power. ## Typical conversion paths - `decision → workflow` - `workflow defaults → de facto policy` - `administrative delay → practical denial` - `execution control → agenda leverage` ## Routing / counterpower direction - explicit roles and workflows - scoped mandate - audit, appeal, revocability, and separation of execution from mandate definition - traceable closure and escalation rules ## kOA touchpoints - Orgo is the principal administrative / operational surface - decision outputs can become governed work rather than disappearing into discussion - operational memory can feed later learning ## Analytical note Administrative power is often underestimated because it can alter outcomes without formally changing policy. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/AI-and-Cognitive-Puissance.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f6eee22ecbb03a08eac4c1bf2af3e977ee38755c4f5a5b31100e67f44bc82c46 CONTENT_BYTES: 711 ================================================================================================ # AI and Cognitive Puissance AI can greatly increase cognitive throughput: reading, synthesis, comparison, generation, translation, semantic processing, and planning. The repository treats AI as **cognitive puissance under governance**, not as an autonomous institutional sovereign. Risks include hidden policy through prompts/defaults, opacity through complexity, semantic centralization, remote-service dependence, unreviewable automation, and substitution of model confidence for governed evidence. AI should assist transformations whose authority remains externally governed and auditable. > **Canonical repo source:** `koa/ai.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/AI-Hidden-Sovereignty.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 23af199c1f1b420b029043f1909717a4c9192c3278d721970352b04642bd90e3 CONTENT_BYTES: 585 ================================================================================================ # AI and Hidden Sovereignty AI can be formally advisory while becoming practically sovereign if institutions cannot understand, challenge, reproduce, or override its outputs. Signals include automatic adoption of model recommendations, inaccessible prompts or policies, no governed fallback, dependence on a remote provider, or model outputs treated as authoritative evidence by default. The case tests the principle `AI assists under governance`. > **Canonical repo source:** `cases/ai-hidden-sovereignty.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Authority-Architecture.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 02cb7f519eb1a1eb4b03c3ccf5a7236465f90d8a9a78555bd73fca35f4e78053 CONTENT_BYTES: 1519 ================================================================================================ # Authority Architecture: Scope, Separation, and Centrality Legitimate authority should specify domain, function, jurisdiction, duration, basis, conditions, review, delegation, and revocation. Authority in one domain should not automatically travel to another. A technical maintainer may authorize releases without deciding political outcomes. An expert may provide domain-bounded advice without receiving universal civic superiority. Separation of functions limits conversion by assigning distinct responsibilities to distinct components or roles. Examples include separating credibility from vote results, narrative from legitimacy, execution from mandate creation, protocol commons from brand stewardship, and AI assistance from final authority. Healthy systems also need not be centerless. A useful pattern is: > **StrongHub + DistributedCapability + ReplicableWhole** Important distinctions: - Functional centrality ≠ domination - Centralized access ≠ centralized truth - Strong center ≠ total sovereignty - Federation ≠ flatness - Local sovereignty ≠ absence of a local center - Composition does not require ownership - Creator-owned channel ≠ mandatory dependency - Independent reproducibility ≠ founder removal The constitutional question is whether actors can verify, substitute, reproduce, branch, and continue when the center changes or fails. > **Canonical repo source:** `constitution/authority-architecture.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Branch-Ecology.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 0fc2019186627fe63477de561d7e4a50313524ea13b996f51aa48c127bf7e644 CONTENT_BYTES: 1417 ================================================================================================ # Branch Ecology Branch ecology is where the Power Show becomes evolutionary: the system should be capable not only of acting, but of improving the mechanisms through which it knows, chooses, acts, and remembers. Branch ecology is the **evolutionary end of the Power Show**. A system is more capable when it can not only act, but also **improve the mechanisms through which it knows, chooses, acts, and remembers**. Branches are therefore not merely emergency responses to capture. They are normal instruments of experimentation under permanent imperfection. The ecology asks: - how lineage and competing Kristals are preserved; - how complementarity avoids dogma without collapsing into relativism; - how alternatives demonstrate added value; - how support, adoption, dominance, truth, and quality remain distinct; - whether a better branch can actually become viable; - how branches coexist, specialize, recombine, merge, or replace one another. The key capability is **branch mobility**: not only the formal right to fork, but the practical ability to preserve provenance, interoperate, attract support, gain discoverability, and eventually influence or replace a dominant branch. > **The core protects evolution; it does not freeze truth.** > **Canonical repo source:** `branch-ecology/README.md` --- ← [Power Constitution](Power-Constitution) · [Home](Home) · [kOA System Map](kOA-System-Map) → ================================================================================================ FILE: Power-Dynamics.wiki/Branch-Mobility.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 2e1f0ca832211835ae0da912cf425f5f3ccb6bf17c0ca605ae1ac6d98b282a1f CONTENT_BYTES: 627 ================================================================================================ # Branch Mobility in Practice Branch mobility is the practical path from alternative to viable competitor or complement. A high-mobility ecosystem lets a branch: `form → preserve lineage → interoperate → demonstrate → be discovered → gather support → deploy → influence / coexist / replace`. Low branch mobility can create dogma without explicit censorship: alternatives formally exist but cannot accumulate enough recognition, compatibility, or infrastructure to matter. > **Canonical repo source:** `branch-ecology/branch-mobility.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Brand-Founder-and-Optionality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b2f8ec546671eac59a6bb69a61300f68d9b42e61df4d8dfd5ea0d428f7dbabe5 CONTENT_BYTES: 2501 ================================================================================================ # Brand, Founder Power and Optionality Brand and founder position can create attention, interpretation, affiliation, release timing, and coordination capacity. Power Dynamics treats those as real assets while separating them from truth, legitimacy, or permanent sovereignty. ## Brand and narrative Brand and narrative create communicative, symbolic, and affiliation puissance. They can compress complex meaning into recognizable symbols, lower transmission cost, mobilize supporters, generate commerce, and make a system culturally legible. `system value → brand recognition → attention / affiliation → revenue / network → reinvestment` The constitutional firewall is that brand or narrative does not become truth, expertise, political legitimacy, or protocol sovereignty by itself. ## Founder power Founder power can include authorship and vocabulary, repository and infrastructure control, domains and brand, signing/release keys, unique architectural knowledge, relationships and narrative authority, and public-identity optionality. The question is not whether an early founder has concentrated puissance, but how that dependence changes over time. `Founder capability → encoded architecture → documentation → distributed mastery → maintainer pluralism → independent reproducibility` ## Founder identity and optionality case A founder whose face or identity is not broadly public preserves privacy, ordinary social mobility, observational freedom, scarcity, and future reveal timing. This is **identity optionality** and **release optionality**, not yet mass-media power. If recognition later grows, disclosure can convert optionality into attention or narrative effects. The irreversible nature of disclosure makes timing itself a resource. > **Canonical repo source:** `koa/brand-narrative.md`, `koa/founder-power.md`, `cases/founder-identity-optionality.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ## Narrative self-binding and symbolic-capital sharing The fiction explicitly publishes ethical constraints and anti-domination norms. It also redirects symbolic returns through public recognition, sharing merit, self-mockery, rejection of dogma, documentation, transmission, and passing the baton. That makes the narrative layer a **power-sharing mechanism**, not only a persuasion mechanism. Read [Ethical Fiction as Self-Binding](Ethical-Fiction-as-Self-Binding) and [Power Routing & Sharing](Power-Routing-and-Sharing). ================================================================================================ FILE: Power-Dynamics.wiki/Capability-Show-Profile.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b9be02bbd8daa025dfc375ad7b0ca7de5d08f9d2b664c912f669ce6bcf48ba4b CONTENT_BYTES: 1995 ================================================================================================ # Capability Show Profile The Capability Show Profile is the preferred format for demonstrating that a system is powerful **without collapsing capability into authority**. For each capability claim, document: ## 1. Baseline limitation What effective possibility is currently constrained? Examples: knowledge is fragmented, expertise is hard to discover, decisions are not executable, institutional memory is weak, exit is costly. ## 2. Resource and mechanism What resources, components, protocols, roles, or institutions are introduced? ## 3. Capacity created What organized ability becomes available? ## 4. Puissance demonstrated Under realistic conditions, what can the actor or collective now effectively do that it could not do before, or could only do at much higher cost? ## 5. Composition gain Which other capabilities become more useful because this capability exists? ## 6. Returns and compounding What reusable assets are left behind? Does the action lower future cost, increase future quality, preserve memory, expand network access, or create shared infrastructure? ## 7. Capability-to-power transition If the capability becomes widely relied upon, which actors' access, standing, visibility, allocation, interpretation, timing, dependency, or ability to act can be affected? ## 8. Conversion pathways What legitimate conversions are expected? What cross-domain conversions should be blocked? ## 9. Counterpowers Can affected actors verify, contest, substitute, exit, revoke, fork, or operate through an alternative branch? ## 10. Evidence and maturity Separate: - source-derived architecture; - implemented technical evidence; - demonstrated deployment evidence; - analytical reconstruction; - open questions. The goal is to make the **Power Show falsifiable and inspectable**, not merely impressive. > **Canonical repo source:** `assessment/capability-show-profile.md` --- ← [kOA System Map](kOA-System-Map) · [Home](Home) · [Glossary](Glossary) → ================================================================================================ FILE: Power-Dynamics.wiki/Capability-Spectrum.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b57fc69714e1b7628007320f9630bcd2d4fac653f6216350949523f0888dcded CONTENT_BYTES: 5032 ================================================================================================ # The kOA Capability Spectrum The Power Show begins by separating **what kOA helps actors do** from **what authority any actor has over others**. The first category is **puissance**: effectively mobilizable capacity. ## Epistemic puissance Create, structure, compare, verify, preserve, cite, derive, and reuse knowledge. Kristal is the primary architectural locus. ## Semantic puissance Make categories, meanings, relations, ambiguity, translation, and ontology explicit enough to inspect and evolve. SemantiK / SenTient are central here. ## Cognitive puissance Reason, synthesize, model, plan, generate, evaluate, and learn at greater throughput. AI can amplify this capability, but its outputs remain subordinate to explicit governance and provenance. ## Individual agency Understand options, make informed choices, refuse, exit, learn, publish, organize, and preserve personal or institutional optionality. ## Collective puissance Combine people who individually possess only partial knowledge, time, skills, resources, and relationships into coordinated capability. ## Network puissance Find expertise, collaborators, communities, institutions, supporters, customers, contributors, or alternative branches. Network capability changes what can be attempted. ## Discoverability puissance Make relevant knowledge, people, needs, proposals, branches, and evidence findable. Discoverability is empowering before it becomes a ranking or agenda relation. ## Credibility puissance Make evidence of contribution, expertise, reliability, or domain-bounded competence legible enough to be used. `Score ≠ competence`; credibility signals are governed readings, not persons. ## Deliberative and decision puissance Compare alternatives, preserve baseline equality, add advisory expertise without silently replacing the baseline, and make reasons inspectable. ## Coordination puissance Sequence actors and information so that many partial capabilities produce coherent action. ## Operational puissance Route work, create ownership, set escalation paths, manage time windows, review outcomes, and close loops. ## Mnemonic puissance Preserve reasons, provenance, decisions, actions, failures, outcomes, versions, and lineage so future action begins with memory rather than amnesia. ## Political and constitutional puissance Deliberate, formulate proposals, authorize, amend, organize mandates, preserve equal political standing, and create legitimate pathways from public judgment to collective action. This is capability; relational political power emerges when one actor or structure can shape others' standing, agenda, decision rights, or mandates. ## Economic and allocation puissance Mobilize, pool, direct, or govern scarce resources. Economic contribution can support collective action without automatically purchasing political authority. ## Monetary, credit, and liquidity puissance Operate or access payment, liquidity, settlement, credit, reserve, or exchange functions when such infrastructure exists. Because monetary rails can condition the rest of economic life, monetary capability becomes a high-leverage constitutional surface when one controller can determine access or terms. ## Technical puissance Build, inspect, modify, test, reproduce, repair, deploy, integrate, and maintain systems. ## Infrastructural puissance Create shared capability that lowers the cost of future action for many actors: protocols, schemas, identity contracts, deployment mechanisms, knowledge formats, workflow primitives. ## Distribution puissance Move knowledge and coordination across languages, communities, institutions, and geographic boundaries. ## Brand and affiliation puissance Create recognition, public signaling, identity, community affiliation, and transmission. Brand can create attention and funding without becoming truth or sovereignty. ## Federation puissance Operate local instances while preserving interoperability, lineage, portability, and the possibility of alternative governance. ## Exit and substitution puissance Leave, replace a dependency, preserve assets, self-host, migrate, or continue through another implementation. ## Forking puissance Create an alternative implementation, policy, ontology, credibility model, reader policy, governance model, or knowledge representation. ## Evolutionary puissance Do more than fork: demonstrate improvement, gather support, remain interoperable, recombine useful ideas, and allow dominant branches to change or be replaced. ## The key distinction A capability is not automatically a relation of power. > **The Power Show maps what actors become able to do. Power Dynamics then asks whose possibilities change because they can do it.** See [Power Surface](Power-Surface) for the v6 domain-by-domain transition from generated puissance to relational power. > **Canonical repo source:** `showcase/01-capability-spectrum.md` --- ← [Power Show](Power-Show) · [Home](Home) · [Composition Engine](Composition-Engine) → ================================================================================================ FILE: Power-Dynamics.wiki/Capsules-and-Federation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 062dd5b907b10824ccec3678ccb6d8aeaaddb3fb322f44420ca84a2088d7dcce CONTENT_BYTES: 710 ================================================================================================ # Capsules and Federation Capsules and federation create **infrastructural autonomy puissance**: local deployment, signed packages, verification, rollback, self-hosting, offline operation, and independent continuity. Their political importance is counterpower. A system is less terminal when communities can continue operating, substitute a deployment, verify artifacts, or form branches without permanent permission from one remote operator. The technical power audit should inspect signing keys, registries, update channels, compatibility contracts, and recovery procedures. > **Canonical repo source:** `koa/capsules-federation.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Case-Studies.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 7f629009678347c49585325709cb0d7ed8aaac0f49b63fe25705de7f1828a633 CONTENT_BYTES: 1747 ================================================================================================ # Case Studies The cases are stress tests for the framework. They are not all claims about current deployment. Some are current analytical reconstructions, some are design examples, and some are explicitly legacy proposals. ## Capability and compounding - [Unpublished Corpus as Epistemic Reservoir](Unpublished-Corpus-as-Epistemic-Reservoir) — accumulated knowledge as retained potential, release optionality, flow, and future epistemic puissance. - [Recognition Loop](Recognition-Loop) — achievement → evidence → credibility → access → new capability. ## Media, discoverability and influence - [Media and State](Media-and-State) — why “more powerful” must be decomposed by domain and mechanism. - [SmartVote Discoverability](SmartVote-Discoverability) — discoverability itself as governance. ## Institutional stacking and allocation - [Desjardins Power Stacking](Desjardins-Power-Stacking) — multiple legitimate functions creating cross-domain concentration risk. - [Zero-Skim Philanthropy](Zero-Skim-Philanthropy) — economic contribution separated from democratic allocation authority. ## Stress tests - [AI Hidden Sovereignty](AI-Hidden-Sovereignty) — cognitive assistance becoming opaque interpretive or prioritization power. - [KingCoin Legacy Stress Test](KingCoin-Legacy-Stress-Test) — a legacy centralizing proposal used as a contrast with later non-domination architecture. These cases should be read with [Capability Show Profile](Capability-Show-Profile) and [Power Analysis Method](Power-Analysis-Method), so that impressive capability claims remain inspectable. > **Canonical repo source:** `cases/README.md`, `cases/*.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Cognitive-and-AI-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 971494d51016289dd448ac9dd5accd9dea164277526b8d62f8b218e6f461df31 CONTENT_BYTES: 1608 ================================================================================================ # Cognitive & AI Power > **Core question:** Who or what can shape reasoning, synthesis, modeling, translation, prioritization, and automated interpretation? ## Generated puissance Effective capability to **analyze, synthesize, model, translate, generate, compare, plan, and accelerate cognitive throughput**. ## Relational power that can emerge Framing power, prioritization power, dependency power, hidden-sovereignty risk. ## Typical conversion paths - `AI output → judgment` - `automated ranking → visibility` - `cognitive acceleration → execution capacity` - `model dependence → infrastructural leverage` ## Routing / counterpower direction - AI under explicit governance - bounded roles and human / institutional authority - provenance and reconstructibility - avoid silently converting assistance into policy authority ## kOA touchpoints - AI amplifies the rest of the knowledge-to-action stack - structured knowledge and provenance can constrain and contextualize AI use - AI Hidden Sovereignty is treated as a specific failure mode ## Analytical note The design target is cognitive amplification without institutional sovereignty. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Complementarity-Branches-and-Kristals.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c9a5db5cae3c75c8f7b9ba6c589f97b3bd2e1ddbcd48a4b4e8c34dda550a358e CONTENT_BYTES: 1851 ================================================================================================ # Complementarity, Branches and Competing Kristals Plurality is not treated as relativism, and dominance is not treated as truth. Different branches or Kristals may illuminate different scopes, evidence, methods, contexts, or trade-offs. The question is whether variation adds useful value while lineage and interoperability remain legible. ## Complementarity and anti-dogma Complementarity exists when several branches jointly provide more value than a single universal branch. Scientific, legal, historical, local, experiential, or cultural representations may answer different questions. Credibility systems can specialize in academic, practical, or community evidence. Complementarity is not relativism. Branches remain comparable on explicit dimensions. Dogma, in this framework, is repetition protected from meaningful comparison, revision, or added value. Useful plurality contributes new evidence, context, method, ontology, implementation, translation, or function. > **No branch should become final merely because alternatives cannot be meaningfully formed, compared, supported, or adopted.** ## Lineage and competing Kristals Kristals can preserve divergent claims, evidence, scopes, policies, and contexts without forcing immediate universal convergence. Two Kristals may each claim better representation of a phenomenon. The system should preserve sources, assumptions, validation policy, scope, uncertainty, lineage, added evidence, and unresolved disagreement. A later Kristal may synthesize, specialize, or challenge both. The objective is cumulative epistemic evolution rather than winner-take-all truth declaration. > **Canonical repo source:** `branch-ecology/complementarity-and-antidogma.md`, `branch-ecology/lineage-and-competing-kristals.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Component-Power-Matrix.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b37589f22bbc4f0bcd67d6a1c0d2840f8256a7bb40f117ff5dd42cc803ef5481 CONTENT_BYTES: 3169 ================================================================================================ # kOA Component Power Matrix ## v6: component matrix inside the Power Surface The component matrix answers **which kOA module creates which capability and gate**. The [Power Surface](Power-Surface) adds the broader question: **in which domain does that gate operate, where can its leverage convert, and where is it routed?** Every kOA component should be read in three steps: 1. **What resource does it organize?** 2. **What puissance does it create?** 3. **What power relations can emerge around successful use?** | Component | Generated / amplified puissance | Possible power relations | Power-routing / sharing mechanisms | Counterweights | |---|---|---|---|---| | SemantiK / SenTient | semantic structuration, ambiguity resolution, translation | classification, ontology, framing | explicit ontologies + local semantic control | provenance, contestable categories, alternatives | | Kristal | epistemic + mnemonic puissance | canonization, validation, standard-setting | portable artifacts, lineage, competing Kristals | provenance, reader policies, migration | | Konnaxion | collective, network, discovery puissance | ranking, moderation, visibility, agenda | portability, federation, alternative discovery paths | transparent policies, export, alternatives | | Koali / EkoH | credibility legibility | standing, certification, opportunity | duplicable/shareable Koali distributions + portable evidence | plural models, contestation, interoperability | | SmartVote | comparative and deliberative puissance | weighting, defaults, discoverability | expertise routed into advisory readings | preserved baseline, deterministic lenses | | Orgo | operational puissance | routing, assignment, escalation, closure | explicit roles distribute operational agency | audit, appeal, revocability | | Capsules / federation | replication and local-operation puissance | signing, update, registry | central capability converted into local autonomy | verification, rollback, multiple hosts | | AI | cognitive amplification | framing, prioritization, dependency | assistance under explicit policy rather than model sovereignty | provenance, bounded roles, human authority | | Brand / narrative | affiliation, distribution, fundraising | attention, legitimacy-by-association | ethical self-binding, attribution, protocol/brand separation | brand ≠ truth, criticism, separate stewardship | | Multilingual layer | semantic access | translation framing, inclusion/exclusion | local semantic control + multilingual access | source links, review, non-equivalence notes | ## The design goal > **Increase generated puissance aggressively, route it deliberately, make resulting power relations legible, and keep counterpower effective.** This is the shortest summary of the repo's normative architecture. > **v6 companion:** [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) · [Power Routing & Sharing](Power-Routing-and-Sharing) > **Canonical repo source:** `showcase/07-component-power-matrix.md` --- ← [Compounding Engine](Compounding-Engine) · [Home](Home) · [Governance After Capability](Governance-After-Capability) → ================================================================================================ FILE: Power-Dynamics.wiki/Composition-Engine.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 2ce2748cb516d6f7cdff3158d8a31e07a7f86b8dd6c477e8751ec3206677488a CONTENT_BYTES: 2652 ================================================================================================ # The Composition Engine kOA becomes significantly more powerful when distinct capabilities **compose**. Composition means that one subsystem's output becomes another subsystem's usable input without requiring one subsystem to own the others. > **Composition does not require ownership.** ## The chain ```text Contribution → semantic resolution → structured knowledge → discoverability → credibility context → deliberation / comparison → collective choice → governed work → coordinated action → outcome → reusable memory → new cycle ``` Each step removes a different failure mode. ## Why the whole can exceed the parts A large knowledge base without discovery can remain unused. A network without credible information can coordinate noise. Credibility without deliberation can become status hierarchy. A good decision without workflow can remain aspirational. Execution without memory can repeatedly pay the same learning cost. Memory without provenance can fossilize error. Forkability without interoperability can fragment. The composition engine matters because it joins these functions while preserving the possibility that each function remains governed separately. ## Generated collective puissance Suppose ten people each have: - incomplete knowledge; - limited time; - different skills; - different contacts; - different resources. Without coordination, their resources remain partly latent. With shared artifacts, discovery, explicit credibility context, a choice mechanism, task routing, and persistent memory, the group can perform actions unavailable to any individual participant. That capability is **generated**, not merely transferred. ## Multiplicative intuition A useful heuristic is: ```text collective effectiveness ≈ knowledge quality × discoverability × coordination × decision quality × execution × memory reuse ``` This is not a literal universal formula. It expresses a systems insight: a severe failure in one necessary transition can suppress the value of strong capabilities elsewhere. ## Constitutional consequence Because composition increases capability, the seams among components become political boundaries. Who controls: - discovery; - identity; - credibility interpretation; - defaults; - routing; - signatures; - update channels; - authority registries; - memory; - migration? Every composition seam is therefore both a capability interface and a possible power interface. > **Canonical repo source:** `showcase/03-composition-engine.md` --- ← [Capability Spectrum](Capability-Spectrum) · [Home](Home) · [Compounding Engine](Compounding-Engine) → ================================================================================================ FILE: Power-Dynamics.wiki/Compounding-Engine.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ffda61b1462a74d67fff7e2def60199341f6a87e35745b1ed6669049f391e54d CONTENT_BYTES: 2185 ================================================================================================ # The Compounding Engine The strongest form of capability is not one-time capability. It is capability that leaves behind assets that lower the cost or raise the quality of future action. ## Core loop > **Action → Result → Return → Asset → Reinvestment → Greater Future Puissance** Possible returns include: - knowledge; - experience; - code; - tools; - infrastructure; - documentation; - provenance; - reputation; - credibility; - network relationships; - data; - institutional access; - financial resources; - memory; - optionality. ## Why memory matters Without reusable memory: ```text Act → learn → forget → pay again ``` With reusable memory: ```text Act → learn → preserve → reuse → start higher ``` This is why Kristal and operational memory are not passive archives. They are future capability infrastructure. ## Tools as crystallized past puissance A tool records prior effort in a form that can be reused. ```text past time + knowledge + experimentation → code / procedure / infrastructure → lower future effort → greater future capacity ``` The same applies to documentation, standards, schemas, trusted relationships, and institutional routines. ## Regenerative vs extractive loops An extractive loop looks like: ```text collective activity → value → narrow owner → more owner capacity ``` A regenerative loop looks like: ```text collective activity → value → participants + shared assets + common infrastructure → more distributed capability ``` The constitutional question is therefore: > **Who receives the returns generated by an exercise of collective puissance?** ## kOA transition A founder can bootstrap an ecosystem through concentrated effort. Long-term resilience requires a transition from: > **Founder-powered → System-powered ecosystem** The test is whether accumulated assets become usable, maintainable, forkable, and improvable by others without requiring unique founder knowledge or permission. > **Canonical repo source:** `showcase/04-compounding-engine.md` --- ← [Composition Engine](Composition-Engine) · [Home](Home) · [Component Power Matrix](Component-Power-Matrix) → ================================================================================================ FILE: Power-Dynamics.wiki/Constitutional-Tests.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 01a91622d1997fdd639daad991b332a90214184dd7206d5257a0bb67994224d1 CONTENT_BYTES: 715 ================================================================================================ # Constitutional Tests Stress-test a system with adversarial questions: - What if the maintainer becomes hostile? - What if a credibility policy is biased? - What if the dominant branch stops improving? - What if ranking favors incumbents? - What if a signing key is lost or captured? - What if the official brand owner disagrees with a protocol fork? - What if a provider changes terms? - What if AI output becomes de facto policy? - Can affected actors verify, contest, substitute, exit, and continue? The objective is not perfect immunity but non-terminal failure modes. > **Canonical repo source:** `assessment/constitutional-tests.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Conversion-Chains.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 3e813b6511f619763da0345afa7803a2a92c7b8c99a50787e5f3f816f25cbe25 CONTENT_BYTES: 2169 ================================================================================================ # Capability and Power Conversion Chains ## v6: make source and destination domains explicit Every chain should now be read as `source domain → mechanism → destination domain → resulting leverage`, then tested for routing, counterpower, and mandate. See [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion). Power rarely remains in one domain. Resources and forms of puissance can be converted into other resources, opportunities, and relations of power. ## Common chains ```text knowledge → credibility → visibility → opportunity → resources → better tools → more knowledge ``` ```text brand → attention → affiliation → sales / funding → infrastructure → reach → stronger brand ``` ```text network → collaborators → execution → results → reputation → broader network ``` ```text technical control → control of defaults → user dependence → agenda influence ``` ```text money → infrastructure → distribution → attention → political influence ``` ## Conversion is not automatically illegitimate Systems need conversion. Expertise should influence advice. Money should fund work. Reputation can help discovery. Technical administration is needed to maintain infrastructure. The danger is **automatic cross-domain conversion**. Examples: - expertise becoming political sovereignty; - money becoming more votes; - brand becoming truth; - technical maintenance becoming control of political outcomes; - credibility becoming unquestionable authority; - infrastructure becoming ownership of users. That is why Power Dynamics uses **conversion firewalls** rather than trying to eliminate conversion itself. ## Power stacking When one actor controls several conversion points, legitimate functions can stack into cross-domain leverage. ```text finance + identity + certification + platform access + philanthropy → high cross-domain leverage ``` The issue is not that any one function is illegitimate. The issue is what the combined position makes possible. > **Canonical repo source:** `showcase/05-conversion-chains.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Core-Ontology.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6214a334d91f7031f355a617e9ba433c2cb4e22bc0945082e3f8b5ebb12eebce CONTENT_BYTES: 1506 ================================================================================================ # Core Ontology The canonical ontology is: > **Resource / Asset → Potential → Capacity → Puissance → Power Relation → Effect → Return** This is not a claim that every real process is linear. It is a conceptual separation that prevents category errors. - **Resource / asset** — something available or accumulated that may support action. - **Potential** — what could become realistically possible because those resources exist. - **Capacity** — an organized ability under defined conditions. - **Puissance** — a capacity that is effectively mobilizable under actual conditions. - **Power relation** — a relation in which one actor's or system's puissance changes another's effective possibilities. - **Effect** — the realized change. - **Return** — a reusable asset created or preserved by the effect. ### Knowledge example `research corpus → potential understanding → organized expertise → epistemic puissance → advisory/recognition relation → changed decision → credibility + memory` ### Money example `financial stock → potential purchasing options → liquid capacity → economic puissance → allocation/bargaining relation → funded project → infrastructure + revenue` The ontology does not make relational power morally negative. Power may enable, coordinate, recognize, protect, allocate, constrain, or dominate. > **Canonical repo source:** `framework/01-core-ontology.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Corpus-Map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 26e52f23de4d1138fb79fdcd045635ad484ba7ca3a056f8491659330ffabac33 CONTENT_BYTES: 6147 ================================================================================================ # Corpus Map The corpus map gives stable S01–S28 identifiers to the unpublished and published materials that informed the repository, without implying that every source has equal maturity or doctrinal status. The repository uses stable source IDs. Source IDs identify provenance; they do not imply endorsement or current status. | ID | File | Status | Relevance | |---|---|---|---| | S01 | `Abuser l'humanité v5 KDP.pdf` | FOUNDATIONAL | Critique of modern dependency, debt, time capture, procedural opacity, merit, justice and effective freedom. | | S02 | `Hacking Reality_ practical guide for the next Christ_26-05-2026_17_15_42(2).md` | FOUNDATIONAL | Language, narrative, symbols, recognition, alliances, transmission, learning and collective agency. | | S03 | `Bank Management, instructions v3.docx` | EXPLORATORY-LEGACY | Bank-management and financial-institution design proposals. | | S04 | `branding gold, high-value collectibles(1).docx` | EXPLORATORY-LEGACY | Conversion of material value into symbolic, scarcity, narrative and brand value. | | S05 | `Business Plan_ Gold and Precious Metals Trading Business(1).docx` | EXPLORATORY-LEGACY | Precious-metals business, storage, trading and financial-capacity design. | | S06 | `charities through your more efficient system, you can greatly reduce administrative costs.docx` | EXPLORATORY-LEGACY | Early philanthropy, administrative-efficiency and allocation ideas. | | S07 | `Contre l’Abus Financier Systémique _ Le Manifeste Stratégique du Mouvement kOA.docx` | FOUNDATIONAL-ECONOMIC | Financial abuse, dependency, redistribution and institutional redesign. | | S08 | `Copie de Abus financier, inégalité.docx` | FOUNDATIONAL-ECONOMIC | Inequality, access, invention, entrepreneurship and economic dependency. | | S09 | `Debt management using King Koin as a stable reserve during currency oscillations, technical mechanisms.docx` | LEGACY-PROPOSAL | King Koin reserve/debt-management mechanisms. | | S10 | `Desjardins_ Projet complet de transformation coopérative.docx` | EXPERIMENTAL-PROPOSAL | Member governance, allocation, identity, certification and cooperative financial infrastructure. | | S11 | `Economic method.docx` | LEGACY-PROPOSAL | Global redistribution, KingCoin, automated enforcement, sanctions and public investment. | | S12 | `Outline redistib richesses et territoires.docx` | LEGACY-PROPOSAL | Redistribution of wealth, territory, migration and international sharing. | | S13 | `kOA Digital Ecosystem — Connaître, choisir, agir, se souvenir(20260902-205259).md` | CURRENT-CORE | Know → Choose → Act → Remember; controlled transformations and collective capability. | | S14 | `Zero-Skim Philanthropy Blueprint(20260902-205251).md` | CURRENT-EXPERIMENTAL | Cooperative donation rail, one-member-one-vote allocation, auditability and structural leakage reduction. | | S15 | `SmartVote _ un « like » de niveau gouvernance qui fait émerger les meilleurs contenus dans Konnaxion(20260902-205251).md` | CURRENT-EXPERIMENTAL | Discoverability as governance; raw and weighted readings; domain-bounded expertise. | | S16 | `Semantic Sovereignty and Non-Domination_ Toward an Offline, Governable Knowledge Infrastructure.docx(20260902-205250).md` | CURRENT-CORE | Non-domination, semantic sovereignty, offline operation, auditability, determinism and multilinguality. | | S17 | `Democracy with Informed Advice_ A Merit-Based, Ethics-Governed Parallel Channel(20260902-205251).md` | CURRENT-EXPERIMENTAL | Parallel advisory channel: expertise informs without replacing political equality. | | S18 | `L’intelligence collective comme nouveau pôle du pouvoir V3 (Roussin)(20260902-205250).md` | CURRENT-CORE | Collective intelligence as infrastructural power; mediation, visibility, credibility, execution and memory. | | S19 | `Jourdain_Toward_a_Governable_Civic_Infrastructure_Thesis_Draft_March_2026 (Benkler)(20260902-205251).md` | CURRENT-ANALYTICAL | Governable civic infrastructure, semantic sovereignty, bounded expertise, recourse and soft-technocracy risks. | | S20 | `Francois_Jourdain_Governable_Civic_Infrastructure_Thesis_Draft_March_2026(Beth)(20260902-205252).md` | CURRENT-ANALYTICAL | Public capacity, civic infrastructure, pilot criteria and institutional governability. | | S21 | `COLLECTIVE INTELLIGENCE AS DEMOCRATIC GOVERNANCE INFRASTRUCTURE(Fung)(20260902-205251).md` | CURRENT-ANALYTICAL | Power, legitimacy, non-domination, execution, memory and advisory safeguards. | | S22 | `Francois_Jourdain_Thesis_Draft_Forming_Publics_Governing_Meaning_March_2026(Marres)(20260902-205251).md` | CURRENT-ANALYTICAL | Meaning, classification, mediation, publics, narrative self-limitation and semantic power. | | S23 | `Rapport sur l'Empire de Réjean McCormick(20260902-205251).md` | EXTERNAL-ANALYTICAL | External-style synthesis of the project's institutional, symbolic and political ambitions; not canonical by itself. | | S24 | `L’ampleur réelle _ pas un projet, mais une architecture du monde social(20260902-205251).md` | ANALYTICAL-RECONSTRUCTION | Macro map of kOA as socio-technical, symbolic and institutional architecture. | | S25 | `kOA_ A Governable Knowledge-to-Action Ecosystem for the Commons(20260902-205251).md` | CURRENT-CORE | Commons-facing account of kOA, collective capability, portability, auditability and non-enclosure. | | S26 | `Analyse Stratégique et Socio-Technique _ La Mutation de la Vérité et le Capital Épistémique(20260902-205251).md` | ANALYTICAL-RECONSTRUCTION | Epistemic capital, compounding collective capacity, EkoH and SmartVote. | | S27 | `A Technosocial Architecture for Knowledge-to-Action.docx(20260902-205258).md` | CURRENT-ANALYTICAL | Integrated knowledge-to-action architecture, open knowledge, validation, collaboration and governance. | | S28 | `FINAL Domain-Bounded Collective Intelligence_ Merit, Safety, and Scale(5).md` | CURRENT-EXPERIMENTAL | Domain-bounded expertise weighting, evidence, time decay, ethics multipliers, audit and human oversight. | > **Canonical repo source:** `sources/corpus-map.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Counterpower-and-Optionality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c4eef9b0b93cb8f1bd72e04bef205cac7f7a7873f7991ce00f45b5e01293c82c CONTENT_BYTES: 2223 ================================================================================================ # Counterpower and Optionality as Capability The Power Show includes not only the ability to **do more**, but also the ability to **depend less**. A system that can coordinate, rank, certify, route, or preserve memory is powerful. A participant who can verify, contest, substitute, exit, fork, or wait also possesses important capability. ## Verification puissance Ability to independently inspect claims, provenance, signatures, rules, calculations, policies, and technical behavior. ## Contestation puissance Ability to challenge a decision, score, category, workflow, authority, branch, or interpretation through a process capable of producing change. ## Substitution puissance Ability to replace a provider, implementation, trust root, reader policy, workflow, branch, or institution with a viable alternative. ## Exit puissance Ability to leave while preserving enough identity, history, knowledge, reputation, data, rights, relationships, and continuity for departure to be meaningful. ## Forking puissance Ability to create an alternative rather than accept the existing implementation as terminal. ## Branch mobility Ability to move beyond a symbolic fork: attract maintainers, preserve interoperability, gain discoverability, gather support, and become institutionally viable. ## Optionality puissance Ability to preserve future choices rather than commit them prematurely. Examples include: - retained financial reserves; - unpublished knowledge; - unused deployment capacity; - privacy and unrevealed identity; - multiple providers; - portable credentials; - branchable software; - independent infrastructure. Optionality is important because **unexercised capability can still change future strategic position**. ## The inversion Traditional power analysis often asks who can compel whom. Power Dynamics also asks: > **Who can refuse? Who can leave? Who can reproduce? Who can create an alternative? Who can preserve the option to act later?** These are central forms of practical freedom and therefore belong inside the Power Show itself. > **Canonical repo source:** `showcase/10-counterpower-and-optionality.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Counterpowers-and-Legibility.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b5f9b716ee49592a517f4df5bab229c18109b7217cad843a5238b115983f0b48 CONTENT_BYTES: 870 ================================================================================================ # Counterpowers, Legibility, Provenance, and Auditability A minimum counterpower package is: > **Verification + Contestation + Substitution + Exit** Power should also be legible enough that affected actors can identify the relevant holder, mechanism, mandate, inputs, outputs, version, and appeal path. **Provenance** preserves where claims, artifacts, decisions, and transformations came from. **Auditability** allows independent reconstruction or verification. Transparency is not sufficient by itself. A transparent system that cannot be contested or substituted can remain dominating. Complexity is not inherently illegitimate either; the problem is complexity functioning as an unanswerable source of authority. > **Canonical repo source:** `constitution/counterpowers-and-legibility.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Credibility-and-Reputation-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c2655b2c80f9458bb486ffa4f6aa9510478edb156087756fc29df94fd265733f CONTENT_BYTES: 1672 ================================================================================================ # Credibility & Reputation Power > **Core question:** Who can shape standing, trust signals, certification, expertise legibility, and access to opportunity? ## Generated puissance Effective capability to **make demonstrated competence, contribution, reliability, and evidence legible under explicit criteria**. ## Relational power that can emerge Standing power, certification power, endorsement power, opportunity power. ## Typical conversion paths - `evidence → credibility` - `credibility → visibility` - `credibility → access / opportunity` - `recognition → network growth` ## Routing / counterpower direction - domain-bounded signals - score ≠ person ≠ competence ≠ truth - plural credibility models and distributions - contestability, history, time decay, and portable evidence ## kOA touchpoints - Koali / EkoH organize credibility and expertise signals - SmartVote can use advisory readings without converting credibility into sovereign votes - Koali protocolization aims to avoid one terminal owner of standing ## Analytical note Credibility is useful precisely because it can affect attention and opportunity. That same usefulness makes credibility infrastructure a major power surface. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Cross-Domain-Power-Conversion.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 7e5e2d2661767b711de9fbd7fbde62e2f2247d8e0199d7385b2f27ddbabc9927 CONTENT_BYTES: 3257 ================================================================================================ # Cross-Domain Power Conversion Power is often most consequential when capability or authority in one domain is converted into leverage in another. ## Conversion A conversion can be represented as: ```text source resource / puissance → conversion mechanism → destination resource / puissance / power relation ``` Examples: ```text knowledge → evidence of competence → credibility credibility → ranking / endorsement → visibility visibility → audience → opportunity money → purchase / funding → infrastructure infrastructure → dependency → bargaining leverage brand → affiliation → revenue administrative control → defaults → de facto policy ``` ## Cross-domain leverage Not all conversion is problematic. Many desirable systems depend on it. The problem begins when: 1. the conversion is hidden; 2. the destination authority exceeds the source mandate; 3. affected actors cannot contest or substitute; 4. the conversion compounds through multiple domains; 5. the resulting leverage becomes durable or terminal. ## Capture > **Capture occurs when control over one legitimate function is converted into durable influence over functions outside its intended mandate.** Canonical warning pattern: > **Functional Control → Cross-Domain Power** ## Power stacking Power stacking occurs when one actor or node combines several functions whose interactions create leverage not visible when each function is assessed separately. For example: ```text identity + credibility + discovery + funding + workflow = cross-domain leverage ``` or: ```text monetary rail + taxation + allocation + sanctions + dispute enforcement = high terminality risk ``` ## Conversion firewalls A conversion firewall does not prohibit composition. It prevents **automatic authority inheritance**. Examples: - expertise → advice, not sovereignty; - money → funding, not votes; - brand → attention, not truth; - credibility → discoverability, not unquestionable authority; - infrastructure → capability, not ownership of users; - execution → mandate implementation, not mandate redefinition. ## Analytical procedure For each important function: 1. Name the source domain. 2. Name the source resource/capability. 3. Identify the conversion mechanism. 4. Name the destination domain. 5. Identify the resulting power relation. 6. Measure dependency and switching cost. 7. Identify returns and compounding. 8. Identify firewall, contestation, substitution, or exit. 9. Test whether the destination authority is within mandate. 10. Test whether capture of the instance would imply capture of the system. ## Relation to the three-axis model Cross-domain conversion connects the three axes: - **ontology** — what changes state; - **dynamic** — conversion / compounding / capture; - **domain** — where the source and destination operate. This is why the domain axis must be explicit rather than a loose list of examples. ## Continue - [Conversion Chains](Conversion-Chains) - [Power Conversion Firewalls](Power-Conversion-Firewalls) - [Desjardins Power Stacking](Desjardins-Power-Stacking) - [Power Surface Audit](Power-Surface-Audit) > **Canonical v6 repo source:** `framework/10-cross-domain-power-conversion.md` ================================================================================================ FILE: Power-Dynamics.wiki/Desjardins-Power-Stacking.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 8df61a15eef3d267133d6f8612d72b03830b2b6b4ee0209b24425bf8bb2b1376 CONTENT_BYTES: 562 ================================================================================================ # Desjardins and Power Stacking The Desjardins proposal combines member governance with possible roles in banking, identity, certification, philanthropy, and Konnaxion access. Each function may be legitimate while their combination creates cross-domain leverage. The design question is how to keep financial infrastructure strong in its mandate without silently becoming identity, epistemic, political, or platform sovereignty. > **Canonical repo source:** `cases/desjardins-stacking.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Dynamics.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 0e9f238054afc1bfa4655791ea4ca281c67ae554d7c2ea08f4ce01ed6b46dac5 CONTENT_BYTES: 2990 ================================================================================================ # Dynamics The Power Show describes **what kOA can generate**. Dynamics describes **what happens to capability and power over time**. The v6 dynamic sequence is: > **Formation → Mobilization → Composition → Conversion → Returns / Compounding → Concentration / Capture → Counterpower → Diversification / Evolution → Decay → Transfer → Externalities / Scale → Routing / Sharing / Devolution** The sequence is recursive rather than linear. ## 1. Formation Resources become potential, organized capacity, and effectively mobilizable puissance. ## 2. Mobilization Retained resources or existing puissance become active through release, flow, mediation, amplification, and throughput. `Reservoir → Release → Flow → Mediation` is one mobilization model, not the whole theory. ## 3. Composition and generated puissance Distinct capabilities combine into higher-order capability that existed nowhere individually. ## 4. Conversion and firewalls One resource, capability, or relational advantage becomes another. v6 makes the **source domain → mechanism → destination domain** path explicit. ## 5. Returns, reinvestment, and compounding Action can leave reusable assets that increase future capability. > **Puissance → Action → Result → Return → Reinvestment → Greater Future Puissance** ## 6. Concentration, stacking, and capture Several legitimate functions or accumulated returns can create cross-domain leverage. > **Functional Control → Cross-Domain Power** ## 7. Counterpower, contestation, and exit Actors can alter the terms of power through verification, challenge, substitution, refusal, exit, or fork. ## 8. Diversification and evolution Alternatives emerge, demonstrate value, gather support, coexist, recombine, or replace dominant branches. ## 9. Decay, dissipation, and loss Reputation, network position, knowledge relevance, infrastructure, liquidity, legitimacy, and organizational capacity can erode. ## 10. Transfer, succession, and inheritance Resources, authority, keys, mandates, memory, and stewardship move across actors and generations. ## 11. Externalities and scale A useful mechanism can acquire systemic power because adoption, network effects, standards, or dependency grow around it. ## 12. Routing, sharing, and devolution v6 adds an explicit dynamic for **where generated capability, authority, returns, and optionality are sent**. ```text generated leverage → concentrating default → routing mechanism → distributed / scoped destination ``` Examples include protocolization, self-hosting, plural Koali distributions, ethical self-binding, advice without sovereignty, democratic allocation, and branch mobility. See [Power Routing & Sharing](Power-Routing-and-Sharing). > **Canonical v6 repo hierarchy:** `dynamics/README.md` as described in `TREE.md`; v6 adds `12-routing-sharing-and-devolution.md`. --- [Home](Home) · [Three-Axis Model](Three-Axis-Model) · [Power Surface](Power-Surface) ================================================================================================ FILE: Power-Dynamics.wiki/Economic-and-Allocation-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 21f2b14b72837bd26d0e9d8ec19f2af00ee0c9b859c6f9b85125897ff299d58d CONTENT_BYTES: 1970 ================================================================================================ # Economic & Allocation Power > **Core question:** Who can mobilize scarce resources and decide which people, projects, institutions, or goals receive them? ## Generated puissance Effective capability to **mobilize money, property, labor, time, funding, procurement, infrastructure, contracts, and productive assets**. ## Relational power that can emerge Bargaining power, property power, allocation power, funding dependence, purchasing leverage. ## Typical conversion paths - `money → infrastructure` - `funding → execution capacity` - `credibility → opportunity / funding` - `brand → revenue` - `network → customers / collaborators / access` ## Routing / counterpower direction - money → funding, not political standing - democratic allocation where collective funds are governed - returns should be audited for who accumulates reusable assets - shared infrastructure can turn collective activity into broader future capability ## kOA touchpoints - Zero-Skim illustrates common resource pooling with political firewalls - brand / merchandise can convert symbolic attention into economic resources - Koali / credibility can affect opportunity and funding access - Orgo converts funding into accountable execution - compounding turns results into future assets ## Analytical note Money is a resource stock, not power by identity. It becomes economic puissance when mobilizable, then relational economic power when its use changes others’ access, bargaining position, allocation, or dependency. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Effective-Possibility.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 510eb816143c88b9b541bb755763ce9e713db0354ed0c1c2ebaf99b0712bd5dd CONTENT_BYTES: 1187 ================================================================================================ # Effective Possibility The framework's central object is not abstract freedom but **effective possibility**. A formal option can exist while remaining practically unusable. A person may possess a legal right but lack time, money, information, institutional recognition, language access, transportation, technical capability, or a viable appeal process. Conversely, infrastructure can expand effective possibility by reducing those barriers. This is why dependency is central. If essential possibilities depend on an actor whose rules are opaque, unilateral, difficult to contest, or costly to exit, that dependency creates relational leverage even if the actor rarely intervenes. Effective possibility should be assessed through access, affordability, time cost, intelligibility, technical operability, legal recognition, portability, alternatives, coordination cost, reversibility, risk, and institutional acceptance. The objective is not perfect quantification. It is to make the relevant constraints and enabling conditions **legible**. > **Canonical repo source:** `framework/02-effective-possibility.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Epistemic-and-Semantic-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: cdcf3834f60e1e423398672d1c9693ce8ff3c7cf2e4345630e50683e15ebd85e CONTENT_BYTES: 1715 ================================================================================================ # Epistemic & Semantic Power > **Core question:** Who can shape what is knowable, valid, categorized, translated, comparable, or admissible? ## Generated puissance Effective capability to **validate, compare, structure, version, translate, preserve, and reuse knowledge and meaning**. ## Relational power that can emerge Canon power, validation power, classification power, framing power, admissibility power, trust-root power. ## Typical conversion paths - `meaning → knowledge` - `knowledge → credibility` - `classification → enforcement / agenda` - `epistemic standing → visibility / opportunity` ## Routing / counterpower direction - portable artifacts and provenance - competing / complementary Kristals - versioned semantics and explicit policy identity - local semantic governance and contestation ## kOA touchpoints - SemantiK / SenTient structure concepts, relations, ambiguity, and translation - Kristal preserves provenance, versioning, and reusable knowledge - reader policies and competing representations prevent one reading from becoming final by default ## Analytical note To govern meaning is already to govern part of the collective field of possibility. The goal is not semantic neutrality but governable, revisable mediation. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Ethical-Fiction-as-Self-Binding.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: dcb95db3321ed79afa8cd96b78dff227fbb6d77143ff6fa6c0134f9d5850f4b6 CONTENT_BYTES: 1822 ================================================================================================ # Ethical Fiction as Self-Binding Fiction can create attention, recognition, affiliation, emotional salience, memory, and transmission. That is real symbolic puissance. One distinctive kOA mechanism is to publish **ethical principles inside the fiction itself**. The source corpus explicitly includes a living ethical code centered on clarity of intention, respect for living beings, vigilance against monopoly, domination and manipulation, public recognition of contributors, self-mockery, regular ethical reassessment, revision, criticism, and non-dogmatic transmission. ## Power redirection This does more than state values. ```text Narrative puissance → ethical constraints carried by the narrative → public commitments → critics and participants can cite them → symbolic authority becomes more contestable ``` The same material also redirects symbolic capital: - recognize contributions; - publicly thank allies; - share merit; - never sanctify the Klown; - reject dogma; - document and transmit; - pass the baton; - treat reinvention rather than fidelity as legitimate succession. A related analytical text describes the public persona as a **diffusion instrument** distinct from the architect identity and oriented toward reducing founder-worship. ## What this does not do Published ethics are not enforcement. They do not prove compliance. They become politically stronger when combined with auditability, attribution, contestation, portability, exit, forkability, and independent operation. > **Narrative may mobilize, but it should also carry instructions for resisting its own capture.** > **Canonical repo source:** `cases/ethical-fiction-self-binding.md` --- ← [Brand, Founder & Optionality](Brand-Founder-and-Optionality) · [Power Routing & Sharing](Power-Routing-and-Sharing) → ================================================================================================ FILE: Power-Dynamics.wiki/Evolutionary-and-Counterpower.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: aa179254b68062d1249858e022215866a14f441bf1a39cf6af5a1560f2314683 CONTENT_BYTES: 1638 ================================================================================================ # Evolutionary & Counterpower > **Core question:** Who can challenge, substitute, fork, recombine, improve, displace, or replace an incumbent implementation or authority? ## Generated puissance Effective capability to **verify, contest, substitute, exit, fork, recombine, demonstrate alternatives, and gather support**. ## Relational power that can emerge Incumbent displacement power, branch mobility, substitution leverage, exit power. ## Typical conversion paths - `criticism → variation` - `variation → demonstration` - `demonstration → support` - `support → adoption / dominance` - `fork → institutional replacement` ## Routing / counterpower direction - branch mobility and lineage - interoperability and data / provenance portability - effective exit and substitution - stable kernel with evolving branches ## kOA touchpoints - competing Kristals preserve plurality - federation and self-hosting create alternative operating paths - branch ecology turns imperfection into ongoing institutional experimentation ## Analytical note Forkability is insufficient if alternatives cannot attract users, preserve history, interoperate, or gather institutional support. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Exit-Portability-and-Federation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 53890451baefd1e4562314077dfad093cf6c75ca182c86c32729b33e8db3ed42 CONTENT_BYTES: 1838 ================================================================================================ # Exit, Portability and Federation Exit is not merely a legal permission. It is an effective capability that depends on portability, substitution, deployability, interoperability, and the practical survival of alternatives. Federation lets capability scale without requiring all sovereignty to scale with it. ## Revocability, exit and portability Revocation removes future authority. Reversal addresses prior effects. They are different. A ranking rule can be changed while earlier reputational effects persist. A decision-maker can be removed while contracts, debts, or standards remain. Exit and fork are structural counterpowers only when effective. Portability can include data, knowledge artifacts, identity, credentials, reputation evidence, decision history, operational records, schemas, protocols, and deployment tooling. A technically forkable project can remain practically monopolistic if forks lose recognition, network access, compatibility, or essential assets. Constitutional analysis should therefore ask both whether authority can be revoked and whether affected actors can actually migrate, recover, or continue. ## Federation and subsidiarity Federation coordinates independently governed nodes through shared contracts rather than requiring a flat or centerless architecture. Subsidiarity places decisions at the lowest level capable of handling them effectively while preserving necessary coordination. The repo rejects `federation = no center`. Strong local hubs, shared standards, and central reference services can coexist with local sovereignty if substitution and independent operation remain meaningful. > **Canonical repo source:** `constitution/revocability-exit-portability.md`, `constitution/federation-subsidiarity.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/FAQ.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: d6cfa2dc4f533cf75631e466b00499690cad4709ad9b6383073671a983efd71a CONTENT_BYTES: 4574 ================================================================================================ # FAQ ## Is Power Dynamics a theory of domination? No. It studies constructive capability as seriously as constraint. The project begins with the kOA Power Show: how people and collectives become more capable. Domination enters when consequential power becomes arbitrary, cross-domain, difficult to verify, impossible to contest, or effectively inescapable. ## Why use the French word *puissance* in an English framework? Because it prevents a useful distinction from collapsing. `Puissance` means effectively mobilizable capacity. `Power` is reserved for relational effects on another actor’s effective possibilities. ## Is money power? Not automatically. Money is a resource stock. Under real conditions it can become economic puissance, which can then create bargaining, allocation, access, ownership, or influence relations. ## Is expertise power? Expertise is first an epistemic capacity. It becomes relational power when it changes standing, access, decisions, ranking, or authority. The framework therefore accepts `expertise → advice` while resisting `expertise → automatic sovereignty`. ## Why is discoverability governance? Because what becomes visible is more likely to be read, cited, funded, reused, adopted, or acted upon. Ranking and discovery systems can therefore shape effective possibility before formal decisions occur. ## Does kOA eliminate capture? No. It tries to make capture **non-terminal** through legibility, scoped authority, substitution, portability, exit, federation, and branch mobility. ## Why allow strong hubs at all? Because useful centrality can lower coordination cost. The target is not flatness; it is `StrongHub + DistributedCapability + ReplicableWhole`. Functional centrality should not silently become total sovereignty. ## Is the dominant branch the true branch? No. `dominance ≠ truth ≠ quality ≠ perfection`. Dominance may reflect network effects, timing, brand, compatibility, or accumulated support. Better or complementary branches need practical mobility, not only a formal right to fork. ## What is the main kOA capability loop? > **Know → Choose → Act → Remember → Know better** The Power Show interprets the same loop as capability generation, composition, action, return, reinvestment, and compounding. ## Where should I start? Start with [Power Show](Power-Show). If you want the rigorous vocabulary immediately afterward, read [Core Ontology](Core-Ontology) and the [Glossary](Glossary). > **Canonical v6 repo sources:** `README.md`, `POWER-SHOW.md`, `POWER-SURFACE.md`, `POWER-ROUTING.md`, `GLOSSARY.md`, `PRINCIPLES.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ## Does kOA try to keep all the power it generates? No. A major design theme is **power routing**: protocolization, plural distributions, self-hosting, advisory separation, branch mobility, public ethical self-binding, and democratic allocation redirect capability and leverage toward participants, communities, protocols, and alternatives rather than treating terminal platform ownership as the objective. See [Power Routing & Sharing](Power-Routing-and-Sharing). ## What is new in v6? v6 makes the **Power Surface** explicit. It separates political, economic, and monetary power; maps cross-domain conversions; adds routing / sharing / devolution as a first-class dynamic; and makes the Power Surface Audit the natural entry point for system analysis. ## Is political power only voting power? No. Political power can be produced before, during, and after a formal vote: > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** That is why semantic, discoverability, credibility, administrative, and mnemonic mechanisms can all have political consequences. ## What is the difference between economic and monetary power? Economic power concerns mobilization and allocation of scarce resources such as money, property, labor, funding, and infrastructure. Monetary power concerns the infrastructure and conditions of exchange itself: issuance, payment rails, settlement, reserves, liquidity, credit, convertibility, and transaction access. ## Why is Power Routing part of the Power Show? Because distributing the capability to operate, reproduce, contest, or leave a system is itself a form of generated puissance. Self-hosting, plural Koali distributions, portable Kristals, branch mobility, and public ethical self-binding are not only defensive constraints; they create new capability for others. ================================================================================================ FILE: Power-Dynamics.wiki/Forms-of-Puissance.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 9cda341ea7f541fa7cc5071aec3a8b2d5fc4d73de1ebac10cb202436fc57ecd7 CONTENT_BYTES: 2486 ================================================================================================ # Forms of Puissance This page is the capability side of the Power Show: the forms of effective capacity that actors and collectives can mobilize before asking what relational power those capacities create. This directory names the **positive capability side of the Power Show**. **Puissance** is effective mobilizable capacity. Before asking who controls whom, Power Dynamics asks what an actor, group, institution, or infrastructure can actually do. ## Agency and cognitive puissance Choose, refuse, learn, reason, synthesize, model, plan, create, evaluate, and use governed AI assistance. ## Epistemic and semantic puissance Produce, structure, validate, compare, translate, preserve, contest, and evolve knowledge and meaning. ## Collective, network, and coordination puissance Find people, combine distributed expertise, form groups, coordinate roles, synchronize action, and create capability no participant possessed alone. ## Deliberative and decision puissance Compare alternatives, preserve reasons, incorporate advisory expertise, and choose through explicit procedures. ## Operational and administrative puissance Route work, assign responsibility, manage timing, escalate, execute, review, and close loops. ## Mnemonic puissance Preserve provenance, decisions, actions, failures, outcomes, and lineage so the next cycle starts from reusable memory. ## Economic and allocation puissance Mobilize material resources, funding, productive assets, and allocation mechanisms. ## Technical and infrastructural puissance Build, inspect, modify, test, reproduce, repair, deploy, self-host, and maintain systems that lower future coordination costs. ## Distribution, brand, and affiliation puissance Transmit knowledge, make people or projects discoverable, create public recognition, affiliation, and reach across communities and languages. ## Federation, exit, and evolutionary puissance Operate independently, substitute dependencies, fork, gather support, preserve interoperability, recombine, and replace dominant branches. These forms can compose. They become **power relations** only when their exercise materially changes another actor's access, options, standing, visibility, allocation, authority, dependency, interpretation, or ability to act. See [Capability Spectrum](Capability-Spectrum) for the kOA-facing presentation. > **Canonical repo source:** `puissance/README.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Founder-Decentering.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6708897ab75edad1166b6faa58686d0be9cb7830be9146d94c3fce8d9a14a99a CONTENT_BYTES: 1068 ================================================================================================ # Founder Decentering Founder power can arise from authorship, vocabulary, repositories, domains, brand, relationships, keys, architecture knowledge, and interpretive authority. The goal is not necessarily founder removal. It is independent reproducibility: > **Founder → Architecture → Distributed Mastery** rather than: > **Founder → Permanent Interpretive Dependency** Useful phases include founder sovereignty, constitutional constraints, maintainer pluralism, institutional federation, and protocol-level continuity. > **Canonical repo source:** `constitution/founder-decentering.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ## From founder power to ecosystem capability The target is not merely less founder power. It is conversion: > **Founder-powered → Architecture-powered → Protocol-powered → Ecosystem-powered** Documentation, reproducibility, self-hosting, Koali plurality, branch mobility, and public ethical self-binding redirect founder-specific assets into capability others can use independently. ================================================================================================ FILE: Power-Dynamics.wiki/From-Individual-to-Federation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: d4e4067612642a414768df7b5c1d5fde1459391d9bcd3677c29d9e7a2a577220 CONTENT_BYTES: 1997 ================================================================================================ # From Individual to Federation kOA's power show is also a **scale show**. The same architecture can increase capability at different social scales without assuming that every scale requires the same center. ## Individual Potential gains include: - better access to structured knowledge; - stronger personal memory and provenance; - AI-assisted cognition; - better discovery of expertise and opportunities; - easier publication and reuse; - more informed choice; - greater exit and optionality. ## Group A group can gain capabilities no member has alone: - shared context; - distributed expertise; - collective comparison; - task routing; - explicit ownership; - coordination; - reusable memory; - stronger network reach. This is **generated collective puissance**. ## Organization At organizational scale, the architecture adds: - roles and mandates; - governed workflows; - escalation; - decision records; - institutional memory; - auditability; - repeatable operating patterns; - succession and continuity. ## Federation A federation can add: - local sovereignty over local operation; - shared interoperability contracts; - portable knowledge; - distributed deployment; - branchable governance; - independent continuity; - cross-instance learning; - substitution of providers or implementations. The target architecture is: > **StrongHub + DistributedCapability + ReplicableWhole** This permits useful centrality without making the center the sole source of truth, continuity, identity, or capability. ## Scaling without scaling sovereignty The important design challenge is: > **Can capability scale faster than dependency on any single sovereign node?** That is why portability, federation, explicit authority scope, provenance, branch mobility, and local operation belong inside the power show rather than being afterthoughts. > **Canonical repo source:** `showcase/02-individual-to-federation.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Getting-Started.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 99f3d673f142a512ff5dca8b2581ff2e029312db0bf169b13fe6abf26574a562 CONTENT_BYTES: 3991 ================================================================================================ # Getting Started Power Dynamics v6.2 has a deliberate reading order: > **Why kOA is powerful → Power Surface → Composition → Compounding → Conversion → Routing → Constitution → Evolution → Audit** ## 10-minute path 1. [Why kOA Is Immensely Powerful](Why-kOA-Is-Immensely-Powerful) 2. [Power Surface](Power-Surface) 3. [Power Routing & Sharing](Power-Routing-and-Sharing) This gives the core thesis: kOA can create capability across many domains, connect those capabilities into recursive loops, and deliberately redirect important forms of leverage outward. ## 30-minute Power Show path 1. [Power Show](Power-Show) 2. [Capability Spectrum](Capability-Spectrum) 3. [Composition Engine](Composition-Engine) 4. [Compounding Engine](Compounding-Engine) 5. [Component Power Matrix](Component-Power-Matrix) 6. [Political, Economic & Monetary Power](Political-Economic-and-Monetary-Power) 7. [Power Routing & Sharing](Power-Routing-and-Sharing) ## 45-minute theory path 1. [Core Ontology](Core-Ontology) 2. [Effective Possibility](Effective-Possibility) 3. [Three-Axis Model](Three-Axis-Model) 4. [Power Domains](Power-Domains) 5. [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) 6. [Dynamics](Dynamics) 7. [Power Relations](Power-Relations) The ontological chain is: > **Resource → Potential → Capacity → Puissance → Power Relation → Effect → Return** ## Governance path 1. [Power Constitution](Power-Constitution) 2. [Power Routing & Sharing](Power-Routing-and-Sharing) 3. [Power Conversion Firewalls](Power-Conversion-Firewalls) 4. [Counterpowers & Legibility](Counterpowers-and-Legibility) 5. [Non-Domination & Terminality](Non-Domination-and-Terminality) 6. [Exit, Portability & Federation](Exit-Portability-and-Federation) 7. [Branch Ecology](Branch-Ecology) The constitutional shorthand is: > **Strong distributed puissance. Weak sovereignty.** ## Political / economic / monetary path 1. [Political, Economic & Monetary Power](Political-Economic-and-Monetary-Power) 2. [Political & Constitutional Power](Political-and-Constitutional-Power) 3. [Economic & Allocation Power](Economic-and-Allocation-Power) 4. [Monetary, Credit & Liquidity Power](Monetary-Credit-and-Liquidity-Power) 5. [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) 6. [Zero-Skim Philanthropy](Zero-Skim-Philanthropy) 7. [KingCoin Legacy Stress Test](KingCoin-Legacy-Stress-Test) ## Audit path Start with [Power Surface Audit](Power-Surface-Audit). It asks, domain by domain: - what resources exist; - what capacity and puissance they create; - what relational power emerges; - who controls the surface; - where power converts; - who receives capability, authority, returns, and optionality; - whether verification, contestation, substitution, exit, and fork remain effective. Then continue to [Power Routing Audit](Power-Routing-Audit), [Power Balance Sheet](Power-Balance-Sheet), and [Constitutional Tests](Constitutional-Tests). ## Academic lineage path Use this path when you want to compare Power Dynamics with established research rather than read the framework only on its own terms: 1. [Academic Lineage](Academic-Lineage) 2. [Power, Dependence, Domination & Conversion](Academic-Lineage-01-Power-Dependence-and-Domination) 3. [Polycentric Governance & Institutions](Academic-Lineage-02-Polycentric-Governance-and-Institutions) 4. [Modularity, Standards & Path Dependence](Academic-Lineage-03-Modularity-Standards-and-Path-Dependence) 5. [Expertise, SmartVote & Collective Judgment](Academic-Lineage-06-Expertise-SmartVote-and-Collective-Judgment) 6. [Classification, Infrastructure & Code](Academic-Lineage-08-Classification-Infrastructure-and-Code) 7. [Academic Lineage Bibliography](Academic-Lineage-Bibliography) The rule for this section is strict: **convergence is not endorsement, and a supporting literature does not validate a specific implementation.** --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Glossary.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: aab8c99db0c7d84d93ecb360b9e6b9482966a838214ddaa9fc29ed9847918424 CONTENT_BYTES: 33154 ================================================================================================ # Canonical Glossary This glossary is normative for repository terminology. It keeps the **kOA Power Show** expressive without allowing broad language such as “powerful” to collapse distinct analytical states. When a term is used differently in a source document, preserve the source meaning and explicitly distinguish it from the repository definition. ## Canonical distinctions | Do not conflate | Canonical distinction | |---|---| | resource / power | a resource supports action; power is relational | | potential / capacity | potential is unrealized possibility; capacity is organized ability | | capacity / puissance | capacity can exist without being effectively mobilizable; puissance is effective under real conditions | | puissance / power | puissance produces effects; power shapes another actor's effective possibilities | | stock / flow | stock is accumulated; flow is movement or throughput | | reservoir / power | a reservoir retains resources or options; it does not store relational power as a substance | | score / competence | a score is a governed reading of evidence, not competence itself | | credibility / truth | credibility affects trust; it does not establish truth by itself | | support / evidence | support is social endorsement; evidence supports a claim or evaluation | | dominance / quality | dominance describes position or adoption; quality is multidimensional and contestable | | forkability / branch mobility | a fork may be possible while remaining unable to attract users, evidence, interoperability, or institutional support | | centrality / sovereignty | a hub may be functionally central without possessing total or terminal authority | ### French / English convention The repository deliberately keeps **puissance** in French even inside English prose when precision matters. English *power* collapses several meanings that this framework separates. - **potential / potentiel** — unrealized possibility; - **capacity / capacité** — organized ability; - **puissance** — effectively mobilizable capacity; - **power / pouvoir relationnel** — relational shaping of another actor's effective possibilities. ## Power Show terms **kOA Power Show** — the presentation layer of Power Dynamics that maps the forms of effective capability kOA can generate, compose, preserve, distribute, and evolve before analyzing the power relations created by successful capability. **Capability spectrum** — the set of distinct forms of potential, capacity, and puissance available to an actor or system across domains. In kOA this includes epistemic, semantic, cognitive, collective, network, credibility, decision, operational, mnemonic, technical, infrastructural, federative, exit, and evolutionary capability. **Capability loop** — a sequence in which one capability feeds the next. The canonical kOA loop is `Know → Choose → Act → Remember → Know better`. **Closed capability loop** — a capability loop in which outputs are sufficiently preserved and fed back as inputs that the system can learn from prior action rather than repeatedly restarting from near-zero institutional memory. “Closed” does not mean perfectly self-contained. **Composition engine** — shorthand for the architecture through which distinct capabilities become interoperable inputs to one another, creating higher-order or generated puissance. **Composition gain** — additional effective capability created because separate functions interoperate. It is the difference between possessing useful components and possessing a coherent capability system. **Compounding engine** — shorthand for feedback loops in which action produces reusable returns that lower the cost, increase the quality, or expand the scope of future action. **Capability infrastructure** — technical, semantic, institutional, or procedural infrastructure whose primary effect is to make future action easier, more reliable, more composable, or more reusable. **Capability surface** — a function or interface through which a system increases what actors can effectively do. A capability surface can later become a power surface if control over it changes other actors’ effective possibilities. **Power surface** — a function, interface, registry, role, default, gate, workflow, standard, or infrastructure boundary through which control can shape other actors’ access, standing, visibility, allocation, timing, interpretation, or ability to act. **Power surface map** — cross-domain inventory of the capability surfaces, relational power surfaces, controllers, conversion paths, counterpowers, and routing mechanisms of a system. **Cross-domain power conversion** — transformation through which a resource, capability, or relational advantage in one domain becomes leverage in another domain. **Conversion path** — explicit sequence connecting a source domain to a destination domain through a mechanism such as funding, ranking, certification, standardization, ownership, or dependency. **Capability-to-power transition** — the point at which successful puissance becomes relationally consequential for other actors. This transition is central to the repository: the same function can be empowering as capability and politically consequential as a controlled gate. ## Ontology **Resource** — anything available to an actor or system that can support future action: money, time, knowledge, code, rights, relationships, reputation, data, infrastructure, identity, property, attention, memory, or other conditions. **Asset** — a resource that has been accumulated, stabilized, owned, controlled, recognized, or made reusable enough to support future action. **Stock** — an accumulated quantity or body of resources/assets at a point in time. A stock is descriptive; it is not automatically puissance or power. **Potential** — unrealized effective possibility preserved or created by resources and conditions. **Capacity** — an organized ability to perform a class of actions under specified conditions. **Puissance** — capacity that is effectively mobilizable under real conditions to produce effects. Puissance is the preferred term for what English often calls *power to*, *power with*, or *power through* when no relational control over others is implied. **Power** — a relational capacity, grounded in puissance, through which one actor, group, institution, or infrastructure shapes another's effective possibilities. **Power relation** — a relation in which another actor's access, options, standing, visibility, allocation, authority, incentives, categories, timing, dependencies, or ability to act are materially changed. **Effect** — a realized change produced by action, mediation, or a power relation. **Return** — a reusable asset created or preserved by an action or effect and available for future cycles. **Effective possibility** — what an actor can realistically understand, choose, refuse, obtain, build, coordinate, contest, preserve, or leave under actual material, institutional, temporal, informational, and social conditions. ## Modes of capability and relation **Puissance d'agir / power to** — effective ability to accomplish, understand, build, decide, refuse, learn, create, or otherwise act. **Collective puissance / power with** — effective capability generated through coordination among multiple actors. **Infrastructure-mediated puissance / power through** — effective capability enabled, stored, routed, amplified, or made reusable through infrastructure. **Power over** — an asymmetric family of power relations in which one actor can condition, constrain, block, allocate, define, authorize, or otherwise shape another's possibilities. It is not the definition of all power. **Mutual power** — a reciprocal power relation in which actors alter one another's possibilities in ways that can expand joint capacity. **Generated puissance** — new effective capacity created by composition that did not exist in any participant separately. **Latent puissance** — capacity that could be mobilized but is currently inactive because of timing, coordination, information, access, or other constraints. ## Dynamics **Formation** — the process through which resources become organized capacity and then effective puissance. **Mobilization** — the activation of available resources or puissance into action, exposure, coordination, or effects. **Reservoir** — a configuration in which accumulated resources or reusable assets are retained for future activation. A reservoir is not stored relational power. **Retention** — preserving a resource, asset, option, or capability rather than immediately committing or releasing it. **Release** — activation, disclosure, deployment, spending, publication, delegation, or other transition from retained resource to active use. **Release puissance** — effective ability to control the timing, sequencing, form, and channels through which a retained resource is activated. **Flow** — movement of mobilized resources, signals, actions, or effects through a system. **Throughput** — the practical rate at which a system can process, deploy, distribute, or convert resources and puissance into effects. **Mediation** — selection, framing, routing, translation, ranking, interpretation, packaging, contextualization, or transformation between source and affected actors. **Amplification** — an increase in scale or intensity of an effect relative to the initiating input because of a network, platform, institution, technology, or channel. **Bottleneck** — a constrained passage that limits throughput or access to a necessary transformation. **Bottleneck power** — relational power created when an actor controls a passage that others must use to convert resources or puissance into effects. **Composition** — combining distinct resources, capacities, or forms of puissance to create a higher-order capability. **Conversion** — transformation of a resource, asset, capacity, puissance, or relational position into another form. **Conversion pathway** — an identifiable sequence through which one form becomes another, e.g. `knowledge → credibility → visibility → opportunity`. **Conversion firewall** — a rule or architecture that permits legitimate composition while blocking automatic conversion into unrelated authority. **Reinvestment** — using returns to create or amplify future capacity and puissance. **Compounding puissance** — growth in future effective capacity caused by reinvestment and reuse across cycles. **Power yield** — the set of returns, effects, and relational positions generated by a given exercise of puissance or power. It should not be reduced to a single scalar metric. **Concentration** — increasing share of relevant resources, puissance, or relational control accumulating in one actor, node, branch, or institution. **Stacking** — accumulation of several distinct functions in the same actor or node, producing cross-domain leverage not visible in any function separately. **Capture** — durable conversion of legitimate functional control into influence or control outside its intended mandate. **Cross-domain conversion** — movement of advantage from one domain into another, e.g. economic assets becoming political influence or technical administration becoming agenda control. **Diversification** — distribution of capability or governance across multiple actors, implementations, branches, domains, or institutions. **Decay** — reduction in usefulness, credibility, adoption, capability, legitimacy, liquidity, network position, or other components of puissance over time. **Dissipation** — loss of potential returns because knowledge, experience, attention, coordination, or other value is not preserved or reused. **Transfer** — movement of resources, capacity, authority, relational position, or responsibility between actors or institutions. **Succession** — governed transfer of roles, stewardship, keys, mandates, or interpretive responsibility across time. ## Dependence, domination, and counterpower **Dependency** — reliance on an actor, system, resource, or infrastructure whose substitution or exit is materially costly, slow, unavailable, or illegible. **Dependency gradient** — degree of dependency, determined by alternatives, switching cost, time, portability, recognition, rights, knowledge, network effects, and other factors. **Domination** — exposure to arbitrary or insufficiently contestable relational power, especially where dependency is high and counterpowers are weak. **Counterpower** — capacity that can verify, contest, substitute, exit, revoke, reverse, fork, or otherwise alter the terms of a power relation. **Verification** — ability to independently inspect claims, artifacts, processes, identities, signatures, calculations, or compliance. **Contestation** — ability to challenge a claim, score, decision, rule, ranking, authority, or implementation through a meaningful process. **Substitution** — ability to replace a provider, branch, implementation, authority root, workflow, or institution with a viable alternative. **Exit** — ability to leave a relationship or system while preserving enough assets, rights, data, identity, reputation, and continuity for exit to be meaningful. **Formal exit** — nominal legal or technical ability to leave. **Effective exit** — practical ability to leave at acceptable cost without disproportionate loss of essential capability. **Forkability** — ability to create a divergent implementation, policy, ontology, or branch from an existing lineage. **Effective forkability** — forkability plus the practical ability to operate, interoperate, attract support, preserve provenance, migrate assets, and become viable. **Revocability** — ability to withdraw authority or permission. **Reversibility** — ability to undo or repair the effects of an earlier action or authority. Revocability does not guarantee reversibility. **Terminal power** — relational power whose capture, failure, or abuse cannot be effectively substituted, reversed, contested, or exited. **Instance capture** — capture of one deployment, organization, branch, or institution. **System capture** — capture of the broader architecture such that meaningful alternatives cannot continue, interoperate, or emerge. ## Branch ecology and evolutionary governance **Branch** — a distinct version, implementation, policy, ontology, or interpretation with enough lineage and provenance to be compared with alternatives. **Lineage** — traceable relationship among versions, forks, sources, transformations, and derived artifacts. **Branch mobility** — practical ability of a branch to become discoverable, credible, supported, interoperable, adopted, and capable of influencing or replacing dominant branches. **Dominance** — a branch's current advantage in adoption, support, visibility, compatibility, institutional recognition, network effects, or infrastructure. Dominance does not imply truth or optimality. **Complementarity** — additional value produced when distinct branches, perspectives, or implementations cover different evidence, contexts, scales, or functions without requiring a universal winner. **Redundant plurality** — multiple branches that add little new evidence, context, method, function, or interoperability value. **Meaningful variation** — branch difference that creates identifiable added value or tests a consequential alternative. **Evolutionary governance** — governance in which consequential rules, policies, interpretations, and implementations remain open to explicit variation, demonstration, comparison, adoption, recombination, amendment, and replacement. **Stable kernel** — shared minimal contracts, formats, provenance rules, or interoperability requirements that permit divergence without fragmentation. **Evolving branch** — a branch whose policies, readings, implementations, or governance may change while preserving lineage and interoperability where feasible. **Recombination** — integration of useful elements from multiple branches into a new branch or later version. **Replacement** — transition in which an alternative becomes more adopted, authoritative, useful, or institutionally supported than an earlier dominant branch. ## Epistemic, semantic, and credibility terms **Epistemic puissance** — effective ability to produce, organize, validate, compare, preserve, or reuse knowledge. **Semantic puissance** — effective ability to create, maintain, translate, contest, and evolve categories, ontologies, definitions, and relations of meaning. **Semantic power** — relational power created when control over categories, definitions, ontologies, thresholds, or classifications shapes how others can understand, qualify, or act. **Semantic sovereignty** — practical capacity of a person or community to govern the terms, categories, ontologies, and knowledge structures through which it generates and shares meaning without arbitrary dependence on external authorities. **Credibility asset** — accumulated evidence or recognition that makes a person, branch, claim, or institution more likely to be trusted in a defined context. **Credibility signal** — governed reading of evidence about expertise, contribution, conduct, reliability, or other criteria. It is not the person or competence itself. **Domain-bounded expertise** — expertise whose relevance and influence are limited to explicit domains rather than generalized into universal authority. **Discoverability puissance** — effective ability to make relevant content, people, or branches findable. **Discoverability power** — relational power created when control of discovery materially shapes what others see, reuse, fund, cite, learn, adopt, or build. **Pre-political power** — power exercised through meaning, knowledge, visibility, credibility, agenda, and framing before a formal decision is made. **Mnemonic puissance** — effective ability to preserve and reuse knowledge, reasons, decisions, actions, failures, and outcomes across time. **Mnemonic power** — relational power created when control of collective memory shapes future interpretation, precedent, options, or institutional learning. ## Political and constitutional terms **Political puissance** — effective ability to participate in, shape, organize, or carry collective judgment, agenda formation, decision, amendment, representation, or public action. **Political power** — relational power to shape political standing, agenda, mandates, decision rights, representation, legitimacy, veto, amendment, or binding collective outcomes. **Constitutional power** — power to define, amend, interpret, or enforce the rules by which other powers are authorized, limited, contested, or transferred. **Decision power** — relational power to determine or materially condition which collective option becomes binding or operative. ## Economic, monetary, and allocation terms **Economic resource** — money, property, goods, productive assets, contractual rights, or other material means. **Economic puissance** — effective ability to mobilize economic resources for action. **Economic power** — relational power created when control or mobilization of scarce economic resources materially changes others’ access, bargaining position, dependency, allocation, or effective options. **Liquidity** — ease and speed with which an asset can be converted into usable resources without excessive loss. **Liquidity puissance** — effective ability to make resources rapidly usable. **Allocation power** — relational power to determine which people, projects, institutions, or goals receive resources. **Monetary puissance** — effective ability to create, access, move, settle, convert, intermediate, or finance value through monetary and credit infrastructure. **Monetary power** — relational power associated with control over units, rails, issuance, settlement, reserves, access, or conditions of exchange. **Custodial power** — relational power arising from control over assets held on behalf of others. **Market-making puissance** — capacity to enable exchange by providing liquidity, matching, standards, custody, or transaction infrastructure. **Property power** — relational power arising from enforceable control of scarce assets, land, infrastructure, intellectual property, or access rights. ## Information, media, network, and narrative terms **Information resource** — data, documents, signals, archives, observations, or other transmissible representations. **Distribution puissance** — effective ability to deliver information, resources, signals, or instructions to relevant actors at scale. **Reach** — number and relevance of actors that can practically be reached through available channels. **Reach puissance** — effective capacity to cross geographic, linguistic, network, or institutional boundaries. **Attention power** — relational power to influence what receives scarce attention. **Visibility power** — relational power to affect whether and how actors, claims, branches, or events become publicly visible. **Agenda power** — relational power to influence what enters collective consideration as a problem, priority, or option. **Framing power** — relational power to shape interpretation by selecting descriptions, categories, narratives, baselines, or causal frames. **Media puissance** — effective ability to gather, package, distribute, synchronize, and amplify information to an audience. **Network resource** — relationships, affiliations, pathways, memberships, trust links, or structural positions that can support future coordination. **Network puissance** — effective ability to mobilize relationships for access, coordination, diffusion, recruitment, or action. **Affiliation power** — relational effects produced by membership, association, endorsement, exclusion, or visible identification with a network or symbol. **Narrative puissance** — effective ability to make complex systems understandable, memorable, transmissible, and emotionally or culturally legible. **Narrative power** — relational power created when narratives shape interpretation, legitimacy, attention, identity, or mobilization. **Brand asset** — accumulated recognition, associations, expectations, reputation, symbols, and identity attached to a name or mark. **Brand puissance** — effective ability to mobilize brand recognition into attention, affiliation, trust, distribution, commerce, or coordination. **Brand power** — relational effects created when brand-mediated trust, attention, certification, or affiliation changes others' opportunities, choices, or standing. ## Technical, infrastructural, administrative, and cognitive terms **Technical resource** — code, tools, protocols, hardware, schemas, standards, credentials, deployment knowledge, or other technical assets. **Technical puissance** — effective ability to build, modify, operate, verify, deploy, repair, or reproduce technical systems. **Infrastructural puissance** — effective ability created by reliable shared systems, protocols, deployment paths, identity rails, data layers, or other infrastructure. **Infrastructural power** — relational power arising when control over infrastructure materially conditions others' access, options, interoperability, or continuity. **Administrative puissance** — effective ability to route, assign, schedule, validate, escalate, record, close, and coordinate work. **Administrative power** — relational power produced when administrative control changes others' timing, workload, access, status, or ability to complete an action. **Execution puissance** — effective ability to transform decisions into coordinated, traceable action. **Cognitive puissance** — effective ability to perceive, reason, synthesize, model, plan, generate, or evaluate. **AI-mediated cognitive puissance** — cognitive capacity amplified through AI tools under explicit governance and human/institutional constraints. **Hidden sovereignty** — effective decision or policy control exercised by a system that is formally described as merely advisory, technical, or assistive. ## Constitutional and institutional terms **Authority** — recognized permission or mandate to perform defined actions within a scope. **Scoped authority** — authority limited by domain, function, duration, jurisdiction, conditions, and review. **Mandate** — explicit basis, purpose, and boundary of legitimate authority. **Separation of functions** — design principle preventing one role or component from silently inheriting unrelated functions. **Functional centrality** — importance of a node to coordination or operation without necessarily implying ownership or sovereignty over the whole system. **Sovereignty** — ultimate or non-subordinate authority within a defined domain. In this repo, technical centrality and practical dependence can create quasi-sovereign effects without formal sovereign status. **Subsidiarity** — placing decisions and authority at the lowest level capable of handling them effectively while preserving necessary coordination. **Federation** — coordination among independently governed nodes or institutions through shared contracts, protocols, or interoperability arrangements. **Local sovereignty** — practical ability of a local deployment or community to govern critical operations and meanings without requiring permanent permission from a remote authority. **Protocol commons** — shared technical or semantic substrate whose reuse and interoperability do not require submission to one commercial or political owner. **Brand stewardship** — governance of official names, marks, certification, and identity separately from protocol ownership or operation. ## Founder and temporal terms **Founder power** — relational leverage derived from authorship, code control, brand ownership, infrastructure, credentials, narrative authority, interpretation, relationships, or unique knowledge. **Founder decentering** — progressive reduction of unique founder dependency through documentation, distributed mastery, independent operation, maintainer pluralism, federation, succession, and reproducibility. **Optionality** — preserved ability to choose among future actions because resources, rights, identity, timing, or commitments have not been irreversibly fixed. **Temporal optionality** — optionality specifically created by retaining control over timing or disclosure. **Identity optionality** — preserved ability to reveal, separate, associate, or withhold public identity under different future conditions. **Release optionality** — preserved ability to decide when and how a retained resource, corpus, asset, or announcement becomes active. ## kOA-specific terms **kOA** — the broader conceptual, cultural, strategic, governance, and narrative framework. **kOA Digital Ecosystem** — the operable digital system-of-systems supporting the cycle `Know → Choose → Act → Remember`. **Kristal** — structured, portable, provenance-preserving knowledge artifact or family of artifacts used to make knowledge auditable, reusable, versioned, and capable of controlled transformation. **Konnaxion** — public collaboration, circulation, coordination, and commons-facing platform layer. **Koali** — credibility/reputation infrastructure envisioned as plural distributions around interoperable structures rather than one universal social-credit authority. **EkoH** — domain-bounded credibility, expertise, ethics, contribution, or trust signal layer, depending on implementation context. **SmartVote** — decision/discoverability mechanism preserving baseline and advisory/weighted readings separately rather than silently replacing political equality. **Orgo** — operational workflow and case-management layer connecting decisions to roles, tasks, routing, escalation, closure, and operational memory. **Capsule** — signed portable deployment/package unit intended to support local operation, verification, rollback, self-hosting, and federation. **SemantiK Architect** — semantic-architecture function concerned with concepts, categories, relations, contexts, and multilingual structures. **SenTient** — semantic reconciliation function concerned with ambiguity, entity linking, uncertain propositions, and structured interpretation. ## Compatibility with earlier Power Dynamics shorthand Earlier drafts used several useful but broader expressions. They remain meaningful if interpreted through the stricter ontology. **Power stock** — legacy shorthand for accumulated resources/assets plus durable relational positions. Prefer specifying the actual stock rather than treating power as a substance stored in one pool. **Power flow** — broad shorthand for movement, mobilization, conversion, mediation, or transfer across the system. Prefer identifying what flows: resources, signals, attention, money, authority, puissance, effects, or returns. **Power return** — shorthand for reusable returns produced by action or power relations. A return may become a resource, asset, relational advantage, or future puissance; it is not necessarily relational power at the moment it returns. **Power reinvestment** — shorthand for using returns to increase future resources, capacity, puissance, or relational leverage. **Power regeneration** — shorthand for recurring cycles in which effects are preserved and reused instead of dissipating, creating renewed or expanded puissance. **Compounding power** — shorthand for cumulative dynamics in which returns increase later relational leverage. Prefer **compounding puissance** when the effect is increased capability without a specified relation to others. **Power reservoir** — avoid as a strict term. Use **resource reservoir**, **epistemic reservoir**, **financial reserve**, or another domain-specific reservoir. Relational power is not stored like a physical substance. ## Repository shorthand **Strong distributed puissance, weak sovereignty** — maximize useful effective capability while limiting non-contestable or terminal control. **Plurality without fragmentation** — allow meaningful divergence while preserving enough shared lineage, contracts, provenance, and interoperability for comparison and recombination. **Instance capture ≠ system capture** — failure or capture of one node should not automatically make alternatives non-viable. **Architecture is governance before governance is written** — schemas, defaults, registries, identity systems, workflows, interfaces, and deployment topology already assign and constrain possibilities before formal policy text is applied. ## Power routing and sharing **Power routing** — explicit design of where generated capability, authority, returns, optionality, visibility, and interpretive leverage are allowed to accumulate. **Power redirection** — deliberate change in the default destination or conversion path of leverage, such as expertise → advice rather than sovereignty or infrastructure → local autonomy rather than operator dependency. **Power sharing** — creation of conditions under which multiple actors can effectively use a capability or participate in a right without requiring exclusive ownership by one actor. **Power devolution** — durable transfer of effective control from a central locus toward local, plural, or lower-level loci. **Self-binding** — public, procedural, contractual, or technical constraints adopted by an actor or institution that make later exercises of power more legible, contestable, or limited. **Narrative self-binding** — use of the same narrative or symbolic channel that creates attention and affiliation to publish ethical limits, anti-domination principles, attribution rules, revision norms, or other constraints on symbolic power. **Protocolization** — conversion of tacit or founder-centric capability into explicit contracts, schemas, specifications, artifacts, tests, and reproducible behavior that others can implement independently. **Ownership decoupling** — separation of a useful function from exclusive ownership of the implementation, brand, registry, or operator that first instantiated it. **Capability commons** — a body of reusable capability that multiple actors can access, reproduce, improve, or instantiate without requiring one terminal owner of the function. **Architect-confirmed design** — a current design intention confirmed in the working process but not yet supported by a canonical source document or direct implementation evidence. It must be labeled separately from source-derived or deployed claims. --- [Home](Home) · [Power Surface](Power-Surface) · [Power Domains](Power-Domains) ================================================================================================ FILE: Power-Dynamics.wiki/Governance-After-Capability.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 60898dd85795983c0c720b638be9f49bc53a8e754ac4dc4debf97b8ba96ebc9a CONTENT_BYTES: 2915 ================================================================================================ # Governance After Capability Power Dynamics does not treat governance as the mechanism that prevents kOA from becoming powerful. It treats governance as the mechanism that allows kOA to become **very capable without making successful capability terminal**. ## The sequence ```text Generate puissance → compose puissance → amplify and preserve it → observe emerging power relations → constrain arbitrary conversion → preserve counterpower → keep alternatives viable → let governance itself evolve ``` ## Governance can redirect power before constraining it The constitutional architecture has two jobs: 1. **redirect useful leverage toward distributed capability where possible;** 2. **preserve counterpower where concentration still occurs.** Examples include protocolizing founder knowledge, making Koali plural and reproducible, publishing ethical constraints in narrative, separating expertise from sovereignty, and turning central infrastructure into self-hostable local capability. Read [Power Routing & Sharing](Power-Routing-and-Sharing). ## Four core counterpowers > **Verification + Contestation + Substitution + Exit** ### Verification Can affected actors independently inspect the claim, rule, calculation, provenance, signature, workflow, or authority? ### Contestation Can they challenge it through a meaningful process? ### Substitution Can another provider, branch, reader, model, implementation, institution, or workflow perform the function? ### Exit Can participants leave without disproportionate loss of identity, history, knowledge, reputation, data, rights, or continuity? ## Non-terminal architecture No architecture can guarantee that capture never occurs. The more realistic objective is: > **Instance Capture ≠ System Capture** A captured organization, deployment, branch, registry, or brand should not automatically capture the whole capability ecology. ## Conversion firewalls Useful functional control should not silently become unrelated sovereignty. ```text expertise → advice yes expertise → permanent rule no automatic path money → contribution yes money → more political votes no automatic path technical administration → upkeep yes technical administration → policy no automatic path ``` ## Evolutionary governance Even the constitution is an approximation. Forks and branches are not only emergency escape valves. They are normal mechanisms of institutional experimentation. The final safeguard is therefore not a perfect center. It is the preservation of a system in which alternatives can remain viable enough to challenge, recombine with, or replace dominant implementations. > **Canonical repo source:** `showcase/08-governance-after-capability.md` --- ← [Component Power Matrix](Component-Power-Matrix) · [Home](Home) · [Power Constitution](Power-Constitution) → ================================================================================================ FILE: Power-Dynamics.wiki/Home.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 5ede6a4411c2d48db418840e2a452730f081613e8444047e9d658f1e39aef986 CONTENT_BYTES: 7980 ================================================================================================ # Power Dynamics **The kOA Power Show — mapped as a cross-domain power surface.** Power Dynamics starts from an affirmative question: > **How much effective capability can kOA generate for people, groups, organizations, institutions, and federations?** Then it asks the constitutional question: > **When those capabilities become socially consequential, where does the resulting power go?** ## Why is kOA immensely powerful? > **Because kOA connects almost the entire lifecycle by which distributed resources become collective agency, reusable assets, and greater future capability.** The v6.2 shorthand is: > **Breadth × Composition × Closure × Memory × Compounding × Replication × Routing** ```text People + knowledge + AI + networks + credibility + money + tools ↓ STRUCTURE + CONNECT ↓ Meaning → Knowledge → Discovery → Credibility → Judgment ↓ Decision → Allocation ↓ Coordination → Execution ↓ Results → Memory → Returns ↓ Reinvestment ↓ Greater future puissance ↓ Replication / federation ↓ Sharing / contestation / evolution ``` The core loop remains: > **Know → Choose → Act → Remember → Know better** A collective that can close that loop does not merely solve one problem. It can become more capable **because it has acted before**. ## The major evolution in v6: see the whole power surface kOA can generate or amplify capability across many domains at once: | Surface | Examples of generated capability | Relational power that can emerge | |---|---|---| | Epistemic / semantic | validate, structure, compare, translate, preserve | canon, classification, framing, admissibility | | Cognitive / AI | reason, synthesize, model, translate | prioritization, hidden framing, dependency | | Information / attention | publish, discover, rank, amplify | visibility, agenda, moderation | | Credibility / reputation | make competence and contribution legible | standing, certification, opportunity | | Network / affiliation | connect, recruit, broker, mobilize | inclusion, exclusion, access | | Political / constitutional | deliberate, decide, authorize, amend | mandate, veto, legitimacy, decision | | Economic | mobilize money, assets, labor, infrastructure | bargaining, property, allocation | | Monetary | organize liquidity, payment, settlement, credit | issuance, rail, reserve, access | | Administrative / operational | assign, route, escalate, execute, close | timing, workload, approval, closure | | Technical / infrastructural | build, host, update, verify, reproduce | compatibility, standards, dependency | | Narrative / symbolic / brand | transmit, affiliate, mobilize, remember | framing, legitimacy-by-association, gatekeeping | | Mnemonic / temporal | preserve precedent, reasons, timing, lineage | memory, delay, succession | | Evolutionary / counterpower | contest, substitute, fork, recombine | incumbent displacement, branch mobility, exit | Read the [kOA Power Surface](Power-Surface). ## Political, economic, and monetary power are distinct v6 makes this separation explicit: ```text POLITICAL standing / agenda / mandate / legitimacy / decision rights ECONOMIC money / property / labor / assets / funding / allocation MONETARY issuance / payment rails / settlement / reserves / liquidity / credit ``` They interact strongly, but they are not interchangeable. The most consequential mechanisms are often **cross-domain conversions**: ```text knowledge → credibility → visibility → agenda → political influence money → infrastructure → reach → attention → political leverage technical control → defaults → dependency → de facto governance brand → affiliation → revenue → infrastructure → greater capability ``` Read [Political, Economic & Monetary Power](Political-Economic-and-Monetary-Power) and [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion). ## The second major evolution: power routing The project does not only ask how to generate leverage. It asks where four things go: ```text CAPABILITY → who can do more? AUTHORITY → who can decide or control more? RETURNS → who receives reusable value? OPTIONALITY→ who can refuse, leave, reproduce, fork, or wait? ``` Examples of deliberate routing include: - expertise → advice, not sovereignty; - money → funding, not more political standing; - ethical fiction → symbolic puissance plus explicit self-binding; - Koali → plural, duplicable distributions rather than terminal personal ownership; - Kristal → portable knowledge and competing representations; - infrastructure → self-hosting, federation, rollback, substitution; - dominant branches → branch mobility rather than final authority. Read [Power Routing, Sharing & Devolution](Power-Routing-and-Sharing). ## Propagation: when returns activate capability elsewhere Power Dynamics now distinguishes local compounding from propagation. ```text compounding → past action makes the same system more capable propagation → a reusable return lowers the activation barrier elsewhere coupled propagation → several loops exchange returns ``` For kOA this includes evidence → credibility → access, revenue → development, training → operators, integration → wider capability, language support → new communities, and documentation → lower review cost. Read [Propagation Engine](Propagation-Engine) and [kOA Propagation & Adoption](kOA-Propagation-and-Adoption). ## The mature Power Show ```text GENERATE immense puissance ↓ COMPOSE capabilities ↓ CLOSE the knowledge-to-action loop ↓ PRESERVE memory and returns ↓ COMPOUND future capability ↓ EXPOSE cross-domain conversions ↓ ROUTE capability / authority / returns / optionality ↓ BLOCK automatic sovereignty conversion ↓ VERIFY / CONTEST / SUBSTITUTE / EXIT / FORK ↓ EVOLVE ``` > **Strong distributed puissance. Weak sovereignty.** ## Reading paths **Fastest explanation:** [Why kOA Is Immensely Powerful](Why-kOA-Is-Immensely-Powerful) → [Power Surface](Power-Surface) → [Power Show](Power-Show). **Cross-domain power:** [Power Domains](Power-Domains) → [Political, Economic & Monetary Power](Political-Economic-and-Monetary-Power) → [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion). **Governance:** [Power Routing & Sharing](Power-Routing-and-Sharing) → [Power Constitution](Power-Constitution) → [Conversion Firewalls](Power-Conversion-Firewalls) → [Counterpowers & Legibility](Counterpowers-and-Legibility). **kOA architecture:** [kOA System Map](kOA-System-Map) → [Component Power Matrix](Component-Power-Matrix) → [Know → Choose → Act → Remember](Know-Choose-Act-Remember). **Audit:** [Power Surface Audit](Power-Surface-Audit) → [Power Routing Audit](Power-Routing-Audit) → [Power Analysis Method](Power-Analysis-Method) → [Constitutional Tests](Constitutional-Tests). **Academic context:** [Academic Lineage](Academic-Lineage) → [Expertise & SmartVote](Academic-Lineage-06-Expertise-SmartVote-and-Collective-Judgment) → [Bibliography](Academic-Lineage-Bibliography). ## Canonical vocabulary > **Resource / Asset → Potential → Capacity → Puissance → Power Relation → Effect → Return** `Puissance` is effective, mobilizable capacity. `Power` is relational: it appears when that puissance changes another actor's effective possibilities. See the [Glossary](Glossary). > **Canonical v6.2 repo sources:** `README.md`, `POWER-SHOW.md`, `POWER-SURFACE.md`, `POWER-ROUTING.md`, `PRINCIPLES.md` --- [Getting Started](Getting-Started) → ================================================================================================ FILE: Power-Dynamics.wiki/Imperfection-and-Plurality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 3f5b3664206a08d650006eea324cd11f0a2e98923e922e397599d63aefc69011 CONTENT_BYTES: 960 ================================================================================================ # Imperfection, Readings, and Plurality Power Dynamics assumes that consequential human and institutional judgments are imperfect. Competence, ethics, credibility, legitimacy, truth, branch quality, and social value cannot be captured perfectly by one score, authority, or implementation. This is not a reason to avoid evaluation. It is a reason to make evaluation **explicitly governed**. `phenomenon ≠ evidence ≠ policy interpreting evidence ≠ reading/score ≠ institutional use of that reading` This permits multiple branches or readings without requiring relativism. A branch may be better supported on one dimension and weaker on another. Different Kristals may preserve different evidence, contexts, ontologies, or scopes. The objective is not perfect governance but **governable imperfection**. > **Canonical repo source:** `framework/07-imperfection-and-plurality.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Improvement-Support-and-Dominance.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 4f0da892465299087446ce1a3badea68fd75fb0c5e79da828d9e2b329dc80e3d CONTENT_BYTES: 906 ================================================================================================ # Improvement, Support, Adoption, and Dominance An alternative should be able to say not only “we disagree,” but **what changed and what value was added**. Possible demonstrations include stronger evidence, better provenance, lower error, lower cost, higher autonomy, better accessibility, improved multilinguality, better outcomes, stronger privacy, better local fit, or improved interoperability. Support, adoption, and dominance are distinct. A branch may be intellectually supported but rarely deployed, or dominant because of history, compatibility, network effects, official status, or funding. > **Dominance ≠ Truth ≠ Quality ≠ Legitimacy** No universal scalar is required. Improvement can be multidimensional and context-dependent. > **Canonical repo source:** `branch-ecology/improvement-support-dominance.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Information-Attention-and-Media-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 75e078094492a1d10305b2379a13cd513e2fec903e00b42e52b012dbf10574e2 CONTENT_BYTES: 1662 ================================================================================================ # Information, Attention & Media Power > **Core question:** Who can make something visible, discoverable, ranked, amplified, moderated, or ignored? ## Generated puissance Effective capability to **publish, search, rank, distribute, recommend, route, amplify, and preserve access to information**. ## Relational power that can emerge Visibility power, agenda power, moderation power, amplification power, discoverability power. ## Typical conversion paths - `attention → affiliation` - `visibility → credibility / opportunity` - `media reach → agenda` - `discoverability → adoption / funding` ## Routing / counterpower direction - explicit discovery and ranking policies - alternative discovery paths and plural networks - export / portability where feasible - distinguish visibility from truth and adoption from legitimacy ## kOA touchpoints - Konnaxion is the main distribution / discovery surface - SmartVote discoverability mechanisms can influence what rises - brand / narrative can increase attention while remaining non-sovereign ## Analytical note A system can preserve formal decision equality while still concentrating considerable pre-political power in ranking and discoverability. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/KingCoin-Legacy-Stress-Test.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: fa3fd6df782c33438691a7906d8fe378afa6da3b8f81e0884140d6e25b9166d1 CONTENT_BYTES: 594 ================================================================================================ # KingCoin as a Legacy Stress Test Legacy KingCoin proposals include global governance, sanctions, blacklisting, automated penalties, and monetary enforcement. These mechanisms create strong monetary and enforcement power and expose tensions with later commitments to non-domination, local sovereignty, branch alternatives, and effective exit. The case is retained as an evolutionary stress test, not silently harmonized with current-core principles. > **Canonical repo source:** `cases/kingcoin-legacy-stress-test.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Know-Choose-Act-Remember.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: fb18f61f705fe60e385c528a99e0f88d363bdda094cfae94d3487d46ba473a24 CONTENT_BYTES: 805 ================================================================================================ # Know → Choose → Act → Remember The kOA loop is a capability-regeneration cycle. ### Know Transform dispersed contributions into structured, provenance-preserving knowledge without prematurely erasing ambiguity. ### Choose Transform knowledge into legible orientation while preserving reasons, options, disagreement, and multiple readings. ### Act Transform orientation into responsibilities, tasks, routing, validation, escalation, and outcomes. ### Remember Transform experience into reusable memory that lowers the cost of future action. The political value lies in the **transitions**, because each transition can become a bottleneck or locus of power. > **Canonical repo source:** `koa/know-choose-act-remember.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/kOA-Propagation-and-Adoption.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 872f13b38f69e3b154e9807522f5f6e5ef15c5cbc24f49b6925cd26b25d1f7ff CONTENT_BYTES: 917 ================================================================================================ # kOA Propagation and Adoption kOA can expose multiple entry paths while converging on one inspectable architecture. ```text notice → understand → examine → contextualize → try → deploy → local value → independent mastery → optional federation ``` Different mechanisms attack different barriers: - Worlds: contextual / empty-platform barrier; - cinematic tours: explanation barrier; - public code and documentation: trust / inspection barrier; - Capsule Manager / Koali: deployment barrier; - self-host / offline / fork: lock-in barrier; - Kintsugi: integration and replacement barrier; - UCKK: operator barrier; - SemantiK: language barrier; - Managed Koali: operations-responsibility barrier; - SmartVote / Kompendio: discovery and prioritization barrier. The strongest propagation evidence is not media reach. It is **independent loop closure** by actors who do not require founder mediation. ================================================================================================ FILE: Power-Dynamics.wiki/kOA-Returns-and-Compounding.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 326b6ec61537b0774158e4656461df114f7cef6904b3e677fe3620661658d07c CONTENT_BYTES: 793 ================================================================================================ # kOA Returns and Compounding kOA can produce returns in several domains: validated knowledge, reusable Kristals, code, operational experience, contributor credibility, network connections, institutional memory, brand recognition, economic resources, standards, and interoperability. These returns can feed other systems and lower future coordination cost, creating a **power ecology of compounding capability**. The same loop can create concentration. Recognition can generate visibility, visibility opportunity, and opportunity more recognition. Power Dynamics therefore tracks who receives returns and whether alternatives can accumulate comparable assets. > **Canonical repo source:** `koa/returns-compounding.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/kOA-System-Map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 22fc562715e30b05757696f106a46448e9b167bd3a19d8592350a0d4058a566e CONTENT_BYTES: 2738 ================================================================================================ # kOA System Map ## v6 power-surface reading Read each component not only as a function, but as a **capability surface** that can become a **power surface** when control over it changes access, standing, visibility, allocation, timing, interpretation, or continuity. See [Power Surface](Power-Surface) and [Component Power Matrix](Component-Power-Matrix). This is the bridge between the Power Show and the actual kOA architecture. Each capability surface is paired with the power relations that may emerge if it becomes widely relied upon. The high-level capability chain is: > **Contribution → Resolution of meaning → Structured knowledge → Discovery / credibility → Collective choice → Governed work → Coordinated action → Experience → Reusable memory → New cycle** ## Capability map ```text SemantiK / SenTient semantic structure ↓ Kristal knowledge + provenance + memory ↓ Konnaxion circulation + people + discovery ↓ Koali / EkoH credibility context ↓ SmartVote comparison + advice + choice ↓ Orgo routing + responsibility + execution ↓ Outcomes ↓ Kristal / operational memory reusable learning ↺ ``` Cross-cutting layers: - **AI** — cognitive amplification; - **Capsules / federation** — portability, deployment, substitution, branch formation; - **brand / narrative** — recognition, affiliation, transmission; - **multilingual semantics** — linguistic access and semantic participation. ## Power overlay Each capability surface can also become a power surface: | Capability surface | Possible relational power | |---|---| | semantic structuration | classification / framing / ontology power | | knowledge validation | epistemic authority / standard-setting | | discoverability | ranking / visibility / agenda power | | credibility interpretation | recognition / standing / opportunity power | | decision support | default / weighting / advisory influence | | workflow | routing / timing / escalation / closure power | | memory | precedent / institutional-memory power | | federation infrastructure | signing / update / compatibility / registry power | | AI | hidden interpretation / prioritization power | | brand | attention / affiliation / legitimacy-by-association | The constitutional problem is therefore not whether kOA should be powerful. Its purpose is to generate capability. The problem is whether the relations created by successful capability remain **scoped, inspectable, contestable, substitutable, and evolvable**. > **Canonical repo source:** `koa/system-map.md` --- ← [Branch Ecology](Branch-Ecology) · [Home](Home) · [Capability Show Profile](Capability-Show-Profile) → ================================================================================================ FILE: Power-Dynamics.wiki/Koali-and-EkoH.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c6f1b186f5897114bcc51a91eda3a03e32223d39a97bca2a215b0b2c804ca6ce CONTENT_BYTES: 1166 ================================================================================================ # Koali / EkoH Koali and EkoH address a problem of **latent competence**: people may possess valuable experience or expertise that is difficult for others to discover, verify, or mobilize. The intended transformation is: `competence evidence → legibility → credibility signal → discoverability → opportunity → participation` The constitutional limit is explicit: > **Score ≠ person ≠ competence ≠ truth ≠ sovereignty.** Signals should be domain-bounded, evidence-linked, versioned, contestable, and portable. Multiple distributions or policies can coexist around common interoperability, supporting **plurality without fragmentation**. > **Canonical repo source:** `koa/koali-ekoh.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ## Power-sharing direction The design direction is not one universal owner of credibility. Koali is intended to become **duplicable, shareable, branchable, and capable of plural distributions**, so useful credibility infrastructure can move from personal property toward an interoperable protocol ecology. Read [Koali: From Property to Protocol](Koali-From-Property-to-Protocol). ================================================================================================ FILE: Power-Dynamics.wiki/Koali-From-Property-to-Protocol.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 04287abab64c470bf3f8ffe6d6cdc1622023181a2be88f1224eef0c9f8e552e9 CONTENT_BYTES: 1813 ================================================================================================ # Koali: From Property to Protocol Koali is a direct test of whether kOA creates a new credibility owner or **shares the capability to organize credibility**. The current architect-confirmed design intention is: > **Koali should not remain an exclusive personal property on which everyone else must depend. Its useful capability should be duplicable, shareable, branchable, and capable of plural distributions.** This is a design intention, not yet a claim that the complete technical mechanism is implemented. ## Why it matters Credibility infrastructure can affect discoverability, standing, opportunity, certification, access, trust, collaboration, and advisory influence. If one operator owns the only meaningful credibility layer, recognition can become gatekeeping. ## Protocolization target ```text founder-created concept → explicit kernel / contracts → portable evidence and history → policy identity → multiple distributions → interoperability → independent operation → branch comparison and evolution ``` The political move is: > **Personal ownership of a capability → stewardship of an interoperable protocol ecology** ## Plurality without fragmentation Different Koali distributions can legitimately use different criteria for different domains or communities, provided their policies remain interpretable. A mature design should support reimplementation, policy legibility, evidence portability, contestation, interoperability, discoverability of alternatives, and branch mobility. The constitutional limit remains: > **Credibility signal ≠ person ≠ competence ≠ ethics ≠ truth ≠ sovereignty.** > **Canonical repo source:** `koa/koali-protocolization.md` --- ← [Koali & EkoH](Koali-and-EkoH) · [Power Routing & Sharing](Power-Routing-and-Sharing) → ================================================================================================ FILE: Power-Dynamics.wiki/Konnaxion.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 82b8ed21f1286879196aeee77bb7b66850649916b5d9a807cd228979a62d6a55 CONTENT_BYTES: 618 ================================================================================================ # Konnaxion Konnaxion creates **associative, communicative, discovery, and coordination puissance** by making people, projects, knowledge, deliberation, and actions visible and connectable. Power relations may arise through moderation, ranking, recommendation, search, routing, identity, access controls, default feeds, and institutional recognition. Because discoverability is governance, Konnaxion should be analyzed as a pre-political mediation infrastructure, not merely a social interface. > **Canonical repo source:** `koa/konnaxion.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Kristal.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 03d87ab461823b7ccf26125999ac05a9ff61cdffb62a116d60d38408724f05fa CONTENT_BYTES: 902 ================================================================================================ # Kristal Kristal creates **epistemic and mnemonic puissance** by structuring claims, provenance, status, versioning, lineage, validation, and reusable artifacts. Potential power relations arise around authority registries, trust roots, validation thresholds, canonical/reference promotion, reader policies, release/version selection, and federation/import rules. Plurality is constitutionally important: competing or complementary Kristals can preserve different evidence, interpretations, scopes, or policies. The system should make lineage and differences legible rather than silently declaring one permanent universal truth. The strongest technical audit still requires direct current specifications for trust roots, policies, registries, signatures, and federation behavior. > **Canonical repo source:** `koa/kristal.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Limitations-and-Open-Questions.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 548328643ddd5c8858396d8c47e5be15e7021e43bc82aede97a7da8bf7f743e4 CONTENT_BYTES: 3931 ================================================================================================ # Limitations and Open Questions Power Dynamics is deliberately ambitious, but the v6 repository does not claim that every capability, measurement, governance mechanism, or deployment path is complete or final. ## Measurement remains approximate Competence, ethics, truth, credibility, contribution, legitimacy, and branch quality cannot be perfectly compressed into a score. The canonical rule is: > **observed evidence → interpretation policy → scoped reading → uncertainty / limitations → governed use** Therefore `score ≠ person`, `score ≠ competence`, `credibility ≠ truth`, and `dominance ≠ quality`. ## Architecture is not deployment evidence A concept can be coherent before all implementation surfaces have been audited. The [Technical Evidence Map](Technical-Evidence-Map) identifies places where the theory should eventually be tied to concrete trust roots, registries, reader policies, RBAC, routing, escalation, signing keys, defaults, moderation rules, update mechanisms, and portability tests. ## Forkability can be formal but ineffective Open source does not automatically guarantee practical branch mobility. Network effects, trademarks, signing keys, identity systems, discoverability, hosting, data portability, and migration costs can leave alternatives formally permitted but practically weak. ## Successful capability creates new power Every empowerment mechanism can create a new locus of power. Discoverability, credibility, memory, AI, workflow, federation infrastructure, and brand all need continued constitutional analysis as they scale. ## Scale changes the problem A mechanism that is harmless or easily contestable in a small community may become infrastructural at large scale. Externalities, lock-in, standard-setting, and coordination dependence can emerge from success rather than malicious intent. ## Branch evolution has trade-offs Plurality can produce learning, but excessive fragmentation can destroy interoperability and shared memory. The framework therefore seeks **plurality without fragmentation**, not maximal divergence. ## Current direction The strongest next layer of evidence is technical: show precisely where power is encoded in schemas, defaults, policies, keys, registries, moderation, routing, ranking, signatures, update paths, and exit mechanisms. > **Canonical repo sources:** `STATUS.md`, `sources/technical-evidence-map.md`, `framework/07-imperfection-and-plurality.md`, `branch-ecology/README.md`, `dynamics/11-externalities-and-scale.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ## Power-routing implementation gap Several power-sharing mechanisms are architectural intentions whose effective implementation still needs direct evidence. In particular, Koali ownership decoupling requires specifications for plural distributions, portability, interoperability, registries, signing, discovery, and brand/protocol separation. ## Domain breadth increases evidence requirements The v6 Power Surface is intentionally broad. A conceptual map of political, economic, monetary, semantic, technical, narrative, and other power surfaces is not evidence that every surface is currently implemented or equally mature. Current-state claims still require direct evidence about policies, registries, keys, defaults, workflows, infrastructure, and governance. ## Monetary analysis is partly legacy-derived The strongest monetary examples in the corpus come from legacy KingCoin proposals. v6 retains them as **LEGACY-PROPOSAL / stress-test material**, not as current constitutional doctrine. ## Koali routing remains a design-direction test Plural Koali distributions and ownership decoupling remain an architect-confirmed direction whose practical reality depends on portable evidence, explicit policy identity, interoperability, branchability, independent operation, discovery, and brand / protocol separation. ================================================================================================ FILE: Power-Dynamics.wiki/Media-and-State.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 7d6c9443afba4ca3e88b9ff4467c5b8f013af10e54ea91e86dcd392d6a8395e9 CONTENT_BYTES: 536 ================================================================================================ # Media and State: Domain-Specific Power Media can possess enormous distribution, framing, and synchronization puissance. This can become visibility, agenda, reputation, and framing power at mass scale. States may possess stronger legal, fiscal, coercive, territorial, or administrative authority. The correct comparison is domain-specific rather than a one-dimensional “most powerful actor” ranking. > **Canonical repo source:** `cases/media-and-state.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Mnemonic-and-Temporal-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 5d19ded0adc57a0ac423ae7c45b0a34e846408bafe15db3ac21833a948cb237b CONTENT_BYTES: 1682 ================================================================================================ # Mnemonic & Temporal Power > **Core question:** Who controls what is remembered, what becomes precedent, when resources are released, how long decisions persist, and how stewardship passes across time? ## Generated puissance Effective capability to **preserve reasons, evidence, decisions, failures, outcomes, history, lineage, timing, and succession**. ## Relational power that can emerge Precedent power, memory power, delay power, release power, succession power. ## Typical conversion paths - `memory → future agenda` - `precedent → legitimacy` - `timing → bargaining leverage` - `retained resources → release optionality` ## Routing / counterpower direction - provenance and versioning - alternative histories / competing representations - explicit succession and stewardship - preserve temporal optionality without opaque gatekeeping ## kOA touchpoints - Kristal preserves structured memory and lineage - Orgo preserves operational traces - branch lineage preserves institutional evolution - unpublished resources can function as reservoirs until deliberately released ## Analytical note Memory is a production factor: preserved experience can lower future coordination cost and increase future puissance. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Monetary-Credit-and-Liquidity-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c177e811c1ba22cc8ffb9cd4f792fac6b5b99f4ad16968d11b3cc0463b713a3d CONTENT_BYTES: 1992 ================================================================================================ # Monetary, Credit & Liquidity Power > **Core question:** Who controls the infrastructure and conditions of exchange: issuance, settlement, liquidity, reserves, credit, convertibility, and transaction access? ## Generated puissance Effective capability to **issue or route units of exchange, provide liquidity, settle transactions, extend credit, manage reserves, define transaction access**. ## Relational power that can emerge Issuance power, settlement power, rail power, reserve power, credit power, access / exclusion power. ## Typical conversion paths - `monetary access → economic opportunity` - `credit conditions → investment / dependency` - `settlement rail → market access` - `monetary infrastructure → political leverage when alternatives are weak` ## Routing / counterpower direction - keep high-leverage monetary functions separable and scoped - audit exclusion, dependency, and substitutability - avoid stacking monetary rails with taxation, sanctions, allocation, and governance without strong counterpower - treat legacy KingCoin as a stacking stress test, not current doctrine ## kOA touchpoints - Current Power Dynamics mainly analyzes monetary power as a domain and constitutional risk surface - legacy KingCoin material demonstrates the consequences of combining issuance, settlement, taxation, redistribution, sanctions, and governance ## Analytical note Monetary power is narrower than economic power but can condition large parts of the economy because exchange infrastructure is highly connective. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Narrative-Symbolic-and-Brand-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f6a916d2ef6d4a6658bea649221bdaa7b781613b191d118440ed74bc5161da5b CONTENT_BYTES: 1689 ================================================================================================ # Narrative, Symbolic & Brand Power > **Core question:** Who can shape memory, identity, affiliation, framing, attention, and legitimacy-by-association? ## Generated puissance Effective capability to **make complex systems memorable, transmissible, teachable, affiliative, and publicly legible**. ## Relational power that can emerge Framing power, mobilization power, symbolic legitimacy, brand gatekeeping, affiliation power. ## Typical conversion paths - `narrative → attention` - `attention → affiliation` - `brand → revenue` - `symbolic recognition → access / mobilization` ## Routing / counterpower direction - narrative self-binding through explicit ethics - self-critique and refusal to sanctify the persona - brand stewardship separated from protocol governance - brand ≠ truth and narrative ≠ ultimate validity ## kOA touchpoints - King Klown / fiction act as transmission mechanisms - the source corpus publishes ethical limits inside the narrative channel itself - official brand scarcity can coexist with a forkable protocol commons ## Analytical note Narrative is legitimate as function, not sovereign. Its role is to translate and transmit the architecture, not become the ultimate source of validity. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Network-and-Affiliation-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 2585fd17e4ba7f1960cbfd0411eecbf5547fcc914abaea93ef534b8a7fea1159 CONTENT_BYTES: 1637 ================================================================================================ # Network & Affiliation Power > **Core question:** Who can connect, broker, recruit, include, exclude, mobilize, or confer value through association? ## Generated puissance Effective capability to **find collaborators, institutions, audiences, expertise, projects, opportunities, and communities**. ## Relational power that can emerge Brokerage power, inclusion / exclusion power, access power, affiliation power. ## Typical conversion paths - `network → collaborators` - `affiliation → trust / attention` - `relationships → execution capacity` - `network → opportunity / funding` ## Routing / counterpower direction - plural networks and multiple entry paths - portable identity / relationships where feasible - avoid one mandatory affiliation graph - separate brand affiliation from truth or political standing ## kOA touchpoints - Konnaxion connects people, projects, knowledge, and institutions - Koali can make relevant expertise findable - brand / narrative can create affiliation without owning the protocol ## Analytical note Networks generate compounding returns: collaborators create results, results create reputation, and reputation can widen the network. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Non-Domination-and-Terminality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 453d3983a709656f67f502aebbac6d5291a1c4369d7cf2cae28b392fb123c973 CONTENT_BYTES: 665 ================================================================================================ # Non-Domination and Non-Terminality Non-domination means more than absence of current interference. A relationship is problematic when an actor remains exposed to discretionary power it cannot meaningfully verify, contest, substitute, or exit. The repository extends this into **non-terminality**: capture of one institution, branch, deployment, or maintainer should not automatically make the broader ecosystem unrecoverable. `Instance Capture ≠ System Capture` is therefore a design objective, not a guarantee. > **Canonical repo source:** `constitution/non-domination-terminality.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Orgo.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ceb8a68110165b27ac1a44ca4f6035fc52ad22349b3c6eee9546a9cd69e2f7a0 CONTENT_BYTES: 688 ================================================================================================ # Orgo Orgo creates **operational and administrative puissance** by transforming signals and decisions into cases, tasks, owners, routing, escalation, time windows, closure, and operational memory. Administrative power appears because control over workflow can alter timing, workload, access, escalation, completion, and practical implementation. Key audit questions: who creates/closes cases, who assigns roles, who controls escalation, what deadlines/defaults exist, how conflicts are appealed, and whether administration can silently redefine the underlying mandate. > **Canonical repo source:** `koa/orgo.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Political-and-Constitutional-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 2d3fe0bc515ef228f47c68728e9820aad32c34b7419e61f3058f855e8c411863 CONTENT_BYTES: 1979 ================================================================================================ # Political & Constitutional Power > **Core question:** Who can shape standing, agenda, representation, mandate, decision rights, amendment, veto, legitimacy, and collective self-government? ## Generated puissance Effective capability to **deliberate, compare proposals, authorize, decide, amend, govern, coordinate public standing**. ## Relational power that can emerge Agenda power, mandate power, veto power, legitimacy power, representation power, decision power. ## Typical conversion paths - `meaning → agenda` - `credibility → political influence` - `economic resources → campaign / infrastructure leverage` - `political mandate → administrative execution` ## Routing / counterpower direction - political equality as baseline - expertise as bounded advice rather than sovereign right - scoped authority and explicit mandates - verification, contestation, substitution, exit where applicable ## kOA touchpoints - SemantiK / Kristal shape what becomes intelligible and evidentially stable - Konnaxion affects discoverability and agenda formation - Koali / EkoH make competence and contribution legible - SmartVote exposes baseline and advisory readings - Orgo connects decisions to execution - memory makes decisions and reasons reusable - branch ecology allows institutional alternatives to emerge ## Analytical note Political power begins before the vote and continues after it. Formal equality at the final ballot does not eliminate upstream asymmetries in meaning, visibility, credibility, or agenda. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Political-Economic-and-Monetary-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6f9d908ef0388dd0ab3dd477ca701cd03a9420289e55802ebf260f19469b0c60 CONTENT_BYTES: 4191 ================================================================================================ # Political, Economic, and Monetary Power These domains interact strongly but should not be collapsed. ## Political power Political power concerns who can shape: - political standing; - agenda; - deliberation; - decision rights; - representation; - mandates; - amendment; - vetoes; - legitimacy; - allocation decisions; - execution of public decisions. kOA touches political power across the full chain: > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** This means a system can preserve formal equality at the ballot and still create major political asymmetries upstream. ### kOA mechanisms - SemantiK / Kristal: what becomes intelligible and evidentially stable; - Konnaxion: what becomes discoverable and discussable; - Koali / EkoH: which competence or contribution becomes legible; - SmartVote: how alternative readings of a decision become visible; - Orgo: how a decision becomes implementation; - memory: what becomes precedent; - branch ecology: how institutional alternatives emerge. ## Economic power Economic power concerns control or mobilization of scarce resources: - money; - property; - productive assets; - labor and time; - infrastructure; - funding; - procurement; - contracts; - philanthropy; - access to markets. Money is a resource stock. When mobilizable, it becomes economic puissance. When used to alter another actor's options, bargaining position, access, or allocation, it becomes relational economic power. ```text money → purchasing / funding / bargaining puissance → access / allocation / dependency effects ``` ### kOA mechanisms - Zero-Skim: common resource pooling and democratic allocation; - brand / merchandise: symbolic → economic conversion; - credibility: opportunity and funding access; - networks: collaborators, customers, institutions, opportunities; - execution: turning funding into actual capability; - compounding: returns become future assets. ## Monetary power Monetary power concerns the infrastructure and rules of exchange itself: - issuance; - unit of account; - liquidity; - settlement; - payment rails; - reserves; - convertibility; - credit and debt conditions; - access to transaction systems. This domain can create exceptional leverage because nearly every economic actor depends on exchange infrastructure. ### Legacy KingCoin as stress test The older KingCoin material proposes highly centralized functions including monetary coordination, taxation, redistribution, sanctions, settlement, and public investment. In the current repository these are **LEGACY-PROPOSAL** material. Their analytical value is to show the danger of: ```text monetary authority + taxation + allocation + sanctions + governance + transaction infrastructure = extreme power stacking ``` The evolution of Power Dynamics moves away from “design a sufficiently just center” toward: > **Design powerful functions that do not become terminal arbitrary authority.** ## Conversion firewalls between the three domains | Conversion | Status | |---|---| | money → funding | desirable | | funding → infrastructure | desirable | | infrastructure → broader capability | desirable | | money → proportional political standing | blocked by principle | | credibility → informed advice | desirable | | credibility → sovereign decision right | blocked by principle | | monetary infrastructure → arbitrary exclusion | constitutional risk | | administrative execution → mandate redefinition | blocked by principle | ## The key question > **How can material and monetary capability increase collective agency without converting wealth, rails, or administration into unaccountable political sovereignty?** That is a core Power Dynamics question, not a side topic. ## Domain profiles - [Political & Constitutional Power](Political-and-Constitutional-Power) - [Economic & Allocation Power](Economic-and-Allocation-Power) - [Monetary, Credit & Liquidity Power](Monetary-Credit-and-Liquidity-Power) - [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) > **Canonical v6 repo source:** `showcase/13-political-economic-monetary-power.md` ================================================================================================ FILE: Power-Dynamics.wiki/Power-Analysis-Method.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 652db9f68234dac98474312e4dcedc0ea528b3b50865fc167155e742b3babf3d CONTENT_BYTES: 1511 ================================================================================================ # Power Analysis Method ## v6 entry point: audit the power surface first Before analyzing a single relation, inventory the domains the system touches, the controllers on each surface, cross-domain conversions, and routing destinations. Use [Power Surface Audit](Power-Surface-Audit) as the front-end instrument. Use this sequence for any actor, institution, subsystem, or branch. 1. **Problem / baseline** — what incapacity, dependency, or coordination problem exists? 2. **Resources** — what stocks and assets are available? 3. **Potential** — what possibilities do they create? 4. **Capacity** — what is organized enough to be used? 5. **Puissance** — what can actually be mobilized now? 6. **Mobilization** — reservoir, release, throughput, channels, mediation, amplification. 7. **Power relations** — whose possibilities change, and how? 8. **Returns** — what assets are created and who receives them? 9. **Conversion pathways** — what can become what? 10. **Stacking / concentration** — what accumulates in one node? 11. **Dependency** — what becomes hard to substitute or exit? 12. **Counterpowers** — verification, contestation, substitution, exit, fork, branch mobility. 13. **Temporal analysis** — compounding, decay, succession, lock-in. 14. **Constitutional requirements** — what should be scoped, separated, portable, or reversible? > **Canonical repo source:** `assessment/analysis-method.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Power-Balance-Sheet.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 8bfd41d34daf8b82a78be92e9b23b0acdc4a51c47f44cb81b49d30e860b036d6 CONTENT_BYTES: 757 ================================================================================================ # Power Balance Sheet A power balance sheet maps accumulated assets and dependencies without pretending they have one common unit. ### Assets / stocks financial, technical, epistemic, human, network, credibility, brand, institutional, operational, mnemonic, optionality. ### Dependencies / liabilities single providers, single maintainers, remote services, legal permissions, proprietary formats, recognition monopolies, key-person knowledge, network effects, update/signing keys, funding concentration. The purpose is to expose conversion pathways and terminal dependencies, not to produce a net “power score.” > **Canonical repo source:** `assessment/power-balance-sheet.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Power-Constitution.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b7cfad9bb022f7c0caa0f40fc231a58ba30109cca88e59f779017c4efbc5f72e CONTENT_BYTES: 3015 ================================================================================================ # Power Constitution The constitution exists **because the Power Show succeeds**. The objective is not to make kOA weak. It is to make strong, cross-domain capability compatible with scoped, contestable, non-terminal authority. > **Strong distributed puissance. Weak sovereignty.** ## Why v6 raises the constitutional stakes The [Power Surface](Power-Surface) makes visible that kOA can touch many consequential domains at once: ```text semantic → epistemic → credibility → attention → political economic → infrastructure → administrative monetary → economic → political narrative → affiliation → funding → adoption ``` The danger is therefore not only concentration inside one module. It is **cross-domain conversion and stacking**. ## Constitutional responsibilities A power constitution governs how useful capability may be: - generated; - composed; - converted; - routed; - concentrated; - challenged; - revoked; - transferred; - substituted; - exited; - forked; - replaced. ## Constitutional core - **political, economic, and monetary domains remain analytically distinct**; - **power-conversion firewalls** prevent automatic authority inheritance; - **power routing** redirects capability, returns, and optionality outward where feasible; - **Verification + Contestation + Substitution + Exit** remain foundational counterpowers; - authority is scoped by domain, mandate, duration, conditions, and review; - functional centrality need not become total sovereignty; - strong hubs are compatible with distributed capability when the whole remains independently reproducible; - branch mobility prevents current dominance from becoming final authority. ## Conversion firewalls ```text expertise → advice ✓ expertise → sovereignty ✗ money → funding ✓ money → proportional political rule✗ brand → attention ✓ brand → truth ✗ infrastructure → capability ✓ infrastructure → captivity ✗ execution → implement mandate ✓ execution → redefine mandate ✗ ``` ## Route before merely restraining The v6 constitution is not only a brake applied after concentration. > **Generate → Route → Scope → Bind → Verify → Contest → Substitute → Exit → Fork → Evolve** Public ethical self-binding, protocolization, Koali plurality, advice without sovereignty, portability, self-hosting, democratic allocation, and branch mobility are therefore constitutional mechanisms. Read [Power Routing & Sharing](Power-Routing-and-Sharing), [Power Conversion Firewalls](Power-Conversion-Firewalls), and [Non-Domination & Terminality](Non-Domination-and-Terminality). > **Canonical v6 repo sources:** `PRINCIPLES.md`, `POWER-ROUTING.md`, `POWER-SURFACE.md`, `constitution/README.md` as described in `TREE.md`. --- [Home](Home) · [Power Show](Power-Show) · [Branch Ecology](Branch-Ecology) ================================================================================================ FILE: Power-Dynamics.wiki/Power-Conversion-and-Routing-Map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 65815d209058641a50b2c9ab8ef1889ecd2d0820db2564a73f56c50eeb302286 CONTENT_BYTES: 2555 ================================================================================================ # Power Conversion and Routing Map This page combines the two v6 questions: > **How does power move across domains?** > **Where is the resulting capability, authority, return, and optionality routed?** ## Master pattern ```text SOURCE DOMAIN ↓ resource / capacity / puissance ↓ CONVERSION MECHANISM ↓ DESTINATION DOMAIN ↓ relational leverage ↓ ROUTING / FIREWALL / COUNTERPOWER ``` ## Canonical examples | Source | Conversion | Destination leverage | Routing / firewall | |---|---|---|---| | knowledge | evidence of competence | credibility / standing | domain-bounded signals; contestation | | credibility | ranking / endorsement | visibility / opportunity | plural models; credibility ≠ truth | | money | funding / purchase | infrastructure / execution | money ≠ political standing | | monetary rail | settlement / access | economic dependency | separability, substitution, constitutional scrutiny | | brand | attention / affiliation | revenue / adoption | brand stewardship ≠ protocol sovereignty | | technical administration | defaults / updates | dependency / de facto policy | scoped mandate, audit, self-hosting | | expertise | advisory reading | informed judgment | advice ≠ sovereign decision right | | founder knowledge | protocolization | independent operating capability | documentation, tests, plural maintainers | | narrative attention | public ethical commitments | self-binding / criticizability | function, not sovereign | | dominant branch | fork / demonstration | alternative institutional support | branch mobility and interoperability | ## Four routing destinations Every conversion should be audited for four separate outcomes: ```text CAPABILITY AUTHORITY RETURNS OPTIONALITY ``` A system can distribute capability while centralizing authority. It can decentralize operation while centralizing returns. It can provide formal exit while preserving practical dependency. These are different outcomes and should be measured separately. ## Capture warning > **Functional Control → Cross-Domain Power** Capture becomes more likely when conversion is hidden, cross-mandate, sticky, compounding, and difficult to contest or substitute. ## Constitutional target > **Composition without automatic conversion.** > **Strong distributed puissance. Weak sovereignty.** See [Power Surface](Power-Surface), [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion), [Power Routing & Sharing](Power-Routing-and-Sharing), and [Power Conversion Firewalls](Power-Conversion-Firewalls). ================================================================================================ FILE: Power-Dynamics.wiki/Power-Conversion-Firewalls.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ffd727f27fdfecc4b402ca256909d24e434800c00e46c6878508712122d92648 CONTENT_BYTES: 731 ================================================================================================ # Power-Conversion Firewalls A conversion firewall permits useful composition while blocking automatic cross-domain authority. Canonical examples: - `Expertise → Advice`, not `Expertise → Sovereignty`. - `Money → Funding`, not `Money → More Votes`. - `Brand → Attention`, not `Brand → Truth`. - `Technical Administration → Maintenance`, not `Administration → Political Outcome Control`. - `Credibility → Discoverability`, not `Credibility → Unquestionable Authority`. Firewalls should be auditable and testable at implementation level, not only stated as principles. > **Canonical repo source:** `constitution/conversion-firewalls.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Power-Domains.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b4e73b871adef9907fa4ede8188efae403f783129b7f3c9e546e1c470b46a27b CONTENT_BYTES: 3882 ================================================================================================ # Power Domains Domains answer **where** resources, capability, puissance, and relational power operate. v6 makes one distinction especially explicit: > **Political power ≠ Economic power ≠ Monetary power** They can convert into one another, but they involve different resources, mechanisms, mandates, risks, and counterpowers. ## Domain map | Domain | Core question | Profile | |---|---|---| | Political / constitutional | Who can decide, bind, represent, amend, veto, or define legitimate public standing? | [Political & Constitutional](Political-and-Constitutional-Power) | | Economic / allocation | Who can mobilize scarce material resources and decide where they go? | [Economic & Allocation](Economic-and-Allocation-Power) | | Monetary / credit / liquidity | Who controls exchange rails, issuance, settlement, reserves, liquidity, or credit conditions? | [Monetary, Credit & Liquidity](Monetary-Credit-and-Liquidity-Power) | | Epistemic / semantic | Who can shape what is knowable, valid, categorized, translated, or admissible? | [Epistemic & Semantic](Epistemic-and-Semantic-Power) | | Information / attention / media | Who can make things visible, discoverable, amplified, ranked, or ignored? | [Information, Attention & Media](Information-Attention-and-Media-Power) | | Credibility / reputation | Who can shape standing, trust signals, certification, or opportunity? | [Credibility & Reputation](Credibility-and-Reputation-Power) | | Network / affiliation | Who can broker access, recruit, include, exclude, connect, or mobilize relationships? | [Network & Affiliation](Network-and-Affiliation-Power) | | Administrative / operational | Who can route, assign, delay, approve, escalate, execute, or close? | [Administrative & Operational](Administrative-and-Operational-Power) | | Technical / infrastructural | Who can build, update, host, sign, standardize, interoperate, or withdraw infrastructure? | [Technical & Infrastructural](Technical-and-Infrastructural-Power) | | Narrative / symbolic / brand | Who can shape memory, affiliation, framing, identity, or symbolic legitimacy? | [Narrative, Symbolic & Brand](Narrative-Symbolic-and-Brand-Power) | | Cognitive / AI | Who or what can shape reasoning, synthesis, modeling, and automated interpretation? | [Cognitive & AI](Cognitive-and-AI-Power) | | Mnemonic / temporal | Who controls memory, precedent, timing, release, delay, expiry, or succession? | [Mnemonic & Temporal](Mnemonic-and-Temporal-Power) | | Evolutionary / counterpower | Who can contest, substitute, fork, recombine, and replace? | [Evolutionary & Counterpower](Evolutionary-and-Counterpower) | | Property / territorial | Who controls scarce physical or legal assets and the right to exclude? | [Property & Territorial](Property-and-Territorial-Power) | ## Domain rule Avoid claims like “X is more powerful than Y” unless the analysis specifies: > **powerful in what domain, through what resource, capacity, relation, mechanism, duration, conversion path, and counterpower environment?** A media organization may dominate attention while a state dominates legal enforcement. A payment rail may have monetary leverage without formal political sovereignty. A technical maintainer may have infrastructural leverage without owning the underlying knowledge. ## Cross-domain analysis The most important questions often concern transitions: ```text knowledge → credibility credibility → visibility visibility → agenda money → infrastructure infrastructure → dependency brand → affiliation administration → de facto policy ``` See [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) and the [Power Surface](Power-Surface). > **Canonical v6 repo sources:** `domains/README.md`, `POWER-SURFACE.md`, `README.md` --- [Home](Home) · [Three-Axis Model](Three-Axis-Model) · [Power Surface Audit](Power-Surface-Audit) ================================================================================================ FILE: Power-Dynamics.wiki/Power-Ecology.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6bc86fca35d0080bd9cd9230b68f46b96d11b620f6bf4f133ee75f9930a2d5cd CONTENT_BYTES: 2530 ================================================================================================ # Power Ecology ## v6: ecology across domains The ecology is now made explicit through the [Power Surface](Power-Surface): political, economic, monetary, semantic, technical, narrative, administrative, and other domains can convert into one another. The ecology must therefore be analyzed as a network of **cross-domain conversion paths**, not only as a list of actors. A **power ecology** is a system in which resources, forms of puissance, relations of power, returns, dependencies, and alternatives continuously interact. The kOA Power Show is best understood ecologically because no single capability explains the whole effect. ## Capability ecology Typical capability-generating chains include: `knowledge → understanding → judgment → action` `network → collaborators → coordination → collective puissance` `memory → lower relearning cost → better future judgment` `AI + provenance + human governance → higher cognitive throughput` `portable infrastructure → substitution → stronger exit capacity` ## Conversion ecology Typical cross-domain chains include: `knowledge → credibility → visibility → opportunity` `execution → results → evidence → credibility` `brand → attention → affiliation → revenue` `money → infrastructure → reach → influence` `technical control → defaults → dependency → agenda leverage` These chains can be productive, extractive, regenerative, or dangerous depending on who receives returns and whether conversions remain scoped. ## Feedback ecology Power Dynamics therefore asks: - what resources are accumulated; - what puissance they support; - how capabilities compose; - how they are mobilized; - what power relations emerge; - what effects and returns are produced; - where returns accumulate; - which nodes become bottlenecks; - what dependencies form; - which counterpowers remain effective; - whether alternatives can survive and evolve. ## kOA as a designed ecology kOA deliberately distributes capability across semantic, epistemic, social, decision, operational, mnemonic, technical, and federative layers. The design challenge is to obtain the **composition gain** without allowing one layer to silently convert its useful function into total cross-domain authority. The constitutional aspiration is therefore: > **Maximum composable capability; minimum terminal sovereignty.** > **Canonical repo source:** `framework/04-power-ecology.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Power-Relations.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f6cc2f0289a9abd194c8dab0c4950f5215267afdca8dfb4481887e07a360b1d3 CONTENT_BYTES: 2561 ================================================================================================ # Power Relations Power Relations begins where the Power Show becomes socially consequential: when effective capability changes access, standing, visibility, allocation, authority, dependency, or another actor’s ability to act. The Power Show maps **what actors become able to do**. This directory maps the next question: > **Whose possibilities change because that capability exists or is controlled?** Power is relational: mobilized puissance becomes power when it changes another actor's effective possibilities. ## Enabling and coordination power Relations that expand possibilities by granting access, recognition, coordination, legal standing, interoperability, or infrastructure use. Even enabling relations can become dependency when one actor becomes the only viable gateway. ## Access, gatekeeping, and allocation power Control over entry conditions and distribution of scarce resources, opportunities, credentials, services, funding, identity, or platform access. ## Visibility, ranking, agenda, and framing power Pre-political relations that shape what becomes seen, prominent, discussable, interpretable, fundable, reusable, or adoptable. ## Recognition, standing, and certification power Relations that affect who is treated as competent, trustworthy, qualified, legitimate, or institutionally relevant. ## Semantic, constitutive, and standard-setting power Definitions, classifications, ontologies, thresholds, translations, formats, trust roots, interoperability contracts, and admissibility rules. ## Authority, administration, and enforcement power Mandates, routing, assignment, timing, escalation, closure, sanctions, compulsion, and denial of consequences. ## Dependency, bottleneck, lock-in, and terminal power Relational leverage created when alternatives are costly, slow, non-portable, unrecognized, or unavailable. Terminal power is the limiting case where capture or failure cannot be effectively verified, contested, substituted, reversed, or exited. ## Veto, blocking, and delay power Preventing, slowing, queuing, withholding approval, or increasing procedural cost. Time is a political variable. Power relations are not automatically illegitimate. Assessment depends on mandate, scope, proportionality, transparency, alternatives, dependency, counterpower, and reversibility. See [Component Power Matrix](Component-Power-Matrix) for how these relations emerge around kOA components. > **Canonical repo source:** `relations/README.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Power-Routing-and-Sharing.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f8e2c9fdcf2edea86c61d6eee8bbcb9974ff97a63adc29a2d6e4b5036a4ccba8 CONTENT_BYTES: 5554 ================================================================================================ # Power Routing, Sharing, and Devolution Power Dynamics does not stop at **how much power kOA can generate**. It asks: > **Where does the capability, leverage, authority, return, and optionality created by kOA actually go?** A system can empower users while still making its operator indispensable. Power routing therefore examines four destinations separately: ```text CAPABILITY → who can do more? AUTHORITY → who can decide or control more? RETURNS → who receives reusable value? OPTIONALITY→ who can refuse, leave, reproduce, fork, or wait? ``` ## Core routing mechanisms | Source of leverage | Concentrating default | Routing / sharing mechanism | Intended destination | |---|---|---|---| | Founder knowledge | permanent founder dependency | documentation, schemas, protocolization, tests | maintainers, branches, independent operators | | Narrative attention | founder/persona centrality | explicit ethics, self-critique, attribution, anti-domination | public principles, procedures, critical readers | | Brand | trademark becomes protocol sovereignty | brand stewardship separated from protocol | protocol commons + bounded official brand | | Koali credibility infrastructure | one owner defines standing | plural distributions, portable evidence, explicit policy identity | communities, domains, alternative operators | | Expertise | expert becomes ruler | baseline + bounded advisory readings | informed public judgment | | Knowledge validation | one owner of truth | provenance, reader policies, competing Kristals | plural epistemic capability | | Infrastructure | operator becomes unavoidable | self-hosting, capsules, federation, rollback, substitution | local operators / communities | | Money | wealth buys rule | one-member-one-vote / allocation firewalls | common funding without pay-to-rule | | Workflow control | administrator becomes policymaker | scoped mandate, audit, appeal, revocability | execution without mandate capture | | AI capability | model becomes hidden sovereign | explicit role boundaries, provenance, human authority | cognitive amplification without institutional sovereignty | | Dominant branch | incumbency becomes final | branch mobility, lineage, recombination | viable alternatives | ## Ethical fiction as power routing The fiction is not only a vehicle for symbolic puissance. It also publishes limits on that puissance. The source corpus includes explicit commitments around: - clarity of intention; - respect for living beings; - vigilance against monopoly, domination, and manipulation; - recognition of contributors and sharing merit; - self-mockery and refusal to sanctify the Klown; - revision, criticism, adaptation, and transmission rather than dogma. Power Dynamics calls this **narrative self-binding**. ```text symbolic power → public ethical commitments → stable grounds for criticism → reduced freedom for arbitrary reinterpretation ``` Self-binding is not proof of compliance. It makes the exercise of power **more legible and criticizable**. ## Koali: from property to protocol ecology Current architect-confirmed design direction: > **Koali should not remain a terminal personal credibility authority. Its useful capability should be duplicable, shareable, branchable, and operable through plural distributions around interoperable structures.** The desired transition is: ```text founder-created capability → explicit kernel / contracts → portable evidence and history → explicit policy identity → multiple distributions → interoperability → independent operation → branch mobility ``` This is not founder erasure. It is **ownership decoupling**: the useful function can outgrow exclusive ownership of the first implementation. ## Power sharing is not flatness The goal is not to make everyone equally expert, equally responsible, or equally authoritative. The goal is: > **Useful asymmetry without terminal dependency.** A maintainer may have more technical authority within a defined scope. An expert may have more epistemic relevance in a defined domain. A coordinator may have routing authority for a workflow. None of those roles should silently acquire unrelated sovereignty. ## Routing and conversion firewalls Routing is strongest when paired with conversion limits: ```text expertise → advice ✓ expertise → sovereign vote weight ✗ money → funding ✓ money → political standing ✗ brand → attention ✓ brand → truth ✗ infrastructure → capability ✓ infrastructure → captivity ✗ execution → implement mandate ✓ execution → redefine mandate ✗ ``` ## Canonical routing test For every important kOA mechanism: 1. What puissance does it create? 2. Where would that puissance naturally concentrate? 3. What relational power does that concentration create? 4. What capability can be routed outward instead? 5. What authority must remain scoped? 6. Who receives the returns? 7. Who receives exit / substitution / fork optionality? 8. What evidence proves that the routing is practical rather than merely formal? See [Power Routing Audit](Power-Routing-Audit). ## Continue - [Ethical Fiction as Self-Binding](Ethical-Fiction-as-Self-Binding) - [Koali: From Property to Protocol](Koali-From-Property-to-Protocol) - [Power Conversion Firewalls](Power-Conversion-Firewalls) - [Power Surface Audit](Power-Surface-Audit) > **Canonical v6 repo source:** `POWER-ROUTING.md` ================================================================================================ FILE: Power-Dynamics.wiki/Power-Routing-Audit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: d1fcebdcafc3eca148b9721221371fb24153445d98887a6f26fe94c3bb6122a8 CONTENT_BYTES: 1029 ================================================================================================ # Power Routing Audit After identifying what puissance a system creates, ask **where it goes**. For each major capability, record: ```text Generated puissance: Concentration vector: Routing mechanism: Primary recipients: Retained central rights: Transferred / shared rights: Return allocation: Exit / substitution path: Failure mode: Evidence needed: ``` Audit six destinations: 1. **Capability** — who can actually do more? 2. **Authority** — who gains decision, validation, ranking, update, or veto rights? 3. **Returns** — who receives money, knowledge, reputation, network, code, data, and memory? 4. **Optionality** — who can leave, self-host, fork, wait, or substitute? 5. **Interpretation** — who controls categories, credibility policies, semantic mappings, and defaults? 6. **Visibility** — who controls discoverability, ranking, attention, and agenda? Then test self-binding, protocolization, ownership decoupling, and effective exit. > **Canonical repo source:** `assessment/power-routing-audit.md` ================================================================================================ FILE: Power-Dynamics.wiki/Power-Show.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 5913915f92e232032a091226aa9ca918b6e14c63728a786788047b3544a3b974 CONTENT_BYTES: 7756 ================================================================================================ # The kOA Power Show The first purpose of this repository is simple: > **Show all the ways kOA can make people, groups, organizations, institutions, and federations more capable.** Then ask what happens when those capabilities become socially consequential. ## The one-paragraph answer kOA is immensely powerful because it can connect **meaning, knowledge, AI, discovery, credibility, networks, deliberation, political choice, economic allocation, coordination, execution, memory, infrastructure, federation, and institutional evolution** inside a recursive loop. The result is not merely more information. It is the possibility of turning distributed resources into collective agency, preserving the returns of action, reinvesting them, reproducing the capability elsewhere, and routing important forms of leverage away from terminal ownership. > **Breadth × Composition × Closure × Memory × Compounding × Replication × Routing** ## 1. Breadth — many forms of puissance kOA can generate or amplify: - semantic puissance; - epistemic puissance; - cognitive / AI-mediated puissance; - information and distribution puissance; - attention / discoverability puissance; - credibility / reputation puissance; - network and affiliation puissance; - collective puissance; - political / deliberative / decision puissance; - economic and allocation puissance; - monetary / liquidity capability where monetary infrastructure exists; - administrative and operational puissance; - technical and infrastructural puissance; - narrative / symbolic / brand puissance; - mnemonic and temporal puissance; - federation, exit, substitution, fork, and evolutionary puissance. See [Power Surface](Power-Surface). ## 2. Composition — the whole can exceed the sum ```text SemantiK / SenTient → meaning Kristal → knowledge + provenance + memory Konnaxion → discovery + network + circulation Koali / EkoH → credibility legibility SmartVote → comparative judgment + decision support Orgo → operational execution AI → cognitive amplification Capsules / federation→ replication + substitution Brand / narrative → transmission + affiliation Economic rails → funding + material capability ↓ compose ↓ coordinated collective puissance ``` A capable population is not automatically a capable collective. Composition creates the ability to use distributed capabilities **together**. ## 3. Closure — knowledge reaches action > **Know → Choose → Act → Remember → Know better** Many systems stop at one stage. kOA attempts to connect the stages. ```text knowledge → judgment → decision → governed work → execution → result → memory ``` This turns intelligence into agency. ## 4. Memory — the past remains usable kOA can preserve: - evidence; - provenance; - definitions; - decisions; - reasons; - workflows; - failures; - outcomes; - contribution history; - branch lineage. Without memory, a collective repeatedly pays the cost of rediscovery. With memory, past action becomes infrastructure for future action. ## 5. Compounding — action creates future capability ```text Puissance → Action → Result → Return → Asset → Reinvestment → Greater Future Puissance ``` Returns can include knowledge, code, tools, data, credibility, network, reputation, money, infrastructure, access, and optionality. This is the **compounding engine**. ## 6. Cross-domain conversion — one capability unlocks another ```text knowledge → credibility → visibility → opportunity money → infrastructure → reach → influence brand → affiliation → revenue → development network → collaborators → execution → results memory → lower coordination cost → faster action ``` Conversion is one reason kOA can become extremely powerful. It is also one reason it can become dangerous. > **Functional Control → Cross-Domain Power** See [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion). ## 7. Political power — before, during, and after the vote kOA touches: > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** That means political power is not confined to SmartVote or formal governance. Semantic definitions, search, ranking, credibility, workflow, and memory can all shape political possibility. ## 8. Economic power — resources become action kOA can help convert: ```text money / property / funding / labor / infrastructure → usable economic capacity → projects / services / coordination / production ``` It can also route economic resources through democratic allocation mechanisms rather than allowing wealth to automatically buy more political standing. ## 9. Monetary power — control of exchange rails Monetary power concerns issuance, liquidity, settlement, payment rails, reserves, credit, debt conditions, and transaction access. The legacy KingCoin material shows why this domain is so constitutionally sensitive: monetary control can stack with taxation, allocation, sanctions, and administration into highly terminal power. The evolved doctrine is therefore not “centralize monetary power well,” but: > **If powerful monetary functions exist, keep their authority scoped, contestable, separable, and substitutable.** ## 10. Scaling — individual to federation ```text individual → team → organization → institution → federation ``` At each scale, kOA can add shared knowledge, coordination, decision, execution, memory, and infrastructure. The design target is: > **Capability can scale without sovereignty scaling at the same rate.** ## 11. Replication — capability can leave the center Self-hosting, capsules, portability, federation, and branchability can transform: ```text use a central service ``` into: ```text possess / reproduce / operate the function locally ``` That is a major transfer of effective possibility. ## 12. Power routing — kOA can equip others instead of only itself The project includes mechanisms intended to redirect the power it creates: ```text expertise → advice, not sovereignty money → funding, not more votes narrative → mobilization + ethical self-binding Koali → plural distributions, not terminal personal ownership Kristal → portable knowledge, not one owner of truth infrastructure → self-hosting / federation, not captivity dominance → branch mobility, not final authority ``` This is why **power sharing** is part of the Power Show, not merely a later defensive layer. ## 13. The constitutional paradox The stronger the Power Show becomes, the more necessary constitutional design becomes. ```text more knowledge capability → more validation power more discovery capability → more agenda power more credibility capability → more standing power more workflow capability → more administrative power more infrastructure capability → more dependency power ``` Therefore: > **The constitution exists because the Power Show succeeds.** ## 14. The mature doctrine > **Generate immense puissance.** > **Compose it.** > **Close the loop.** > **Preserve the returns.** > **Compound future capability.** > **Make cross-domain conversions visible.** > **Route capability outward.** > **Block automatic conversion into unrelated sovereignty.** > **Preserve verification, contestation, substitution, exit, and forkability.** > **Allow the whole system to evolve.** In compressed form: > **Strong distributed puissance. Weak sovereignty.** --- [Home](Home) · [Power Surface](Power-Surface) · [Power Routing & Sharing](Power-Routing-and-Sharing) ================================================================================================ FILE: Power-Dynamics.wiki/Power-Surface-Audit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b3bff62c9c7c406088a5eeda3dbca7dbce7cd9387a36b1cb2b7877ada78f99ef CONTENT_BYTES: 2386 ================================================================================================ # Power Surface Audit Use this audit to answer: > **What kinds of power does this system generate, where can they convert, and where are they routed?** ## 1. Domain inventory For each domain, record: | Domain | Resources | Capacity | Puissance | Relational power | Main controllers | |---|---|---|---|---|---| | Political | | | | | | | Economic | | | | | | | Monetary | | | | | | | Epistemic | | | | | | | Semantic | | | | | | | Information / attention | | | | | | | Credibility | | | | | | | Network | | | | | | | Administrative | | | | | | | Technical / infrastructure | | | | | | | Narrative / brand | | | | | | | Cognitive / AI | | | | | | | Mnemonic / temporal | | | | | | | Evolutionary / counterpower | | | | | | ## 2. Conversion inventory For every major conversion: ```text source domain → mechanism → destination domain → resulting leverage ``` Record whether the conversion is: - explicit or hidden; - intended or emergent; - reversible or sticky; - scoped or cross-mandate; - contestable or terminal. ## 3. Stacking test Which actor or node controls multiple high-leverage surfaces? Look especially for combinations of: - identity; - credibility; - discoverability; - allocation; - workflow; - infrastructure; - signing / updates; - brand / certification; - monetary rails. ## 4. Routing test For each major capability, identify who receives: - **capability**; - **authority**; - **returns**; - **optionality**. ## 5. Counterpower test Can affected actors effectively: - verify? - contest? - substitute? - exit? - self-host? - fork? - preserve identity / history / evidence? - gather support for an alternative? ## 6. Terminality test Ask: > If this controller fails, captures the function, changes policy arbitrarily, or disappears, can the ecosystem continue through another viable path? If not, the surface may be **terminal power**. ## 7. Output A complete audit should produce: 1. a domain map; 2. a conversion graph; 3. a stacking map; 4. a routing map; 5. a counterpower map; 6. a terminality assessment; 7. a list of technical evidence still required. ## Related instruments - [Power Routing Audit](Power-Routing-Audit) - [Power Analysis Method](Power-Analysis-Method) - [Power Balance Sheet](Power-Balance-Sheet) - [Constitutional Tests](Constitutional-Tests) > **Canonical v6 repo source:** `assessment/power-surface-audit.md` ================================================================================================ FILE: Power-Dynamics.wiki/Power-Surface.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 323f34a853aa8979a2ab63b09b2d908acfbf37a48a5615d6088eecab6b9aee61 CONTENT_BYTES: 6310 ================================================================================================ # The kOA Power Surface A **power surface** is any function, interface, role, registry, workflow, standard, narrative, resource rail, or infrastructural boundary through which control can materially alter effective possibility. The kOA Power Show is strongest when it makes the whole surface visible at once. > **kOA is powerful because it can create capability across many domains and connect those domains into conversion and feedback loops.** ## Master map | Domain | Generated puissance | Relational power that may emerge | Typical conversion outward | kOA routing / firewall direction | |---|---|---|---|---| | Epistemic | validate, compare, preserve, reuse knowledge | validation, canon, trust-root | knowledge → credibility | portable artifacts, provenance, competing Kristals | | Semantic | structure concepts, categories, translation, ambiguity | classification, framing, admissibility | meaning → agenda / enforcement | versioned semantics, local governance, contestation | | Cognitive / AI | reasoning, synthesis, modeling, translation | hidden framing, prioritization, dependency | cognition → judgment / execution | AI under explicit governance, bounded authority | | Information / attention | publish, search, rank, distribute, amplify | visibility, agenda, moderation | attention → affiliation / legitimacy / funding | explicit discovery policies, alternatives, export | | Credibility / reputation | make evidence of competence/contribution legible | standing, certification, opportunity | credibility → visibility / access | domain-bounded signals, plural models, contestation | | Network / affiliation | association, brokerage, recruitment, diffusion | inclusion, exclusion, access | network → execution / opportunity | portable identity/relationships where feasible, plural networks | | Political / constitutional | deliberate, decide, authorize, amend, govern | mandate, veto, legitimacy, decision | political → administrative / allocation | political equality, scoped authority, contestation | | Economic | mobilize scarce resources, assets, labor, funding | bargaining, ownership, allocation | money → infrastructure / reach | democratic allocation, anti-pay-to-rule firewalls | | Monetary | liquidity, exchange, payment, credit, settlement | issuance, rail, reserve, access | monetary → economic / political dependency | treat high-stack monetary designs as constitutional risk | | Administrative / operational | assign, route, schedule, escalate, close | timing, workload, approval, closure | administration → de facto policy | explicit workflows, audit, appeal, revocability | | Technical / infrastructural | build, deploy, verify, operate, reproduce | compatibility, update, identity, dependency | infrastructure → standards / access | self-hosting, capsules, federation, substitution | | Narrative / symbolic / brand | memory, attention, affiliation, transmission | framing, legitimacy-by-association, gatekeeping | brand → attention → revenue / adoption | ethical self-binding, brand ≠ truth, protocol separation | | Mnemonic / temporal | preserve reasons, outcomes, precedent, timing | precedent, delay, succession | memory → future agenda / legitimacy | provenance, versioning, alternative histories | | Evolutionary / counterpower | fork, substitute, recombine, replace | displacement of incumbents | alternative → support → dominance | branch mobility, lineage, interoperability | ## Why breadth matters A system that is powerful in one domain can still be constrained by other systems. A system that touches many domains can create much larger **cross-domain leverage**. For example: ```text semantic control → epistemic interpretation → credibility → visibility → agenda → political influence ``` or: ```text money → infrastructure → distribution → attention → affiliation → political leverage ``` or: ```text technical control → defaults → dependency → administrative necessity → de facto governance ``` The same breadth that makes kOA capable is therefore the reason it needs explicit constitutional design. ## Political surface kOA can influence political capacity through: - issue formation and semantic framing; - discoverability and agenda formation; - credibility and advisory signals; - deliberation and proposal comparison; - voting / reading mechanisms; - resource allocation; - workflow and execution; - memory and precedent; - branch evolution and institutional alternatives. Political power therefore begins **before the vote** and continues **after the vote**. ## Economic surface Economic puissance includes the ability to mobilize: - money; - property; - productive assets; - labor and time; - infrastructure; - funding; - contracts; - procurement; - philanthropy; - bargaining position. kOA can increase economic capability by improving coordination, credibility, discoverability, resource pooling, allocation, execution, and compounding. ## Monetary surface Monetary power is narrower than economic power. It concerns control over: - issuance; - units of account; - liquidity; - payment rails; - settlement; - reserves; - credit and debt conditions; - convertibility; - transaction access. A monetary layer can become extraordinarily powerful because it conditions other domains. This is why the legacy KingCoin proposals are useful as a **stacking stress test**, not as current constitutional doctrine. ## The core constitutional question For every surface, ask: 1. **Who gains capability?** 2. **Who gains authority?** 3. **Who receives returns?** 4. **Who gains optionality?** 5. **What other domain can this convert into?** 6. **What prevents that conversion from becoming arbitrary?** 7. **Can affected actors verify, contest, substitute, exit, or fork?** The desired architecture is not flatness. It is a **governable ecology of strong capabilities and non-terminal asymmetries**. ## Continue - [Power Surface](Power-Surface) - [Political, Economic & Monetary Power](Political-Economic-and-Monetary-Power) - [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) - [Power Routing & Sharing](Power-Routing-and-Sharing) - [Power Domains](Power-Domains) --- [Home](Home) · [Power Domains](Power-Domains) · [Power Surface Audit](Power-Surface-Audit) ================================================================================================ FILE: Power-Dynamics.wiki/Pre-Political-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ea4a11df856cb01534ffaedab5da23bf293894a6af9b02bf8bbaba0068bfa2ba CONTENT_BYTES: 1817 ================================================================================================ # The Pre-Political Chain Power begins before formal voting or command. > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** kOA touches nearly every step. ## Meaning Categories determine what can be described, compared, included, or excluded. Semantic infrastructure can create semantic puissance; control over definitions can create semantic power. ## Knowledge What becomes structured, provenance-bearing, canonical, disputed, or reusable affects later reasoning. ## Visibility What is discoverable has a higher chance of being cited, funded, reused, adopted, or debated. Discoverability is therefore both capability and governance. ## Credibility Signals about expertise or contribution can help groups navigate complexity. They can also affect opportunity and standing. ## Agenda What is surfaced repeatedly becomes more likely to be treated as worthy of collective attention. ## Deliberation and decision Decision tools can expand comparative capacity. Defaults, lenses, weighting, and presentation can also shape the decision environment. ## Execution Routing, ownership, time, escalation, and closure determine whether a nominal decision becomes an effective outcome. ## Memory What is preserved becomes precedent, evidence, training data, institutional learning, and the starting point for future decisions. ## Why this belongs in the Power Show The impressive capability of kOA is precisely that it links these stages. The governance challenge is that a system spanning these stages could also accumulate pre-political leverage if the same node controls too many transitions. > **Canonical repo source:** `showcase/06-pre-political-chain.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Principles.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a8a6938f0be48bde6c9e2913408d5856ef8f4e1cab9923c421c115849e394a24 CONTENT_BYTES: 8079 ================================================================================================ # Principles Power Dynamics begins from an affirmative premise: **people and collectives should be able to become dramatically more capable**. The constitutional problem is how to preserve that capability without allowing successful functions to harden into arbitrary, cross-domain, or terminal sovereignty. ## Generate immense but usable puissance 1. **Increase effective possibility.** expand what actors can realistically understand, choose, build, coordinate, refuse, preserve, and accomplish. 2. **Turn dispersed resources into mobilizable capability rather than merely accumulating resources.** 3. **Collective puissance can be generated.** coordinated capability can exceed the sum of isolated capabilities. 4. **Infrastructure should crystallize past effort into reusable future capacity.** 5. **Knowledge, memory, tools, and institutional learning should become cumulative.** 6. **Capability should scale from individual to federation without requiring sovereignty to scale at the same rate.** 7. **Composition does not require ownership.** interoperating functions need not collapse into one owner or authority. ## Keep domains explicit 8. **Political power, economic power, and monetary power are distinct even when they convert into one another.** 9. **Political power begins before formal decision.** meaning, visibility, credibility, and agenda are political surfaces. 10. **Economic puissance concerns mobilization of scarce resources.** economic power concerns relational effects of that control. 11. **Monetary power concerns the infrastructure and conditions of exchange.** issuance, rails, liquidity, settlement, reserves, credit, and access. 12. **Administrative power can alter outcomes without changing formal policy.** 13. **Semantic and epistemic power can shape the field in which later political decisions become intelligible.** 14. **Every domain analysis should name resources, capability, relation, conversion paths, duration, and counterpowers.** ## Maintain ontological discipline 15. **Resource ≠ Potential ≠ Capacity ≠ Puissance ≠ Power.** 16. **A resource is not automatically power.** 17. **Puissance is effective mobilizable capacity under real conditions.** 18. **Power is relational and domain-specific.** 19. **Power to / with / through are primarily capability questions.** power over is primarily a relational question. 20. **Stock, reservoir, flow, reach, influence, authority, legitimacy, and sovereignty are not synonyms.** ## Expose conversion and stacking 21. **Different forms of puissance should remain composable without automatically converting into unrelated authority.** 22. **Expertise may inform.** it does not automatically govern. 23. **Money may fund.** it does not automatically buy political standing. 24. **Brand may attract attention.** it does not become truth. 25. **Technical administration may maintain infrastructure.** it does not silently inherit political authority. 26. **Credibility may improve discoverability.** it does not become unquestionable legitimacy. 27. **Execution may carry out a mandate.** it does not silently redefine the mandate. 28. **Infrastructure may create capability.** it does not thereby own its users. 29. **Power stacking must be assessed across domains, not function by function.** 30. **Capture is a conversion problem.** Functional Control → Cross-Domain Power. ## Route and share power deliberately 31. **Power should be routed, not merely constrained after concentration.** 32. **Generated capability should preferentially become reusable capability for participants and communities where feasible.** 33. **Public ethical commitments can be a self-binding mechanism.** they do not prove compliance but create stable grounds for criticism. 34. **Narrative power should carry its own limits through explicit anti-domination, attribution, humility, and revision principles.** 35. **Protocolization is power sharing.** tacit founder mastery should become explicit, testable, documented, and independently reproducible. 36. **Useful functions should be decoupled from exclusive ownership where feasible.** 37. **Koali is a key ownership-decoupling test.** credibility capability should be duplicable, shareable, branchable, and capable of plural distributions. 38. **Returns are part of power routing.** who receives knowledge, money, reputation, network, code, memory, and infrastructure is constitutional. 39. **Exit, substitution, self-hosting, and forkability distribute optionality.** 40. **Sharing capability does not require flatness.** the target is non-terminal asymmetry. 41. **The strongest center is one that can create capability beyond itself.** ## Make emerging power legible 42. **Architecture is governance before governance is written.** 43. **Every technical boundary is also a potential political boundary.** 44. **Every mechanism that distributes capability creates a new locus of power.** 45. **Dependency is a gradient.** formal choice is not effective choice when switching costs are prohibitive. 46. **Terminal power is a primary constitutional risk.** 47. **Functional centrality is not automatically domination, but centrality plus dependency plus weak counterpower can become domination.** 48. **Instance capture must not imply system capture.** ## Preserve counterpower 49. **Verification + Contestation + Substitution + Exit are foundational counterpowers.** 50. **Formal exit is insufficient.** exit must be effective. 51. **Formal forkability is insufficient.** branch mobility matters. 52. **Revocability and reversibility are distinct.** 53. **Strong hubs are compatible with distributed capability when the whole remains independently reproducible.** 54. **Portability must include the artifacts, history, provenance, evidence, and configuration needed for meaningful continuity.** ## Preserve epistemic humility 55. **No measure of competence, ethics, credibility, contribution, or legitimacy should be treated as perfectly complete or permanently final.** 56. **Score ≠ person ≠ competence ≠ ethics ≠ truth.** 57. **Support is not evidence.** 58. **Dominance is not truth, quality, or final legitimacy.** 59. **Uncertainty, disagreement, and competing representations must remain representable.** 60. **Plurality is useful when it adds evidence, context, method, function, challenge, translation, or synthesis.** ## Make capability regenerative 61. **Action should leave assets behind.** 62. **Who receives the returns matters.** 63. **Returns can compound future puissance.** 64. **Compounding can also compound concentration and must be audited.** 65. **Shared infrastructure should convert collective activity into broader future capability where feasible.** 66. **Memory is a production factor, not merely an archive.** ## Keep the system evolvable 67. **Imperfection is permanent.** authority need not be. 68. **Variation is normal institutional experimentation, not only an emergency response to capture.** 69. **Complementarity can be superior to convergence.** 70. **The stable kernel should protect evolution, not freeze outcomes.** 71. **A better branch should be able to demonstrate value, gather support, remain interoperable, and influence or replace a dominant branch.** 72. **Improvement claims should state the dimension, beneficiaries, conditions, evidence, and trade-offs.** ## kOA constitutional orientation 73. **Strong distributed puissance.** Weak sovereignty. 74. **StrongHub + DistributedCapability + ReplicableWhole.** 75. **AI assists under governance.** AI does not silently inherit institutional sovereignty. 76. **Semantic sovereignty requires practical control, not merely formal openness.** 77. **Founder independence is a resilience criterion, not a requirement to erase the founder.** 78. **Brand stewardship and protocol governance are distinct.** 79. **The system should remain capable of learning from its own alternatives.** --- [Home](Home) · [Power Constitution](Power-Constitution) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Propagation-Engine.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f89b9beae2077c138e843a5a061e590d1e3205da016203c5b00df4004ce45c1a CONTENT_BYTES: 1475 ================================================================================================ # Propagation Engine Power Dynamics distinguishes **compounding** from **propagation**. ```text COMPOUNDING A acts → reusable return → A becomes more capable PROPAGATION A acts → reusable return → activation barrier for B falls → B becomes capable COUPLED PROPAGATION A strengthens B → B strengthens C → C strengthens A ``` For kOA, propagation can occur through reusable money, evidence, credibility, code, tools, operators, integrations, language resources, documentation, content, relationships, and institutional access. ## Example coupled loop ```text technical capability → World / demonstration → institutional pilot → evidence → credibility → more institutional access → deployment / managed service → revenue → development → greater technical capability ``` Additional loops can attach through SmartVote, Kintsugi, UCKK, multilingual expansion, machine-readable documentation, federation, and founder decentering. The constitutional condition is: > **Healthy propagation increases distributed capability faster than terminal dependency.** Positive feedback therefore needs governors: domain-bounded expertise, baseline/advisory separation, authority boundaries, self-hosting, exit, forkability, optional federation, provenance, publication gates, founder opposition, and `money ≠ votes / brand ≠ truth / credibility ≠ sovereignty` firewalls. See the repository canonical page `PROPAGATION.md` for the full analysis. ================================================================================================ FILE: Power-Dynamics.wiki/Property-and-Territorial-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 650cfde9595c0cdb552de627db7a07f3fa1746b2642e9bc2cf1713c866a5d4c0 CONTENT_BYTES: 1732 ================================================================================================ # Property & Territorial Power > **Core question:** Who controls scarce physical or legal assets and the enforceable right to exclude others from them? ## Generated puissance Effective capability to **own, use, lease, sell, collateralize, restrict access to, or allocate scarce property and territory**. ## Relational power that can emerge Exclusion power, access power, ownership leverage, bargaining power, territorial control. ## Typical conversion paths - `property → collateral / finance` - `ownership → access conditions` - `territory → infrastructure control` - `IP / trademark → commercial or symbolic leverage` ## Routing / counterpower direction - distinguish protocol commons from scarce brand or property stewardship - audit ownership dependencies - preserve substitution where feasible - avoid treating ownership of one asset as sovereignty over unrelated functions ## kOA touchpoints - brand / trademark governance can create property-like choke points - infrastructure ownership matters when local operation depends on one host or asset - Power Dynamics treats property as one domain among several rather than the definition of all power ## Analytical note Property power is strongest where the controlled asset is scarce and substitutes are weak. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/README-WIKI-SETUP.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 053b2930edaf5492bd875f8705947b555502cc6a9ed8e87c0d47f00d3e106d42 CONTENT_BYTES: 1502 ================================================================================================ # GitHub Wiki Setup — v6.2 This directory is ready to be used as the separate Git repository behind the `Power-Dynamics` GitHub Wiki. ## Publication flow 1. Enable Wiki in the main repository. 2. Clone the wiki repository created by GitHub, normally `Power-Dynamics.wiki.git`. 3. Replace its contents with this directory. 4. Commit and push. GitHub Wiki uses `Home.md` as the landing page and `_Sidebar.md` / `_Footer.md` as navigation chrome. ## GitHub Wiki link rule Keep files as `.md`, but internal wiki links **must not include `.md`**: ```md [Power Surface](Power-Surface) [Political Power](Political-and-Constitutional-Power) ``` Rendered URL: ```text https://github.com/Rejean-McCormick/Power-Dynamics/wiki/Power-Surface ``` Do not link rendered navigation to `Power-Surface.md`, and do not use `raw.githubusercontent.com` when you want formatted Markdown. ## Canonical-source rule The main Power Dynamics repository remains canonical. The wiki is the reader-facing synthesis layer. Update canonical definitions in the repo first, then propagate them here. ## v6.2 front door The recommended public entry sequence is: > **Why kOA Is Immensely Powerful → Power Surface → Power Show → Power Routing → Constitution** ## v6.2 academic layer The wiki includes a reader-facing [Academic Lineage](Academic-Lineage) synchronized from the canonical repo `Academic-Lineage/` directory. Keep canonical research claims in the main repository first, then propagate changes here. ================================================================================================ FILE: Power-Dynamics.wiki/Recognition-Loop.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 68aeccb83e793e842a50513b400559b583fa12ef9af411d96a0618ff048f1a93 CONTENT_BYTES: 576 ================================================================================================ # Recognition Loop and Incumbency A healthy recognition loop: `Contribution → Evidence → Recognition → Opportunity → More Contribution` can become: `Recognition → Visibility → Opportunity → Recognition` The second loop lets incumbency reproduce itself even when new evidence is weak. Branch mobility, portable evidence, domain-bounded credibility, time decay, and alternative discovery policies can counterbalance this dynamic. > **Canonical repo source:** `cases/recognition-loop.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Recombination-and-Replacement.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 81bd7135521b7da6a53f0022dc819a8db5ad7e0541cedbdaa8558a12fb2aeb6e CONTENT_BYTES: 494 ================================================================================================ # Recombination and Replacement Evolution is not always replacement. Branches may coexist, specialize, merge, import specific improvements, recombine into a new branch, decline, or be replaced. A healthy ecosystem preserves enough lineage to explain how later branches inherit or reject earlier decisions. Replacement should not erase history. > **Canonical repo source:** `branch-ecology/recombination-replacement.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Repository-Map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 65d427388768bf69af76d9ac4931d06fc2c599f42047c84156ef76bbd6794b2b CONTENT_BYTES: 2636 ================================================================================================ # Repository Map The wiki is the **guided reading layer**. The main repository is the **canonical analytical layer**. ## v6.2 reading hierarchy > **Why kOA is powerful → Power Surface → Composition → Compounding → Conversion → Routing → Constitution → Evolution → Audit** The v6 repository is organized conceptually around: ```text POWER-SHOW.md → capability showcase POWER-SURFACE.md → cross-domain map POWER-ROUTING.md → where capability / authority / returns / optionality go showcase/ → composition, compounding, conversion, component maps framework/ → ontology and systems theory resources/ → resource stocks and latent possibility puissance/ → effective capability relations/ → relational power domains/ → explicit domain profiles dynamics/ → how capability and power change over time constitution/ → non-domination, firewalls, counterpowers, routing branch-ecology/ → variation, mobility, complementarity, replacement koa/ → application to kOA components assessment/ → audits and profiles cases/ → examples and stress tests schemas/ → machine-readable analytical structures sources/ → corpus, provenance, maturity, evidence research/ → disciplinary and literature roadmap Academic-Lineage/ → external research crosswalks, constraints and bibliography GLOSSARY.md → canonical terminology ``` ## v6 additions emphasized in this wiki - [Why kOA Is Immensely Powerful](Why-kOA-Is-Immensely-Powerful) - [Power Surface](Power-Surface) - [Political, Economic & Monetary Power](Political-Economic-and-Monetary-Power) - [Power Domains](Power-Domains) - [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) - [Power Conversion & Routing Map](Power-Conversion-and-Routing-Map) - [Power Routing & Sharing](Power-Routing-and-Sharing) - [Power Surface Audit](Power-Surface-Audit) - [Principles](Principles) - [Academic Lineage](Academic-Lineage) - [Academic Lineage Bibliography](Academic-Lineage-Bibliography) ## Wiki vs repo Use the **wiki** to learn and navigate. Use the **repo** for canonical wording, claim status, schemas, source mapping, and implementation-oriented evidence. The wiki intentionally merges or reframes some short repo documents so one reader-facing concept has one destination. It does not replace the source files. > **Canonical v6.2 repo sources:** `TREE.md`, `README.md`, `POWER-SURFACE.md` --- [Home](Home) · [Getting Started](Getting-Started) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Research-and-Literature.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 5d7a407a321ea613c2f6fd46ce2f399790c16c6ee0be1697594ffb16cfcf5283 CONTENT_BYTES: 4895 ================================================================================================ # Research and Literature Power Dynamics sits across political theory, sociology of power, political economy, information systems, science and technology studies, network science, cybernetics, organizational theory, social epistemology, social choice, expertise research, and software architecture. The external literature is a **constraint and comparison layer**, not a substitute for the project's own corpus and not a claim that cited scholars endorse kOA. ## Academic Lineage The v6.2 wiki now includes a structured [Academic Lineage](Academic-Lineage) that maps established academic findings and problem formulations to Power Dynamics concepts and selected kOA mechanisms. Each connection is documented using four questions: 1. **Academic finding or problem** — what the literature actually established or argued. 2. **Power Dynamics correspondence** — which concept, audit surface, or kOA mechanism is structurally related. 3. **Design implication** — what should be tested, measured, separated, or protected. 4. **Limit of correspondence** — what the citation does **not** prove. This distinction matters. The lineage documents **convergence of problems, concepts, and mechanisms**; it does not retroactively claim historical influence where none is documented. ## Main research lineages - [Power, Dependence, Domination & Conversion](Academic-Lineage-01-Power-Dependence-and-Domination) — Dahl, Bachrach & Baratz, Lukes, Emerson, Cook et al., Pfeffer & Salancik, French & Raven, Pettit, Morriss, Foucault, Crozier & Friedberg. - [Polycentric Governance & Institutions](Academic-Lineage-02-Polycentric-Governance-and-Institutions) — Ostrom, Crawford & Ostrom, rules-about-rules, federation, subsidiarity and constitutional levels. - [Modularity, Standards & Path Dependence](Academic-Lineage-03-Modularity-Standards-and-Path-Dependence) — Simon, Baldwin & Clark, Farrell & Saloner, Katz & Shapiro, Pierson; including interface power, installed-base power and ossification. - [Open Source, Exit, Fork & Peer Production](Academic-Lineage-04-Open-Source-Exit-Fork-and-Peer-Production) — Hirschman, Nyman & Lindman, O'Mahony & Ferraro, Benkler. - [Network Power & Social Capital](Academic-Lineage-05-Network-Power-and-Social-Capital) — Freeman, Bonacich, Granovetter, Burt, Coleman. - [Expertise, SmartVote & Collective Judgment](Academic-Lineage-06-Expertise-SmartVote-and-Collective-Judgment) — Chi, Ericsson & Lehmann, Goldman, Cooke, Budescu & Chen, Hong & Page, Mannes et al., Arrow, Gibbard, Satterthwaite and Tetlock. - [Metrics, Reputation & Gaming](Academic-Lineage-07-Metrics-Reputation-and-Gaming) — Campbell, Merton and related metric/reputation failure modes. - [Classification, Infrastructure & Code](Academic-Lineage-08-Classification-Infrastructure-and-Code) — Winner, Lessig, Bowker & Star, Star & Ruhleder. - [Epistemic Power, Provenance & Plurality](Academic-Lineage-09-Epistemic-Power-Provenance-and-Plurality) — Fricker, Goldman, AGM belief revision, Dung argumentation. - [Systems, Cybernetics & Adaptation](Academic-Lineage-10-Systems-Cybernetics-and-Adaptation) — Ashby, Beer, Meadows. - [Collective Action, Mobilization & Diffusion](Academic-Lineage-11-Collective-Action-Mobilization-and-Diffusion) — Olson, McCarthy & Zald, Granovetter thresholds, Rogers, Centola. - [Capabilities, Concerted Power & Legibility](Academic-Lineage-12-Capabilities-Concerted-Power-and-Legibility) — Sen, Arendt, James C. Scott. The consolidated source list is in the [Academic Lineage Bibliography](Academic-Lineage-Bibliography). ## Why this matters for Power Dynamics The literature does not merely provide citations for claims already made. It supplies **failure modes and adversarial tests**. Examples include: - dependency can survive decentralization if meaningful alternatives do not exist; - compatibility can create installed-base power and protocol lock-in; - modularity can shift sovereignty into interface control; - expertise can be domain-bounded while still creating prestige spillovers; - voting and aggregation mechanisms face manipulation and impossibility constraints; - reputation metrics can become targets and self-reinforcing prestige loops; - infrastructure and classification can govern invisibly through defaults and standards; - legibility can empower coordination while flattening local knowledge; - exit is only credible when assets, knowledge and operating capacity are portable. The strongest use of academic lineage is therefore not ceremonial citation. It is **better names for failure modes, sharper tests, and clearer limits on what an architecture can claim to have solved**. > **Canonical repo sources:** `Academic-Lineage/`, `research/disciplinary-map.md`, `research/literature-roadmap.md` --- [Home](Home) · [Academic Lineage](Academic-Lineage) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Resources-and-Stocks.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c993f7ed3618872a19a08deb9324be16387bc8918b64e03761d49379457d7dde CONTENT_BYTES: 3457 ================================================================================================ # Resources, Assets, Stocks and Reservoirs Power Dynamics begins with what is available or accumulated, but it does not call every resource “power.” Resources become politically or socially consequential only through organization, mobilization, composition, and relation. This page keeps stock, potential, capacity, and puissance distinct. ## Canonical resource model Resources are inputs, not power by definition. A stock becomes politically significant only through the capacities, conversions, dependencies, and relations it supports. ### Material, financial, and time resources Money, property, energy, equipment, housing, physical infrastructure, and time are foundational because many other capacities depend on them. Time is especially political: formal rights can be unusable when work, debt, bureaucracy, care burdens, or procedure consume the time needed to exercise them. Financial resources are unusually convertible because they can purchase labor, infrastructure, attention, expertise, legal support, mobility, or time. ### Knowledge, expertise, and memory Knowledge can be shared without consuming the original resource, which makes it strongly generative. Expertise is not identical to credentials or reputation; it includes accumulated practice, methods, understanding, and evidence. Memory includes decisions, reasons, failures, outcomes, and operational traces. When made reusable, memory lowers the cost of future action. ### Networks, reputation, and brand Relationships, trust, reputation, affiliations, and brand recognition can lower coordination cost and open pathways to attention, collaboration, funding, and institutional access. They are not automatically authority. These resources are especially prone to positive feedback and incumbency effects. ### Technical, data, and infrastructure Code, schemas, hardware, APIs, data, keys, registries, protocols, and operational knowledge can be small artifacts with large systemic effects. Their significance depends on custody, reproducibility, substitution, recovery, and whether others must pass through them. ### Identity, rights, and optionality Identity, privacy, credentials, legal rights, licenses, and preserved choices condition future action. Optionality is valuable because action has not yet been irreversibly committed. A private identity or unpublished corpus can preserve future timing and strategy. Optionality is potential until it becomes effectively usable. ## Stock, capacity, flow and return An earlier useful distinction is preserved in refined form. - **Stock** — what has accumulated. - **Capacity** — what the actor or system is organized to do. - **Puissance** — what it can effectively mobilize under current conditions. - **Flow** — the practical movement or throughput of resources, action, information, or effects. - **Return** — what comes back into the system and can be reused. The combined model is: > **Stock → Potential → Capacity → Puissance → Flow / Relation → Effect → Return → New Stock** This is especially useful for compounding analysis. A large stock can remain politically weak if it cannot be mobilized or converted; a small initial stock can compound through code, experience, methods, reputation, and network assets. > **Canonical repo source:** `resources/README.md`, `framework/06-stock-capacity-flow-return.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Semantic-Layer.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 19eb164e5a166db1f90fe85dc9c97b63ac76cd68f312b007419414efd62749ee CONTENT_BYTES: 1634 ================================================================================================ # Semantic Layer — SemantiK, SenTient and Multilingualism Semantic puissance concerns the ability to structure categories, relations, ambiguity, and meaning. In kOA this is not a cosmetic layer: meaning precedes knowledge, discoverability, credibility, and decision. Multilingual participation is part of the same capability because language can otherwise become an access boundary. ## SemantiK and SenTient SemantiK Architect concerns the architecture of meaning: concepts, categories, relations, contexts, and multilingual mappings. SenTient concerns reconciliation of ambiguous or uncertain propositions, entity relations, and semantic interpretation. These functions create semantic puissance but can also create **constitutive power** if their categories become mandatory or opaque. Semantic sovereignty therefore requires versioned ontologies, explicit uncertainty, local control where appropriate, traceable transformations, and meaningful alternatives. ## Multilingualism Multilingualism creates two distinct capacities. **Reach puissance** expands geographic and linguistic participation. **Semantic participation puissance** lets communities participate without abandoning their language, categories, and local meaning structures. Translation is therefore political. A system can claim global reach while imposing one dominant ontology through translation defaults. Traceability, uncertainty, local revision, and plural mappings are important safeguards. > **Canonical repo source:** `koa/semantik-sentient.md`, `koa/multilingualism.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/SmartVote-Discoverability.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: efeb6f086cc424b5a552eeb18f5a4541584e17a9bfe2c36d580aa2604d32de0c CONTENT_BYTES: 587 ================================================================================================ # SmartVote and Discoverability Power SmartVote demonstrates that discovery is governance. What rises is more likely to be reused, cited, learned, funded, adopted, or built. Even when final political equality is preserved, ranking criteria can shape the agenda before the final decision. The case separates baseline support, credibility signals, weighted advisory readings, and discoverability effects rather than collapsing them into one score. > **Canonical repo source:** `cases/smartvote-discoverability.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/SmartVote.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 44fec491acf0bdb2cae5352e733e9f6aa58eb46118a795d8c3daae4096b378da CONTENT_BYTES: 2809 ================================================================================================ # SmartVote SmartVote creates **comparative judgment and discoverability puissance** by preserving multiple readings of support rather than hiding evaluation inside one opaque score. A critical separation is between baseline/raw democratic readings and expertise/ethics or other advisory readings. The political baseline is not silently superseded by advisory weight. **Domain-bounded credibility informs rather than automatically governs.** Power relations arise through lens selection, defaults, criteria, discoverability, ranking, and institutional interpretation of weighted results. Those elements require explicit registries, versioning, auditability, and branch alternatives. ## Academic constraints The external-research layer documents several constraints directly relevant to SmartVote: - **Expert performance is domain- and task-bounded.** Expertise in one field should not silently become generalized epistemic authority. Work by Chi, Feltovich & Glaser and by Ericsson & Lehmann supports treating expertise as structured by domain and task. - **Nonexperts still face an expert-selection problem.** Goldman frames the problem of deciding which experts to trust when the evaluator is not already an expert in the same domain. - **Performance-sensitive aggregation can help in some settings.** Cooke, Budescu & Chen, and related work show that calibration or measured contribution can sometimes improve expert aggregation. - **Diversity can add independent problem-solving value.** Hong & Page provide an important counterweight to simply selecting the highest-scoring individuals. - **Selection itself changes the crowd.** Mannes, Soll & Larrick show that selected subsets can sometimes outperform undifferentiated aggregation, but the selection rule becomes a new governance surface. - **No voting rule escapes all structural tradeoffs.** Arrow, Gibbard and Satterthwaite establish deep limits and manipulation constraints for broad classes of social-choice mechanisms. - **Metrics become gaming surfaces when consequential.** Campbell's law and cumulative-advantage dynamics associated with Merton matter whenever EkoH, credibility, ranking or reputation affects visibility or opportunity. These constraints support the architecture's separation of **baseline political standing**, **domain-scoped expertise**, and **advisory lenses**. They do **not** validate a particular SmartVote formula, weight, threshold or deployment. See [Expertise, SmartVote & Collective Judgment](Academic-Lineage-06-Expertise-SmartVote-and-Collective-Judgment) and [Metrics, Reputation & Gaming](Academic-Lineage-07-Metrics-Reputation-and-Gaming). > **Canonical repo source:** `koa/smartvote.md` --- [Home](Home) · [Academic Lineage](Academic-Lineage) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Sources-and-Provenance.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: da796110e0b6cd9ab8f9355680310421358c73260df61ff199c9e85ba040549a CONTENT_BYTES: 3247 ================================================================================================ # Sources, Provenance and Epistemic Status Power Dynamics separates where a claim came from, how mature it is, and what kind of claim it is. The framework should never silently turn a legacy proposal into current doctrine or an analytical reconstruction into a source quotation. ## Source layer The supplied corpus is the repository's primary evidence base. Source IDs are stable references to the 28 supplied files. They identify provenance, not endorsement or current status. The repo distinguishes: - **FOUNDATIONAL / CURRENT-CORE** source material; - **CURRENT-EXPERIMENTAL** designs; - **ANALYTICAL** thesis drafts and reconstructions; - **LEGACY-PROPOSAL** material preserved for genealogy and stress testing. The source corpus contains real internal tensions. These should not be silently reconciled. ## Epistemic rules 1. Preserve source terminology when summarizing a source. 2. Label reconstructions and new concepts explicitly. 3. Do not silently convert legacy proposals into current principles. 4. Preserve disagreements among current documents. 5. Treat technical claims about current implementation as provisional unless supported by direct specifications or code. 6. Avoid treating analytical thesis drafts as canonical technical specifications. 7. Do not infer perfect measurement of competence, ethics, credibility, legitimacy, or truth from the presence of a scoring mechanism. 8. Use source IDs for provenance and technical evidence for implementation claims. ## Source status `CURRENT-CORE` and `CURRENT-EXPERIMENTAL` describe recent design direction. `LEGACY-PROPOSAL` identifies earlier proposals retained for historical and stress-test value. `ANALYTICAL-RECONSTRUCTION` identifies synthesis rather than primary architecture. Status is not truth ranking. A legacy proposal can still expose a useful mechanism, and a recent analytical document is not automatically a canonical technical specification. See [Corpus Map](Corpus-Map) for per-source classification. > **Canonical repo source:** `sources/README.md`, `sources/epistemic-rules.md`, `sources/source-status.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ## Architect-confirmed design Some current design intentions are explicitly confirmed during repository development but are not yet represented by a canonical specification in the supplied corpus. The repo labels these `USER-CONFIRMED-DESIGN` rather than silently presenting them as source-derived or implemented facts. Koali ownership decoupling is currently in this category. ## v6 maturity notes - The **Power Surface**, cross-domain conversion model, and routing model are analytical reconstructions built from the corpus and current design discussion. - **KingCoin** remains `LEGACY-PROPOSAL`: analytically useful for monetary / political / administrative stacking, but not current kOA doctrine. - **Koali ownership decoupling / plural distributions** remain architect-confirmed design direction until current technical specifications demonstrate the intended portability, policy identity, interoperability, and independent operation. - Domain profiles in this wiki are reader-facing analytical syntheses. They should not be read as implementation claims. ================================================================================================ FILE: Power-Dynamics.wiki/System-Power-Profile.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 15a0ccb16641acd38190612f01fa5cc94836458919f54ccc1e86fe84891c4846 CONTENT_BYTES: 2370 ================================================================================================ # System Power Profile A System Power Profile turns the theory into an audit surface. It identifies resource stocks, capability surfaces, domains, conversion paths, dependencies, power relations, returns, counterpowers, and changes over time. ## System profile A system profile should summarize major resource stocks, main forms of puissance, major power relations, mediators and bottlenecks, conversion pathways, return loops, concentration, stacking, dependency gradients, counterpowers, branch ecology, founder/maintainer dependencies, temporal risks, and technical-evidence confidence. This is the preferred top-level audit output. ## Flow, conversion and capture audit This audit combines the stock/flow, conversion, and stacking views. ### Stock → Capacity → Flow For each major resource, trace: `Stock → Potential → Capacity → Puissance → Flow → Relation → Return` ### Conversion map List all material conversions and intermediate steps. Example: `expertise evidence → credibility signal → ranking weight → discoverability → opportunity` Ask who controls each step, whether the conversion crosses domains, whether it is contestable, and whether an alternative branch can implement a different policy. ### Stacking Inventory every function held by the same actor or node. Ask what leverage appears only because several legitimate functions are combined. ### Capture Test whether functional control has become durable cross-domain power: `Functional Control → Cross-Domain Power` Document mandate drift, default expansion, dependency growth, recognition loops, reduced branch mobility, and rising exit costs. ## Temporal evolution Power relations change over time. ### Formation phase Who supplies scarce initial capability? ### Scaling phase Which feedback loops, network effects, standards, and dependencies emerge? ### Succession / maturity phase Can authority, knowledge, keys, brand stewardship, and maintenance transfer without collapse? Also inspect decay: credibility can expire, technical knowledge can become obsolete, and branches can lose fitness. A static snapshot is insufficient. > **Canonical repo source:** `assessment/system-profile.md`, `assessment/flow-conversion-capture-audit.md`, `assessment/temporal-evolution.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Technical-and-Infrastructural-Power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 68c742c801066e44f2ef3f4a7943f60579905f20598b1c3bffe1718d0c4cb293 CONTENT_BYTES: 1705 ================================================================================================ # Technical & Infrastructural Power > **Core question:** Who can build, host, sign, update, standardize, interoperate, withdraw, verify, or reproduce critical infrastructure? ## Generated puissance Effective capability to **build, deploy, verify, operate, repair, self-host, reproduce, federate, rollback, and substitute systems**. ## Relational power that can emerge Compatibility power, standards power, update power, signing power, access power, dependency power. ## Typical conversion paths - `technical control → defaults` - `defaults → dependency` - `infrastructure → standards` - `hosting / signing → access / continuity` ## Routing / counterpower direction - self-hosting and capsules - federation and substitution - rollback and independent verification - explicit technical boundaries and multiple operators ## kOA touchpoints - Capsules support portability, verification, local operation, and rollback - federation aims to scale capability without one mandatory operator - technical evidence remains necessary for keys, registries, update paths, and current topology ## Analytical note Infrastructure can be empowering as a capability surface and dominating as a gate. The distinction depends on dependency and counterpower. This is an analytical domain profile, not a claim that every listed mechanism is fully implemented. Use [Technical Evidence Map](Technical-Evidence-Map) when moving from architecture to current-state implementation claims. > **Canonical v6 repo sources:** `POWER-SURFACE.md`, `domains/README.md`, `README.md` --- [Power Domains](Power-Domains) · [Power Surface](Power-Surface) · [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion) ================================================================================================ FILE: Power-Dynamics.wiki/Technical-Evidence-Map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 0648675fa47471ccb58d7633a76ca1b043cf9071743ed9a2437f26b72b70dffe CONTENT_BYTES: 3098 ================================================================================================ # Technical Evidence Map This page distinguishes conceptual power analysis from the technical artifacts needed to verify where power is actually encoded: policies, defaults, roles, registries, keys, routing, schemas, and deployment controls. The 28-file corpus is strong on philosophy, architecture summaries, institutional proposals, and analytical reconstructions. A rigorous next-stage audit should add direct technical specifications for the exact loci where **capacity becomes puissance and puissance becomes relational power**. ## Highest-priority evidence to import 1. **Civilizational Coherence — power/capture chapters**: capture, lock-in, verification, contestation, substitution, exit. 2. **kOA Digital Ecosystem Layer Model / Layer 0**: separation of functions and mandate boundaries. 3. **Kristal authority registry, trust roots, reader policies, federation/versioning**: epistemic puissance, authority, branch lineage. 4. **EkoH ScoreConfiguration, ScoreHistory, visibility/access policies**: who defines credibility readings and how those readings affect opportunity. 5. **SmartVote lens registry, defaults, raw/weighted storage, version governance**: decision puissance, discoverability, advisory power. 6. **Orgo RBAC, routing, escalation, closure, override rules**: operational puissance and execution power. 7. **Konnaxion moderation, discovery, identity, ranking policies**: collective puissance, attention, agenda power. 8. **Capsule Manager signing, registry, update, rollback, deployment profiles**: deployment puissance, infrastructural dependency, choke points. 9. **Koali distribution specification**: credibility portability, alternative distributions, interoperability. 10. **Brand / trademark governance and founder-control inventory**: symbolic assets, domains, repos, release keys, registries, marks, current relational control. ## Audit rule A normative statement such as “EkoH is non-sovereign” is not sufficient technical evidence. The audit must identify the configuration, permission, key, role, registry, default, or protocol boundary that explains: 1. what resource and potential exist; 2. what becomes usable capacity; 3. what becomes effective puissance; 4. where that puissance creates relational power; 5. which counterpowers constrain that relation. ## Mobilization / mediation evidence Also inspect release permissions, publication gates, queueing, rate limits, ranking, recommendation, translation, summarization, distribution dependencies, analytics feedback, alternative channels, moderation controls, update keys, and bottlenecks. > **Canonical repo source:** `sources/technical-evidence-map.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ## Koali protocolization / ownership decoupling To verify the current design intention, the repo still needs direct technical evidence for the common kernel, evidence portability, distribution identity, policy versioning, fork procedure, discovery/registry design, signing governance, and the relationship between official branding and alternative implementations. ================================================================================================ FILE: Power-Dynamics.wiki/Three-Axis-Model.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f073a9aa992679ae128b7686e836b845ce669a0c6b1010849cae139a5ddcf8fc CONTENT_BYTES: 1974 ================================================================================================ # Three-Axis Model Every Power Dynamics analysis should locate a phenomenon on three axes. ## Axis 1 — Ontological state > **Resource → Potential → Capacity → Puissance → Power Relation → Effect → Return** This axis asks **what state the phenomenon is in**. ## Axis 2 — Dynamic Formation, mobilization, composition, conversion, return, reinvestment, compounding, concentration, stacking, capture, counterpower, diversification, evolution, decay, transfer, succession, externalities, scale, routing, sharing, and devolution. This axis asks **what is happening to it over time**. ## Axis 3 — Domain v6 makes the domain axis explicit rather than leaving it as a loose list: - political / constitutional; - economic / allocation; - monetary / credit / liquidity; - epistemic / semantic; - information / attention / media; - credibility / reputation; - network / affiliation; - administrative / operational; - technical / infrastructural; - narrative / symbolic / brand; - cognitive / AI; - mnemonic / temporal; - evolutionary / counterpower; - property / territorial. This axis asks **where the resource, capability, or relation operates**. A media organization can be stronger in attention power while a state is stronger in legal enforcement. A payment rail can be stronger in monetary access while a platform is stronger in discoverability. “More powerful” without naming the domain and mechanism is incomplete. ## Cross-domain movement The domain axis also allows explicit conversion analysis: ```text source domain → conversion mechanism → destination domain → resulting leverage ``` See [Power Domains](Power-Domains) and [Cross-Domain Power Conversion](Cross-Domain-Power-Conversion). > **Canonical v6 repo sources:** `framework/03-three-axis-model.md` in the v6 tree, `domains/README.md`, `framework/10-cross-domain-power-conversion.md`. --- [Home](Home) · [Core Ontology](Core-Ontology) · [Power Surface](Power-Surface) ================================================================================================ FILE: Power-Dynamics.wiki/Unpublished-Corpus-as-Epistemic-Reservoir.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a03b370e4c6a51b6db768f64eae738865a65c2d2b8b432bb22bbb3a88ae8dece CONTENT_BYTES: 691 ================================================================================================ # Unpublished Corpus as an Epistemic Reservoir A large unpublished corpus is best modeled as an **epistemic resource reservoir**, not stored power. It can preserve knowledge stock, narrative options, release timing, future publication paths, synthesis possibilities, and documentation value. External influence depends on later transformations: `organization → release → distribution → comprehension → credibility → reuse → adoption` The case demonstrates why reservoir size, puissance, reach, influence, and authority are distinct. > **Canonical repo source:** `cases/unpublished-corpus-reservoir.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/Why-kOA-Is-Immensely-Powerful.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c6bc40bbf7ab1da161e2a945385d7bce0931f15493887b4e5ba5ce970a1d9bbe CONTENT_BYTES: 3060 ================================================================================================ # Why kOA Is Immensely Powerful > **kOA is immensely powerful because it connects the full lifecycle of collective capability and makes the outputs of one cycle usable as inputs to the next.** ## Seven multipliers ### 1. Breadth kOA touches many domains at once: meaning, knowledge, cognition, discovery, credibility, networks, politics, economics, coordination, execution, memory, infrastructure, narrative, federation, and evolution. ### 2. Composition Those capabilities can strengthen one another. ```text structured knowledge + AI + credibility + discoverability + decision + workflow + memory = generated collective puissance ``` ### 3. Closure kOA attempts to close the loop: > **Know → Choose → Act → Remember → Know better** Information can become judgment; judgment can become action; action can become reusable memory. ### 4. Memory The system can preserve reasons, evidence, provenance, decisions, failures, outcomes, and implementation history instead of forcing every cycle to restart. ### 5. Compounding Action can leave assets behind: > **Action → Return → Asset → Reinvestment → Greater Future Puissance** ### 6. Replication Portability, self-hosting, capsules, federation, and branchability can transform one functioning capability into many independently operated capabilities. ### 7. Routing kOA does not only ask how to generate leverage. It also creates mechanisms to redirect it: - expertise → advice rather than sovereignty; - money → funding rather than more votes; - narrative → mobilization plus ethical self-binding rather than unquestionable legitimacy; - Koali → plural distributions rather than one terminal credibility owner; - infrastructure → self-hosting and substitution rather than captivity; - dominance → branch mobility rather than final authority. ## The master loop ```text Distributed resources → meaning → structured knowledge → discovery → credibility → deliberation → decision / allocation → coordination → execution → results → memory / returns → reinvestment → greater capability → federation / replication → contestation / evolution ``` This is why the system can become more capable **because it has already acted**. ## The central warning The same architecture that increases collective capability can also create: - semantic power; - agenda power; - political power; - economic and monetary leverage; - administrative power; - infrastructural dependency; - narrative capture; - founder power; - standards and registry power. Therefore: > **The Power Show and the Power Constitution are the same project viewed from opposite directions.** The first asks how much capability can be generated. The second asks whether those capabilities remain governable. ## Continue - [Power Surface](Power-Surface) - [Composition Engine](Composition-Engine) - [Compounding Engine](Compounding-Engine) - [Power Routing & Sharing](Power-Routing-and-Sharing) > **Canonical v6 repo source:** `showcase/00-why-koa-is-immensely-powerful.md` ================================================================================================ FILE: Power-Dynamics.wiki/Why-kOA-Is-Not-Just-Software.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: e8f00d490f73579cfe049cfedf23fb3fc551da5a9b0bcf817fedc8198d9b91c2 CONTENT_BYTES: 1595 ================================================================================================ # Why kOA Is Not Just Software Software is one layer of kOA's capability architecture. The broader system combines: - knowledge structures; - semantic conventions; - provenance; - credibility interpretations; - coordination rules; - decision procedures; - workflows; - institutional memory; - identity and affiliation; - deployment infrastructure; - governance; - branching and federation; - human and AI cognition. That means kOA can affect not only computation but **what a collective can know, notice, compare, decide, coordinate, preserve, and reproduce**. ## Capability infrastructure A useful definition is: > **kOA is capability infrastructure for converting knowledge into governed collective action and action back into reusable knowledge.** Its deeper loop is: ```text knowledge → orientation → choice → execution → experience → memory → better knowledge ``` ## Why infrastructure matters politically Infrastructure disappears into normality when it works. Once widely adopted, technical defaults and interfaces can become de facto political boundaries. A powerful infrastructure may therefore create: - standard-setting power; - compatibility power; - identity gatekeeping; - discoverability power; - administrative power; - mnemonic power; - dependency and lock-in. The objective is not to avoid infrastructure. It is to make infrastructural puissance **governable, portable, inspectable, and non-terminal**. > **Canonical repo source:** `showcase/09-why-this-is-not-just-software.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: Power-Dynamics.wiki/WIKI-LINK-VALIDATION.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 445b3beb3cb2fe253b7dd179878dc5bd415e41c50243f4a7350d7d6067c04492 CONTENT_BYTES: 1387 ================================================================================================ # Wiki Link Validation — v6.2 This page records the final validation of the generated GitHub Wiki package after the Academic Lineage update. ## Result - Markdown pages: **112** - Markdown lines: **6,516** - Approximate words: **36,102** - Internal wiki links checked: **614** - Broken internal targets: **0** - Internal links using forbidden `.md` suffix: **0** - Reader-facing orphan pages: **0** ## v6.2 Academic Lineage addition The wiki now contains a complete reader-facing Academic Lineage layer synchronized from the canonical repo research package: - 1 Academic Lineage overview; - 12 thematic lineage pages; - 1 consolidated bibliography; - SmartVote academic constraints integrated into the SmartVote page; - navigation links from Home, Getting Started, Research & Literature, Repository Map, sidebar, and footer. ## GitHub Wiki rule Files remain Markdown files such as `Power-Surface.md`, but rendered internal links use: ```md [Power Surface](Power-Surface) [Academic Lineage](Academic-Lineage) ``` not `Power-Surface.md` or `Academic-Lineage.md` as the link target. ## Validation status > **PASS** — all internal page targets resolve, navigation uses GitHub-Wiki-native page slugs, and all reader-facing pages are reachable. --- [Home](Home) · [Getting Started](Getting-Started) · [Academic Lineage](Academic-Lineage) · [Repository Map](Repository-Map) ================================================================================================ FILE: Power-Dynamics.wiki/Zero-Skim-Philanthropy.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 846dc14a100728ec22625dd9554c4b548e9a5dad502a38a709d64092d1b20be0 CONTENT_BYTES: 476 ================================================================================================ # Zero-Skim Philanthropy The Zero-Skim model separates economic contribution from democratic allocation. `Money → donation resources` does not automatically become `Money → more votes`. A cooperative rail can provide financial and compliance puissance while members retain allocation authority through one-member-one-vote mechanisms. > **Canonical repo source:** `cases/zero-skim-philanthropy.md` --- [Home](Home) · [Power Show](Power-Show) · [Glossary](Glossary) ================================================================================================ FILE: power_dynamics/.github/ISSUE_TEMPLATE/concept-proposal.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 03e6fe6d91967c4399635cdedf59617110ab2e63d77684bb0069af40a682ef58 CONTENT_BYTES: 434 ================================================================================================ --- name: Concept proposal about: Propose or refine a Power Dynamics concept title: "[Concept] " labels: concept assignees: '' --- ## Proposed concept ## Why it is needed ## Three-axis placement - Ontological state: - Dynamic: - Domain(s): ## Definition ## Distinctions from neighboring concepts ## Source basis - Source IDs: - Technical evidence: - External research: ## Conversion / capture implications ## Open questions ================================================================================================ FILE: power_dynamics/.github/ISSUE_TEMPLATE/power-audit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 63733dcce29792606a818da10da35e03bf9cd698283bd7793a60ff43ed1f8704 CONTENT_BYTES: 950 ================================================================================================ --- name: Power audit about: Analyze a system or subsystem using the Power Dynamics method title: "[Audit] " labels: audit assignees: '' --- ## System / subsystem ## Baseline problem ## Resources / stocks ## Potential ## Capacity ## Puissance ## Mobilization Reservoir / release / flow / mediation / bottlenecks: ## Power relations Holder → affected actor → mechanism → effect on effective possibility: ## Returns and reinvestment ## Domain surface Political / economic / monetary / epistemic / semantic / information / credibility / network / administrative / technical / narrative / cognitive / mnemonic / evolutionary: ## Conversion pathways ## Stacking / concentration / capture ## Dependency ## Power routing Capability / authority / returns / optionality destinations: ## Counterpowers Verification / contestation / substitution / exit / fork / branch mobility: ## Technical evidence ## Open questions / uncertainty ================================================================================================ FILE: power_dynamics/.github/ISSUE_TEMPLATE/power-surface-audit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 17f37e8979ea432c539b1f4c1fc9c56dc2c2d49a1ec6c1efccbf2468dc10405e CONTENT_BYTES: 1091 ================================================================================================ --- name: Power surface audit about: Map a system across political, economic, monetary, epistemic, technical, and other power domains title: "[Power Surface] " labels: audit assignees: '' --- ## System / subsystem ## Why this system is capable ## Domain inventory - Political / constitutional: - Economic / allocation: - Monetary / credit / liquidity: - Epistemic / semantic: - Information / attention / media: - Credibility / reputation: - Network / affiliation: - Administrative / operational: - Technical / infrastructural: - Narrative / symbolic / brand: - Cognitive / AI: - Mnemonic / temporal: - Evolutionary / counterpower: - Property / territorial: ## Cross-domain conversions Source domain → mechanism → destination domain → resulting leverage: ## Stacking nodes ## Power routing - Capability goes to: - Authority goes to: - Returns go to: - Optionality goes to: ## Conversion firewalls ## Counterpowers Verification / contestation / substitution / exit / self-host / fork / branch mobility: ## Terminality ## Technical evidence ## Open questions / uncertainty ================================================================================================ FILE: power_dynamics/.github/PULL_REQUEST_TEMPLATE.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ef84dafed953cfa966a1307edd6938b5699b7875f5834ffaac5a3bcfc158e2fb CONTENT_BYTES: 930 ================================================================================================ # Pull Request Checklist - [ ] I identified the ontological state(s): resource / potential / capacity / puissance / power relation / effect / return. - [ ] I identified the dynamic(s): formation / mobilization / composition / conversion / returns / capture / evolution / etc. - [ ] I identified the relevant domain(s), including political / economic / monetary distinctions where relevant. - [ ] Source-derived claims include source IDs or technical evidence. - [ ] New concepts are labeled `NEW-CONCEPT`. - [ ] I did not silently reconcile conflicting sources. - [ ] I did not collapse competence, ethics, credibility, legitimacy, or quality into false precision. - [ ] I mapped important cross-domain conversions and conversion firewalls. - [ ] I identified where capability, authority, returns, and optionality are routed. - [ ] I considered verification, contestation, substitution, exit, and branch mobility where relevant. ================================================================================================ FILE: power_dynamics/Academic-Lineage/01-power-dependence-and-domination.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ff2886c0a534321f1e21341cd6ac9de7ffaa2dc97b2f8e7748f8787725a336a0 CONTENT_BYTES: 9405 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Power, Dependence, Domination, and Conversion" source_basis: --- # Power, Dependence, Domination, and Conversion This lineage is the closest academic neighbor to the repo's distinction between **capability** and **relational power**. ## Robert A. Dahl — relational power Dahl's 1957 formulation treats power as a relation in which A can affect B's behavior. This is a useful baseline for Power Dynamics because it rejects `power = possession` and directs attention toward **relations, scope, and effects**. **Correspondence:** `Resource → Potential → Capacity → Puissance → Power Relation → Effect`. **Limit:** Dahl's behavioral formulation is narrower than Power Dynamics' interest in agenda formation, infrastructures, dependency, and latent possibility. Reference: Robert A. Dahl, “The Concept of Power,” *Behavioral Science* 2(3), 1957. https://doi.org/10.1002/bs.3830020303 ## Bachrach & Baratz; Steven Lukes — visible decisions are not the whole power surface Bachrach and Baratz's “two faces” argument expands power analysis beyond observable decisions to **nondecision and agenda control**. Lukes' later three-dimensional account adds preference-shaping and forms of domination that may not present as open conflict. **Correspondence:** the **pre-political chain** in Power Dynamics: classification, discoverability, ranking, agenda formation, defaults, and legitimacy can shape outcomes before a formal vote occurs. **Design implication:** an audit that only inspects formal decision rights will miss important upstream power. References: - Peter Bachrach and Morton S. Baratz, “Two Faces of Power,” *American Political Science Review* 56(4), 1962. https://doi.org/10.2307/1952796 - Steven Lukes, *Power: A Radical View*, first published 1974; later editions expand the argument. https://www.bloomsbury.com/ca/power-9781350544758/ ## Richard M. Emerson — power-dependence relations Emerson's 1962 theory is exceptionally close to the repo's dependency logic: power emerges from a relation in which one actor depends on resources, services, or opportunities controlled by another, and dependence is reduced when meaningful alternatives exist. **Correspondence:** - `Strong capability. Weak sovereignty.` - `credible exit`; - substitutability; - alternative providers / branches; - dependency-exit audits; - founder decentering through reproducibility. **Design implication:** for each critical capability, ask not only *who can provide it?* but also *who becomes dependent on that provider, and what alternatives remain viable?* Reference: Richard M. Emerson, “Power-Dependence Relations,” *American Sociological Review* 27(1), 1962, pp. 31–41. https://www.jstor.org/stable/2089716 ## Cook, Emerson, Gillmore & Yamagishi — network structure changes power Cook et al. experimentally studied power in exchange networks and found that simple centrality measures can fail where dependency structure predicts power more accurately. **Correspondence:** Power Dynamics should not infer `most connected = most powerful`. Network power depends on **alternatives, scarcity, exchange structure, and dependency topology**. **Design implication:** network audits should combine centrality with dependency / substitutability measures. Reference: Karen S. Cook, Richard M. Emerson, Mary R. Gillmore, and Toshio Yamagishi, “The Distribution of Power in Exchange Networks,” *American Journal of Sociology* 89(2), 1983. https://doi.org/10.1086/227866 ## Pfeffer & Salancik — resource dependence Resource Dependence Theory studies how organizations become constrained by actors controlling critical external resources. **Correspondence:** DNS, hosting, registries, funding, compute, signing keys, maintainer knowledge, payment rails, distribution, trademarks, and scarce operators can all create hidden sovereignty even when governance documents appear decentralized. **Design implication:** extend the power audit from formal authority to **critical-resource dependency**. Reference: Jeffrey Pfeffer and Gerald R. Salancik, *The External Control of Organizations: A Resource Dependence Perspective*, 1978. https://www.gsb.stanford.edu/faculty-research/books/external-control-organizations-resource-dependence-perspective ## French & Raven — distinct bases of social power French and Raven distinguished bases of social influence such as legitimate, reward, coercive, expert, and referent power. **Correspondence:** Power Dynamics' separation of domains and conversion firewalls. Expertise, money, brand, technical administration, and political standing should not be treated as interchangeable permissions. **Design implication:** identify the **source** of leverage before deciding the legitimate **scope** of that leverage. Reference: John R. P. French Jr. and Bertram Raven, “The Bases of Social Power,” in *Studies in Social Power*, 1959. https://cdn.isr.umich.edu/pubFiles/historicPublications/studiesinsocialpower_1413_.pdf ## Pierre Bourdieu — multiple forms of capital and convertibility Bourdieu distinguishes economic, cultural, and social forms of capital and emphasizes that resources can be accumulated and converted across social fields. His broader work on symbolic power is especially relevant to cases where recognition and classification become consequential without direct coercion. **Correspondence:** Power Dynamics' cross-domain conversion model: money, network position, knowledge, credentials, reputation, and symbolic standing can become leverage in other domains. **Design implication:** conversion pathways need explicit firewalls because different resources do not remain in the domains where they were originally earned. Reference: Pierre Bourdieu, “The Forms of Capital,” in John G. Richardson (ed.), *Handbook of Theory and Research for the Sociology of Education*, Greenwood, 1986, pp. 241–258. ## Philip Pettit — non-domination Republican non-domination focuses not merely on actual interference, but on exposure to **arbitrary power**: another actor may possess uncontrolled capacity to interfere even if it is not presently exercised. **Correspondence:** `non-domination-terminality`, revocability, contestability, exit, and constitutional limits on successful functions becoming terminal sovereigns. **Design implication:** “the administrator is benevolent” is not a sufficient safeguard. The architecture should reduce arbitrary dependency itself. Reference: Philip Pettit, *Republicanism: A Theory of Freedom and Government*. Oxford University Press. https://doi.org/10.1093/0198296428.001.0001 ## Peter Morriss — power as ability Morriss' philosophical analysis is especially relevant to the repo's use of **puissance**. He argues that power is usefully understood as a form of **ability / capacity**, not only as successful influence over another actor. **Correspondence:** this is a close conceptual neighbor to the repo's insistence that `capacity / puissance` must be distinguished from an exercised `power relation`. **Limit:** similar vocabulary does not imply identity between Morriss' analysis and the Power Dynamics ontology. Reference: Peter Morriss, *Power: A Philosophical Analysis*, Manchester University Press, 1987. ## Michel Foucault — power relations revealed through resistance Foucault's “The Subject and Power” emphasizes studying concrete relations of power and using forms of resistance to locate their points of application. **Correspondence:** counterpower, contestation, founder-opposition rehearsals, and adversarial audits can be used diagnostically: resistance is not merely a threat to the system; it is evidence about where power actually sits. Reference: Michel Foucault, “The Subject and Power,” *Critical Inquiry* 8(4), 1982. https://doi.org/10.1086/448181 ## Crozier & Friedberg — zones of uncertainty Crozier and Friedberg's strategic analysis of organizations emphasizes how actors gain leverage through organizational **zones of uncertainty** — areas where rules do not fully determine outcomes and where some actors control information, expertise, external relations, or operational contingencies. **Correspondence:** hidden maintainer knowledge, undocumented exceptions, manual override paths, scarce operational expertise, and discretionary queues can create power even when formal permissions are symmetrical. **Design implication:** audit uncertainty control, not only explicit roles. Reference: Michel Crozier and Erhard Friedberg, *L'acteur et le système: les contraintes de l'action collective*, Seuil, 1977. ## Power conversion as the synthesis opportunity The literature above generally studies **particular relations or domains**. Power Dynamics adds a cross-domain question: > **How does legitimate capability in one domain convert into leverage in another?** Examples include: ```text expertise → credibility → agenda leverage brand → attention → affiliation → revenue money → infrastructure → dependency technical administration → defaults → governance leverage network brokerage → opportunity allocation ``` The academic lineage strengthens the need for **Power Conversion Firewalls**. It does not by itself establish that the current firewalls are sufficient. ================================================================================================ FILE: power_dynamics/Academic-Lineage/02-polycentric-governance-and-institutions.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6ef6c06e48518a2366ec87d4930d19d625bb8a70d2347697691ee2f7a1ed178b CONTENT_BYTES: 3237 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Polycentric Governance and Institutional Grammar" source_basis: --- # Polycentric Governance and Institutional Grammar ## Elinor Ostrom — polycentric governance Ostrom's work rejects the assumption that complex collective-action problems must be solved either by a single state hierarchy or by simple privatization. Polycentric systems can contain multiple, partially autonomous centers of decision-making that interact, experiment, monitor, and learn. **Correspondence:** - federation and subsidiarity; - local autonomy; - independently governed branches; - multiple implementations sharing protocols; - `Founder-powered → Architecture-powered → Protocol-powered → Ecosystem-powered`. **Design implication:** decentralization is not merely “no center.” A viable polycentric ecology still needs rules for coordination, conflict, monitoring, nested levels, and cross-scale learning. References: - Elinor Ostrom, *Governing the Commons*, Cambridge University Press, 1990. - Elinor Ostrom, “Beyond Markets and States: Polycentric Governance of Complex Economic Systems,” Nobel Prize Lecture, 2009/2010. https://www.nobelprize.org/prizes/economic-sciences/2009/ostrom/lecture/ ## Crawford & Ostrom — a grammar of institutions Crawford and Ostrom proposed a structured grammar for analyzing institutional statements — rules, norms, and shared strategies. **Correspondence:** kOA's ambition to represent institutional structures as explicit, inspectable, versionable artifacts rather than leaving them as tacit custom or inaccessible legal prose. **Design implication:** common syntax can increase legibility without requiring identical institutions. This is a strong academic precedent for **shared grammar + local institutional variation**. Reference: Sue E. S. Crawford and Elinor Ostrom, “A Grammar of Institutions,” *American Political Science Review* 89(3), 1995. https://www.cambridge.org/core/journals/american-political-science-review/article/grammar-of-institutions/7D37CD3BC5ED2D9FD57D2EE292958F47 ## Institutional levels: operational, collective-choice, constitutional The Institutional Analysis and Development tradition distinguishes rules that govern day-to-day action from rules governing collective choice and higher-level constitutional rules that determine who can alter the system itself. **Correspondence:** Power Dynamics' authority architecture and the recurring question: > **Who can change the rules that determine who can change the rules?** **Design implication:** audits should classify authority by level, not merely by feature. A system can be democratic operationally while constitutional amendment remains concentrated. ## Polycentricity is not automatically non-dominating A federation can still contain: - a dominant reference implementation; - a registry everyone depends on; - an interface controlled by one maintainer group; - a financially dominant node; - a credibility system that becomes de facto mandatory. Therefore: > **Polycentric topology ≠ non-domination.** Power Dynamics adds dependency, conversion, and exit analysis to the polycentric frame. ================================================================================================ FILE: power_dynamics/Academic-Lineage/03-modularity-standards-and-path-dependence.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 808472e1512519aab57db4d3d5db7360806c75fc6d226ae086ef4a94b90fd9e0 CONTENT_BYTES: 4403 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Modularity, Standards, Compatibility, and Path Dependence" source_basis: --- # Modularity, Standards, Compatibility, and Path Dependence This lineage is central to the repo's attempt to combine **local freedom** with a **common compatible substrate**. ## Herbert Simon — near decomposability Simon argued that complex systems often become tractable and evolvable when organized into subsystems with relatively strong internal interaction and weaker interaction across subsystem boundaries. **Correspondence:** capsules, replaceable services, bounded modules, and the ambition to let parts of kOA evolve without requiring total-system redesign. Reference: Herbert A. Simon, “The Architecture of Complexity,” *Proceedings of the American Philosophical Society* 106(6), 1962. ## Baldwin & Clark — modularity and visible design rules Baldwin and Clark formalize modular systems in which components can change independently while obeying shared **design rules** / interfaces. **Correspondence:** > **Freeze only what is necessary for interoperability; allow everything else to mutate.** This provides a strong academic parallel to kOA's intended combination of independent implementations, shared artifact contracts, and branch evolution. Reference: Carliss Y. Baldwin and Kim B. Clark, *Design Rules, Volume 1: The Power of Modularity*, MIT Press, 2000. https://doi.org/10.7551/mitpress/2366.001.0001 ## Interface power The same modularity that creates freedom can create a new concentration point: **the interface itself**. A party that controls the shared interface can shape all modules while appearing not to control them internally. Power Dynamics should therefore treat shared interfaces as **governance surfaces**: - Who can change the interface? - Who bears migration cost? - Can an older version remain viable? - Can adapters bridge divergent versions? - Can competing standards coexist? - Who certifies compatibility? ## Farrell & Saloner — excess inertia Farrell and Saloner analyze how the benefits of standardization can trap an industry in an inferior or obsolete standard under incomplete information — **excess inertia**. **Correspondence:** a successful kOA compatibility layer could become difficult to change precisely because compatibility is valuable. Reference: Joseph Farrell and Garth Saloner, “Standardization, Compatibility, and Innovation,” *RAND Journal of Economics* 16(1), 1985, pp. 70–83. https://doi.org/10.2307/2555589 ## Katz & Shapiro — network externalities and installed-base power Network goods become more valuable as more compatible users / complements exist. Adoption itself can therefore create structural advantage. **New Power Dynamics concept proposed:** **Installed-Base Power** — the ability of an adopted protocol, implementation, or standard to constrain future choice because participants depend on continued interoperability. Reference: Michael L. Katz and Carl Shapiro, “Network Externalities, Competition, and Compatibility,” *American Economic Review* 75(3), 1985, pp. 424–440. https://www.jstor.org/stable/1814809 ## Paul Pierson — path dependence and increasing returns Pierson describes how increasing returns can make timing and sequence matter, amplify initially small differences, and make established paths difficult to reverse. **Correspondence:** early defaults, registries, naming conventions, scoring systems, reference implementations, and trust roots can become constitutionally significant long after they were introduced as convenience choices. Reference: Paul Pierson, “Increasing Returns, Path Dependence, and the Study of Politics,” *American Political Science Review* 94(2), 2000, pp. 251–267. https://doi.org/10.2307/2586011 ## Proposed constitutional invariant > **Compatibility must not imply constitutional subordination.** Related audit propositions: - `Shared interface → explicit governance surface`; - `Installed base → migration obligation`; - `Compatibility benefit → ossification risk`; - `Forkability without bridges → fragmentation risk`; - `Version pluralism + adapters → evolutionary optionality`. The academic literature establishes the failure modes. It does not prove that a particular kOA versioning or federation scheme solves them. ================================================================================================ FILE: power_dynamics/Academic-Lineage/04-open-source-exit-fork-and-peer-production.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 2eae3ea0c2b2f51c8dcec9f3aa0136ccf7e1a48c0850430c53d16ee02961f80a CONTENT_BYTES: 3257 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Exit, Voice, Forking, and Peer Production" source_basis: --- # Exit, Voice, Forking, and Peer Production ## Albert O. Hirschman — exit and voice Hirschman's classic distinction asks how members respond when an organization deteriorates: they may **exit** or use **voice** to attempt repair. **Correspondence:** Power Dynamics deliberately combines contestation and credible exit rather than treating either as sufficient alone. **Design implication:** - voice without exit can leave participants captive; - exit without voice can cause unnecessary fragmentation; - formal exit without portable assets may be practically meaningless. Reference: Albert O. Hirschman, *Exit, Voice, and Loyalty*, Harvard University Press, 1970. ## Nyman & Lindman — forking as governance Nyman and Lindman explicitly analyze code forking as a governance and sustainability mechanism across software, community, and ecosystem levels. **Correspondence:** forkability, branch mobility, incumbent replacement, and the idea that the **possibility** of a fork can constrain maintainers before a fork occurs. Reference: Linus Nyman and Juho Lindman, “Code Forking, Governance, and Sustainability in Open Source Software,” *Technology Innovation Management Review*, January 2013. https://www.timreview.ca/article/644 ## O'Mahony & Ferraro — authority can emerge without conventional ownership Their study of an open-source community shows the development of formal authority combined with democratic mechanisms and evolving conceptions of legitimate leadership. **Correspondence:** a commons still needs governance; `open` does not mean `authority-free`. The relevant question is whether authority remains bounded, contestable, and revisable. Reference: Siobhán O'Mahony and Fabrizio Ferraro, “The Emergence of Governance in an Open Source Community,” *Academy of Management Journal* 50(5), 2007. https://doi.org/10.5465/amj.2007.27169153 ## Yochai Benkler — commons-based peer production Benkler's analysis of Linux and peer production demonstrates a mode of large-scale production that is neither simply firm hierarchy nor price-mediated market organization. **Correspondence:** independent contributors can take responsibility for branches, modules, documentation, institutions, or deployments without becoming employees of a central owner. Reference: Yochai Benkler, “Coase's Penguin, or, Linux and The Nature of the Firm,” *Yale Law Journal* 112, 2002. https://yalelawjournal.org/article/coases-penguin-or-linux-and-the-nature-of-the-firm ## Founder decentering as protocolization Power Dynamics goes beyond “the founder promises not to interfere.” It seeks conversion of founder-specific capability into: - explicit schemas; - reproducible builds; - documentation; - public interfaces; - branch rights; - independent maintenance capacity; - portable data and artifacts. The academic lineage above supports the importance of these mechanisms while also warning that informal reputation, scarce expertise, release keys, brand ownership, and installed-base dominance can preserve founder power after formal control has been removed. ================================================================================================ FILE: power_dynamics/Academic-Lineage/05-network-power-and-social-capital.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6fdcfdb8851ce80d92b1536440fa467acdc4a1023f03299ca32ced819d85e259 CONTENT_BYTES: 3106 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Network Power, Brokerage, Diffusion, and Social Capital" source_basis: --- # Network Power, Brokerage, Diffusion, and Social Capital ## Linton Freeman — centrality is multidimensional Freeman clarified distinct concepts of centrality rather than treating “central” as one thing. **Correspondence:** network / affiliation power should be measured through several structural lenses rather than a single universal score. Reference: Linton C. Freeman, “Centrality in Social Networks: Conceptual Clarification,” *Social Networks* 1(3), 1978–79. https://doi.org/10.1016/0378-8733(78)90021-7 ## Phillip Bonacich — centrality is not automatically power Bonacich explicitly addresses cases in which network centrality and power diverge. **Correspondence:** Power Dynamics should resist `many connections = sovereignty`. Dependency structure and the positions of one's neighbors matter. Reference: Phillip Bonacich, “Power and Centrality: A Family of Measures,” *American Journal of Sociology* 92(5), 1987. https://doi.org/10.1086/228631 ## Mark Granovetter — weak ties and cross-cluster diffusion Weak ties can connect otherwise separated social clusters and play an outsized role in information diffusion, mobility, and community organization. **Correspondence:** mobilization capacity is not only a function of audience size or strong affiliation. **Bridging ties** can matter disproportionately for spreading initiatives across communities. Reference: Mark S. Granovetter, “The Strength of Weak Ties,” *American Journal of Sociology* 78(6), 1973. https://doi.org/10.1086/225469 ## Ronald Burt — structural holes and brokerage Burt's structural-hole theory treats gaps between otherwise disconnected actors as opportunities for brokerage, information access, and strategic advantage. **Correspondence:** identify actors or services whose brokerage position becomes a hidden allocation or gatekeeping surface. Reference: Ronald S. Burt, *Structural Holes: The Social Structure of Competition*, Harvard University Press, 1992. ## James Coleman — social capital as a resource for action Coleman describes obligations, expectations, information channels, and norms as forms of social capital that enable action. **Correspondence:** Power Dynamics' broad resource → capacity model can explicitly recognize network relations and trust structures as **resources that alter effective possibility**. Reference: James S. Coleman, “Social Capital in the Creation of Human Capital,” *American Journal of Sociology* 94, 1988. https://doi.org/10.1086/228943 ## Audit consequence A network power audit should inspect at least: - centrality; - dependency / substitutability; - brokerage; - bridge positions; - control of discovery / introductions; - access to high-trust clusters; - concentration of communication channels; - ability to route opportunities to others. Network maps show topology. They do **not** by themselves show legitimacy, authority, or domination. ================================================================================================ FILE: power_dynamics/Academic-Lineage/06-expertise-smartvote-and-collective-judgment.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 08675a176587e3ffa36e12360cbde82cd2a851002e0663ef7c91f8510eb6d460 CONTENT_BYTES: 6269 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Expertise, SmartVote, and Collective Judgment" source_basis: --- # Expertise, SmartVote, and Collective Judgment This is the most direct academic lineage for the SmartVote principle: > **Expertise should be bounded by domain and used as an advisory reading rather than silently converted into universal political sovereignty.** ## Chi, Feltovich & Glaser — experts structure problems differently within a domain Their classic physics study found systematic differences between expert and novice representations: experts tended to organize problems around deeper domain principles rather than surface features. **Correspondence:** expert standing should be attached to a **domain / problem class**, not treated as a universal personal property. Reference: Michelene T. H. Chi, Paul J. Feltovich, and Robert Glaser, “Categorization and Representation of Physics Problems by Experts and Novices,” *Cognitive Science* 5(2), 1981. https://doi.org/10.1207/s15516709cog0502_2 ## Ericsson & Lehmann — expert performance is adapted to domain-specific constraints Their broad review emphasizes domain-specific cognitive, perceptual-motor, and physiological adaptations behind expert performance. **Correspondence:** a universal “expert score” would collapse heterogeneous competence into an invalid abstraction. EkoH / SmartVote credibility should be scoped to demonstrable domains and tasks. Reference: K. Anders Ericsson and Andreas C. Lehmann, “Expert and Exceptional Performance: Evidence of Maximal Adaptation to Task Constraints,” *Annual Review of Psychology* 47, 1996. https://doi.org/10.1146/annurev.psych.47.1.273 ## Alvin Goldman — the layperson's expert-selection problem Goldman analyzes how nonexperts can rationally decide which experts to trust when they cannot directly evaluate the technical subject matter. **Correspondence:** SmartVote should not merely expose an `expert` badge. It should make evidence of expertise, track record, relevant credentials / contribution, disagreement, and source relations legible. Reference: Alvin I. Goldman, “Experts: Which Ones Should You Trust?”, *Philosophy and Phenomenological Research* 63(1), 2001. https://doi.org/10.1111/j.1933-1592.2001.tb00093.x ## Roger Cooke — calibrated expert judgment Cooke develops methods for eliciting, evaluating, and weighting expert judgments, including performance-based calibration rather than reliance on status alone. **Correspondence:** `expertise → weighted advisory reading` can be grounded in observable performance and calibration rather than title-based authority. Reference: Roger M. Cooke, *Experts in Uncertainty: Opinion and Subjective Probability in Science*, Oxford University Press, 1991. https://doi.org/10.1093/oso/9780195064650.001.0001 ## Budescu & Chen — identify contributors who improve the crowd Budescu and Chen show that aggregation can be improved by identifying judges whose forecasts consistently make positive contributions relative to the group. **Correspondence:** reputation may be **performance-sensitive** and task-sensitive rather than merely social prestige. Reference: David V. Budescu and Eva Chen, “Identifying Expertise to Extract the Wisdom of Crowds,” *Management Science* 61(2), 2015. https://doi.org/10.1287/mnsc.2014.1909 ## Mannes, Soll & Larrick — select crowds Their work shows that in some estimation settings, averaging judgments from a carefully selected small group can be robust and accurate. **Correspondence:** Power Dynamics should allow multiple aggregation lenses rather than assuming either `all votes always equal epistemically` or `single best expert decides`. Reference: Albert E. Mannes, Jack B. Soll, and Richard P. Larrick, “The Wisdom of Select Crowds,” *Journal of Personality and Social Psychology* 107(2), 2014. https://doi.org/10.1037/a0036677 ## Hong & Page — diversity can outperform selection of individually strongest solvers Under their model's conditions, a diverse group of problem solvers can outperform a group selected only for individual ability. **Correspondence:** SmartVote should not turn expertise weighting into an anti-diversity filter. Diversity of representations and heuristics can itself be an epistemic resource. Reference: Lu Hong and Scott E. Page, “Groups of Diverse Problem Solvers Can Outperform Groups of High-Ability Problem Solvers,” *PNAS* 101(46), 2004. https://doi.org/10.1073/pnas.0403723101 ## Social choice: Arrow, Gibbard, and Satterthwaite Social choice theory supplies an important warning: there is no universal voting mechanism that simultaneously satisfies every attractive property under unrestricted conditions, and broad classes of voting systems are vulnerable to strategic manipulation. **Correspondence:** SmartVote should present itself as a **plural, inspectable set of readings and decision aids**, not as a mathematically perfect replacement for politics. References: - Kenneth J. Arrow, *Social Choice and Individual Values*, 1951/1963. - Allan Gibbard, “Manipulation of Voting Schemes: A General Result,” *Econometrica* 41(4), 1973. https://doi.org/10.2307/1914083 - Mark A. Satterthwaite, “Strategy-proofness and Arrow's Conditions,” *Journal of Economic Theory* 10(2), 1975. https://doi.org/10.1016/0022-0531(75)90050-2 ## SmartVote design implications The literature supports several strong constraints: 1. **Domain-bounded expertise** — no universal expert authority. 2. **Performance evidence** — title or prestige is not enough. 3. **Plural aggregation** — different lenses can answer different questions. 4. **Diversity preservation** — selecting only high-status experts can destroy useful heterogeneity. 5. **Political firewall** — epistemic weighting does not automatically purchase political sovereignty. 6. **Manipulation awareness** — every ranking / voting mechanism exposes gaming surfaces. 7. **Baseline visibility** — raw democratic readings should remain visible when advisory lenses are added. None of these references validates a particular SmartVote weighting formula. They provide **design constraints and testable failure modes**. ================================================================================================ FILE: power_dynamics/Academic-Lineage/07-metrics-reputation-and-gaming.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 46592989636864b14db948eed85bdedea51b830f5a830386e1a5a7c121c28d12 CONTENT_BYTES: 2973 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Metrics, Reputation, Prestige, and Gaming" source_basis: --- # Metrics, Reputation, Prestige, and Gaming Any system that makes expertise, contribution, trust, or credibility legible creates a new power surface. ## Donald Campbell — indicators become corruption targets Campbell's work on social indicators is associated with a recurring warning: when quantitative indicators become important targets for decision-making, actors have incentives to corrupt or optimize the indicator rather than the underlying goal. **Correspondence:** EkoH, reputation, contribution metrics, moderation metrics, and SmartVote-derived standings must be treated as **adversarially optimizable surfaces**. Reference: Donald T. Campbell, “Assessing the Impact of Planned Social Change,” *Evaluation and Program Planning* 2(1), 1979. https://doi.org/10.1016/0149-7189(79)90048-X ## Robert K. Merton — the Matthew effect Merton analyzed cumulative advantage in science: recognition and resources can disproportionately accrue to already prominent actors. **Correspondence:** credibility systems can produce a positive feedback loop: ```text initial recognition → more visibility → more opportunities → more visible contribution → more recognition ``` **Design implication:** distinguish demonstrated contribution from **recognition compounding**, and monitor whether discoverability causes prestige to become self-validating. Reference: Robert K. Merton, “The Matthew Effect in Science,” *Science* 159(3810), 1968. https://doi.org/10.1126/science.159.3810.56 ## Prestige, reputation, and authority are not identical Power Dynamics should retain separate concepts for: - observed performance; - domain expertise; - social prestige; - contribution history; - institutional credential; - political standing; - moral / ethical trust; - brand affiliation. A reputation system becomes dangerous when one of these silently converts into all the others. ## Proposed audit questions For every score or ranking: 1. What exactly is being measured? 2. Is the construct domain-specific? 3. Can participants optimize the metric without improving the underlying objective? 4. Does early visibility create cumulative advantage? 5. Are negative evidence and uncertainty preserved? 6. Is the score portable, contestable, and versioned? 7. Can users inspect the weighting rule? 8. Does the score grant authority outside the domain it measures? 9. Can alternative scoring systems coexist? 10. What happens to newcomers with no historical data? ## Proposed invariant > **Legibility should increase informed choice without turning measurement into universal sovereignty.** The academic literature makes the gaming and cumulative-advantage risks difficult to dismiss. It does not determine the correct scoring architecture; that remains an engineering and governance question. ================================================================================================ FILE: power_dynamics/Academic-Lineage/08-classification-infrastructure-and-code.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: dfc55292723cc35868017533eb3f6aeb698058a1b02b643f95c1efb23d2687be CONTENT_BYTES: 3034 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Classification, Infrastructure, Code, and Hidden Governance" source_basis: --- # Classification, Infrastructure, Code, and Hidden Governance This lineage supports one of Power Dynamics' most important claims: > **Power can be embedded in technical and semantic architecture before any formal political decision occurs.** ## Langdon Winner — artifacts can embody politics Winner argues that technical artifacts and systems can embody or require particular distributions of power and authority. **Correspondence:** technical design choices belong on the Power Surface; they are not merely neutral implementation details. Reference: Langdon Winner, “Do Artifacts Have Politics?”, *Daedalus* 109(1), 1980. https://www.jstor.org/stable/20024652 ## Lawrence Lessig — code regulates Lessig's work on cyberspace argues that software and hardware architecture regulate behavior alongside law, norms, and markets. **Correspondence:** permissions, defaults, data models, ranking, reader policies, trust roots, update mechanisms, and interoperability rules are governance mechanisms. Reference: Lawrence Lessig, *Code and Other Laws of Cyberspace*, 1999; *Code: Version 2.0*, 2006. https://hls.harvard.edu/bibliography/code-and-other-laws-of-cyberspace-version-2-0/ ## Bowker & Star — classification has consequences Bowker and Star show that classification systems and standards organize worlds, distribute visibility, and can encode consequential social assumptions. **Correspondence:** SemantiK, Kristal schemas, ontologies, category systems, admissibility criteria, and metadata are forms of **semantic / classificatory power**. Reference: Geoffrey C. Bowker and Susan Leigh Star, *Sorting Things Out: Classification and Its Consequences*, MIT Press, 1999. https://doi.org/10.7551/mitpress/6352.001.0001 ## Star & Ruhleder — infrastructure is relational and becomes visible on breakdown Their infrastructure studies emphasize that infrastructure is not merely equipment; it is embedded in practices, communities, standards, learned conventions, and installed bases. **Correspondence:** kOA's technical layer should be audited in relation to actual users and institutions, not only against internal architectural elegance. Reference: Susan Leigh Star and Karen Ruhleder, “Steps Toward an Ecology of Infrastructure,” *Information Systems Research* 7(1), 1996. https://doi.org/10.1287/isre.7.1.111 ## Hidden-sovereignty audit A technically decentralized system may still concentrate power through: - default schemas; - canonical registries; - ranking algorithms; - update keys; - API compatibility requirements; - moderation queues; - model prompts / AI system instructions; - search and discovery; - identity providers; - documentation that defines the “normal” implementation. This literature strongly supports treating those mechanisms as constitutional surfaces rather than implementation trivia. ================================================================================================ FILE: power_dynamics/Academic-Lineage/09-epistemic-power-provenance-and-plurality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 2a4abe1fc51c046003f341d282475d38d45bf48632798cdf7bdc3e6fda74614b CONTENT_BYTES: 3607 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Epistemic Power, Provenance, Disagreement, and Plurality" source_basis: --- # Epistemic Power, Provenance, Disagreement, and Plurality Kristal and Konnaxion operate in a space that social epistemology, argumentation theory, and belief-revision research have studied from different angles. ## Miranda Fricker — epistemic injustice Fricker distinguishes forms of injustice in which a speaker is given an unfair credibility deficit or lacks shared interpretive resources for making an experience intelligible. **Correspondence:** credibility systems, semantic categories, moderation, and expert-weighted discovery can either reduce or amplify epistemic exclusion. **Design implication:** a credibility system should inspect not only false positive authority, but also **systematic credibility deficits** and missing conceptual categories. Reference: Miranda Fricker, *Epistemic Injustice: Power and the Ethics of Knowing*, Oxford University Press, 2007. https://doi.org/10.1093/acprof:oso/9780198237907.001.0001 ## Alvin Goldman — social epistemology and expert trust Goldman's work treats knowledge practices as social systems that can be evaluated partly by how well they support truth-seeking and rational trust. **Correspondence:** provenance, source comparison, expert-selection evidence, and visible disagreement should support users' own epistemic judgment rather than simply replace it with authority. Reference: Alvin I. Goldman, “Experts: Which Ones Should You Trust?”, 2001. https://doi.org/10.1111/j.1933-1592.2001.tb00093.x ## AGM belief revision — changing a knowledge state should be explicit Alchourrón, Gärdenfors, and Makinson formalized belief revision as a problem of changing a knowledge / belief set while preserving rational structure. **Correspondence:** versioned Kristals, explicit revisions, lineage, conflict, supersession, and rollback are related to the general problem that **new information should alter a knowledge state without erasing how the change occurred**. Reference: Carlos E. Alchourrón, Peter Gärdenfors, and David Makinson, “On the Logic of Theory Change: Partial Meet Contraction and Revision Functions,” *Journal of Symbolic Logic* 50(2), 1985. https://doi.org/10.2307/2274239 ## Dung — argumentation frameworks and conflicting claims Dung's abstract argumentation framework models arguments and attack relations without requiring all participants to share a single consistent knowledge base. **Correspondence:** competing claims / Kristals can remain explicitly related through support, challenge, provenance, and evaluation rather than being collapsed into false consensus. Reference: Phan Minh Dung, “On the Acceptability of Arguments and Its Fundamental Role in Nonmonotonic Reasoning, Logic Programming and n-Person Games,” *Artificial Intelligence* 77(2), 1995. https://doi.org/10.1016/0004-3702(94)00041-X ## Epistemic design implications 1. **Cryptographic integrity ≠ truth.** 2. **Provenance ≠ authority.** 3. **Source multiplicity ≠ source independence.** 4. **Forkability ≠ epistemic equivalence.** 5. **Consensus ≠ absence of dissent.** 6. **Credibility ≠ infallibility.** 7. **Revision should preserve lineage.** 8. **Competing worldviews should remain comparable where possible.** The academic lineage reinforces the repo's adversarial epistemic tests. It also supplies a warning: making epistemic structure explicit does not eliminate disagreement; it makes disagreement more inspectable. ================================================================================================ FILE: power_dynamics/Academic-Lineage/10-systems-cybernetics-and-adaptation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b48b810452f61eee92085628d8df085266d117b930ae9ca4ec3eb72d6bb62dce CONTENT_BYTES: 2607 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Systems, Cybernetics, Feedback, and Adaptation" source_basis: --- # Systems, Cybernetics, Feedback, and Adaptation Power Dynamics is not only a theory of authority. It is also a theory of **capability formation, feedback, memory, and evolutionary adaptation**. ## W. Ross Ashby — requisite variety Ashby's cybernetics is associated with the principle that effective regulation requires sufficient variety in the regulator to respond to the variety of disturbances in the system. **Correspondence:** centralized simplification can fail when local contexts vary more than the center can represent. Federation, local autonomy, plural branches, and specialized modules can preserve response variety. Reference: W. Ross Ashby, *An Introduction to Cybernetics*, 1956. ## Stafford Beer — viable systems and recursive autonomy Beer's Viable System Model studies how viable organizations combine operational autonomy with coordination, control, intelligence, and identity across recursive levels. **Correspondence:** kOA's local / federated architecture and the attempt to avoid both total centralization and incoherent fragmentation. Reference: Stafford Beer, *Brain of the Firm*, 1972; later editions. ## Donella Meadows — leverage points Meadows' systems work distinguishes interventions at different depths, from parameters to information flows, rules, system goals, and paradigms. **Correspondence:** Power Dynamics' cross-domain approach asks whether changing a UI parameter, a ranking rule, a constitutional permission, or an underlying paradigm produces radically different leverage. Reference: Donella H. Meadows, “Leverage Points: Places to Intervene in a System,” Sustainability Institute, 1999. ## Feedback and the kOA capability loop The canonical kOA cycle: > **Know → Choose → Act → Remember → Know better** can be interpreted as a feedback architecture: ```text state / evidence → interpretation → decision → action → result → memory → revised state / evidence ``` The key Power Dynamics addition is that **feedback channels themselves are power surfaces**. Whoever controls what gets measured, remembered, ranked, or ignored can influence future adaptation. ## Systems caution A system can be technically adaptive while politically dominating. Cybernetic viability is not identical to legitimacy, justice, or non-domination. Therefore the systems lineage should be paired with the constitutional lineage rather than used as a substitute for it. ================================================================================================ FILE: power_dynamics/Academic-Lineage/11-collective-action-mobilization-and-diffusion.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c70e65da377d522ccb3bc647133f20ba5f4b24e7d99eb05979cff155d1c313f6 CONTENT_BYTES: 4225 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Collective Action, Mobilization, Diffusion, and Thresholds" source_basis: --- # Collective Action, Mobilization, Diffusion, and Thresholds Power Dynamics includes a mobilization layer: resources do not become social power merely because they exist. They must be **released, routed, coordinated, and adopted**. ## Mancur Olson — collective action is not automatic Olson's classic work shows why groups with shared interests may still fail to organize or contribute to collective goods because individual incentives and group outcomes can diverge. **Correspondence:** kOA cannot assume that a good common objective automatically produces participation. Roles, incentives, visibility of contribution, modular tasks, local ownership, and low-friction entry all affect whether latent capacity becomes mobilized capacity. Reference: Mancur Olson, *The Logic of Collective Action*, Harvard University Press, 1965. https://doi.org/10.4159/9780674041660 ## McCarthy & Zald — resource mobilization Resource Mobilization Theory shifts attention from grievances alone toward the resources, organizations, media relations, alliances, and structural conditions that make sustained collective action possible. **Correspondence:** Power Dynamics' `Reservoir → Release → Flow → Mediation` model and the distinction between possessing resources and actually mobilizing them. Reference: John D. McCarthy and Mayer N. Zald, “Resource Mobilization and Social Movements: A Partial Theory,” *American Journal of Sociology* 82(6), 1977. https://doi.org/10.1086/226464 ## Granovetter — threshold models of collective behavior Granovetter models individuals as having different participation thresholds: some act early, while others act only after enough others have acted first. Small differences in the distribution of thresholds can produce very different collective outcomes. **Correspondence:** a network can contain substantial **latent commitment** that becomes visible only after credibility, adoption, or social proof crosses thresholds. This directly supports analysis of: - delayed activation of previously contacted collaborators; - tipping dynamics; - adoption cascades; - why early visible participants can disproportionately affect later mobilization; - why aggregate inactivity does not prove absence of latent support. Reference: Mark Granovetter, “Threshold Models of Collective Behavior,” *American Journal of Sociology* 83(6), 1978. https://doi.org/10.1086/226707 ## Everett Rogers — diffusion of innovations Rogers' diffusion framework studies how innovations spread through communication channels over time and how uncertainty, social networks, and adopter categories affect uptake. **Correspondence:** cultural / narrative corridors, demonstrations, reference implementations, peer testimony, and local adoption can be treated as parts of a diffusion system rather than generic “marketing.” Reference: Everett M. Rogers, *Diffusion of Innovations*, 5th ed., Free Press, 2003. ## Damon Centola — complex contagion Centola's experimental work shows that behavioral adoption can differ from simple information diffusion: some behaviors benefit from **reinforcement through multiple social contacts** rather than one weak exposure. **Correspondence:** mobilization for costly participation may require redundant trust paths and local reinforcement, even when information itself can spread through weak ties. Reference: Damon Centola, “The Spread of Behavior in an Online Social Network Experiment,” *Science* 329(5996), 2010. https://doi.org/10.1126/science.1185231 ## Power Dynamics consequence Mobilization should be modeled as a conversion problem: ```text latent resource / willingness → visibility → credibility / social proof → threshold crossing → contribution → coordination → result → public evidence → lower thresholds for later participants ``` This creates a possible compounding loop, but also a capture risk: whoever controls visibility, endorsement, discovery, or narrative framing may control which latent resources ever become mobilized. ================================================================================================ FILE: power_dynamics/Academic-Lineage/12-capabilities-concerted-power-and-legibility.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 05d70ea188ee47db5354d671c30ee931e162a8d28c96f65c8ffebd77292f40d4 CONTENT_BYTES: 3313 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Capabilities, Concerted Power, and the Risks of Legibility" source_basis: --- # Capabilities, Concerted Power, and the Risks of Legibility Three academic traditions sharpen the normative stakes of Power Dynamics: **capabilities**, **collective agency**, and the dangers of making society legible through simplified administrative categories. ## Amartya Sen — capability and substantive freedom Sen's capability approach shifts attention from resources alone toward what people are **actually able to do and be**. Resources matter partly through the substantive freedoms they make possible. **Correspondence:** Power Dynamics' concept of **effective possibility** is structurally close to a capability-oriented question: possession is not enough; what matters is the real action space available under actual constraints. **Design implication:** a system should not measure empowerment only through nominal access. Ask whether participants can actually use, contest, exit, reproduce, and benefit from the capability. Reference: Amartya Sen, *Development as Freedom*, 1999/2000. https://www.penguinrandomhouse.com/books/163962/development-as-freedom-by-amartya-sen/ ## Hannah Arendt — power as acting in concert Arendt distinguishes power from simple coercion or violence and ties political power to a group's capacity to **act in concert**. **Correspondence:** this is a useful academic neighbor to **generated collective puissance**: composition can create a capacity at group scale that no isolated participant possesses. **Limit:** Arendt's political concept of power is normatively and philosophically distinct from the broader Power Dynamics ontology. Reference: Hannah Arendt, *On Violence*, 1970. ## James C. Scott — legibility can become domination Scott's *Seeing Like a State* studies failures of high-modernist schemes that simplified complex local realities into administratively legible categories and then governed through those abstractions. **Correspondence:** kOA deliberately increases legibility — schemas, classifications, provenance, metrics, workflows, registries, institutional grammar. That is a capability **and a danger**. **Design implication:** semantic clarity must not erase local knowledge or turn the reference model into compulsory reality. The anti-capture answer is not “avoid legibility,” but combine legibility with: - local override / interpretation; - plural schemas where necessary; - provenance and uncertainty; - reversible mappings; - branch alternatives; - explicit scope; - user-visible disagreement. Reference: James C. Scott, *Seeing Like a State: How Certain Schemes to Improve the Human Condition Have Failed*, Yale University Press, 1998/1999. https://yalebooks.yale.edu/book/9780300078152/seeing-like-a-state/ ## Synthesis These three traditions create a useful triangle: ```text Sen: What can people actually do? Arendt: What can people do together? Scott: What happens when institutions simplify people in order to coordinate them? ``` Power Dynamics can use that triangle as a normative test: > **Increase effective individual and collective capability without making the legibility infrastructure a new sovereign.** ================================================================================================ FILE: power_dynamics/Academic-Lineage/BIBLIOGRAPHY.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 3ccd73b299cdefeed569d9c7f56a129356ace2754367d44b216d7b69628c6f90 CONTENT_BYTES: 11346 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Academic Lineage Bibliography" source_basis: --- # Academic Lineage Bibliography This bibliography is intentionally **selective rather than exhaustive**. Entries are grouped by their strongest use in Power Dynamics. A work may belong to several groups. ## Power, dependency, domination - Bachrach, Peter, and Morton S. Baratz. “Two Faces of Power.” *American Political Science Review* 56(4), 1962. https://doi.org/10.2307/1952796 - Bourdieu, Pierre. “The Forms of Capital.” In John G. Richardson (ed.), *Handbook of Theory and Research for the Sociology of Education*, Greenwood, 1986: 241–258. - Dahl, Robert A. “The Concept of Power.” *Behavioral Science* 2(3), 1957: 201–215. https://doi.org/10.1002/bs.3830020303 - Emerson, Richard M. “Power-Dependence Relations.” *American Sociological Review* 27(1), 1962: 31–41. https://www.jstor.org/stable/2089716 - Cook, Karen S., Richard M. Emerson, Mary R. Gillmore, and Toshio Yamagishi. “The Distribution of Power in Exchange Networks: Theory and Experimental Results.” *American Journal of Sociology* 89(2), 1983: 275–305. https://doi.org/10.1086/227866 - French, John R. P. Jr., and Bertram Raven. “The Bases of Social Power.” In *Studies in Social Power*, 1959. https://cdn.isr.umich.edu/pubFiles/historicPublications/studiesinsocialpower_1413_.pdf - Lukes, Steven. *Power: A Radical View*. First published 1974; later editions. https://www.bloomsbury.com/ca/power-9781350544758/ - Pettit, Philip. *Republicanism: A Theory of Freedom and Government*. Oxford University Press. https://doi.org/10.1093/0198296428.001.0001 - Pfeffer, Jeffrey, and Gerald R. Salancik. *The External Control of Organizations: A Resource Dependence Perspective*. 1978. https://www.gsb.stanford.edu/faculty-research/books/external-control-organizations-resource-dependence-perspective - Morriss, Peter. *Power: A Philosophical Analysis*. Manchester University Press, 1987. - Foucault, Michel. “The Subject and Power.” *Critical Inquiry* 8(4), 1982: 777–795. https://doi.org/10.1086/448181 - Crozier, Michel, and Erhard Friedberg. *L'acteur et le système: les contraintes de l'action collective*. Seuil, 1977. ## Institutions, polycentric governance, commons - Crawford, Sue E. S., and Elinor Ostrom. “A Grammar of Institutions.” *American Political Science Review* 89(3), 1995. https://www.cambridge.org/core/journals/american-political-science-review/article/grammar-of-institutions/7D37CD3BC5ED2D9FD57D2EE292958F47 - Ostrom, Elinor. *Governing the Commons*. Cambridge University Press, 1990. - Ostrom, Elinor. “Beyond Markets and States: Polycentric Governance of Complex Economic Systems.” Nobel Prize Lecture, 2009/2010. https://www.nobelprize.org/prizes/economic-sciences/2009/ostrom/lecture/ ## Modularity, standards, path dependence - Baldwin, Carliss Y., and Kim B. Clark. *Design Rules, Volume 1: The Power of Modularity*. MIT Press, 2000. https://doi.org/10.7551/mitpress/2366.001.0001 - Farrell, Joseph, and Garth Saloner. “Standardization, Compatibility, and Innovation.” *RAND Journal of Economics* 16(1), 1985: 70–83. https://doi.org/10.2307/2555589 - Katz, Michael L., and Carl Shapiro. “Network Externalities, Competition, and Compatibility.” *American Economic Review* 75(3), 1985: 424–440. https://www.jstor.org/stable/1814809 - Pierson, Paul. “Increasing Returns, Path Dependence, and the Study of Politics.” *American Political Science Review* 94(2), 2000: 251–267. https://doi.org/10.2307/2586011 - Simon, Herbert A. “The Architecture of Complexity.” *Proceedings of the American Philosophical Society* 106(6), 1962: 467–482. ## Exit, forking, open source, peer production - Benkler, Yochai. “Coase's Penguin, or, Linux and The Nature of the Firm.” *Yale Law Journal* 112, 2002. https://yalelawjournal.org/article/coases-penguin-or-linux-and-the-nature-of-the-firm - Hirschman, Albert O. *Exit, Voice, and Loyalty*. Harvard University Press, 1970. - Nyman, Linus, and Juho Lindman. “Code Forking, Governance, and Sustainability in Open Source Software.” *Technology Innovation Management Review*, January 2013. https://www.timreview.ca/article/644 - O'Mahony, Siobhán, and Fabrizio Ferraro. “The Emergence of Governance in an Open Source Community.” *Academy of Management Journal* 50(5), 2007. https://doi.org/10.5465/amj.2007.27169153 ## Network power and social capital - Bonacich, Phillip. “Power and Centrality: A Family of Measures.” *American Journal of Sociology* 92(5), 1987. https://doi.org/10.1086/228631 - Burt, Ronald S. *Structural Holes: The Social Structure of Competition*. Harvard University Press, 1992. - Coleman, James S. “Social Capital in the Creation of Human Capital.” *American Journal of Sociology* 94, 1988. https://doi.org/10.1086/228943 - Freeman, Linton C. “Centrality in Social Networks: Conceptual Clarification.” *Social Networks* 1(3), 1978–79. https://doi.org/10.1016/0378-8733(78)90021-7 - Granovetter, Mark S. “The Strength of Weak Ties.” *American Journal of Sociology* 78(6), 1973. https://doi.org/10.1086/225469 ## Expertise and collective judgment - Budescu, David V., and Eva Chen. “Identifying Expertise to Extract the Wisdom of Crowds.” *Management Science* 61(2), 2015. https://doi.org/10.1287/mnsc.2014.1909 - Chi, Michelene T. H., Paul J. Feltovich, and Robert Glaser. “Categorization and Representation of Physics Problems by Experts and Novices.” *Cognitive Science* 5(2), 1981. https://doi.org/10.1207/s15516709cog0502_2 - Cooke, Roger M. *Experts in Uncertainty: Opinion and Subjective Probability in Science*. Oxford University Press, 1991. https://doi.org/10.1093/oso/9780195064650.001.0001 - Ericsson, K. Anders, and Andreas C. Lehmann. “Expert and Exceptional Performance: Evidence of Maximal Adaptation to Task Constraints.” *Annual Review of Psychology* 47, 1996. https://doi.org/10.1146/annurev.psych.47.1.273 - Goldman, Alvin I. “Experts: Which Ones Should You Trust?” *Philosophy and Phenomenological Research* 63(1), 2001. https://doi.org/10.1111/j.1933-1592.2001.tb00093.x - Hong, Lu, and Scott E. Page. “Groups of Diverse Problem Solvers Can Outperform Groups of High-Ability Problem Solvers.” *PNAS* 101(46), 2004. https://doi.org/10.1073/pnas.0403723101 - Mannes, Albert E., Jack B. Soll, and Richard P. Larrick. “The Wisdom of Select Crowds.” *Journal of Personality and Social Psychology* 107(2), 2014. https://doi.org/10.1037/a0036677 - Tetlock, Philip E. *Expert Political Judgment: How Good Is It? How Can We Know?* Princeton University Press, 2005. ## Social choice and strategic manipulation - Arrow, Kenneth J. *Social Choice and Individual Values*. 1951; 2nd ed. 1963. - Gibbard, Allan. “Manipulation of Voting Schemes: A General Result.” *Econometrica* 41(4), 1973: 587–601. https://doi.org/10.2307/1914083 - Satterthwaite, Mark Allen. “Strategy-proofness and Arrow's Conditions: Existence and Correspondence Theorems for Voting Procedures and Social Welfare Functions.” *Journal of Economic Theory* 10(2), 1975: 187–217. https://doi.org/10.1016/0022-0531(75)90050-2 ## Metrics, prestige, cumulative advantage - Campbell, Donald T. “Assessing the Impact of Planned Social Change.” *Evaluation and Program Planning* 2(1), 1979: 67–90. https://doi.org/10.1016/0149-7189(79)90048-X - Merton, Robert K. “The Matthew Effect in Science.” *Science* 159(3810), 1968: 56–63. https://doi.org/10.1126/science.159.3810.56 ## Infrastructure, classification, code - Bowker, Geoffrey C., and Susan Leigh Star. *Sorting Things Out: Classification and Its Consequences*. MIT Press, 1999. https://doi.org/10.7551/mitpress/6352.001.0001 - Lessig, Lawrence. *Code and Other Laws of Cyberspace*. 1999; *Code: Version 2.0*, 2006. https://hls.harvard.edu/bibliography/code-and-other-laws-of-cyberspace-version-2-0/ - Star, Susan Leigh, and Karen Ruhleder. “Steps Toward an Ecology of Infrastructure: Design and Access for Large Information Spaces.” *Information Systems Research* 7(1), 1996. https://doi.org/10.1287/isre.7.1.111 - Winner, Langdon. “Do Artifacts Have Politics?” *Daedalus* 109(1), 1980: 121–136. https://www.jstor.org/stable/20024652 ## Epistemic power, disagreement, revision - Alchourrón, Carlos E., Peter Gärdenfors, and David Makinson. “On the Logic of Theory Change: Partial Meet Contraction and Revision Functions.” *Journal of Symbolic Logic* 50(2), 1985. https://doi.org/10.2307/2274239 - Dung, Phan Minh. “On the Acceptability of Arguments and Its Fundamental Role in Nonmonotonic Reasoning, Logic Programming and n-Person Games.” *Artificial Intelligence* 77(2), 1995. https://doi.org/10.1016/0004-3702(94)00041-X - Fricker, Miranda. *Epistemic Injustice: Power and the Ethics of Knowing*. Oxford University Press, 2007. https://doi.org/10.1093/acprof:oso/9780198237907.001.0001 - Goldman, Alvin I. *Knowledge in a Social World*. Oxford University Press, 1999. ## Collective action, mobilization, diffusion - Centola, Damon. “The Spread of Behavior in an Online Social Network Experiment.” *Science* 329(5996), 2010. https://doi.org/10.1126/science.1185231 - Granovetter, Mark. “Threshold Models of Collective Behavior.” *American Journal of Sociology* 83(6), 1978. https://doi.org/10.1086/226707 - McCarthy, John D., and Mayer N. Zald. “Resource Mobilization and Social Movements: A Partial Theory.” *American Journal of Sociology* 82(6), 1977. https://doi.org/10.1086/226464 - Olson, Mancur. *The Logic of Collective Action*. Harvard University Press, 1965. https://doi.org/10.4159/9780674041660 - Rogers, Everett M. *Diffusion of Innovations*, 5th ed. Free Press, 2003. ## Capabilities, concerted action, legibility - Arendt, Hannah. *On Violence*. 1970. - Scott, James C. *Seeing Like a State: How Certain Schemes to Improve the Human Condition Have Failed*. Yale University Press, 1998/1999. https://yalebooks.yale.edu/book/9780300078152/seeing-like-a-state/ - Sen, Amartya. *Development as Freedom*. 1999/2000. https://www.penguinrandomhouse.com/books/163962/development-as-freedom-by-amartya-sen/ ## Systems and cybernetics - Ashby, W. Ross. *An Introduction to Cybernetics*. 1956. - Beer, Stafford. *Brain of the Firm*. 1972; later editions. - Meadows, Donella H. “Leverage Points: Places to Intervene in a System.” Sustainability Institute, 1999. ## Candidates for later expansion These are significant enough to deserve later treatment but are not yet integrated in detail: - Hannah Arendt — power as acting in concert, and distinction from violence; - Pierre Bourdieu — economic, cultural, social, and symbolic capital and conversion; - Michel Foucault — productive / dispersed power, normalization, and conduct; - Crozier & Friedberg — organizational power through zones of uncertainty; - mechanism design / incentive compatibility; - platform governance and recommender-system power; - algorithmic accountability and AI-mediated authority; - common-pool resource design principles in digital infrastructure; - standards governance and Internet protocol ossification; - epistemic democracy and deliberative systems; - institutional diversity and comparative constitutional design. ================================================================================================ FILE: power_dynamics/Academic-Lineage/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 03802af9de883e16c79cbcc960d438a9e19a611ef92e25ad689d71d95095cdf0 CONTENT_BYTES: 7015 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Academic Lineage" source_basis: --- # Academic Lineage This directory situates **Power Dynamics** and selected kOA mechanisms beside established academic traditions that study the same classes of problems. > **This is a lineage of problems, concepts, and convergent mechanisms — not a claim of historical influence, endorsement, or proof.** A cited author may have identified a problem that Power Dynamics also identifies, formalized a mechanism that helps explain a Power Dynamics claim, or supplied a counterexample / impossibility result that a kOA mechanism must survive. None of that means the author endorsed kOA, and none of it validates a particular implementation. ## Why this layer exists Power Dynamics crosses fields that are usually separated: political theory, organizational sociology, institutional economics, social choice, network science, open-source governance, systems theory, science and technology studies, social epistemology, expertise research, and software architecture. The purpose of this directory is therefore to make four things explicit for each major connection: 1. **Academic finding or problem** — what the literature actually established or argued. 2. **Power Dynamics correspondence** — which concept, audit surface, or kOA mechanism is structurally related. 3. **Design implication** — what should be tested, measured, separated, or protected. 4. **Limit of correspondence** — what the citation does **not** prove. ## High-level map | Academic lineage | Problem / insight | Power Dynamics correspondence | |---|---|---| | Dahl; Bachrach & Baratz; Lukes | power includes decisions, agenda control, and preference shaping | pre-political chain; discoverability; narrative / classification power | | Emerson; Cook et al.; Pfeffer & Salancik | power grows from dependency and scarce alternatives | effective possibility; dependency-exit audit; strong capability / weak sovereignty | | French & Raven; Bourdieu | power has multiple bases and convertible forms | power domains; cross-domain conversion; credibility ≠ authority | | Pettit | freedom requires protection against arbitrary domination | non-domination terminality; contestation; credible exit | | Ostrom; Crawford & Ostrom | polycentric governance and institutional rules can be analyzed at multiple levels | federation; subsidiarity; rules-about-rules; constitutional architecture | | Simon; Baldwin & Clark | complex systems can remain evolvable through modularity and explicit interfaces | capsules; protocolization; branch ecology; local variation + compatibility | | Farrell & Saloner; Katz & Shapiro; Pierson | compatibility can create lock-in, installed-base power, and path dependence | protocol power; ossification audits; migration paths; version pluralism | | Hirschman; Nyman & Lindman; O'Mahony & Ferraro; Benkler | exit, voice, forking, peer production, and open governance constrain hierarchy | forkability; branch mobility; founder decentering; capability commons | | Freeman; Bonacich; Granovetter; Burt; Coleman | network position, brokerage, weak ties, and social capital alter effective capacity | network / affiliation power; mobilization; brokerage and dependency audits | | Chi; Ericsson & Lehmann; Goldman | expertise is structured, domain-bounded, and difficult for nonexperts to evaluate | SmartVote domain scopes; EkoH context; expertise → advice, not sovereignty | | Cooke; Budescu & Chen; Mannes et al.; Hong & Page | calibrated weighting can help, but diversity and aggregation rules matter | plural lenses; measured contribution; diverse advisory readings | | Arrow; Gibbard; Satterthwaite | collective choice mechanisms face structural impossibility and manipulation limits | SmartVote transparency; baseline vs advisory lenses; no universal perfect voting rule | | Campbell; Merton | metrics and prestige can self-reinforce and be gamed | EkoH / reputation audits; Matthew effects; anti-Goodhart safeguards | | Winner; Lessig; Bowker & Star; Star & Ruhleder | artifacts, code, classifications, and infrastructure embed governance | power surface; semantic power; interface power; hidden sovereignty | | Fricker; Goldman; argumentation / belief-revision traditions | epistemic standing, testimony, disagreement, and revision are power-laden | Kristal provenance; competing Kristals; epistemic authority corruption tests | | Ashby; Beer; Meadows | viable systems require feedback, requisite variety, adaptation, and attention to leverage points | Know → Choose → Act → Remember; local autonomy; feedback; systemic audits | | Olson; McCarthy & Zald; Granovetter thresholds; Rogers; Centola | collective action requires mobilization, diffusion, threshold crossing, and sometimes social reinforcement | mobilization flow; latent resources; cultural corridors; adoption cascades | | Sen; Arendt; James C. Scott | real capability, concerted action, and dangers of administrative legibility | effective possibility; generated collective puissance; plural / contestable legibility | ## Reading order 1. [`01-power-dependence-and-domination.md`](01-power-dependence-and-domination.md) 2. [`02-polycentric-governance-and-institutions.md`](02-polycentric-governance-and-institutions.md) 3. [`03-modularity-standards-and-path-dependence.md`](03-modularity-standards-and-path-dependence.md) 4. [`04-open-source-exit-fork-and-peer-production.md`](04-open-source-exit-fork-and-peer-production.md) 5. [`05-network-power-and-social-capital.md`](05-network-power-and-social-capital.md) 6. [`06-expertise-smartvote-and-collective-judgment.md`](06-expertise-smartvote-and-collective-judgment.md) 7. [`07-metrics-reputation-and-gaming.md`](07-metrics-reputation-and-gaming.md) 8. [`08-classification-infrastructure-and-code.md`](08-classification-infrastructure-and-code.md) 9. [`09-epistemic-power-provenance-and-plurality.md`](09-epistemic-power-provenance-and-plurality.md) 10. [`10-systems-cybernetics-and-adaptation.md`](10-systems-cybernetics-and-adaptation.md) 11. [`11-collective-action-mobilization-and-diffusion.md`](11-collective-action-mobilization-and-diffusion.md) 12. [`12-capabilities-concerted-power-and-legibility.md`](12-capabilities-concerted-power-and-legibility.md) 13. [`BIBLIOGRAPHY.md`](BIBLIOGRAPHY.md) ## Core caution Academic literature can support a **problem diagnosis**, a **mechanism**, an **impossibility constraint**, or a **design principle**. It does not automatically validate: - a specific SmartVote weighting formula; - an EkoH scoring implementation; - the security or decentralization of a current deployment; - a claim that kOA is optimal; - a claim that Power Dynamics is derived from these authors; - or a claim that any cited scholar endorses kOA. The strongest use of this literature is adversarial: **it gives the framework better names for failure modes and better tests for whether the architecture actually solves them.** ================================================================================================ FILE: power_dynamics/assessment/analysis-method.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 53431cb746023eef7f52b7258a2d046a51f0482fd2801a44c8976990c472c4ff CONTENT_BYTES: 1223 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Power Analysis Method" --- # Power Analysis Method Use this sequence for any actor, institution, subsystem, or branch. 1. **Problem / baseline** — what incapacity, dependency, or coordination problem exists? 2. **Resources** — what stocks and assets are available? 3. **Potential** — what possibilities do they create? 4. **Capacity** — what is organized enough to be used? 5. **Puissance** — what can actually be mobilized now? 6. **Mobilization** — reservoir, release, throughput, channels, mediation, amplification. 7. **Power relations** — whose possibilities change, and how? 8. **Returns** — what assets are created and who receives them? 9. **Conversion pathways** — what can become what? 10. **Stacking / concentration** — what accumulates in one node? 11. **Dependency** — what becomes hard to substitute or exit? 12. **Counterpowers** — verification, contestation, substitution, exit, fork, branch mobility. 13. **Temporal analysis** — compounding, decay, succession, lock-in. 14. **Constitutional requirements** — what should be scoped, separated, portable, or reversible? ================================================================================================ FILE: power_dynamics/assessment/branch-comparison.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: d68c6361610c6bcd2a1234e6db3d39cd07331148eb6f61ddb9730d89139bd658 CONTENT_BYTES: 552 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Branch Comparison" --- # Branch Comparison Compare branches multidimensionally rather than producing one winner score. Suggested dimensions: evidence quality, provenance, uncertainty handling, outcomes, autonomy, auditability, privacy, interoperability, cost, complexity, accessibility, multilinguality, contestability, branch mobility, unique contribution, and complementarity. A valid conclusion may be that no global winner is required. ================================================================================================ FILE: power_dynamics/assessment/capability-show-profile.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 37dbf1afb6d53556886274f04a950a00346ebc9d4a3651f86c8ea0fdfad3bce4 CONTENT_BYTES: 2462 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Capability Show Profile" --- # Capability Show Profile The Capability Show Profile is the preferred format for demonstrating that a system is powerful **without collapsing capability into authority**. For each capability claim, document: ## 1. Baseline limitation What effective possibility is currently constrained? Examples: knowledge is fragmented, expertise is hard to discover, decisions are not executable, institutional memory is weak, exit is costly. ## 2. Resource and mechanism What resources, components, protocols, roles, or institutions are introduced? ## 3. Capacity created What organized ability becomes available? ## 4. Puissance demonstrated Under realistic conditions, what can the actor or collective now effectively do that it could not do before, or could only do at much higher cost? ## 5. Composition gain Which other capabilities become more useful because this capability exists? ## 6. Returns and compounding What reusable assets are left behind? Does the action lower future cost, increase future quality, preserve memory, expand network access, or create shared infrastructure? ## 7. Capability-to-power transition If the capability becomes widely relied upon, which actors' access, standing, visibility, allocation, interpretation, timing, dependency, or ability to act can be affected? ## 8. Conversion pathways What legitimate conversions are expected? What cross-domain conversions should be blocked? ## 9. Counterpowers Can affected actors verify, contest, substitute, exit, revoke, fork, or operate through an alternative branch? ## 10. Evidence and maturity Separate: - source-derived architecture; - implemented technical evidence; - demonstrated deployment evidence; - analytical reconstruction; - open questions. The goal is to make the **Power Show falsifiable and inspectable**, not merely impressive. ## Power routing A strong capability claim should now also state: - who gains the capability; - what new relational leverage may arise; - whether the mechanism redirects any leverage away from a central operator; - who receives the returns; - what can be duplicated, shared, self-hosted, forked, or independently maintained; - which rights remain centralized and why. This prevents the Power Show from confusing **a powerful ecosystem** with **a powerful owner of the ecosystem**. ================================================================================================ FILE: power_dynamics/assessment/constitutional-tests.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 900e662557b831ee9d0416c4d450465ae5e91267d15553feb952c3743ff0c60c CONTENT_BYTES: 712 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Constitutional Tests" --- # Constitutional Tests Stress-test a system with adversarial questions: - What if the maintainer becomes hostile? - What if a credibility policy is biased? - What if the dominant branch stops improving? - What if ranking favors incumbents? - What if a signing key is lost or captured? - What if the official brand owner disagrees with a protocol fork? - What if a provider changes terms? - What if AI output becomes de facto policy? - Can affected actors verify, contest, substitute, exit, and continue? The objective is not perfect immunity but non-terminal failure modes. ================================================================================================ FILE: power_dynamics/assessment/dependency-exit-audit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c5ca609903634a7adf2769fa0d089e7e1460932322fe51428eb74d1be162d691 CONTENT_BYTES: 532 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Dependency and Exit Audit" --- # Dependency and Exit Audit Assess effective dependency through alternatives, migration time, data portability, identity portability, reputation portability, legal barriers, network loss, retraining cost, infrastructure requirements, institutional recognition, recovery, and rollback. Report both **formal exit** and **effective exit**. Their difference is often the locus of hidden power. ================================================================================================ FILE: power_dynamics/assessment/flow-conversion-capture-audit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 80998ac936fad5e6ca00e43d5921712516a859c55e84f106c5f4e0dc8dd5d62f CONTENT_BYTES: 1246 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Flow, Conversion, Stacking, and Capture Audit" source_basis: - S10 - S15 - S16 - S21 - S25 - S28 --- # Flow, Conversion, Stacking, and Capture Audit This audit combines the stock/flow, conversion, and stacking views. ## Stock → Capacity → Flow For each major resource, trace: `Stock → Potential → Capacity → Puissance → Flow → Relation → Return` ## Conversion map List all material conversions and intermediate steps. Example: `expertise evidence → credibility signal → ranking weight → discoverability → opportunity` Ask who controls each step, whether the conversion crosses domains, whether it is contestable, and whether an alternative branch can implement a different policy. ## Stacking Inventory every function held by the same actor or node. Ask what leverage appears only because several legitimate functions are combined. ## Capture Test whether functional control has become durable cross-domain power: `Functional Control → Cross-Domain Power` Document mandate drift, default expansion, dependency growth, recognition loops, reduced branch mobility, and rising exit costs. ================================================================================================ FILE: power_dynamics/assessment/power-balance-sheet.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a93483759c7dbaa42e4b181e8947fb6cb98ad2f7985dded0a89a9e4c00dea7b6 CONTENT_BYTES: 754 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Power Balance Sheet" --- # Power Balance Sheet A power balance sheet maps accumulated assets and dependencies without pretending they have one common unit. ### Assets / stocks financial, technical, epistemic, human, network, credibility, brand, institutional, operational, mnemonic, optionality. ### Dependencies / liabilities single providers, single maintainers, remote services, legal permissions, proprietary formats, recognition monopolies, key-person knowledge, network effects, update/signing keys, funding concentration. The purpose is to expose conversion pathways and terminal dependencies, not to produce a net “power score.” ================================================================================================ FILE: power_dynamics/assessment/power-routing-audit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 01d594c96fad05dad77a5847946d52126cf263f94c95a522fd92e55ff4815dce CONTENT_BYTES: 2119 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "NEW-CONCEPT" scope: "GENERAL" version: "6.0" title: "Power Routing Audit" source_basis: - S02 - S14 - S15 - S16 - S17 - S19 - S21 - S25 --- # Power Routing Audit Use this audit after identifying a system's generated puissance. ## 1. Capability destination - Who becomes more capable? - Is the capability reusable outside the original operator? - Can participants teach, reproduce, or transfer it? ## 2. Authority destination - Who gains approval, ranking, validation, certification, moderation, routing, update, or veto rights? - Are those rights scoped? - Can they be revoked or substituted? ## 3. Return destination - Who receives money, data, reputation, network effects, knowledge, code, memory, and institutional access generated by collective activity? - Do collective returns become shared assets or private concentration? ## 4. Optionality destination - Who can leave? - Who can self-host? - Who can fork? - Who can preserve identity, history, reputation, and knowledge after exit? ## 5. Interpretive destination - Who defines categories, credibility policies, semantic mappings, reader policies, and defaults? - Can alternative interpretations coexist? ## 6. Self-binding - Are ethical or constitutional commitments public? - Can affected actors cite them against the operator or founder? - Are they connected to procedures or only aspirational prose? ## 7. Protocolization - Which functions remain dependent on tacit founder knowledge? - Which have explicit specifications? - Can another maintainer or institution reproduce the function without unique permission? ## 8. Ownership decoupling - Is a useful function inseparable from one brand, registry, identity provider, key, or operator? - Could a compatible alternative become socially and technically viable? ## Output For each major capability, record: ```text Generated puissance: Concentration vector: Routing mechanism: Primary recipients: Retained central rights: Transferred / shared rights: Return allocation: Exit / substitution path: Failure mode: Evidence needed: ``` ================================================================================================ FILE: power_dynamics/assessment/power-surface-audit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 3b8ff9c56ceaeba651951393249cb21ce9f6a6db21312d9fe96b69982434f778 CONTENT_BYTES: 2301 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Power Surface Audit" source_basis: - S13 - S15 - S16 - S18 - S21 - S25 --- # Power Surface Audit Use this audit to answer: > **What kinds of power does this system generate, where can they convert, and where are they routed?** ## 1. Domain inventory For each domain, record: | Domain | Resources | Capacity | Puissance | Relational power | Main controllers | |---|---|---|---|---|---| | Political | | | | | | | Economic | | | | | | | Monetary | | | | | | | Epistemic | | | | | | | Semantic | | | | | | | Information / attention | | | | | | | Credibility | | | | | | | Network | | | | | | | Administrative | | | | | | | Technical / infrastructure | | | | | | | Narrative / brand | | | | | | | Cognitive / AI | | | | | | | Mnemonic / temporal | | | | | | | Evolutionary / counterpower | | | | | | ## 2. Conversion inventory For every major conversion: ```text source domain → mechanism → destination domain → resulting leverage ``` Record whether the conversion is: - explicit or hidden; - intended or emergent; - reversible or sticky; - scoped or cross-mandate; - contestable or terminal. ## 3. Stacking test Which actor or node controls multiple high-leverage surfaces? Look especially for combinations of: - identity; - credibility; - discoverability; - allocation; - workflow; - infrastructure; - signing / updates; - brand / certification; - monetary rails. ## 4. Routing test For each major capability, identify who receives: - **capability**; - **authority**; - **returns**; - **optionality**. ## 5. Counterpower test Can affected actors effectively: - verify? - contest? - substitute? - exit? - self-host? - fork? - preserve identity / history / evidence? - gather support for an alternative? ## 6. Terminality test Ask: > If this controller fails, captures the function, changes policy arbitrarily, or disappears, can the ecosystem continue through another viable path? If not, the surface may be **terminal power**. ## 7. Output A complete audit should produce: 1. a domain map; 2. a conversion graph; 3. a stacking map; 4. a routing map; 5. a counterpower map; 6. a terminality assessment; 7. a list of technical evidence still required. ================================================================================================ FILE: power_dynamics/assessment/propagation-audit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6f8ac614742bc652b31f9038b4b1282d8ed799313f7927fa7b96673be2bd6646 CONTENT_BYTES: 2268 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Propagation Audit" source_basis: - S21 - S25 - S29 --- # Propagation Audit Use this audit to determine whether a claimed growth mechanism actually propagates capability or merely creates attention, dependency, or local compounding. ## A. Loop identity 1. What is the loop called? 2. What actor / branch / domain owns each stage? 3. What begins the loop? 4. What event counts as closure? ## B. Return 5. What reusable return is produced? 6. Is it rival or non-rival? 7. Is it portable? 8. Does it retain provenance? 9. Who receives it? ## C. Propagation 10. Which other actor / branch can consume the return? 11. What activation barrier does it lower? 12. How much does it lower that barrier? 13. Can the transfer occur without founder intervention? 14. Can the transfer occur without mandatory central service dependency? ## D. Coupling 15. Which other loop does this feed? 16. Does that loop return an asset back? 17. Is the coupling intentional or accidental? 18. What shared dependency could break both loops? ## E. Governance 19. What authority grows as the loop grows? 20. What cross-domain conversion becomes possible? 21. What prevents money, credibility, brand, expertise, or infrastructure from becoming unrelated sovereignty? 22. What exit / substitution / fork remains practical? ## F. Damping 23. What causes saturation? 24. What slows or stops the loop when quality declines? 25. What signal distinguishes healthy growth from runaway growth? 26. Can operators intentionally pause or remain local? ## G. Evidence 27. Is the loop only designed, demonstrated, used, repeated, independently replicated, or federated? 28. What metric is currently observed? 29. What metric is only projected? 30. What result would falsify the mechanism? ## H. Founder-dependency test 31. Founder minutes per cycle? 32. Founder-only credentials / keys / relationships? 33. Founder-only interpretive knowledge? 34. Can another operator close the loop? 35. Can another operator teach a third operator? A claimed propagation mechanism should not be considered mature until at least one non-founder actor has closed the relevant loop independently. ================================================================================================ FILE: power_dynamics/assessment/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 70ff429cda2f510210f6a1d63683462dd5cd1c7a96d21dbdc40cf653f6d77929 CONTENT_BYTES: 1429 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Assessment" source_basis: - S13 - S15 - S16 - S18 - S21 - S25 --- # Assessment Assessment converts Power Dynamics into repeatable audits. ## Core instruments - [`analysis-method.md`](analysis-method.md) — general method. - [`capability-show-profile.md`](capability-show-profile.md) — document why a claimed capability is real. - [`power-surface-audit.md`](power-surface-audit.md) — map political, economic, monetary, epistemic, technical, and other domains together. - [`flow-conversion-capture-audit.md`](flow-conversion-capture-audit.md) — trace conversion and capture. - [`power-routing-audit.md`](power-routing-audit.md) — identify where capability, authority, returns, and optionality go. - [`dependency-exit-audit.md`](dependency-exit-audit.md) — distinguish formal from effective exit. - [`power-balance-sheet.md`](power-balance-sheet.md) — assets, dependencies, liabilities, and optionality. - [`constitutional-tests.md`](constitutional-tests.md) — test non-domination and terminality. - [`branch-comparison.md`](branch-comparison.md) — compare alternatives without assuming one final metric. - [`temporal-evolution.md`](temporal-evolution.md) — inspect change, drift, succession, and compounding over time. - [`system-profile.md`](system-profile.md) — system-level summary. ================================================================================================ FILE: power_dynamics/assessment/system-profile.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 69cf0ff0c73e3ea15c355187836de1d392b4798961fdd51779bfe9a542f298ad CONTENT_BYTES: 535 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "System Power Profile" --- # System Power Profile A system profile should summarize major resource stocks, main forms of puissance, major power relations, mediators and bottlenecks, conversion pathways, return loops, concentration, stacking, dependency gradients, counterpowers, branch ecology, founder/maintainer dependencies, temporal risks, and technical-evidence confidence. This is the preferred top-level audit output. ================================================================================================ FILE: power_dynamics/assessment/temporal-evolution.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 56241585fa5d2f89d05ccc59cdc6243b661c9327b522294dac1f218a082e8134 CONTENT_BYTES: 641 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Temporal Evolution Analysis" --- # Temporal Evolution Analysis Power relations change over time. ### Formation phase Who supplies scarce initial capability? ### Scaling phase Which feedback loops, network effects, standards, and dependencies emerge? ### Succession / maturity phase Can authority, knowledge, keys, brand stewardship, and maintenance transfer without collapse? Also inspect decay: credibility can expire, technical knowledge can become obsolete, and branches can lose fitness. A static snapshot is insufficient. ================================================================================================ FILE: power_dynamics/branch-ecology/branch-mobility.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b3b359d471ed714cf8c501aea2db6242317f345a405ef4dd7e38c73c90988d32 CONTENT_BYTES: 670 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Branch Mobility in Practice" source_basis: - S16 - S19 - S25 --- # Branch Mobility in Practice Branch mobility is the practical path from alternative to viable competitor or complement. A high-mobility ecosystem lets a branch: `form → preserve lineage → interoperate → demonstrate → be discovered → gather support → deploy → influence / coexist / replace`. Low branch mobility can create dogma without explicit censorship: alternatives formally exist but cannot accumulate enough recognition, compatibility, or infrastructure to matter. ================================================================================================ FILE: power_dynamics/branch-ecology/complementarity-and-antidogma.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 364d86ab0d9f63adbd67aadd4be67f645b16c9559cce0c4e704eb7a314d2e424 CONTENT_BYTES: 957 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Complementarity and Anti-Dogma" source_basis: - S02 - S16 - S22 - S25 --- # Complementarity and Anti-Dogma Complementarity exists when several branches jointly provide more value than a single universal branch. Scientific, legal, historical, local, experiential, or cultural representations may answer different questions. Credibility systems can specialize in academic, practical, or community evidence. Complementarity is not relativism. Branches remain comparable on explicit dimensions. Dogma, in this framework, is repetition protected from meaningful comparison, revision, or added value. Useful plurality contributes new evidence, context, method, ontology, implementation, translation, or function. > **No branch should become final merely because alternatives cannot be meaningfully formed, compared, supported, or adopted.** ================================================================================================ FILE: power_dynamics/branch-ecology/improvement-support-dominance.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 34737a5c599919734bc46b6cad75bb8bde2a8453871e6e0e897a2ad6b30f4642 CONTENT_BYTES: 977 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Improvement, Support, Adoption, and Dominance" source_basis: - S13 - S15 - S16 - S18 - S22 - S25 --- # Improvement, Support, Adoption, and Dominance An alternative should be able to say not only “we disagree,” but **what changed and what value was added**. Possible demonstrations include stronger evidence, better provenance, lower error, lower cost, higher autonomy, better accessibility, improved multilinguality, better outcomes, stronger privacy, better local fit, or improved interoperability. Support, adoption, and dominance are distinct. A branch may be intellectually supported but rarely deployed, or dominant because of history, compatibility, network effects, official status, or funding. > **Dominance ≠ Truth ≠ Quality ≠ Legitimacy** No universal scalar is required. Improvement can be multidimensional and context-dependent. ================================================================================================ FILE: power_dynamics/branch-ecology/lineage-and-competing-kristals.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a309402aa928d404161eab52b45b6014ff725acc4891fa89c8d14e94e5b9dfbc CONTENT_BYTES: 1078 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Lineage and Competing Kristals" source_basis: - S13 - S16 - S22 - S25 --- # Lineage and Competing Kristals Kristals can preserve divergent claims, evidence, scopes, policies, and contexts without forcing immediate universal convergence. Two Kristals may each claim better representation of a phenomenon. The system should preserve sources, assumptions, validation policy, scope, uncertainty, lineage, added evidence, and unresolved disagreement. A later Kristal may synthesize, specialize, or challenge both. The objective is cumulative epistemic evolution rather than winner-take-all truth declaration. Branch plurality does not imply epistemic equivalence. A branch can be preserved because it is culturally meaningful, institutionally adopted, experimentally useful, adversarial, or fictional while still carrying weaker evidentiary support than another branch. Lineage should make both **difference of worldview** and **difference of support** visible. ================================================================================================ FILE: power_dynamics/branch-ecology/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6db9733893795e13e0dcddadc85b7ba77760fd093b4d5aae42eb59ea00417f5b CONTENT_BYTES: 1231 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Branch Ecology" source_basis: - S13 - S16 - S22 - S25 --- # Branch Ecology Branch ecology is the **evolutionary end of the Power Show**. A system is more capable when it can not only act, but also **improve the mechanisms through which it knows, chooses, acts, and remembers**. Branches are therefore not merely emergency responses to capture. They are normal instruments of experimentation under permanent imperfection. The ecology asks: - how lineage and competing Kristals are preserved; - how complementarity avoids dogma without collapsing into relativism; - how alternatives demonstrate added value; - how support, adoption, dominance, truth, and quality remain distinct; - whether a better branch can actually become viable; - how branches coexist, specialize, recombine, merge, or replace one another. The key capability is **branch mobility**: not only the formal right to fork, but the practical ability to preserve provenance, interoperate, attract support, gain discoverability, and eventually influence or replace a dominant branch. > **The core protects evolution; it does not freeze truth.** ================================================================================================ FILE: power_dynamics/branch-ecology/recombination-replacement.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a65575b7586c37ac1a267a73283dd320b44c79ac8f6a953cdf858be6a13d0818 CONTENT_BYTES: 529 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Recombination and Replacement" source_basis: - S13 - S16 - S25 --- # Recombination and Replacement Evolution is not always replacement. Branches may coexist, specialize, merge, import specific improvements, recombine into a new branch, decline, or be replaced. A healthy ecosystem preserves enough lineage to explain how later branches inherit or reject earlier decisions. Replacement should not erase history. ================================================================================================ FILE: power_dynamics/cases/ai-hidden-sovereignty.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 536d76bfefa83626d31f2a09b10f8e7fad59fca5b4c733e297ad8955afbc0181 CONTENT_BYTES: 629 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "AI and Hidden Sovereignty" source_basis: - S16 - S21 - S25 --- # AI and Hidden Sovereignty AI can be formally advisory while becoming practically sovereign if institutions cannot understand, challenge, reproduce, or override its outputs. Signals include automatic adoption of model recommendations, inaccessible prompts or policies, no governed fallback, dependence on a remote provider, or model outputs treated as authoritative evidence by default. The case tests the principle `AI assists under governance`. ================================================================================================ FILE: power_dynamics/cases/bootstrap-koa.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 53aefc26c8c6f45a1d48e3eef31df8e525e0c851c52b8289ba44320853ff67f2 CONTENT_BYTES: 621 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Bootstrapping kOA" source_basis: - S25 --- # Bootstrapping kOA The two-year bootstrap case illustrates conversion of temporary personal resources into persistent assets. `time + skill + AI + personal resources → code + architecture + documentation + methods + experience + brand → lower future development cost → greater technical/cognitive/organizational puissance → more systems built` The later question is whether these assets become ecosystem resources or remain founder-dependent bottlenecks. ================================================================================================ FILE: power_dynamics/cases/brand-merchandise-affiliation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 102267fbc80e6226cbbd950d3f8971399c070639fee2443e569be3af1e2277c0 CONTENT_BYTES: 627 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Brand, Merchandise, and Affiliation" source_basis: - S04 - S02 --- # Brand, Merchandise, and Affiliation Brand can convert symbolic resources into economic and network returns: `system value → brand recognition → affiliation / attention → merchandise → revenue → reinvestment` Merchandise also creates public signaling: purchase becomes both funding and visible affiliation. The firewall is that commercial or symbolic success should not silently become epistemic truth or institutional sovereignty. ================================================================================================ FILE: power_dynamics/cases/competing-kristals.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 001e5b6baa2cc42a73c5047fab2a82f80b3183b53e63f4d2d49619d12696d164 CONTENT_BYTES: 1443 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Competing and Complementary Kristals" source_basis: - S13 - S16 - S22 - S25 --- # Competing and Complementary Kristals Two Kristals can each claim a better representation without requiring immediate centralized adjudication. The system should preserve lineage, provenance, evidence, policy differences, scope, uncertainty, and added value. A third branch may synthesize or specialize. The governance capability is the ability to compare and evolve rather than repeat one official answer without added value. ## Pluralism is not epistemic equivalence Forkability protects the right to maintain incompatible representations. It does not require the system to pretend that all branches have equal support. A branch may encode a religious cosmology, a minority scientific interpretation, a deliberately adversarial worldview, or an explicitly fictional universe. The system should preserve the branch's own axioms and lineage while also making differences in evidence, provenance, uncertainty, contradiction, and validation policy legible. > **Freedom to fork a knowledge representation is not ownership of truth, and it is not immunity from comparison with evidence.** A reference or institutionally stewarded Kristal should therefore function as a visible reference branch, not as an irreversible global truth monopoly. ================================================================================================ FILE: power_dynamics/cases/desjardins-stacking.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 76e3ade5e1a4b49c44a998e8efbfe3cdd2fce27220dfb928ebe4fa47b496b603 CONTENT_BYTES: 596 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Desjardins and Power Stacking" source_basis: - S10 --- # Desjardins and Power Stacking The Desjardins proposal combines member governance with possible roles in banking, identity, certification, philanthropy, and Konnaxion access. Each function may be legitimate while their combination creates cross-domain leverage. The design question is how to keep financial infrastructure strong in its mandate without silently becoming identity, epistemic, political, or platform sovereignty. ================================================================================================ FILE: power_dynamics/cases/epistemic-authority-corruption.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c37e3a3471782fd70600f183220fdef3e54cf7812573c29860abdcc677532cf8 CONTENT_BYTES: 3003 ================================================================================================ --- maturity: "DESIGN-DIRECTION" claim_type: "USER-CONFIRMED-DESIGN" scope: "kOA" version: "6.1" title: "Epistemic Authority Corruption Drill" source_basis: --- # Epistemic Authority Corruption Drill A forkable knowledge system must remain usable even when an actor deliberately tries to make a false worldview look well supported. Current architect-confirmed design includes an adversarial Kristal centered on a known false conclusion — a flat-Earth worldview — so that the system can study **how apparent knowledge can be manufactured** without ambiguity about the ground truth. The object of study is not the truth of the flat-Earth claim. The object is the **construction of epistemic authority around it**. ## Power conversion under test ```text claims / documents / credentials / popularity / citations → apparent credibility → apparent source multiplicity → discoverability and repetition → perceived consensus → epistemic authority ``` The stress test asks where these conversions become misleading and which controls reveal the distortion. ## Threat classes The drill is intended to expose classes of corruption such as: - unverified or fabricated authority claims; - circular citation; - dependent sources presented as independent confirmation; - selective evidence and omitted counterevidence; - prestige transfer from institutions, titles, or formats; - popularity treated as evidentiary weight; - semantic reframing and definition drift; - repetition interpreted as consensus; - scientific material quoted or transformed beyond what it actually supports. This repository treats these as **threat classes**, not as instructions for deceiving external institutions or audiences. ## Apparent independence vs causal independence A central analytical distinction is: > **Many references do not imply many independent evidentiary lineages.** For example: ```text 100 apparent references → 12 intermediary summaries → 3 shared source chains → 1 unsupported origin ``` A robust epistemic system should make this compression visible where provenance allows it. ## Postmortem as the primary output The valuable artifact is the autopsy: ```text How did the false conclusion acquire authority? Which signals were trusted too easily? Which sources were not actually independent? Where did provenance become weak or opaque? Which counterevidence was excluded? Which detection rules worked? Which controls failed? What should change before the same pattern appears in a subtler domain? ``` The result can become a reusable library of epistemic pathologies for later analysis of political propaganda, pseudoscience, commercial persuasion, institutional bias, or other contested knowledge environments. ## Constitutional objective Forkability permits incompatible representations. It does **not** require equal evidentiary standing. > **Freedom to maintain a worldview is distinct from immunity from provenance, comparison, contradiction, and evidentiary audit.** ================================================================================================ FILE: power_dynamics/cases/ethical-fiction-self-binding.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 58c2c385d224e50c13e4551dc24be37323e236b964ab3b9b2755397fb5aded75 CONTENT_BYTES: 4082 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.1" title: "Ethical Fiction as Narrative Self-Binding" source_basis: - S02 - S19 - S21 - S22 --- # Ethical Fiction as Narrative Self-Binding Fiction can generate symbolic power: attention, recognition, emotional salience, affiliation, memory, and transmission. One distinctive mechanism in the kOA / King Klown corpus is that ethical principles are published **inside the fictional and symbolic layer itself**. The source material includes a living ethical code that emphasizes clarity of intention, respect for living beings, vigilance against monopoly, domination, and manipulation, public recognition of contributors, self-mockery, regular ethical reassessment, revision, criticism, and non-dogmatic transmission. ## Power Dynamics interpretation This can be understood as **narrative self-binding**. ```text fiction / symbol → attention and affiliation puissance → explicit ethical constraints embedded in the same channel → public commitments → criticism can cite the commitments → symbolic authority becomes more contestable ``` The mechanism redirects some of the symbolic power away from loyalty to a persona and toward **principles that can be carried, quoted, criticized, and reinterpreted by others**. ## Why this is unusual Public narratives often maximize persuasive power while leaving their ethical limits external, implicit, or privately intended. Here the ethical content is part of the transmission payload. That creates several distinct redirection effects: 1. **Self-limitation** — the narrative states what it should not become. 2. **Public contestability** — critics can compare behavior against published principles. 3. **Symbolic-capital sharing** — recognition is explicitly redirected toward contributors through gratitude, attribution, and “share the merit” norms. 4. **Anti-sanctification** — self-mockery and explicit rejection of sanctifying the Klown reduce the claim that symbolic centrality should become unquestionable authority. 5. **Transmissibility of limits** — people can copy the ethical constraints even when they reinterpret or detach from the original symbolic figure. 6. **Succession without fidelity** — the text emphasizes documentation, transmission, reinvention, and “passing the baton,” redirecting inheritance from loyalty to a founder-model toward the capacity to transform and continue the work. The related public-brand analysis reinforces the same direction by treating the persona as a **diffusion instrument** distinct from the architect identity and explicitly oriented toward reducing founder-worship. In Power Dynamics terms, this is an attempt to route narrative puissance toward transmission rather than personal sovereignty. ## What it does not prove Published ethics are not enforcement. They do not prove that a founder, community, brand, or future branch will behave ethically. Narrative self-binding is strongest when paired with institutional mechanisms such as auditability, contestation, attribution, exit, forkability, and independent operation. The constitutional objective is therefore: > **Narrative may mobilize, but it should also carry the instructions for resisting its own capture.** ## Trickster function as counterpower training Narrative self-binding can go beyond publishing limits. A trickster figure can also create an adversarial but bounded situation in which readers or participants must **use those limits against the symbolic figure itself**. In Power Dynamics terms, this converts narrative centrality into a training surface for counterpower: ```text symbolic authority → deliberate contradiction or provocation → public scrutiny → organized objection → practiced resistance to symbolic authority ``` The important output is not obedience to the trickster's intended lesson. It is a precedent that the persona can be challenged, analyzed, rejected in part, and prevented from converting attention into unquestionable authority. ================================================================================================ FILE: power_dynamics/cases/founder-identity-optionality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 4b1748556ec1095fe39d72aeda05ee5ced1f4d4d5cfd2c95bfdf1c7af7384fd4 CONTENT_BYTES: 608 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Founder Identity Optionality" source_basis: --- # Founder Identity Optionality A founder whose face or identity is not broadly public preserves privacy, ordinary social mobility, observational freedom, scarcity, and future reveal timing. This is **identity optionality** and **release optionality**, not yet mass-media power. If recognition later grows, disclosure can convert optionality into attention or narrative effects. The irreversible nature of disclosure makes timing itself a resource. ================================================================================================ FILE: power_dynamics/cases/founder-opposition-rehearsal.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 2538cf15f94117bc8a5ec260e5955a28e9dac094c0667be9fc53e735b48a5e38 CONTENT_BYTES: 3504 ================================================================================================ --- maturity: "DESIGN-DIRECTION" claim_type: "USER-CONFIRMED-DESIGN" scope: "kOA" version: "6.1" title: "Founder Opposition Rehearsal" source_basis: --- # Founder Opposition Rehearsal A system is not founder-independent merely because its code can run without the founder. It must also remain capable of **disagreeing with, organizing against, and defeating the founder's proposals** when those proposals are wrong. Current architect-confirmed design includes a deliberately adversarial civic drill built around a politically coherent party that contains one conspicuously abusive policy: a state prohibition on tattoos combined with compulsory removal of existing tattoos. The policy is not the point of the exercise. The intended test is whether founder or persona authority can be converted into political leverage **without becoming political immunity**. ## Power conversion under test ```text founder authorship / symbolic capital / rhetorical skill → attention → trust / deference → agenda influence → political mobilization → attempted policy leverage ``` The constitutional requirement is that this chain remain interruptible. ```text attention ≠ truth trust ≠ immunity from criticism founder status ≠ policy authority movement coherence ≠ mandatory agreement ``` ## Civic fire-drill logic A fire drill creates practiced evacuation pathways before a real fire exists. This case applies the same logic to counterpower. The intended pathway is: ```text problematic proposal → recognition → objection → evidence and rights analysis → argument registry → relevant expertise → coalition formation → institutional contestation → amendment / rejection → postmortem → reusable civic memory ``` The desired outcome is not hostility to the founder. It is **legitimate divisible agreement**: participants can support a broader project while rejecting and organizing against a specific proposal. ## Rehearsed counterpower Power Dynamics distinguishes **formal counterpower** from **rehearsed counterpower**. A right to contest that has never been exercised may remain socially expensive, procedurally unclear, or symbolically taboo. A successful drill can establish a precedent that opposition to the founder is normal, legitimate, and survivable. The resulting pattern can become a reusable reference — informally, a **Tattoo Protocol** — for later cases in which an authority makes a subtler or genuinely unintended error. ## Success criteria The drill is successful if: - the proposal can be isolated from the rest of the platform; - critics can organize without being treated as enemies of the whole project; - evidence, rights, proportionality, expertise, and consequences can be made legible; - founder symbolic power does not silently become sovereign authority; - opposition can succeed without requiring censorship or destruction of the surrounding movement; - the process leaves reusable institutional memory. ## Failure modes Important failure modes include: - supporters rationalize the proposal primarily because of founder loyalty; - critics must exit the whole system to oppose one proposal; - persona prestige overrides evidence or rights; - counterpower exists formally but is too costly to exercise; - the exercise creates a precedent of obedience rather than a precedent of contestation. The constitutional objective is: > **A system should not merely permit opposition to its founder. It should know how to practice it.** ================================================================================================ FILE: power_dynamics/cases/kingcoin-legacy-stress-test.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a502d7c9f7dabc1dcb67d10a9cc2a5fb387410cb22f61f05df4edc1cb89684b4 CONTENT_BYTES: 631 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "KingCoin as a Legacy Stress Test" source_basis: - S09 - S11 --- # KingCoin as a Legacy Stress Test Legacy KingCoin proposals include global governance, sanctions, blacklisting, automated penalties, and monetary enforcement. These mechanisms create strong monetary and enforcement power and expose tensions with later commitments to non-domination, local sovereignty, branch alternatives, and effective exit. The case is retained as an evolutionary stress test, not silently harmonized with current-core principles. ================================================================================================ FILE: power_dynamics/cases/media-and-state.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 56c01c0cc89cb7e936f581b7486efc16b80376e5d8eda059ca068e04cd1fc87a CONTENT_BYTES: 599 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Media and State: Domain-Specific Power" source_basis: - S18 - S21 - S22 --- # Media and State: Domain-Specific Power Media can possess enormous distribution, framing, and synchronization puissance. This can become visibility, agenda, reputation, and framing power at mass scale. States may possess stronger legal, fiscal, coercive, territorial, or administrative authority. The correct comparison is domain-specific rather than a one-dimensional “most powerful actor” ranking. ================================================================================================ FILE: power_dynamics/cases/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 66fd280c3c57985372922ebbb6e2d70183b1d75dde69dbb0273d93afc2ee521f CONTENT_BYTES: 1545 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Case Studies" source_basis: --- # Case Studies Cases are where the Power Show and the analytical theory meet. Each case should ideally answer: 1. what resources are present; 2. what capability is generated; 3. how that capability composes or compounds; 4. what relations of power emerge; 5. what returns and dependencies follow; 6. what counterpowers and alternatives remain. The cases are not all equally current. Legacy proposals are retained when they expose useful failure modes, centralization risks, or conceptual evolution. Notable cases include: - kOA bootstrap and founder-to-system transition; - unpublished corpus as epistemic reservoir; - media vs state as a domain-specific power comparison; - SmartVote discoverability; - competing Kristals; - recognition loops; - Desjardins power stacking; - Zero-Skim allocation governance; - brand, merchandise, and affiliation; - AI hidden sovereignty; - KingCoin as a legacy stress test. - [`ethical-fiction-self-binding.md`](ethical-fiction-self-binding.md) — publishing ethical limits inside a narrative as a form of symbolic self-binding; - [`founder-opposition-rehearsal.md`](founder-opposition-rehearsal.md) — civic fire-drill logic for practicing legitimate opposition to founder authority; - [`epistemic-authority-corruption.md`](epistemic-authority-corruption.md) — adversarial Kristal stress test for apparent authority, source dependence, and false consensus. ================================================================================================ FILE: power_dynamics/cases/recognition-loop.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 44f23f4d8fb4394c934f391867e458eb99949325c148c88d5326d5f90b2263f2 CONTENT_BYTES: 623 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Recognition Loop and Incumbency" source_basis: - S15 - S28 --- # Recognition Loop and Incumbency A healthy recognition loop: `Contribution → Evidence → Recognition → Opportunity → More Contribution` can become: `Recognition → Visibility → Opportunity → Recognition` The second loop lets incumbency reproduce itself even when new evidence is weak. Branch mobility, portable evidence, domain-bounded credibility, time decay, and alternative discovery policies can counterbalance this dynamic. ================================================================================================ FILE: power_dynamics/cases/smartvote-discoverability.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 9bdd6ad3b071ef0e3e8ed54c9bf1f11497eb93e70cef75e3f287e880c62feb9f CONTENT_BYTES: 637 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "SmartVote and Discoverability Power" source_basis: - S15 - S17 - S28 --- # SmartVote and Discoverability Power SmartVote demonstrates that discovery is governance. What rises is more likely to be reused, cited, learned, funded, adopted, or built. Even when final political equality is preserved, ranking criteria can shape the agenda before the final decision. The case separates baseline support, credibility signals, weighted advisory readings, and discoverability effects rather than collapsing them into one score. ================================================================================================ FILE: power_dynamics/cases/unpublished-corpus-reservoir.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 29e2369982ab4cf802e04f9b4b3893a8a6891b1826413c119296e2568f6cfe9e CONTENT_BYTES: 747 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Unpublished Corpus as an Epistemic Reservoir" source_basis: - S02 - S13 - S25 --- # Unpublished Corpus as an Epistemic Reservoir A large unpublished corpus is best modeled as an **epistemic resource reservoir**, not stored power. It can preserve knowledge stock, narrative options, release timing, future publication paths, synthesis possibilities, and documentation value. External influence depends on later transformations: `organization → release → distribution → comprehension → credibility → reuse → adoption` The case demonstrates why reservoir size, puissance, reach, influence, and authority are distinct. ================================================================================================ FILE: power_dynamics/cases/zero-skim-philanthropy.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: bd34206ab66cb54f3ee3027d75954af27e94b852000ae2c077d7fbe08f064d46 CONTENT_BYTES: 500 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Zero-Skim Philanthropy" source_basis: - S14 --- # Zero-Skim Philanthropy The Zero-Skim model separates economic contribution from democratic allocation. `Money → donation resources` does not automatically become `Money → more votes`. A cooperative rail can provide financial and compliance puissance while members retain allocation authority through one-member-one-vote mechanisms. ================================================================================================ FILE: power_dynamics/CHANGELOG.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ae88fd85dfa4c271bc14c50b1d9fe15ca95fbe5348664fd5db26c5e245f253ff CONTENT_BYTES: 9063 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Changelog" --- # Changelog ## 6.3 — Propagation & Coupled Loops - Added top-level `PROPAGATION.md`. - Distinguished **compounding** (returns deepen capability) from **propagation** (returns activate capability elsewhere). - Added **coupled propagation** for cross-loop return exchange. - Added `propagation/` deep-dive layer and kOA loop catalog. - Added propagation audit and feedback-loop / coupled-loop schemas. - Added adoption stack: notice → understand → examine → contextualize → try → deploy → local value → independent mastery → optional federation. - Added cross-branch return classes: money, code, evidence, credibility, relationships, knowledge, operators, language assets, integrations, content, brand, and technical legitimacy. - Added explicit damping / runaway-prevention analysis. - Added founder-absence as a measurable propagation criterion. - Added S29 architect-confirmed propagation notes for Worlds, cinematic demonstrations, machine-readable documentation, multilingual scaling, cultural diffusion, pre-exposure discipline, and movement self-use. - Extended Power Show formula to **Breadth × Composition × Closure × Memory × Compounding × Propagation × Replication × Routing**. ## 6.2 — Academic Lineage - Added `Academic-Lineage/` with ten thematic crosswalks plus a selective bibliography. - Added relational-power and dependence lineages: Dahl, Emerson, Cook et al., Pfeffer & Salancik, French & Raven, Lukes, Pettit. - Added polycentric-governance and institutional-grammar lineages: Ostrom and Crawford & Ostrom. - Added modularity / standards / lock-in / path-dependence lineages: Simon, Baldwin & Clark, Farrell & Saloner, Katz & Shapiro, Pierson. - Added exit / voice / fork / peer-production lineages: Hirschman, Nyman & Lindman, O'Mahony & Ferraro, Benkler. - Added network-power lineages: Freeman, Bonacich, Granovetter, Burt, Coleman. - Added SmartVote / expertise lineages: Chi et al., Ericsson & Lehmann, Goldman, Cooke, Budescu & Chen, Mannes et al., Hong & Page, plus Arrow / Gibbard / Satterthwaite constraints. - Added metric-gaming and cumulative-advantage lineages: Campbell and Merton. - Added technology-as-governance lineages: Winner, Lessig, Bowker & Star, Star & Ruhleder. - Added epistemic-power and revision lineages: Fricker, AGM belief revision, Dung argumentation. - Added systems / cybernetics lineages: Ashby, Beer, Meadows. - Added collective-action / mobilization lineages: Olson, McCarthy & Zald, Granovetter threshold models, Rogers, Centola. - Added capability / concerted-power / legibility lineages: Sen, Arendt, James C. Scott; plus Morriss, Foucault, and Crozier & Friedberg in the power-theory layer. - Added explicit academic-claim discipline: correspondence is not endorsement, historical influence, or implementation validation. - Proposed `Installed-Base Power` and interface governance as future first-class Power Dynamics concepts. ## 6.1 — Adversarial Resilience - Added founder fallibility as an explicit long-run power condition. - Added `cases/founder-opposition-rehearsal.md` with civic fire-drill / Tattoo Protocol logic. - Added `cases/epistemic-authority-corruption.md` for adversarial Kristal analysis. - Added **rehearsed counterpower** as a distinction from merely formal counterpower. - Strengthened founder decentering with an opposition test in addition to the absence test. - Clarified `Forkability ≠ Epistemic Equivalence`. - Added apparent-independence vs causal-independence analysis for citations and sources. - Added founder/persona, reference-stewardship, and citation-independence conversion firewalls. - Recorded architect-confirmed design directions for proposed reference Kristal stewardship and adversarial drills. ## 6.0 — Power Surface - Re-centered the repo on an immediate answer to **why kOA is immensely powerful**. - Added `POWER-SURFACE.md` and `POWER-ROUTING.md` as top-level maps. - Added `showcase/00-why-koa-is-immensely-powerful.md`. - Split political, economic, and monetary power into distinct domains. - Added 14 detailed domain profiles. - Added cross-domain conversion theory and maps. - Added explicit political/economic/monetary Power Show page. - Added Power Surface Audit plus `power-domain` and `power-surface` schemas. - Integrated ethical fiction, Koali protocolization, democratic allocation, self-hosting, and branch mobility into a single power-routing architecture. - Strengthened Power Conversion Firewalls in the front-stage narrative. - Preserved legacy KingCoin as a power-stacking stress test rather than current doctrine. ## 5.1 — Power Routing and Sharing - Made **“What makes kOA immensely powerful?”** answerable directly from the first section of the README. - Formalized the Power Show multiplier as **Breadth × Composition × Closure × Memory × Compounding × Replication**. - Added **Power Routing**, **Power Redirection**, **Power Sharing**, **Power Devolution**, **Self-Binding**, **Narrative Self-Binding**, **Protocolization**, **Ownership Decoupling**, and **Capability Commons**. - Added a new front-stage sequence: `Generate → Compose → Compound → Route → Share → Bind → Contest → Fork → Evolve`. - Added [`showcase/11-power-routing-and-sharing.md`](showcase/11-power-routing-and-sharing.md). - Added [`framework/09-power-routing-and-sharing.md`](framework/09-power-routing-and-sharing.md). - Added [`constitution/power-redirection-sharing.md`](constitution/power-redirection-sharing.md). - Added [`assessment/power-routing-audit.md`](assessment/power-routing-audit.md). - Added [`cases/ethical-fiction-self-binding.md`](cases/ethical-fiction-self-binding.md), grounded in S02's explicit living ethical code and anti-monopoly / anti-domination principles. - Added [`koa/koali-protocolization.md`](koa/koali-protocolization.md) to record the architect-confirmed intention that Koali become duplicable, shareable, branchable, and plural rather than a terminal personal credibility property. - Added `USER-CONFIRMED-DESIGN` as an epistemic label so current design intent is not misrepresented as source-derived or implemented fact. - Expanded the component power matrix with a **Power-routing / sharing mechanisms** column. - Reframed founder decentering as conversion of founder-specific assets into ecosystem capability, not merely founder limitation. ## 5.0 — kOA Power Show - Restored the repository's original front-facing purpose: **show all the major ways kOA can make individuals, groups, organizations, and federations more capable**. - Added top-level [`POWER-SHOW.md`](POWER-SHOW.md). - Added [`showcase/`](showcase/) as the guided presentation layer. - Reframed the repo around the sequence `Generate → Compose → Compound → Become Relationally Consequential → Govern → Evolve`. - Added the **capability spectrum** and scale path from individual to federation. - Added **composition engine**, **composition gain**, **capability surface**, **power surface**, and **capability-to-power transition** to the canonical glossary. - Made generated collective puissance a prominent concept. - Restored conversion chains, pre-political power, mnemonic power, counterpower, optionality, brand, network, economic, media, founder, and infrastructural capability to the visible Power Show. - Repositioned the ontology as a precision layer rather than the repository's primary narrative. - Reframed the constitution as **governance after capability**: the architecture exists to let kOA become powerful without making successful functions terminal sovereigns. - Reframed branch ecology as **evolutionary capability**, not only an emergency anti-capture mechanism. - Preserved the v4 three-axis analytical model and all major audit methods. ## 4.0 — Integrated Dynamics - Reconciled the original broad Power Dynamics theory with the later `Potential → Capacity → Puissance → Power` ontology. - Made dynamics first-class again. - Added the three-axis model: ontology × dynamics × domains. - Repositioned `Reservoir → Release → Flow → Mediation` as one mobilization dynamic rather than the overall architecture. - Restored pre-political power, mnemonic power, conversion firewalls, power stacking, capture, recognition loops, founder power, brand/affiliation, monetary/allocation power, and counterpower as central concepts. - Rebuilt the canonical glossary. ## 3.1 — Reservoir, Flow, and Mediation Added mobilization analysis for retained resources, release control, throughput, mediation, and media influence. ## 3.0 — Puissance / Power Ontology Separated resources, potential, capacity, puissance, and relational power. ## 2.x — Evolutionary Governance Developed branch ecology, complementarity, branch mobility, and non-terminal architecture. ## 1.x — Initial Power Dynamics Established power domains, conversion, stacking, capture, counterpowers, founder analysis, and kOA subsystem mapping. ================================================================================================ FILE: power_dynamics/constitution/authority-architecture.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 8ece80483108c18b85c47dd0ac5e187d7507d9f307f840bfb3388889117c0537 CONTENT_BYTES: 1619 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Authority Architecture: Scope, Separation, and Centrality" source_basis: - S15 - S16 - S17 - S18 - S21 - S25 - S28 --- # Authority Architecture: Scope, Separation, and Centrality Legitimate authority should specify domain, function, jurisdiction, duration, basis, conditions, review, delegation, and revocation. Authority in one domain should not automatically travel to another. A technical maintainer may authorize releases without deciding political outcomes. An expert may provide domain-bounded advice without receiving universal civic superiority. Separation of functions limits conversion by assigning distinct responsibilities to distinct components or roles. Examples include separating credibility from vote results, narrative from legitimacy, execution from mandate creation, protocol commons from brand stewardship, and AI assistance from final authority. Healthy systems also need not be centerless. A useful pattern is: > **StrongHub + DistributedCapability + ReplicableWhole** Important distinctions: - Functional centrality ≠ domination - Centralized access ≠ centralized truth - Strong center ≠ total sovereignty - Federation ≠ flatness - Local sovereignty ≠ absence of a local center - Composition does not require ownership - Creator-owned channel ≠ mandatory dependency - Independent reproducibility ≠ founder removal The constitutional question is whether actors can verify, substitute, reproduce, branch, and continue when the center changes or fails. ================================================================================================ FILE: power_dynamics/constitution/branch-evolution.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: cc34a964e51576812c86ec85c96a89a75ec7764c2028727392c5aac515321ca3 CONTENT_BYTES: 897 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Constitutional Branch Evolution" source_basis: - S13 - S16 - S19 - S25 --- # Constitutional Branch Evolution A stable kernel protects the ability to diverge without losing all comparability. The stable layer may include provenance formats, identifiers, versioning, signatures, interoperability contracts, or minimum audit requirements. Branches may diverge in policies, criteria, ontologies, interfaces, rankings, governance, and implementation. **Branch mobility** measures whether an alternative can become consequential. A branch may technically exist but remain irrelevant if it cannot be found, imported, supported, recognized, funded, deployed, or integrated. The goal is: > **stability at the level of evolutionary capacity, diversity at the level of implementation** ================================================================================================ FILE: power_dynamics/constitution/conversion-firewalls.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: db2b9f09eaa7c670a2487f599cd451b5fca80b9edd2e4a385e468eb3fe7a9963 CONTENT_BYTES: 1107 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Power-Conversion Firewalls" source_basis: - S15 - S17 - S21 - S22 - S28 --- # Power-Conversion Firewalls A conversion firewall permits useful composition while blocking automatic cross-domain authority. Canonical examples: - `Expertise → Advice`, not `Expertise → Sovereignty`. - `Money → Funding`, not `Money → More Votes`. - `Brand → Attention`, not `Brand → Truth`. - `Technical Administration → Maintenance`, not `Administration → Political Outcome Control`. - `Credibility → Discoverability`, not `Credibility → Unquestionable Authority`. - `Founder / Persona → Attention`, not `Founder / Persona → Truth or Policy Immunity`. - `Reference Stewardship → Maintained Reference`, not `Reference Stewardship → Monopoly on Reality`. - `Many Citations → Apparent Support`, not `Many Citations → Independent Evidence` unless lineage supports independence. Firewalls should be auditable and testable at implementation level, not only stated as principles. ================================================================================================ FILE: power_dynamics/constitution/counterpowers-and-legibility.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 0c7155f9450b6390afa531d175b60739029cee85fe3e542ded9c1f7d90027b48 CONTENT_BYTES: 1603 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Counterpowers, Legibility, Provenance, and Auditability" source_basis: - S01 - S13 - S16 - S19 - S21 - S25 --- # Counterpowers, Legibility, Provenance, and Auditability A minimum counterpower package is: > **Verification + Contestation + Substitution + Exit** Power should also be legible enough that affected actors can identify the relevant holder, mechanism, mandate, inputs, outputs, version, and appeal path. **Provenance** preserves where claims, artifacts, decisions, and transformations came from. **Auditability** allows independent reconstruction or verification. Transparency is not sufficient by itself. A transparent system that cannot be contested or substituted can remain dominating. Complexity is not inherently illegitimate either; the problem is complexity functioning as an unanswerable source of authority. ## Rehearsed counterpower Counterpower can be formally available yet socially unusable. A community may possess appeal, fork, exit, or objection mechanisms that no one knows how to activate against a prestigious internal authority. Power Dynamics therefore distinguishes **available counterpower** from **rehearsed counterpower**. Deliberate drills can create procedural memory, lower the symbolic cost of dissent, expose coordination failures, and establish legitimate opposition as normal system behavior. ```text formal right → practiced procedure → remembered precedent → lower activation cost → stronger effective counterpower ``` ================================================================================================ FILE: power_dynamics/constitution/federation-subsidiarity.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 527ad2d9212d6e84f140adc995c96fbb25757af8a740bc0201efe39121c081b8 CONTENT_BYTES: 674 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Federation and Subsidiarity" source_basis: - S16 - S25 --- # Federation and Subsidiarity Federation coordinates independently governed nodes through shared contracts rather than requiring a flat or centerless architecture. Subsidiarity places decisions at the lowest level capable of handling them effectively while preserving necessary coordination. The repo rejects `federation = no center`. Strong local hubs, shared standards, and central reference services can coexist with local sovereignty if substitution and independent operation remain meaningful. ================================================================================================ FILE: power_dynamics/constitution/founder-decentering.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 9f115b3b0e38563eef5cd994452affab4eae4b415e7df75f4f889741ee330b75 CONTENT_BYTES: 2313 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Founder Decentering" source_basis: - S18 - S25 --- # Founder Decentering Founder power can arise from authorship, vocabulary, repositories, domains, brand, relationships, keys, architecture knowledge, and interpretive authority. The goal is not necessarily founder removal. It is independent reproducibility: > **Founder → Architecture → Distributed Mastery** rather than: > **Founder → Permanent Interpretive Dependency** Useful phases include founder sovereignty, constitutional constraints, maintainer pluralism, institutional federation, and protocol-level continuity. ## Power redirection, not only founder limitation Founder decentering can be designed as a productive conversion rather than simple loss of control: ```text founder knowledge → documentation / schemas / protocols → shared implementation capacity founder infrastructure → portable deployments / federation → local operational autonomy founder-created credibility mechanism → interoperable Koali distributions → plural credibility capacity founder narrative → published ethical constraints → public self-binding and reinterpretability ``` This is **power redirection**: leverage that could remain attached to the founder is converted into capability that other actors can reuse independently. ## Founder fallibility and opposition rehearsal Independent reproducibility is necessary but not sufficient. A community can reproduce the system technically while remaining socially dependent on the founder's interpretive or symbolic authority. The stronger criterion is: > **The system can continue when the founder is absent, and it can correct the founder when the founder is present and wrong.** This adds a distinct transition: ```text founder centrality → published limits → practical contestation → rehearsed opposition → precedent of legitimate disagreement → lower symbolic dependency ``` Founder error should be treated as an expected long-run condition, not an exceptional edge case. A durable system should therefore make disagreement, amendment, branch formation, and opposition procedurally and culturally usable before they become necessary in a high-stakes crisis. ================================================================================================ FILE: power_dynamics/constitution/non-domination-terminality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6fc05944ad5d1f849f7adce22019174e4adb06017ff746a855e1b308f5752214 CONTENT_BYTES: 714 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Non-Domination and Non-Terminality" source_basis: - S16 - S19 - S21 - S25 --- # Non-Domination and Non-Terminality Non-domination means more than absence of current interference. A relationship is problematic when an actor remains exposed to discretionary power it cannot meaningfully verify, contest, substitute, or exit. The repository extends this into **non-terminality**: capture of one institution, branch, deployment, or maintainer should not automatically make the broader ecosystem unrecoverable. `Instance Capture ≠ System Capture` is therefore a design objective, not a guarantee. ================================================================================================ FILE: power_dynamics/constitution/power-redirection-sharing.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 963a87598e4a453fc732dcff16690574e8a0f0643df792e496855e699b7559bb CONTENT_BYTES: 3801 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Power Redirection and Sharing" source_basis: - S02 - S14 - S15 - S16 - S17 - S19 - S21 - S22 - S25 --- # Power Redirection and Sharing The Power Constitution is not only defensive. It does not wait for a powerful center to emerge and then attempt to constrain it. It also asks how architecture can **redirect leverage before it becomes terminal**. ## Constitutional objective > **Generate strong distributed puissance, route its returns and control deliberately, and prevent useful coordination from becoming exclusive sovereignty.** ## Six constitutional mechanisms ### 1. Conversion firewalls Prevent one legitimate form of capability from silently becoming unrelated authority. ### 2. Power routing Specify where capability, authority, returns, and optionality are intended to accumulate. ### 3. Self-binding Make principles, procedures, limits, and revision rules public enough that later behavior can be compared against them. ### 4. Protocolization Translate unique personal or institutional mastery into reusable, testable, and independently implementable forms. ### 5. Devolution and plurality Permit local operation, multiple distributions, branches, reader policies, or implementations rather than one mandatory operator. ### 6. Counterpower Preserve verification, contestation, substitution, exit, forkability, and branch mobility when routing fails or capture occurs. ## Public ethics as a power mechanism Publishing ethical principles in a symbolic or fictional layer is politically relevant when the symbolic layer itself creates influence. The mechanism is: ```text narrative puissance → explicit public commitments → interpretable limits → expectations and criticism → self-binding of symbolic authority ``` This is stronger than private intention because the commitment becomes externalized and reusable by others. It remains weaker than enforceable institutional governance unless tied to procedures, audit, recourse, or material control. ## Protocol commons and founder power A founder may legitimately create, coordinate, steward, or brand a system while still redirecting much of the system's practical capability outward. The desired transition is: > **Founder-powered → Architecture-powered → Protocol-powered → Ecosystem-powered** Independent reproducibility is the key test. ## Koali as a power-sharing test Credibility infrastructure is especially sensitive because it can affect opportunity, standing, discoverability, and access. A non-terminal design should make it possible for multiple Koali distributions or compatible implementations to exist without one founder or operator owning the only meaningful credibility layer. The audit questions are: - Can another group instantiate the function? - Can evidence and history move? - Can policy differ while identity and provenance remain interpretable? - Can alternative distributions become discoverable and viable? - Can one operator deny interoperability to all competitors? - Does the official brand control the protocol, or only a particular distribution? ## Failure modes Power-sharing language can hide concentration if: - the code is open but the registry is not; - forks exist but network access does not; - principles are public but behavior is not auditable; - data is portable but identity or reputation is not; - local hosting exists but updates require one signing authority; - multiple credibility models exist but one platform controls discoverability; - democratic allocation exists but capital controls eligibility upstream. For that reason, power redirection must be assessed as an **effective system property**, not a slogan. ================================================================================================ FILE: power_dynamics/constitution/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b44adc345ae62721a692ef674dfdd1606de87f8ed8b6ed31eac4160556cc84b2 CONTENT_BYTES: 1853 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Power Constitution" source_basis: - S16 - S18 - S21 - S25 --- # Power Constitution The constitution exists **because the Power Show succeeds**. The objective is not to make kOA weak. It is to make strong capability compatible with weak, scoped, and non-terminal sovereignty. > **Strong puissance. Weak sovereignty.** A power constitution governs how useful capability may be: - exercised; - composed; - converted; - concentrated; - challenged; - revoked; - transferred; - substituted; - forked; - replaced. ## Constitutional problem A successful capability layer can become a gate: ```text discovery → ranking power credibility → standing power workflow → administrative power identity → access power standards → compatibility power memory → precedent power AI → interpretive power infrastructure → dependency power ``` The architecture must therefore make emerging power legible before it becomes terminal. ## Constitutional core - **non-domination and non-terminality**; - **scoped authority and separation of functions**; - **power-conversion firewalls**; - **Verification + Contestation + Substitution + Exit**; - **revocability, reversibility, portability, and effective exit**; - **federation and subsidiarity**; - **stable kernels with evolving branches**; - **founder decentering without requiring founder erasure**. Useful centers are compatible with this model. The issue is not centrality itself but whether the rest of the system remains practically capable without permanent submission to that center. - [`power-redirection-sharing.md`](power-redirection-sharing.md) — redirecting leverage before it becomes terminal and sharing capability through protocolization, plurality, and devolution. ================================================================================================ FILE: power_dynamics/constitution/revocability-exit-portability.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 19eda7fbdb5358adfec997df0037428aea244453485b0c59728aaf923783d686 CONTENT_BYTES: 1066 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Revocability, Reversibility, Exit, Fork, and Portability" source_basis: - S16 - S19 - S21 - S25 --- # Revocability, Reversibility, Exit, Fork, and Portability Revocation removes future authority. Reversal addresses prior effects. They are different. A ranking rule can be changed while earlier reputational effects persist. A decision-maker can be removed while contracts, debts, or standards remain. Exit and fork are structural counterpowers only when effective. Portability can include data, knowledge artifacts, identity, credentials, reputation evidence, decision history, operational records, schemas, protocols, and deployment tooling. A technically forkable project can remain practically monopolistic if forks lose recognition, network access, compatibility, or essential assets. Constitutional analysis should therefore ask both whether authority can be revoked and whether affected actors can actually migrate, recover, or continue. ================================================================================================ FILE: power_dynamics/CONTRIBUTING.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: e0f9a34ac5236e4df6d90c3e36e2141895234132ec3e0b324010f15fc58b8fe1 CONTENT_BYTES: 2587 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Contributing" --- # Contributing Contributions should preserve both faces of the repository: 1. **Power Show clarity** — make concrete what a capability enables; 2. **Power Dynamics rigor** — distinguish capability from the relations of power created around it. ## Before adding a concept Ask six questions: 1. **What becomes possible?** What practical capability does the mechanism create or amplify? 2. **What is its ontological state?** Resource, potential, capacity, puissance, power relation, effect, or return? 3. **What dynamic is occurring?** Formation, mobilization, composition, conversion, reinvestment, capture, diversification, decay, transfer, etc.? 4. **In which domain does it occur?** Keep political, economic, and monetary domains distinct where relevant. 5. **What can it convert into?** Name important cross-domain conversion paths and firewalls. 6. **Where does the power go?** Identify the destinations of capability, authority, returns, and optionality. Avoid shorthand such as `money = power`, `expertise = authority`, or `brand = legitimacy`. Trace the mechanism. ## Power Show additions A new showcase claim should state: - the baseline limitation; - what kOA component or mechanism changes it; - what new puissance becomes available; - how it composes with other capabilities; - what power relations can emerge if the capability becomes consequential; - how the capability or leverage is routed; - what cross-domain conversions are possible; - what counterpowers or scope limits apply. Do not turn aspirational capability into an unsupported deployment claim. Use the repository's maturity and claim-type labels. ## Evidence A claim should identify at least one of: - source IDs from [`sources/corpus-map.md`](sources/corpus-map.md); - direct technical evidence; - explicit analytical reconstruction; - external research, clearly labeled. ## Branches and disagreement Do not rewrite disagreement into artificial consensus. Preserve divergence and state the scope, evidence, trade-offs, and conditions of each claim. ## Metrics Avoid false precision. Prefer multidimensional assessment to universal scores when constructs are not directly measurable. ## Architect-confirmed design claims When a current design intention has been confirmed by the project architect but is not yet documented in the canonical corpus or implementation evidence, label it `USER-CONFIRMED-DESIGN` and state what technical evidence is still required. ================================================================================================ FILE: power_dynamics/domains/01-political-constitutional.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 3c7bb0cfb688fb062bd1a8af51dc7c3bcd4eecd7d79a9d707424bae5e3801879 CONTENT_BYTES: 1704 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Political and Constitutional Power" source_basis: - S15 - S17 - S18 - S21 - S22 - S25 - S28 --- # Political and Constitutional Power Political / constitutional power concerns standing, legitimacy, mandate, representation, agenda, decision rights, veto, amendment, jurisdiction, and the authority to bind collective action. ## kOA power surface kOA can increase political puissance by making publics better able to frame issues, discover evidence, compare proposals, expose advisory readings, make decisions, route implementation, and preserve institutional memory. The canonical chain is: > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** This makes political power partly **pre-political**: control of categories, discovery, ranking, and credibility can shape what reaches formal decision. ## Main relational powers - agenda power; - decision power; - mandate power; - veto / amendment power; - legitimacy power; - administrative implementation power; - precedent power. ## kOA safeguards - political equality as baseline; - expertise as bounded advice rather than sovereignty; - explicit lenses and multiple readings; - scoped authority; - auditability and recourse; - branch mobility and institutional alternatives. ## Key conversion risks ```text credibility → political authority money → political standing technical administration → policy control narrative popularity → legitimacy ``` These are precisely the kinds of conversions Power Conversion Firewalls are meant to expose. ================================================================================================ FILE: power_dynamics/domains/02-economic-allocation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: fb3077e0edb0bfaac4ffb72eb67f5862debc1f98d72135e584e559de7a77fe60 CONTENT_BYTES: 1461 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Economic and Allocation Power" source_basis: - S10 - S14 - S26 --- # Economic and Allocation Power Economic puissance is the effective ability to mobilize scarce material resources for action. Economic power appears when control of resources changes others' access, bargaining position, options, or dependency. ## Resources - money; - property; - productive assets; - labor and time; - contracts; - funding; - procurement; - infrastructure; - philanthropy; - market access. ## kOA pathways ```text knowledge → credibility → opportunity → income network → collaborators → execution → output → funding brand → attention → affiliation → revenue money → infrastructure → capability collective activity → returns → shared assets → greater future capability ``` ## Allocation power Allocation power is the relational power to determine which people, projects, institutions, or goals receive resources. Zero-Skim is important because it attempts to route: > **Economic contribution → common resource pool → democratic allocation** rather than: > **Economic contribution → proportional political authority** ## Main risks - donor / funder capture; - capital → governance conversion; - infrastructure dependency; - property bottlenecks; - returns flowing narrowly to an operator instead of participants. ================================================================================================ FILE: power_dynamics/domains/03-monetary-credit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 42d2d44ce08b9173e8d8f091a3b0ccbf3e44298d0253b40d9a52d2bb41a2f895 CONTENT_BYTES: 1303 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Monetary, Credit, and Liquidity Power" source_basis: - S09 - S11 --- # Monetary, Credit, and Liquidity Power Monetary power is not identical to economic power. It concerns control over the infrastructure and conditions of exchange. ## Monetary surfaces - currency issuance; - units of account; - liquidity; - settlement; - payment rails; - reserves; - convertibility; - credit access; - debt terms; - transaction permissions. A monetary operator can alter effective possibility without owning all underlying economic assets because other actors depend on the rail itself. ## Why it is high leverage ```text rail access → ability to transact → business continuity → economic dependency → bargaining / political leverage ``` ## Legacy stress test KingCoin legacy proposals combine monetary governance, taxation, redistribution, sanctions, public investment, and dispute enforcement. In current doctrine this is not a recommendation; it is a useful demonstration of **power stacking and terminality risk**. ## Current constitutional lesson > Powerful monetary functions require especially strong separation, substitution, transparency, and limits on cross-domain conversion. ================================================================================================ FILE: power_dynamics/domains/04-epistemic-semantic.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 9525cb058fe7c0abf741e7d7f39cc4d98d105c7ad8558e0b11b51f6505d4e50a CONTENT_BYTES: 1480 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Epistemic and Semantic Power" source_basis: - S13 - S16 - S18 - S22 - S25 - S28 --- # Epistemic and Semantic Power Epistemic puissance is the ability to produce, validate, compare, preserve, and reuse knowledge. Semantic puissance is the ability to structure concepts, categories, relations, translation, and ambiguity. ## kOA mechanisms - Kristal; - provenance and lineage; - trust roots / reader policies; - SemantiK Architect; - SenTient; - multilingual structures; - competing and complementary Kristals. ## Power relations - validation power; - canonization power; - classification power; - framing power; - admissibility power; - trust-root power; - apparent-consensus power; - provenance-obscuration power. ## Core insight > **To govern meaning is already to govern the collective.** Definitions affect what can count as harm, evidence, competence, fairness, or action-worthy knowledge. ## Counterpower Versioning, provenance, alternative readers, competing representations, local semantic governance, portability, and contestation keep epistemic capability from becoming ownership of truth. A further requirement is **causal-lineage legibility**: source count, citation count, credentials, popularity, and institutional presentation should not be treated as independent evidence when they derive from the same origin or cannot be verified. ================================================================================================ FILE: power_dynamics/domains/05-information-attention-media.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 4dd7f7dabfd647511f55881bf36c943f8d66940a73bc73d1c88d309a38e695ca CONTENT_BYTES: 981 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Information, Attention, and Media Power" source_basis: - S13 - S15 - S18 - S21 - S25 --- # Information, Attention, and Media Power Information and media puissance includes the ability to publish, package, search, rank, recommend, moderate, synchronize, and amplify signals. ## Relational powers - visibility power; - discoverability power; - agenda power; - moderation power; - framing power; - attention power. Konnaxion matters because discoverability is not merely convenience. What becomes findable can become reusable, fundable, discussable, and politically salient. ## Risk A system can preserve formal freedom of speech while controlling practical visibility. ## Counterpower Explicit discovery policies, alternative ranking/discovery layers, portability, federation, transparency, and branch discoverability reduce terminal control of attention. ================================================================================================ FILE: power_dynamics/domains/06-credibility-reputation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 19fdba100531596dbb055a73f70192ffd03cd22a8259dba8e4e2ecb7cb9d65e0 CONTENT_BYTES: 1863 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Credibility, Reputation, and Certification Power" source_basis: - S15 - S17 - S18 - S25 - S28 --- # Credibility, Reputation, and Certification Power Credibility infrastructure makes evidence about expertise, contribution, conduct, or reliability legible. That is useful capability, but it can become standing power. ## kOA mechanisms - Koali; - EkoH; - evidence histories; - domain-bounded policies; - SmartVote advisory readings; - certification / attestation structures. ## Main distinction > **Score ≠ person ≠ competence ≠ ethics ≠ truth.** > > **Credential claim ≠ verified credential. Popularity ≠ evidence. Citation count ≠ independent confirmation.** A system should produce governed readings of evidence, not claim perfect measurement of human worth. ## Conversion risks ```text credibility → visibility credibility → opportunity credibility → funding credibility → political influence ``` These can be useful, but should not silently become universal authority. ## Routing direction Koali is intended to move toward plural distributions, portable evidence, explicit policy identity, interoperability, and independent operation rather than terminal founder ownership. ## Authority-signal corruption Credibility systems are vulnerable when surface signals can be converted into standing without tracing their basis. Titles, publication formats, follower counts, endorsements, and citation volume can all create useful heuristics, but they can also be manufactured, inherited, or recursively amplified. The constitutional objective is not to eliminate heuristics. It is to prevent **prestige signals from silently becoming truth claims** and to preserve enough provenance for independent evaluation. ================================================================================================ FILE: power_dynamics/domains/07-network-affiliation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 568aec0bae262b1d03069a02ac0b36bfd37d31562b0a7e6d8924e23ca025fdae CONTENT_BYTES: 1006 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Network and Affiliation Power" source_basis: - S02 - S13 - S18 - S25 - S26 --- # Network and Affiliation Power Network puissance is the ability to mobilize relationships for access, diffusion, recruitment, coalition, collaboration, or action. ## Resources - relationships; - memberships; - trust links; - brokerage positions; - audiences; - institutional access; - affiliation with brands or communities. ## kOA effects Konnaxion, brand, public contribution, credibility, and project collaboration can convert isolated capability into networked capability. ```text knowledge → contribution → recognition → network → opportunity → execution ``` ## Relational powers - brokerage power; - inclusion / exclusion power; - affiliation power; - recruitment power; - access power. Network power compounds because every successful collaboration can create new future pathways. ================================================================================================ FILE: power_dynamics/domains/08-administrative-operational.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c71835c94f154835ee9d1bdabb694340854026e3f9ba3bee1fb45e801c6cb8e4 CONTENT_BYTES: 972 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Administrative and Operational Power" source_basis: - S13 - S18 - S21 - S25 --- # Administrative and Operational Power Administrative puissance is the ability to route, assign, schedule, validate, escalate, record, and close work. Operational puissance is the ability to turn decisions into coordinated execution. ## Orgo surface ```text decision → task → owner → routing → deadline → escalation → action → closure → memory ``` ## Relational powers - assignment power; - timing power; - approval power; - escalation power; - closure power; - workload power. ## Political significance Administration can change outcomes without formally changing policy. Therefore: > **Execution ≠ mandate redefinition.** Scoped roles, audit trails, appeal, revocability, and explicit decision-to-work boundaries are constitutional requirements. ================================================================================================ FILE: power_dynamics/domains/09-technical-infrastructural.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 7b6d00d9690ab770774eba0b8ce240360dae0b582fcf1e7571ccb78025a1b58f CONTENT_BYTES: 1000 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Technical and Infrastructural Power" source_basis: - S13 - S16 - S25 --- # Technical and Infrastructural Power Technical puissance is the ability to build, modify, verify, deploy, repair, and reproduce systems. Infrastructural puissance is capability created by reliable shared systems and protocols. ## Power surfaces - code repositories; - signing keys; - identity rails; - registries; - APIs; - standards; - deployment topology; - hosting; - update channels; - compatibility rules. ## Relational powers - access power; - compatibility power; - update power; - dependency power; - standards power. ## kOA routing direction Self-hosting, offline capability, capsules, verification, rollback, federation, portability, and substitution seek to convert infrastructure into **local capability rather than terminal operator dependency**. > **Instance capture ≠ system capture.** ================================================================================================ FILE: power_dynamics/domains/10-narrative-symbolic-brand.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 05e1bbc7047ab8d87f954fad1ee80557f70f15665765091dfa790cbb7d1550e1 CONTENT_BYTES: 1244 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Narrative, Symbolic, and Brand Power" source_basis: - S02 - S04 - S23 --- # Narrative, Symbolic, and Brand Power Narrative puissance makes complex systems memorable, transmissible, culturally legible, and capable of affiliation. Brand puissance can convert recognition into attention, trust, distribution, commerce, or coordination. ## Conversion chains ```text narrative → attention → affiliation → mobilization brand → recognition → merchandise / funding → infrastructure symbol → memory → identity → network ``` ## Relational risks - charisma replacing procedure; - brand becoming truth; - symbolic centrality becoming founder worship; - trademark control becoming protocol control. ## Ethical self-binding The source fiction explicitly publishes a living ethical code, vigilance against monopoly and domination, recognition and shared merit, self-mockery, criticism, revision, and non-dogmatic transmission. This is treated as **narrative self-binding**: the channel that creates symbolic power also carries public constraints on that power. Narrative is legitimate as **function, not sovereign**. ================================================================================================ FILE: power_dynamics/domains/11-cognitive-ai.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ff5193c9011f452360b13cea360dfafa25993cb3f20038782e7bc9262d800003 CONTENT_BYTES: 998 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Cognitive and AI-Mediated Power" source_basis: - S13 - S16 - S25 --- # Cognitive and AI-Mediated Power Cognitive puissance is the effective ability to reason, synthesize, model, plan, generate, compare, interpret, and learn. AI can multiply cognitive throughput, especially when combined with structured knowledge, provenance, memory, and workflow. ```text AI + Kristal + policy + human judgment → higher cognitive throughput ``` ## Risks - hidden framing; - silent prioritization; - opaque synthesis; - model dependency; - AI-generated defaults becoming policy; - cognitive convenience becoming hidden sovereignty. ## Principle > **AI assists under governance; it does not silently acquire governance.** The key question is not whether AI is powerful. It is whether its cognitive amplification remains subordinate to explicit authority and reconstructible evidence paths. ================================================================================================ FILE: power_dynamics/domains/12-mnemonic-temporal.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 03f313f6fdcc0c83e16c37620efd7735ad65ec81d9fb851fc62b3a0d055816e6 CONTENT_BYTES: 1039 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Mnemonic and Temporal Power" source_basis: - S13 - S18 - S25 - S26 --- # Mnemonic and Temporal Power Mnemonic puissance is the ability to preserve and reuse reasons, knowledge, decisions, actions, failures, provenance, and outcomes across time. ## Compounding role ```text action → experience → memory → lower future coordination cost → better action ``` Memory is therefore a production factor, not merely an archive. ## Relational power Control of memory can shape: - precedent; - institutional interpretation; - which failures are remembered; - which actors receive recognition; - what counts as historical continuity. Temporal power also includes control over timing, delay, deadlines, release, expiry, succession, and disclosure. ## Counterpower Provenance, versioning, portable history, alternative representations, succession planning, and release optionality make temporal power more governable. ================================================================================================ FILE: power_dynamics/domains/13-evolutionary-counterpower.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a1264bbd73d7fb42e3eeeb812d8ac0f4c0000943b3b001244eb66d498ede37e3 CONTENT_BYTES: 1070 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Evolutionary Power and Counterpower" source_basis: - S16 - S18 - S21 - S22 - S25 - S28 --- # Evolutionary Power and Counterpower Evolutionary puissance is the practical ability to improve, fork, substitute, recombine, or replace systems and institutions. This is not merely emergency resistance to corruption. It is a normal mechanism of institutional experimentation. ```text imperfection / opportunity → criticism → variation → demonstration → comparison → support → coexistence / merge / replacement → further variation ``` ## Core counterpowers > **Verification + Contestation + Substitution + Exit** ## Branch mobility Formal forkability is insufficient. A better branch must be able to: - preserve data and provenance; - remain interoperable; - gather maintainers and support; - become discoverable; - operate independently; - influence or replace a dominant branch. The goal is **improvement without final authority**. ================================================================================================ FILE: power_dynamics/domains/14-property-territorial.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 8e8a26b5f79e46a11019a471afb7dd04ab5afa2496b50b7158281e57c2c22dda CONTENT_BYTES: 1188 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Property and Territorial Power" source_basis: - S01 - S10 - S13 --- # Property and Territorial Power Property and territorial power arise from enforceable control over scarce physical assets, land, facilities, infrastructure locations, housing, intellectual property, or jurisdictional access. This domain is less specific to current kOA software than other domains, but it remains necessary in a general systems theory of power because digital capability ultimately depends on material substrates. ## Conversion chains ```text property → exclusion / access → economic leverage physical infrastructure → service continuity → dependency IP rights → licensing conditions → technical / economic leverage jurisdiction → legal authority → operational constraints ``` ## kOA relevance Power Dynamics should track whether supposedly distributed systems remain materially dependent on a small set of datacenters, institutions, domains, signing credentials, trademarks, or physical operators. Formal software openness does not eliminate material bottlenecks. ================================================================================================ FILE: power_dynamics/domains/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 1ddb0c150e52335bf55393a7f38b5bdfb801921ad1e72869481d192c018ed721 CONTENT_BYTES: 3688 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Power Domains" source_basis: - S01 - S02 - S10 - S13 - S14 - S15 - S16 - S17 - S18 - S21 - S22 - S25 - S26 --- # Power Domains Domains answer **where** resources, capability, puissance, and relational power operate. Version 6 separates domains that were previously grouped too loosely, especially: > **Political ≠ Economic ≠ Monetary** The distinction matters because the mechanisms, mandates, risks, and counterpowers differ. ## Domain map | Domain | Core question | Detailed page | |---|---|---| | Political / constitutional | Who can decide, bind, represent, amend, veto, or define legitimate public standing? | [`01-political-constitutional.md`](01-political-constitutional.md) | | Economic / allocation | Who can mobilize scarce material resources and decide where they go? | [`02-economic-allocation.md`](02-economic-allocation.md) | | Monetary / credit / liquidity | Who controls exchange rails, issuance, settlement, reserves, liquidity, or credit conditions? | [`03-monetary-credit.md`](03-monetary-credit.md) | | Epistemic / semantic | Who can shape what is knowable, valid, categorized, translated, or admissible? | [`04-epistemic-semantic.md`](04-epistemic-semantic.md) | | Information / attention / media | Who can make things visible, discoverable, amplified, ranked, or ignored? | [`05-information-attention-media.md`](05-information-attention-media.md) | | Credibility / reputation | Who can shape standing, trust signals, certification, or opportunity? | [`06-credibility-reputation.md`](06-credibility-reputation.md) | | Network / affiliation | Who can broker access, recruit, include, exclude, connect, or mobilize relationships? | [`07-network-affiliation.md`](07-network-affiliation.md) | | Administrative / operational | Who can route, assign, delay, approve, escalate, execute, or close? | [`08-administrative-operational.md`](08-administrative-operational.md) | | Technical / infrastructural | Who can build, update, host, sign, standardize, interoperate, or withdraw infrastructure? | [`09-technical-infrastructural.md`](09-technical-infrastructural.md) | | Narrative / symbolic / brand | Who can shape memory, affiliation, framing, identity, or symbolic legitimacy? | [`10-narrative-symbolic-brand.md`](10-narrative-symbolic-brand.md) | | Cognitive / AI | Who or what can shape reasoning, synthesis, modeling, and automated interpretation? | [`11-cognitive-ai.md`](11-cognitive-ai.md) | | Mnemonic / temporal | Who controls memory, precedent, timing, release, delay, expiry, or succession? | [`12-mnemonic-temporal.md`](12-mnemonic-temporal.md) | | Evolutionary / counterpower | Who can contest, substitute, fork, recombine, and replace? | [`13-evolutionary-counterpower.md`](13-evolutionary-counterpower.md) | | Property / territorial | Who controls scarce physical or legal assets and the right to exclude? | [`14-property-territorial.md`](14-property-territorial.md) | ## Domain rule Avoid statements such as “X is more powerful than Y” without specifying: > **powerful in what domain, through what resource, capacity, relation, mechanism, duration, conversion path, and counterpower environment?** ## Cross-domain analysis The most important questions often concern transitions between domains: ```text knowledge → credibility credibility → visibility visibility → agenda money → infrastructure infrastructure → dependency brand → affiliation administration → de facto policy ``` See [`../framework/10-cross-domain-power-conversion.md`](../framework/10-cross-domain-power-conversion.md). ================================================================================================ FILE: power_dynamics/dynamics/01-formation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a61f69fc3f729ac0b0fd83ea0847e05c628d2fa9f92c4f6958f75fddbdf51317 CONTENT_BYTES: 860 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Formation" source_basis: - S01 - S13 - S18 - S25 - S26 --- # Formation Formation is the process through which resources become organized capacity and effective puissance. Typical transitions: `information → knowledge` `practice → expertise` `money → liquid capacity` `relationships → network capacity` `code → technical capability` `rules → institutional capacity` `memory → lower future learning cost` Formation has costs: time, attention, education, infrastructure, coordination, verification, maintenance, and trust. Actors with similar resource stocks can therefore have very different effective puissance. A central kOA ambition is to reduce the loss between dispersed resources and usable collective capacity. ================================================================================================ FILE: power_dynamics/dynamics/02-mobilization.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f94d268e3a4ad7117d2e0e79892a9fb239d1616f540729b8a89caab4b6c9a9c0 CONTENT_BYTES: 1275 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Mobilization: Reservoir, Release, Flow, and Mediation" source_basis: - S13 - S15 - S18 - S21 - S22 - S25 --- # Mobilization: Reservoir, Release, Flow, and Mediation Mobilization explains how retained resources or existing puissance become externally effective. > **Reservoir / Retention → Release → Flow / Throughput → Mediation / Amplification → Relation or Effect** This is **one dynamic inside Power Dynamics**, not the architecture of the whole field. - **Reservoir** — accumulated resources retained for possible future use. - **Release** — disclosure, deployment, spending, publication, delegation, or activation. - **Flow / throughput** — rate at which resources and puissance become action, distribution, coordination, or effects. - **Mediation / amplification** — selection, ranking, translation, framing, routing, synchronization, and multiplication. A large unpublished corpus can have high epistemic stock and optionality while producing little public effect until organized, released, distributed, understood, and reused. Media demonstrate the inverse: very high distribution throughput can create large agenda effects. ================================================================================================ FILE: power_dynamics/dynamics/03-composition-generated-puissance.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: cf4739b0f5ebb549a04fdaba4610b3f115d5c897a5f9d7c0acdf03c5323a310a CONTENT_BYTES: 986 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Composition and Generated Puissance" source_basis: - S13 - S18 - S21 - S25 - S26 --- # Composition and Generated Puissance Composition combines distinct capacities to create higher-order capability. `expertise + local knowledge + coordination → project capacity` `knowledge + translation + distribution → multilingual reach` `code + governance + deployment → operational infrastructure` `money + network + technical capacity → implementation capacity` The resulting **generated puissance** may exist nowhere individually. This is why collective intelligence can become a new pole of capability. Composition does not require ownership. Independent systems can compose through explicit contracts. The risk appears when the orchestration layer becomes a necessary bottleneck and silently inherits authority over the resources or decisions being composed. ================================================================================================ FILE: power_dynamics/dynamics/04-conversion-and-firewalls.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c400a2ce7708722101609a0fa8a47307fc51e97935bfcd83c18c46a085a45b47 CONTENT_BYTES: 1324 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Conversion and Power-Conversion Firewalls" source_basis: - S15 - S17 - S21 - S22 - S28 --- # Conversion and Power-Conversion Firewalls Conversion is one of the most important dynamics in Power Dynamics. Examples: `knowledge → credibility → visibility → opportunity` `money → infrastructure → distribution → influence` `brand → attention → affiliation → revenue` `technical administration → defaults → agenda leverage` `adoption → dependency → standard-setting power` The question is not whether conversion exists but **which conversions are visible, legitimate, bounded, and contestable**. Canonical firewalls: | Useful conversion | Prohibited automatic conversion | |---|---| | expertise → advice | expertise → universal sovereignty | | money → funding | money → extra votes | | brand → attention | brand → truth | | credibility → discoverability | credibility → unquestionable authority | | administration → maintenance | administration → self-expanding mandate | | narrative → mobilization | narrative → legitimacy by itself | Different forms of puissance should remain composable without becoming silently convertible into unrelated power. ================================================================================================ FILE: power_dynamics/dynamics/05-returns-reinvestment-compounding.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 8e10b507e845a6405d67fe9554448c5a68992ded63254ed0e47431fe7c0749e2 CONTENT_BYTES: 1123 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Returns, Reinvestment, and Compounding" source_basis: - S13 - S21 - S25 - S26 --- # Returns, Reinvestment, and Compounding Action can leave reusable assets behind. > **Puissance → Action → Result → Return → Reinvestment → Greater Future Puissance** Returns include money, code, tools, experience, methods, evidence, data, memory, credibility, relationships, brand recognition, standards, and optionality. The key question is: > **Who receives the returns generated by collective activity?** An extractive system may channel collective activity into assets controlled by a narrow owner. An empowering system may return more value to participants, shared infrastructure, public memory, reusable knowledge, or interoperable commons. Compounding can also entrench incumbents. A healthy loop: `Contribution → Evidence → Recognition → Opportunity → More Contribution` can degrade into: `Recognition → Visibility → Opportunity → Recognition` where incumbency reproduces itself. ================================================================================================ FILE: power_dynamics/dynamics/06-concentration-stacking-capture.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: d9167a5bd723ecc7b4e248b36748f21f15431934a517429d27874210573d4166 CONTENT_BYTES: 1234 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Concentration, Stacking, and Capture" source_basis: - S10 - S16 - S18 - S21 - S25 --- # Concentration, Stacking, and Capture Concentration is multidimensional. An actor can be decentralized economically while centralized technically, or plural in formal governance while dependent on one trust root, identity provider, brand, maintainer, or deployment key. ## Stacking Stacking occurs when multiple legitimate functions accumulate in one node. `banking + identity + certification + philanthropy + platform access → cross-domain leverage` No individual function must be abusive for the stack to create new dependency. ## Capture Capture occurs when control over one legitimate function is converted into durable influence outside its intended mandate: > **Functional Control → Cross-Domain Power** Capture is a gradient, not merely a binary state. Signals include mandate drift, default expansion, dependency growth, weakened substitution, recognition loops, reduced branch mobility, and increased exit cost. The constitutional aim is not impossible-to-capture systems. It is **non-terminal capture**. ================================================================================================ FILE: power_dynamics/dynamics/07-counterpower-contestation-exit.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a0c76c6f518214e732985cd8889cedad7851663d50f0bc761bdb9e1d3e4ddcaa CONTENT_BYTES: 1671 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Counterpower: Verification, Contestation, Substitution, Exit" source_basis: - S01 - S16 - S19 - S21 - S25 --- # Counterpower: Verification, Contestation, Substitution, Exit Counterpower is practical capacity to alter the terms of a power relation. > **Verification + Contestation + Substitution + Exit** - **Verification** — inspect what happened and why. - **Contestation** — meaningfully challenge the claim, decision, ranking, score, rule, or authority. - **Substitution** — replace the provider, branch, trust root, policy, or infrastructure. - **Exit** — leave without disproportionate loss of identity, data, reputation, continuity, rights, or capability. These are gradients, not checkboxes. Branch systems add **branch mobility**: an alternative must be able not only to exist but to become discoverable, credible, interoperable, supported, and viable. ## Counterpower can be trained Effective counterpower depends not only on available mechanisms but on practiced activation. Drills can reveal whether participants know how to identify a problem, assemble evidence, coordinate objection, invoke procedures, form alternatives, and preserve the result as institutional memory. This creates a compounding loop: ```text contestable event → exercised counterpower → procedural memory → lower future coordination cost → stronger future counterpower ``` A system that repeatedly practices legitimate disagreement can become more resistant to later capture even when the later failure is subtler than the original exercise. ================================================================================================ FILE: power_dynamics/dynamics/08-diversification-and-evolution.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 958d7114aca1b0af225408f6e2393704395b9320ebb57812c683d2a6c140ed2f CONTENT_BYTES: 1011 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Diversification and Evolution" source_basis: - S13 - S16 - S22 - S25 --- # Diversification and Evolution Diversification distributes implementation, interpretation, governance, or capability across multiple actors or branches. `imperfection / new context / new evidence → variation → lineage → demonstration → comparison → support/adoption → coexistence/specialization/recombination/replacement → further variation` The goal is not permanent fragmentation. Stable lineage, provenance, shared interfaces, and interoperability can permit divergence while retaining a shared ecosystem. Distinguish: - **competition** — branches seek the same role; - **complementarity** — branches add different useful views or functions; - **recombination** — later branches integrate useful elements from earlier ones. Evolutionary governance constitutionalizes the ability to improve. ================================================================================================ FILE: power_dynamics/dynamics/09-decay-dissipation-and-loss.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: e7da359c4b23f9007aa125f34f3d2f0f5b009a020194088b18802aae12b02956 CONTENT_BYTES: 954 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Decay, Dissipation, and Loss" source_basis: - S13 - S21 - S25 - S28 --- # Decay, Dissipation, and Loss Power Dynamics must study loss as seriously as accumulation. Resources and puissance can decay through obsolescence, forgotten knowledge, declining credibility, network fragmentation, depleted finance, technical debt, unmaintained infrastructure, loss of recognition, legal change, language drift, or increasing coordination cost. **Dissipation** occurs when useful returns are not captured in reusable form. Institutions may repeatedly solve the same problem because experience remains trapped in staff memory, inaccessible archives, or transient conversation. Decay can also be constitutionally useful. Time decay, sunset clauses, and periodic revalidation can prevent delegated authority or reputation from becoming permanent. ================================================================================================ FILE: power_dynamics/dynamics/10-transfer-succession-and-inheritance.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 4a0b2158560933c5f61cd0ebaa7b5fd4138086bc6561b18253a0d8f07ab2b00e CONTENT_BYTES: 981 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Transfer, Succession, and Inheritance" source_basis: - S16 - S18 - S21 - S25 --- # Transfer, Succession, and Inheritance Power and puissance persist across time through transfer mechanisms. Transfer may involve money, property, credentials, code, repositories, signing keys, administrative roles, authority registries, institutional mandates, brands, knowledge, relationships, and interpretive authority. Succession is especially important in founder-dependent systems. A system is not independently reproducible if operation, legitimacy, keys, vocabulary, or interpretation remain dependent on one person's unique knowledge or permission. Distinguish founder authorship from permanent interpretive sovereignty; brand stewardship from protocol sovereignty; maintainer authority from political authority; technical custody from ownership of collective meaning. ================================================================================================ FILE: power_dynamics/dynamics/11-externalities-and-scale.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ab8e38798b3fe58b6afb1ccc37c728eebee4236027dd3937567b62d723f1c8d2 CONTENT_BYTES: 1173 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Power Externalities and Scale" source_basis: - S15 - S16 - S18 - S21 - S25 --- # Power Externalities and Scale Success can create power even without an explicit decision to concentrate it. A useful system can become a default. A default can become a standard. A standard can create dependency. A credibility system can become expected by employers. A platform can become the place where discoverability occurs. A brand can become a de facto certification mark. This is a **power externality**: `usefulness → adoption → network effects → standardization → dependency / leverage` Scale also changes the political meaning of mechanisms. A ranking rule affecting 100 users and the same rule affecting 100 million users are not constitutionally equivalent even if the code is identical. Analyze scale transitions: - local tool; - network infrastructure; - institutional standard; - ecosystem dependency; - systemic infrastructure. At each transition, reassess scope, branch mobility, substitution cost, auditability, and conversion firewalls. ================================================================================================ FILE: power_dynamics/dynamics/12-routing-sharing-and-devolution.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 5379152d1e96c65af324734bc2206646364699b2dc65d341bc4074a8ded68212 CONTENT_BYTES: 2129 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Routing, Sharing, and Devolution" source_basis: - S02 - S14 - S15 - S16 - S17 - S25 --- # Routing, Sharing, and Devolution Routing is the dynamic through which newly generated capability, authority, returns, or optionality are directed toward particular actors, levels, protocols, or communities. ## Canonical pattern ```text new capability / leverage → default locus of accumulation → routing mechanism → redistributed capability / authority / returns / optionality ``` Examples: ```text founder mastery → protocolization → distributed mastery ``` ```text expertise → bounded advisory channel → informed public judgment ``` ```text infrastructure → self-hosting / federation → local continuity and substitution ``` ```text money → common pool → democratic allocation ``` ```text symbolic attention → explicit ethical self-binding → public grounds for criticism and reinterpretation ``` ## Sharing Sharing occurs when multiple actors gain effective use of a capability or right without requiring one terminal owner of the function. Sharing should be tested practically, not only legally: > Can others actually understand, operate, reproduce, adapt, and continue the capability? ## Devolution Devolution is a durable movement of effective control from a central locus toward local, plural, or lower-level loci. It can involve: - local semantic governance; - self-hosted infrastructure; - distributed maintainership; - community-run Koali distributions; - branch autonomy; - local decision rights; - portable evidence and memory. ## Failure modes - nominal openness with impractical replication; - distributed software but centralized identity; - portable data but non-portable credibility/history; - self-hosting without discoverability; - forkability without branch mobility; - shared capability with centralized authority; - shared authority with centralized returns. Routing therefore must track **capability, authority, returns, and optionality separately**. ================================================================================================ FILE: power_dynamics/dynamics/13-propagation-and-coupled-loops.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ee4827f0a57bdcdf84e08b784be1001f9a9e660155680b58616c118ce2948609 CONTENT_BYTES: 1503 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Propagation and Coupled Loops" source_basis: - S13 - S18 - S21 - S25 - S29 --- # Propagation and Coupled Loops Compounding explains how returns increase future capability. Propagation explains how those returns can activate capability **elsewhere**. > **Compounding deepens capability. Propagation spreads or activates capability. Coupled propagation lets several loops exchange returns.** A general sequence is: ```text resource / capability A → action → return X → transfer / reuse → lower activation barrier for B → capability B → return Y → reinvestment into A or C ``` Propagation therefore extends the dynamic sequence after returns and compounding: > **Formation → Mobilization → Composition → Conversion → Effects → Returns → Compounding → Propagation → Concentration / Contestation → Diversification / Evolution → Routing / Sharing** The primary risks are: - positive feedback producing capture; - cross-loop hidden dependencies; - prestige / credibility self-reproduction; - standards or interface choke points; - founder bottlenecks; - network effects that reduce exit; - growth in content or integration complexity faster than validation capacity. The constitutional target is not weak capability. It is: > **distributed compounding with bounded sovereignty and practical exit.** See [`../PROPAGATION.md`](../PROPAGATION.md). ================================================================================================ FILE: power_dynamics/dynamics/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b8a53758ff655ca3abcc77d9815fd21e124d124d911fbe562aae9ff0fb11abfa CONTENT_BYTES: 2908 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Power Dynamics: Dynamic Processes" source_basis: - S01 - S02 - S13 - S18 - S25 - S26 --- # Dynamic Processes The Power Show answers **what kOA can make possible**. This directory explains **how capability and power change over time**. The main dynamic sequence is: > **Formation → Mobilization → Composition → Conversion → Effects → Returns → Reinvestment → Compounding → Propagation → Concentration / Contestation → Diversification / Evolution → Decay / Transfer → Routing / Sharing** ## 1. Formation How resources become potential, capacity, and eventually effectively mobilizable puissance. ## 2. Mobilization How retained stocks are released, routed, distributed, mediated, amplified, or blocked. `Reservoir → Release → Flow → Mediation` is a mobilization model, not the whole theory. ## 3. Composition and generated puissance How distinct capabilities combine to create higher-order individual or collective capability. ## 4. Conversion and firewalls How one resource, capability, or relational advantage becomes another — and where conversion should be constrained. ## 5. Returns, reinvestment, and compounding How action leaves reusable assets that increase or redistribute future capability. ## 6. Concentration, stacking, and capture How several legitimate functions or returns accumulate into cross-domain leverage. ## 7. Counterpower, contestation, and exit How actors alter the terms of power through verification, challenge, substitution, refusal, exit, or fork. ## 8. Diversification and evolution How variants emerge, demonstrate value, gather support, coexist, recombine, or replace dominant branches. ## 9. Decay, dissipation, and loss How reputation, network position, knowledge relevance, infrastructure, liquidity, legitimacy, or organizational capacity erode. ## 10. Transfer, succession, and inheritance How resources, authority, keys, mandates, memory, and stewardship move across actors and generations. ## 11. Externalities and scale How a useful mechanism can acquire systemic power because adoption, network effects, standards, or infrastructure dependence grow around it. ## 12. Routing, sharing, and devolution How newly generated capability, authority, returns, and optionality are deliberately directed away from default concentration and toward participants, communities, protocols, local operators, or viable alternatives. The sequence is recursive rather than linear. Returns from one cycle become resources for another. ## 13. Propagation and coupled loops How returns from one actor, branch, or deployment lower activation barriers elsewhere, and how several feedback loops exchange assets. Propagation is distinct from local compounding and must be audited for hidden dependency and runaway feedback. ================================================================================================ FILE: power_dynamics/framework/00-field-definition.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 949eebb55338782bd723df4447fbce37a76cc92a2e2ba0615c0b4dbba99d0e74 CONTENT_BYTES: 2984 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "What Power Dynamics Studies" source_basis: - S01 - S13 - S16 - S18 - S21 - S25 --- # What Power Dynamics Studies Power Dynamics has a deliberate double purpose. First, it is a **map of capability**: what can an architecture such as kOA make individuals, groups, organizations, and federations effectively able to do? Second, it is a **systems theory of social consequence**: what happens when those capabilities alter access, visibility, standing, allocation, dependency, authority, interpretation, coordination, or future possibility for others? The field therefore begins with two questions: > **What can this actor or system effectively do?** and: > **Whose possibilities change because it can do that?** The first concerns **puissance**. The second concerns **power**. ## Why kOA is a useful primary case kOA intentionally spans a large portion of the knowledge-to-action chain: > **Meaning → Knowledge → Visibility → Credibility → Deliberation → Decision → Execution → Memory** That makes it useful for studying how many forms of capability can compose: - semantic; - epistemic; - cognitive; - network; - reputational; - political / constitutional; - economic / allocation; - monetary / credit / liquidity; - deliberative; - operational; - mnemonic; - infrastructural; - federative; - evolutionary. The repo therefore places the **kOA Power Show** in front of the theory. The theory then explains the mechanisms visible in the show. ## Full lifecycle The canonical ontology is: > **Resources / Assets → Potential → Capacity → Puissance → Power Relation → Effect → Return** The dynamic lifecycle is: > **Formation → Mobilization → Composition → Conversion → Action / Relation → Return → Reinvestment → Compounding → Concentration / Contestation → Diversification / Evolution → Decay / Transfer → Routing / Sharing** A return can be money, knowledge, code, reputation, network access, credibility, standards, infrastructure, memory, data, legitimacy, dependency, or optionality. These returns can increase or reduce future capability. ## The field is broader than domination Power Dynamics studies: - empowerment; - generated collective capability; - infrastructure-mediated capability; - relational influence; - domination and dependency; - composition and conversion; - returns and compounding; - concentration and capture; - counterpower; - plurality and branch evolution; - decay, succession, and transfer; - routing, sharing, and devolution; - cross-domain political, economic, and monetary conversion. The normative question is not whether a system has power. Any sufficiently useful collective infrastructure will create consequential relations. The question is whether those relations remain **legible, scoped, contestable, substitutable, revocable, portable, and non-terminal**. ================================================================================================ FILE: power_dynamics/framework/01-core-ontology.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 9870cedcd7e56114d37d52ca5d514ef2fdd4491867c31965bb98e99bc275279b CONTENT_BYTES: 1563 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Core Ontology" source_basis: - S01 - S13 - S16 - S18 - S21 - S25 --- # Core Ontology The canonical ontology is: > **Resource / Asset → Potential → Capacity → Puissance → Power Relation → Effect → Return** This is not a claim that every real process is linear. It is a conceptual separation that prevents category errors. - **Resource / asset** — something available or accumulated that may support action. - **Potential** — what could become realistically possible because those resources exist. - **Capacity** — an organized ability under defined conditions. - **Puissance** — a capacity that is effectively mobilizable under actual conditions. - **Power relation** — a relation in which one actor's or system's puissance changes another's effective possibilities. - **Effect** — the realized change. - **Return** — a reusable asset created or preserved by the effect. ### Knowledge example `research corpus → potential understanding → organized expertise → epistemic puissance → advisory/recognition relation → changed decision → credibility + memory` ### Money example `financial stock → potential purchasing options → liquid capacity → economic puissance → allocation/bargaining relation → funded project → infrastructure + revenue` The ontology does not make relational power morally negative. Power may enable, coordinate, recognize, protect, allocate, constrain, or dominate. ================================================================================================ FILE: power_dynamics/framework/02-effective-possibility.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 4fe40c6b06581229e61ff0d45eacfb14c0e7a5162bf3c792855b383fb3839186 CONTENT_BYTES: 1220 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Effective Possibility" source_basis: - S01 - S16 - S18 --- # Effective Possibility The framework's central object is not abstract freedom but **effective possibility**. A formal option can exist while remaining practically unusable. A person may possess a legal right but lack time, money, information, institutional recognition, language access, transportation, technical capability, or a viable appeal process. Conversely, infrastructure can expand effective possibility by reducing those barriers. This is why dependency is central. If essential possibilities depend on an actor whose rules are opaque, unilateral, difficult to contest, or costly to exit, that dependency creates relational leverage even if the actor rarely intervenes. Effective possibility should be assessed through access, affordability, time cost, intelligibility, technical operability, legal recognition, portability, alternatives, coordination cost, reversibility, risk, and institutional acceptance. The objective is not perfect quantification. It is to make the relevant constraints and enabling conditions **legible**. ================================================================================================ FILE: power_dynamics/framework/03-three-axis-model.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: d98ab9f724a383157d84f1906ec4fc0990e1783d0ea032acabe0da5a05f81d06 CONTENT_BYTES: 1124 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Three-Axis Model" source_basis: - S18 - S21 - S22 --- # Three-Axis Model Every Power Dynamics analysis should locate a phenomenon on three axes. ## Axis 1 — Ontological state `resource → potential → capacity → puissance → power relation → effect → return` ## Axis 2 — Dynamic Formation, mobilization, composition, conversion, return, reinvestment, compounding, concentration, stacking, capture, counterpower, diversification, branch evolution, decay, transfer, succession, routing, sharing, devolution. ## Axis 3 — Domain Economic, monetary, political, epistemic, semantic, informational, reputational, attention, network, technical, infrastructural, administrative, operational, narrative, symbolic, brand, cognitive, mnemonic, allocation, certification, property, territorial, and others. A media organization can therefore be strong in distribution and agenda power while a state is stronger in legal enforcement. “More powerful” without a domain and mechanism is incomplete. ================================================================================================ FILE: power_dynamics/framework/04-power-ecology.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c18ba690b0bd08794ea8fe9a63cc2d0fbd32a521c590b6acaaeaab0043b90665 CONTENT_BYTES: 2630 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Power Ecology" source_basis: - S13 - S15 - S18 - S21 - S25 - S26 --- # Power Ecology A **power ecology** is a system in which resources, forms of puissance, relations of power, returns, dependencies, and alternatives continuously interact. The kOA Power Show is best understood ecologically because no single capability explains the whole effect. ## Capability ecology Typical capability-generating chains include: `knowledge → understanding → judgment → action` `network → collaborators → coordination → collective puissance` `memory → lower relearning cost → better future judgment` `AI + provenance + human governance → higher cognitive throughput` `portable infrastructure → substitution → stronger exit capacity` ## Conversion ecology Typical cross-domain chains include: `knowledge → credibility → visibility → opportunity` `execution → results → evidence → credibility` `brand → attention → affiliation → revenue` `money → infrastructure → reach → influence` `technical control → defaults → dependency → agenda leverage` These chains can be productive, extractive, regenerative, or dangerous depending on who receives returns and whether conversions remain scoped. ## Feedback ecology Power Dynamics therefore asks: - what resources are accumulated; - what puissance they support; - how capabilities compose; - how they are mobilized; - what power relations emerge; - what effects and returns are produced; - where returns accumulate; - which nodes become bottlenecks; - what dependencies form; - which counterpowers remain effective; - whether alternatives can survive and evolve. ## kOA as a designed ecology kOA deliberately distributes capability across semantic, epistemic, cognitive, social, political, economic, administrative, operational, mnemonic, technical, and federative layers. The design challenge is to obtain the **composition gain** without allowing one layer to silently convert its useful function into total cross-domain authority. The constitutional aspiration is therefore: > **Maximum composable capability; minimum terminal sovereignty.** ## Routing ecology A power ecology is shaped not only by where capability emerges but by where it is deliberately sent. kOA therefore tracks four routing dimensions: **capability, authority, returns, and optionality**. A regenerative ecology routes useful returns toward broader future capability while keeping high-leverage authority scoped and contestable. ================================================================================================ FILE: power_dynamics/framework/05-pre-political-chain.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 137833c4bb9bee00cf252bdd3b9ecf7c8c6b3326d1978065691b18875ea68f30 CONTENT_BYTES: 1084 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Pre-Political Power" source_basis: - S15 - S18 - S19 - S21 - S22 --- # Pre-Political Power Formal decisions are only one stage in a longer chain: > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** Each stage is a locus of puissance and potentially of relational power. Definitions shape what can be perceived. Validation shapes credibility. Discovery shapes visibility. Ranking shapes attention. Agenda setting shapes what enters decision. Administrative routing shapes what becomes executable. Memory shapes what later actors inherit. A system can preserve one-person-one-vote while still concentrating major influence upstream in search, ranking, classification, moderation, recommendation, defaults, identity, or workflow routing. Power Dynamics therefore studies the entire mediation chain rather than treating the ballot or final command as the only politically meaningful event. ================================================================================================ FILE: power_dynamics/framework/06-stock-capacity-flow-return.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: d34c73c5ad6f1b07cd1c921b79bab3c0e2b6f42630966c05d966662e04f956ea CONTENT_BYTES: 1011 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Stock, Capacity, Flow, and Return" source_basis: - S13 - S21 - S25 - S26 --- # Stock, Capacity, Flow, and Return An earlier useful distinction is preserved in refined form. - **Stock** — what has accumulated. - **Capacity** — what the actor or system is organized to do. - **Puissance** — what it can effectively mobilize under current conditions. - **Flow** — the practical movement or throughput of resources, action, information, or effects. - **Return** — what comes back into the system and can be reused. The combined model is: > **Stock → Potential → Capacity → Puissance → Flow / Relation → Effect → Return → New Stock** This is especially useful for compounding analysis. A large stock can remain politically weak if it cannot be mobilized or converted; a small initial stock can compound through code, experience, methods, reputation, and network assets. ================================================================================================ FILE: power_dynamics/framework/07-imperfection-and-plurality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 90a7d912e0cca2dbdb137b1212102e8f3bf43435bc527e11230aaf44abd94e3e CONTENT_BYTES: 1020 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Imperfection, Readings, and Plurality" source_basis: - S15 - S16 - S17 - S22 - S28 --- # Imperfection, Readings, and Plurality Power Dynamics assumes that consequential human and institutional judgments are imperfect. Competence, ethics, credibility, legitimacy, truth, branch quality, and social value cannot be captured perfectly by one score, authority, or implementation. This is not a reason to avoid evaluation. It is a reason to make evaluation **explicitly governed**. `phenomenon ≠ evidence ≠ policy interpreting evidence ≠ reading/score ≠ institutional use of that reading` This permits multiple branches or readings without requiring relativism. A branch may be better supported on one dimension and weaker on another. Different Kristals may preserve different evidence, contexts, ontologies, or scopes. The objective is not perfect governance but **governable imperfection**. ================================================================================================ FILE: power_dynamics/framework/08-constitutional-thesis.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 0b8841e37581d3ef849495e885e94c31c14ad0e342276d569a13e76502787ee7 CONTENT_BYTES: 1631 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Constitutional Thesis" source_basis: - S16 - S18 - S19 - S21 - S22 - S25 --- # Constitutional Thesis The central constitutional problem is: > **How can an infrastructure distribute enormous puissance without becoming sovereign over the puissance it distributes?** The answer is not decentralization in one dimension. It requires scoped authority, separation of functions, conversion firewalls, provenance, verification, contestation, substitution, exit, revocability, reversibility, local operability, federation, branch mobility, founder decentering, and non-terminal dependency. The repository's shorthand is: > **Strong distributed puissance. Weak sovereignty.** A system can have a strong hub, useful defaults, recognized brands, maintainers, registries, and standards. The issue is whether those centers can silently convert functional centrality into unchallengeable cross-domain control. > **Architecture is governance before governance is written.** ## From restraint to routing The constitution should not be understood only as a brake on successful capability. It also governs **where the benefits and leverage of capability go**. > **Generate strong puissance → route it deliberately → bind authority → preserve counterpower → keep alternatives viable.** This is why protocolization, public ethical self-binding, Koali plurality, democratic allocation, portability, self-hosting, and branch mobility belong to the constitutional architecture rather than only to product design. ================================================================================================ FILE: power_dynamics/framework/09-power-routing-and-sharing.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 19fc6658b7ec0a37dffe5ad520f2cddf4061f1a750c20737395b8007bfc053da CONTENT_BYTES: 4893 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "NEW-CONCEPT" scope: "GENERAL" version: "6.0" title: "Power Routing and Sharing" source_basis: - S02 - S14 - S15 - S16 - S17 - S19 - S21 - S22 - S25 --- # Power Routing and Sharing Power Dynamics studies not only the **generation** and **constraint** of power, but its **routing**. > **Power routing is the explicit design of where generated capability, authority, returns, and optionality are allowed to accumulate.** This adds a missing question to ordinary power analysis. It is not enough to identify a source of power and ask how it is limited. A system can often redirect the same source into a different institutional destination. ## Core terms ### Power redirection A deliberate change in the default destination or conversion path of leverage. Examples: - expertise → advice rather than sovereignty; - capital → shared funding rather than extra votes; - infrastructure → user autonomy rather than operator dependency; - founder knowledge → protocol rather than permanent personal gatekeeping. ### Power sharing The creation of conditions under which multiple actors can effectively use a capability or participate in a decision-right without requiring exclusive ownership by one actor. Sharing can concern capability, authority, returns, or optionality. ### Power devolution A durable transfer of effective control from a central locus toward local, plural, or lower-level loci. ### Self-binding A mechanism by which a powerful actor or institution publishes, encodes, or accepts constraints that make later exercises of power more legible, contestable, or limited. ### Protocolization The conversion of tacit, founder-centric, or institution-centric capability into explicit contracts, schemas, specifications, portable artifacts, and reproducible behavior that others can implement or operate. ### Ownership decoupling The separation of a useful function from exclusive ownership of the implementation, brand, registry, or operator that first instantiated it. ## Routing dimensions | Dimension | Question | |---|---| | Capability | Who can actually do more because the system exists? | | Authority | Who can approve, validate, rank, route, certify, update, or decide? | | Returns | Who receives the assets generated by successful action? | | Optionality | Who can refuse, leave, substitute, fork, self-host, or wait? | | Interpretation | Who can define categories, credibility policies, readings, and meanings? | | Visibility | Who controls discoverability, ranking, attention, and agenda? | A system is not meaningfully power-sharing merely because one dimension is open. Open code can coexist with closed identity, centralized ranking, proprietary credibility, or terminal network effects. ## Redirection matrix | Concentration vector | Redirection pattern | |---|---| | founder mastery | protocolization + documentation + maintainer pluralism | | brand / narrative | public ethical self-binding + architecture-first references | | credibility | plural distributions + portable evidence + contestable policy | | expertise | bounded advisory influence + preserved political baseline | | knowledge validation | provenance + reader plurality + competing artifacts | | infrastructure | portability + self-hosting + federation + substitution | | capital | contribution separated from political standing | | incumbent branch | branch mobility + compatibility + demonstrable replacement | | AI cognition | explicit policy + provenance + human-governed authority boundaries | ## Self-binding is not self-certification Publishing principles is not proof that they are followed. A self-binding mechanism becomes stronger when commitments are: - explicit; - stable enough to cite; - connected to procedures; - auditable against behavior; - revisable through a visible process; - usable by critics and participants as grounds for contestation. This distinction is essential for narrative ethics. Ethical principles inside fiction can constrain symbolic drift by making the narrative carry its own limits, but they do not replace institutional safeguards. ## Sharing without flattening Power sharing does not require identical influence or identical expertise. The target is **non-terminal asymmetry**: differences may exist, but affected actors retain meaningful routes to understand, contest, substitute, leave, learn, reproduce, or build alternatives. ## Relation to the constitution Traditional constitutional design asks how to constrain authority after it forms. Power routing asks an earlier question: > **Can the architecture prevent some authority from concentrating in the first place by routing capability somewhere else?** The full constitutional sequence becomes: > **Generate → Route → Scope → Bind → Verify → Contest → Substitute → Exit → Fork → Evolve** ================================================================================================ FILE: power_dynamics/framework/10-cross-domain-power-conversion.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 22d6aeadbe8a2b6f82d5897adee1e56d79cb1c63144c7b9ca62099f5157399fa CONTENT_BYTES: 3375 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Cross-Domain Power Conversion" source_basis: - S01 - S04 - S10 - S13 - S14 - S15 - S16 - S18 - S25 - S26 --- # Cross-Domain Power Conversion Power is often most consequential when capability or authority in one domain is converted into leverage in another. ## Conversion A conversion can be represented as: ```text source resource / puissance → conversion mechanism → destination resource / puissance / power relation ``` Examples: ```text knowledge → evidence of competence → credibility credibility → ranking / endorsement → visibility visibility → audience → opportunity money → purchase / funding → infrastructure infrastructure → dependency → bargaining leverage brand → affiliation → revenue founder / persona → trust → agenda leverage citation volume → apparent consensus → epistemic authority reference stewardship → canon visibility → truth-monopoly risk administrative control → defaults → de facto policy ``` ## Cross-domain leverage Not all conversion is problematic. Many desirable systems depend on it. The problem begins when: 1. the conversion is hidden; 2. the destination authority exceeds the source mandate; 3. affected actors cannot contest or substitute; 4. the conversion compounds through multiple domains; 5. the resulting leverage becomes durable or terminal. ## Capture > **Capture occurs when control over one legitimate function is converted into durable influence over functions outside its intended mandate.** Canonical warning pattern: > **Functional Control → Cross-Domain Power** ## Power stacking Power stacking occurs when one actor or node combines several functions whose interactions create leverage not visible when each function is assessed separately. For example: ```text identity + credibility + discovery + funding + workflow = cross-domain leverage ``` or: ```text monetary rail + taxation + allocation + sanctions + dispute enforcement = high terminality risk ``` ## Conversion firewalls A conversion firewall does not prohibit composition. It prevents **automatic authority inheritance**. Examples: - expertise → advice, not sovereignty; - money → funding, not votes; - brand → attention, not truth; - credibility → discoverability, not unquestionable authority; - infrastructure → capability, not ownership of users; - execution → mandate implementation, not mandate redefinition. ## Analytical procedure For each important function: 1. Name the source domain. 2. Name the source resource/capability. 3. Identify the conversion mechanism. 4. Name the destination domain. 5. Identify the resulting power relation. 6. Measure dependency and switching cost. 7. Identify returns and compounding. 8. Identify firewall, contestation, substitution, or exit. 9. Test whether the destination authority is within mandate. 10. Test whether capture of the instance would imply capture of the system. ## Relation to the three-axis model Cross-domain conversion connects the three axes: - **ontology** — what changes state; - **dynamic** — conversion / compounding / capture; - **domain** — where the source and destination operate. This is why the domain axis must be explicit rather than a loose list of examples. ================================================================================================ FILE: power_dynamics/framework/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ca75bfafa4e1975588bf8e8ce28cee259ad0f857ab5acff147213b5dc3d53654 CONTENT_BYTES: 1373 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Framework" source_basis: - S01 - S13 - S15 - S16 - S18 - S21 - S25 --- # Framework The framework is the analytical engine behind the kOA Power Show. ## Reading order 1. [`00-field-definition.md`](00-field-definition.md) 2. [`01-core-ontology.md`](01-core-ontology.md) 3. [`02-effective-possibility.md`](02-effective-possibility.md) 4. [`03-three-axis-model.md`](03-three-axis-model.md) 5. [`04-power-ecology.md`](04-power-ecology.md) 6. [`05-pre-political-chain.md`](05-pre-political-chain.md) 7. [`06-stock-capacity-flow-return.md`](06-stock-capacity-flow-return.md) 8. [`07-imperfection-and-plurality.md`](07-imperfection-and-plurality.md) 9. [`08-constitutional-thesis.md`](08-constitutional-thesis.md) 10. [`09-power-routing-and-sharing.md`](09-power-routing-and-sharing.md) 11. [`10-cross-domain-power-conversion.md`](10-cross-domain-power-conversion.md) ## Core model > **Resource / Asset → Potential → Capacity → Puissance → Power Relation → Effect → Return** The broader dynamics study how those states **form, mobilize, compose, convert, return, compound, concentrate, capture, contest, diversify, evolve, decay, transfer, scale, and route**. The domain axis is detailed in [`../domains/README.md`](../domains/README.md). ================================================================================================ FILE: power_dynamics/GLOSSARY.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b56812c85cc4c07007f0957c38a9d5f62fcf0ab744d1b5d3b61ab90ff49afb0d CONTENT_BYTES: 34710 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Canonical Glossary" source_basis: - S01 - S02 - S10 - S13 - S15 - S16 - S18 - S21 - S22 - S25 - S26 - S28 --- # Canonical Glossary This glossary is normative for repository terminology. It keeps the **kOA Power Show** expressive without allowing broad language such as “powerful” to collapse distinct analytical states. When a term is used differently in a source document, preserve the source meaning and explicitly distinguish it from the repository definition. ## Canonical distinctions | Do not conflate | Canonical distinction | |---|---| | resource / power | a resource supports action; power is relational | | potential / capacity | potential is unrealized possibility; capacity is organized ability | | capacity / puissance | capacity can exist without being effectively mobilizable; puissance is effective under real conditions | | puissance / power | puissance produces effects; power shapes another actor's effective possibilities | | stock / flow | stock is accumulated; flow is movement or throughput | | reservoir / power | a reservoir retains resources or options; it does not store relational power as a substance | | score / competence | a score is a governed reading of evidence, not competence itself | | credibility / truth | credibility affects trust; it does not establish truth by itself | | support / evidence | support is social endorsement; evidence supports a claim or evaluation | | dominance / quality | dominance describes position or adoption; quality is multidimensional and contestable | | forkability / branch mobility | a fork may be possible while remaining unable to attract users, evidence, interoperability, or institutional support | | centrality / sovereignty | a hub may be functionally central without possessing total or terminal authority | ### French / English convention The repository deliberately keeps **puissance** in French even inside English prose when precision matters. English *power* collapses several meanings that this framework separates. - **potential / potentiel** — unrealized possibility; - **capacity / capacité** — organized ability; - **puissance** — effectively mobilizable capacity; - **power / pouvoir relationnel** — relational shaping of another actor's effective possibilities. ## Power Show terms **kOA Power Show** — the presentation layer of Power Dynamics that maps the forms of effective capability kOA can generate, compose, preserve, distribute, and evolve before analyzing the power relations created by successful capability. **Capability spectrum** — the set of distinct forms of potential, capacity, and puissance available to an actor or system across domains. In kOA this includes epistemic, semantic, cognitive, collective, network, credibility, decision, operational, mnemonic, technical, infrastructural, federative, exit, and evolutionary capability. **Capability loop** — a sequence in which one capability feeds the next. The canonical kOA loop is `Know → Choose → Act → Remember → Know better`. **Closed capability loop** — a capability loop in which outputs are sufficiently preserved and fed back as inputs that the system can learn from prior action rather than repeatedly restarting from near-zero institutional memory. “Closed” does not mean perfectly self-contained. **Composition engine** — shorthand for the architecture through which distinct capabilities become interoperable inputs to one another, creating higher-order or generated puissance. **Composition gain** — additional effective capability created because separate functions interoperate. It is the difference between possessing useful components and possessing a coherent capability system. **Compounding engine** — shorthand for feedback loops in which action produces reusable returns that lower the cost, increase the quality, or expand the scope of future action. **Capability infrastructure** — technical, semantic, institutional, or procedural infrastructure whose primary effect is to make future action easier, more reliable, more composable, or more reusable. **Capability surface** — a function or interface through which a system increases what actors can effectively do. A capability surface can later become a power surface if control over it changes other actors’ effective possibilities. **Power surface** — a function, interface, registry, role, default, gate, workflow, standard, or infrastructure boundary through which control can shape other actors’ access, standing, visibility, allocation, timing, interpretation, or ability to act. **Power surface map** — cross-domain inventory of the capability surfaces, relational power surfaces, controllers, conversion paths, counterpowers, and routing mechanisms of a system. **Cross-domain power conversion** — transformation through which a resource, capability, or relational advantage in one domain becomes leverage in another domain. **Conversion path** — explicit sequence connecting a source domain to a destination domain through a mechanism such as funding, ranking, certification, standardization, ownership, or dependency. **Capability-to-power transition** — the point at which successful puissance becomes relationally consequential for other actors. This transition is central to the repository: the same function can be empowering as capability and politically consequential as a controlled gate. ## Ontology **Resource** — anything available to an actor or system that can support future action: money, time, knowledge, code, rights, relationships, reputation, data, infrastructure, identity, property, attention, memory, or other conditions. **Asset** — a resource that has been accumulated, stabilized, owned, controlled, recognized, or made reusable enough to support future action. **Stock** — an accumulated quantity or body of resources/assets at a point in time. A stock is descriptive; it is not automatically puissance or power. **Potential** — unrealized effective possibility preserved or created by resources and conditions. **Capacity** — an organized ability to perform a class of actions under specified conditions. **Puissance** — capacity that is effectively mobilizable under real conditions to produce effects. Puissance is the preferred term for what English often calls *power to*, *power with*, or *power through* when no relational control over others is implied. **Power** — a relational capacity, grounded in puissance, through which one actor, group, institution, or infrastructure shapes another's effective possibilities. **Power relation** — a relation in which another actor's access, options, standing, visibility, allocation, authority, incentives, categories, timing, dependencies, or ability to act are materially changed. **Effect** — a realized change produced by action, mediation, or a power relation. **Return** — a reusable asset created or preserved by an action or effect and available for future cycles. **Effective possibility** — what an actor can realistically understand, choose, refuse, obtain, build, coordinate, contest, preserve, or leave under actual material, institutional, temporal, informational, and social conditions. ## Modes of capability and relation **Puissance d'agir / power to** — effective ability to accomplish, understand, build, decide, refuse, learn, create, or otherwise act. **Collective puissance / power with** — effective capability generated through coordination among multiple actors. **Infrastructure-mediated puissance / power through** — effective capability enabled, stored, routed, amplified, or made reusable through infrastructure. **Power over** — an asymmetric family of power relations in which one actor can condition, constrain, block, allocate, define, authorize, or otherwise shape another's possibilities. It is not the definition of all power. **Mutual power** — a reciprocal power relation in which actors alter one another's possibilities in ways that can expand joint capacity. **Generated puissance** — new effective capacity created by composition that did not exist in any participant separately. **Latent puissance** — capacity that could be mobilized but is currently inactive because of timing, coordination, information, access, or other constraints. ## Dynamics **Formation** — the process through which resources become organized capacity and then effective puissance. **Mobilization** — the activation of available resources or puissance into action, exposure, coordination, or effects. **Reservoir** — a configuration in which accumulated resources or reusable assets are retained for future activation. A reservoir is not stored relational power. **Retention** — preserving a resource, asset, option, or capability rather than immediately committing or releasing it. **Release** — activation, disclosure, deployment, spending, publication, delegation, or other transition from retained resource to active use. **Release puissance** — effective ability to control the timing, sequencing, form, and channels through which a retained resource is activated. **Flow** — movement of mobilized resources, signals, actions, or effects through a system. **Throughput** — the practical rate at which a system can process, deploy, distribute, or convert resources and puissance into effects. **Mediation** — selection, framing, routing, translation, ranking, interpretation, packaging, contextualization, or transformation between source and affected actors. **Amplification** — an increase in scale or intensity of an effect relative to the initiating input because of a network, platform, institution, technology, or channel. **Bottleneck** — a constrained passage that limits throughput or access to a necessary transformation. **Bottleneck power** — relational power created when an actor controls a passage that others must use to convert resources or puissance into effects. **Composition** — combining distinct resources, capacities, or forms of puissance to create a higher-order capability. **Conversion** — transformation of a resource, asset, capacity, puissance, or relational position into another form. **Conversion pathway** — an identifiable sequence through which one form becomes another, e.g. `knowledge → credibility → visibility → opportunity`. **Conversion firewall** — a rule or architecture that permits legitimate composition while blocking automatic conversion into unrelated authority. **Reinvestment** — using returns to create or amplify future capacity and puissance. **Compounding puissance** — growth in future effective capacity caused by reinvestment and reuse across cycles. **Power yield** — the set of returns, effects, and relational positions generated by a given exercise of puissance or power. It should not be reduced to a single scalar metric. **Concentration** — increasing share of relevant resources, puissance, or relational control accumulating in one actor, node, branch, or institution. **Stacking** — accumulation of several distinct functions in the same actor or node, producing cross-domain leverage not visible in any function separately. **Capture** — durable conversion of legitimate functional control into influence or control outside its intended mandate. **Cross-domain conversion** — movement of advantage from one domain into another, e.g. economic assets becoming political influence or technical administration becoming agenda control. **Diversification** — distribution of capability or governance across multiple actors, implementations, branches, domains, or institutions. **Decay** — reduction in usefulness, credibility, adoption, capability, legitimacy, liquidity, network position, or other components of puissance over time. **Dissipation** — loss of potential returns because knowledge, experience, attention, coordination, or other value is not preserved or reused. **Transfer** — movement of resources, capacity, authority, relational position, or responsibility between actors or institutions. **Succession** — governed transfer of roles, stewardship, keys, mandates, or interpretive responsibility across time. ## Dependence, domination, and counterpower **Dependency** — reliance on an actor, system, resource, or infrastructure whose substitution or exit is materially costly, slow, unavailable, or illegible. **Dependency gradient** — degree of dependency, determined by alternatives, switching cost, time, portability, recognition, rights, knowledge, network effects, and other factors. **Domination** — exposure to arbitrary or insufficiently contestable relational power, especially where dependency is high and counterpowers are weak. **Counterpower** — capacity that can verify, contest, substitute, exit, revoke, reverse, fork, or otherwise alter the terms of a power relation. **Verification** — ability to independently inspect claims, artifacts, processes, identities, signatures, calculations, or compliance. **Contestation** — ability to challenge a claim, score, decision, rule, ranking, authority, or implementation through a meaningful process. **Substitution** — ability to replace a provider, branch, implementation, authority root, workflow, or institution with a viable alternative. **Exit** — ability to leave a relationship or system while preserving enough assets, rights, data, identity, reputation, and continuity for exit to be meaningful. **Formal exit** — nominal legal or technical ability to leave. **Effective exit** — practical ability to leave at acceptable cost without disproportionate loss of essential capability. **Forkability** — ability to create a divergent implementation, policy, ontology, or branch from an existing lineage. **Effective forkability** — forkability plus the practical ability to operate, interoperate, attract support, preserve provenance, migrate assets, and become viable. **Revocability** — ability to withdraw authority or permission. **Reversibility** — ability to undo or repair the effects of an earlier action or authority. Revocability does not guarantee reversibility. **Terminal power** — relational power whose capture, failure, or abuse cannot be effectively substituted, reversed, contested, or exited. **Instance capture** — capture of one deployment, organization, branch, or institution. **System capture** — capture of the broader architecture such that meaningful alternatives cannot continue, interoperate, or emerge. ## Branch ecology and evolutionary governance **Branch** — a distinct version, implementation, policy, ontology, or interpretation with enough lineage and provenance to be compared with alternatives. **Lineage** — traceable relationship among versions, forks, sources, transformations, and derived artifacts. **Branch mobility** — practical ability of a branch to become discoverable, credible, supported, interoperable, adopted, and capable of influencing or replacing dominant branches. **Dominance** — a branch's current advantage in adoption, support, visibility, compatibility, institutional recognition, network effects, or infrastructure. Dominance does not imply truth or optimality. **Complementarity** — additional value produced when distinct branches, perspectives, or implementations cover different evidence, contexts, scales, or functions without requiring a universal winner. **Redundant plurality** — multiple branches that add little new evidence, context, method, function, or interoperability value. **Meaningful variation** — branch difference that creates identifiable added value or tests a consequential alternative. **Evolutionary governance** — governance in which consequential rules, policies, interpretations, and implementations remain open to explicit variation, demonstration, comparison, adoption, recombination, amendment, and replacement. **Stable kernel** — shared minimal contracts, formats, provenance rules, or interoperability requirements that permit divergence without fragmentation. **Evolving branch** — a branch whose policies, readings, implementations, or governance may change while preserving lineage and interoperability where feasible. **Recombination** — integration of useful elements from multiple branches into a new branch or later version. **Replacement** — transition in which an alternative becomes more adopted, authoritative, useful, or institutionally supported than an earlier dominant branch. ## Epistemic, semantic, and credibility terms **Epistemic puissance** — effective ability to produce, organize, validate, compare, preserve, or reuse knowledge. **Semantic puissance** — effective ability to create, maintain, translate, contest, and evolve categories, ontologies, definitions, and relations of meaning. **Semantic power** — relational power created when control over categories, definitions, ontologies, thresholds, or classifications shapes how others can understand, qualify, or act. **Semantic sovereignty** — practical capacity of a person or community to govern the terms, categories, ontologies, and knowledge structures through which it generates and shares meaning without arbitrary dependence on external authorities. **Credibility asset** — accumulated evidence or recognition that makes a person, branch, claim, or institution more likely to be trusted in a defined context. **Credibility signal** — governed reading of evidence about expertise, contribution, conduct, reliability, or other criteria. It is not the person or competence itself. **Domain-bounded expertise** — expertise whose relevance and influence are limited to explicit domains rather than generalized into universal authority. **Discoverability puissance** — effective ability to make relevant content, people, or branches findable. **Discoverability power** — relational power created when control of discovery materially shapes what others see, reuse, fund, cite, learn, adopt, or build. **Pre-political power** — power exercised through meaning, knowledge, visibility, credibility, agenda, and framing before a formal decision is made. **Mnemonic puissance** — effective ability to preserve and reuse knowledge, reasons, decisions, actions, failures, and outcomes across time. **Mnemonic power** — relational power created when control of collective memory shapes future interpretation, precedent, options, or institutional learning. ## Political and constitutional terms **Political puissance** — effective ability to participate in, shape, organize, or carry collective judgment, agenda formation, decision, amendment, representation, or public action. **Political power** — relational power to shape political standing, agenda, mandates, decision rights, representation, legitimacy, veto, amendment, or binding collective outcomes. **Constitutional power** — power to define, amend, interpret, or enforce the rules by which other powers are authorized, limited, contested, or transferred. **Decision power** — relational power to determine or materially condition which collective option becomes binding or operative. ## Economic, monetary, and allocation terms **Economic resource** — money, property, goods, productive assets, contractual rights, or other material means. **Economic puissance** — effective ability to mobilize economic resources for action. **Economic power** — relational power created when control or mobilization of scarce economic resources materially changes others’ access, bargaining position, dependency, allocation, or effective options. **Liquidity** — ease and speed with which an asset can be converted into usable resources without excessive loss. **Liquidity puissance** — effective ability to make resources rapidly usable. **Allocation power** — relational power to determine which people, projects, institutions, or goals receive resources. **Monetary puissance** — effective ability to create, access, move, settle, convert, intermediate, or finance value through monetary and credit infrastructure. **Monetary power** — relational power associated with control over units, rails, issuance, settlement, reserves, access, or conditions of exchange. **Custodial power** — relational power arising from control over assets held on behalf of others. **Market-making puissance** — capacity to enable exchange by providing liquidity, matching, standards, custody, or transaction infrastructure. **Property power** — relational power arising from enforceable control of scarce assets, land, infrastructure, intellectual property, or access rights. ## Information, media, network, and narrative terms **Information resource** — data, documents, signals, archives, observations, or other transmissible representations. **Distribution puissance** — effective ability to deliver information, resources, signals, or instructions to relevant actors at scale. **Reach** — number and relevance of actors that can practically be reached through available channels. **Reach puissance** — effective capacity to cross geographic, linguistic, network, or institutional boundaries. **Attention power** — relational power to influence what receives scarce attention. **Visibility power** — relational power to affect whether and how actors, claims, branches, or events become publicly visible. **Agenda power** — relational power to influence what enters collective consideration as a problem, priority, or option. **Framing power** — relational power to shape interpretation by selecting descriptions, categories, narratives, baselines, or causal frames. **Media puissance** — effective ability to gather, package, distribute, synchronize, and amplify information to an audience. **Network resource** — relationships, affiliations, pathways, memberships, trust links, or structural positions that can support future coordination. **Network puissance** — effective ability to mobilize relationships for access, coordination, diffusion, recruitment, or action. **Affiliation power** — relational effects produced by membership, association, endorsement, exclusion, or visible identification with a network or symbol. **Narrative puissance** — effective ability to make complex systems understandable, memorable, transmissible, and emotionally or culturally legible. **Narrative power** — relational power created when narratives shape interpretation, legitimacy, attention, identity, or mobilization. **Brand asset** — accumulated recognition, associations, expectations, reputation, symbols, and identity attached to a name or mark. **Brand puissance** — effective ability to mobilize brand recognition into attention, affiliation, trust, distribution, commerce, or coordination. **Brand power** — relational effects created when brand-mediated trust, attention, certification, or affiliation changes others' opportunities, choices, or standing. ## Technical, infrastructural, administrative, and cognitive terms **Technical resource** — code, tools, protocols, hardware, schemas, standards, credentials, deployment knowledge, or other technical assets. **Technical puissance** — effective ability to build, modify, operate, verify, deploy, repair, or reproduce technical systems. **Infrastructural puissance** — effective ability created by reliable shared systems, protocols, deployment paths, identity rails, data layers, or other infrastructure. **Infrastructural power** — relational power arising when control over infrastructure materially conditions others' access, options, interoperability, or continuity. **Administrative puissance** — effective ability to route, assign, schedule, validate, escalate, record, close, and coordinate work. **Administrative power** — relational power produced when administrative control changes others' timing, workload, access, status, or ability to complete an action. **Execution puissance** — effective ability to transform decisions into coordinated, traceable action. **Cognitive puissance** — effective ability to perceive, reason, synthesize, model, plan, generate, or evaluate. **AI-mediated cognitive puissance** — cognitive capacity amplified through AI tools under explicit governance and human/institutional constraints. **Hidden sovereignty** — effective decision or policy control exercised by a system that is formally described as merely advisory, technical, or assistive. ## Constitutional and institutional terms **Authority** — recognized permission or mandate to perform defined actions within a scope. **Scoped authority** — authority limited by domain, function, duration, jurisdiction, conditions, and review. **Mandate** — explicit basis, purpose, and boundary of legitimate authority. **Separation of functions** — design principle preventing one role or component from silently inheriting unrelated functions. **Functional centrality** — importance of a node to coordination or operation without necessarily implying ownership or sovereignty over the whole system. **Sovereignty** — ultimate or non-subordinate authority within a defined domain. In this repo, technical centrality and practical dependence can create quasi-sovereign effects without formal sovereign status. **Subsidiarity** — placing decisions and authority at the lowest level capable of handling them effectively while preserving necessary coordination. **Federation** — coordination among independently governed nodes or institutions through shared contracts, protocols, or interoperability arrangements. **Local sovereignty** — practical ability of a local deployment or community to govern critical operations and meanings without requiring permanent permission from a remote authority. **Protocol commons** — shared technical or semantic substrate whose reuse and interoperability do not require submission to one commercial or political owner. **Brand stewardship** — governance of official names, marks, certification, and identity separately from protocol ownership or operation. ## Founder and temporal terms **Founder power** — relational leverage derived from authorship, code control, brand ownership, infrastructure, credentials, narrative authority, interpretation, relationships, or unique knowledge. **Founder decentering** — progressive reduction of unique founder dependency through documentation, distributed mastery, independent operation, maintainer pluralism, federation, succession, and reproducibility. **Optionality** — preserved ability to choose among future actions because resources, rights, identity, timing, or commitments have not been irreversibly fixed. **Temporal optionality** — optionality specifically created by retaining control over timing or disclosure. **Identity optionality** — preserved ability to reveal, separate, associate, or withhold public identity under different future conditions. **Release optionality** — preserved ability to decide when and how a retained resource, corpus, asset, or announcement becomes active. ## kOA-specific terms **kOA** — the broader conceptual, cultural, strategic, governance, and narrative framework. **kOA Digital Ecosystem** — the operable digital system-of-systems supporting the cycle `Know → Choose → Act → Remember`. **Kristal** — structured, portable, provenance-preserving knowledge artifact or family of artifacts used to make knowledge auditable, reusable, versioned, and capable of controlled transformation. **Konnaxion** — public collaboration, circulation, coordination, and commons-facing platform layer. **Koali** — credibility/reputation infrastructure envisioned as plural distributions around interoperable structures rather than one universal social-credit authority. **EkoH** — domain-bounded credibility, expertise, ethics, contribution, or trust signal layer, depending on implementation context. **SmartVote** — decision/discoverability mechanism preserving baseline and advisory/weighted readings separately rather than silently replacing political equality. **Orgo** — operational workflow and case-management layer connecting decisions to roles, tasks, routing, escalation, closure, and operational memory. **Capsule** — signed portable deployment/package unit intended to support local operation, verification, rollback, self-hosting, and federation. **SemantiK Architect** — semantic-architecture function concerned with concepts, categories, relations, contexts, and multilingual structures. **SenTient** — semantic reconciliation function concerned with ambiguity, entity linking, uncertain propositions, and structured interpretation. ## Compatibility with earlier Power Dynamics shorthand Earlier drafts used several useful but broader expressions. They remain meaningful if interpreted through the stricter ontology. **Power stock** — legacy shorthand for accumulated resources/assets plus durable relational positions. Prefer specifying the actual stock rather than treating power as a substance stored in one pool. **Power flow** — broad shorthand for movement, mobilization, conversion, mediation, or transfer across the system. Prefer identifying what flows: resources, signals, attention, money, authority, puissance, effects, or returns. **Power return** — shorthand for reusable returns produced by action or power relations. A return may become a resource, asset, relational advantage, or future puissance; it is not necessarily relational power at the moment it returns. **Power reinvestment** — shorthand for using returns to increase future resources, capacity, puissance, or relational leverage. **Power regeneration** — shorthand for recurring cycles in which effects are preserved and reused instead of dissipating, creating renewed or expanded puissance. **Compounding power** — shorthand for cumulative dynamics in which returns increase later relational leverage. Prefer **compounding puissance** when the effect is increased capability without a specified relation to others. **Power reservoir** — avoid as a strict term. Use **resource reservoir**, **epistemic reservoir**, **financial reserve**, or another domain-specific reservoir. Relational power is not stored like a physical substance. ## Repository shorthand **Strong distributed puissance, weak sovereignty** — maximize useful effective capability while limiting non-contestable or terminal control. **Plurality without fragmentation** — allow meaningful divergence while preserving enough shared lineage, contracts, provenance, and interoperability for comparison and recombination. **Instance capture ≠ system capture** — failure or capture of one node should not automatically make alternatives non-viable. **Architecture is governance before governance is written** — schemas, defaults, registries, identity systems, workflows, interfaces, and deployment topology already assign and constrain possibilities before formal policy text is applied. ## Power routing and sharing **Power routing** — explicit design of where generated capability, authority, returns, optionality, visibility, and interpretive leverage are allowed to accumulate. **Power redirection** — deliberate change in the default destination or conversion path of leverage, such as expertise → advice rather than sovereignty or infrastructure → local autonomy rather than operator dependency. **Power sharing** — creation of conditions under which multiple actors can effectively use a capability or participate in a right without requiring exclusive ownership by one actor. **Power devolution** — durable transfer of effective control from a central locus toward local, plural, or lower-level loci. **Self-binding** — public, procedural, contractual, or technical constraints adopted by an actor or institution that make later exercises of power more legible, contestable, or limited. **Narrative self-binding** — use of the same narrative or symbolic channel that creates attention and affiliation to publish ethical limits, anti-domination principles, attribution rules, revision norms, or other constraints on symbolic power. **Protocolization** — conversion of tacit or founder-centric capability into explicit contracts, schemas, specifications, artifacts, tests, and reproducible behavior that others can implement independently. **Ownership decoupling** — separation of a useful function from exclusive ownership of the implementation, brand, registry, or operator that first instantiated it. **Capability commons** — a body of reusable capability that multiple actors can access, reproduce, improve, or instantiate without requiring one terminal owner of the function. **Architect-confirmed design** — a current design intention confirmed in the working process but not yet supported by a canonical source document or direct implementation evidence. It must be labeled separately from source-derived or deployed claims. ## Adversarial resilience terms **Rehearsed counterpower** — counterpower whose activation pathway has been practiced sufficiently that participants know how to recognize a problem, organize objection, invoke procedures, and preserve the result as institutional memory. **Founder opposition test** — resilience test asking whether a system can reject a founder-backed proposal while the founder remains influential. Distinct from the founder absence test. **Epistemic authority corruption** — process by which weak, dependent, misleading, or fabricated authority signals are converted into apparent credibility, consensus, or truth status. **Apparent source independence** — surface appearance that several sources independently support a claim. **Causal source independence** — support that arises from genuinely distinct evidentiary lineages rather than repeated dependence on the same origin. **Worldview fork** — a Kristal branch that intentionally changes assumptions, interpretive rules, or ontological commitments while preserving lineage to the branch from which it diverged. **Tattoo Protocol** — informal name for a reusable civic counterpower pattern derived from a proposed founder-opposition drill: isolate a problematic proposal, document it, mobilize evidence and expertise, organize contestation, seek correction, and preserve the postmortem as reusable memory. ================================================================================================ FILE: power_dynamics/history/central-correction-to-nondomination.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: d26db69f5cafec0f5787cbf247a2275823049102b2e27f61c8686fcc5c7c77bf CONTENT_BYTES: 893 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "From Central Correction to Non-Domination" source_basis: - S09 - S11 - S16 - S19 - S21 - S25 --- # From Central Correction to Non-Domination Some legacy economic proposals imagine very strong global coordination, automated enforcement, sanctions, and monetary controls. Later current-core texts emphasize semantic sovereignty, local operation, auditability, bounded expertise, multiple readings, federation, recourse, and non-domination. The evolution can be summarized as a movement from: > **find a sufficiently just center to correct the system** toward: > **design institutions so that even useful centers remain bounded, contestable, substitutable, and non-terminal**. This is a major constitutional evolution and should remain explicit in the corpus history. ================================================================================================ FILE: power_dynamics/history/dependency-to-empowerment.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 9659d2d8a4950bb49be56c7046a2a061003e4340803dd06d04a25e6f1ae6e7f6 CONTENT_BYTES: 830 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "From Dependency to Empowerment" source_basis: - S01 - S02 - S13 - S25 --- # From Dependency to Empowerment `Abuser l'humanité` diagnoses how debt, time capture, bureaucracy, justice cost, desire, work, and procedural complexity can shrink effective possibility. `Hacking Reality` develops the opposite movement: language, symbols, alliances, learning, narrative, and organization can expand possibility. kOA later formalizes the transition as infrastructure: transform dispersed knowledge and commitment into governed collective action and reusable memory. Power Dynamics therefore inherits both halves: > **How systems shrink effective possibility** and > **How systems generate effective possibility**. ================================================================================================ FILE: power_dynamics/history/founder-to-protocol.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c57200716fcc6386bd319ecc87127be2a4a8ea87327b4fba420bf36beb28149b CONTENT_BYTES: 583 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Founder Power Across Phases" source_basis: - S18 - S25 --- # Founder Power Across Phases A possible maturity trajectory is: 1. founder sovereignty; 2. explicit constitutional constraints; 3. maintainer pluralism; 4. institutional federation; 5. protocol-level continuity. The goal is not to erase authorship. It is to ensure that independent reproduction, operation, interpretation, and branching do not depend on unique founder permission or inaccessible knowledge. ================================================================================================ FILE: power_dynamics/history/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c7d8393007d030196a56c8c56500ac34180cd16b8aefd5c09f301682be6cc647 CONTENT_BYTES: 812 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Genealogy of the Power Model" source_basis: - S01 - S02 - S07 - S10 - S11 - S13 - S16 - S18 - S25 --- # Genealogy of the Power Model The corpus shows an evolution rather than one fixed doctrine. Broadly: 1. **diagnosis of dependency and structural abuse**; 2. **experiments in strong corrective economic institutions**; 3. **language, narrative, alliance, and empowerment**; 4. **knowledge-to-action architecture**; 5. **non-domination, semantic sovereignty, bounded expertise, auditability, federation**; 6. **Power Dynamics synthesis: capability creation plus constitutionalized evolution**. The repository preserves tensions instead of retroactively making all documents agree. ================================================================================================ FILE: power_dynamics/koa/ai.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ab870e24420c7cc24af7b03ff2fa7ce0e5c040092f10b9d365d47b0dc7689dfe CONTENT_BYTES: 785 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "AI and Cognitive Puissance" source_basis: - S13 - S16 - S21 - S25 --- # AI and Cognitive Puissance AI can greatly increase cognitive throughput: reading, synthesis, comparison, generation, translation, semantic processing, and planning. The repository treats AI as **cognitive puissance under governance**, not as an autonomous institutional sovereign. Risks include hidden policy through prompts/defaults, opacity through complexity, semantic centralization, remote-service dependence, unreviewable automation, and substitution of model confidence for governed evidence. AI should assist transformations whose authority remains externally governed and auditable. ================================================================================================ FILE: power_dynamics/koa/brand-narrative.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 4b6f0f38f63a2e5aba46b8cb8568aec777367a879946a2c53fedabe8e5f89934 CONTENT_BYTES: 2020 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Brand, Narrative, and Affiliation" source_basis: - S02 - S04 - S22 - S25 --- # Brand, Narrative, and Affiliation Brand and narrative create communicative, symbolic, and affiliation puissance. They can compress complex meaning into recognizable symbols, lower transmission cost, mobilize supporters, generate commerce, and make a system culturally legible. `system value → brand recognition → attention / affiliation → revenue / network → reinvestment` The constitutional firewall is that brand or narrative does not become truth, expertise, political legitimacy, or protocol sovereignty by itself. ## Narrative self-binding The corpus also uses fiction to publish explicit ethical constraints: clarity of intention, vigilance against monopoly and domination, recognition of contributors, self-mockery, revision, and non-dogmatic transmission. This creates a **narrative self-binding** mechanism. The symbolic layer does not only transmit affiliation; it also transmits limits that participants and critics can reuse against symbolic capture. Public ethics do not replace enforceable governance, but they redirect some narrative power away from unquestionable persona authority and toward explicit principles. See [`../cases/ethical-fiction-self-binding.md`](../cases/ethical-fiction-self-binding.md). ## Sharing symbolic capital The narrative ethics do more than limit abuse. They also redirect symbolic returns: recognize contributors, thank allies publicly, share merit, practice self-mockery, reject dogma, document, transmit, and pass the baton. That means the narrative layer can be designed to **share symbolic capital rather than merely accumulate followers around a persona**. The public-brand distinction between mobilization persona and architect identity reinforces the same direction: the persona functions as a diffusion instrument, not the source of protocol validity. ================================================================================================ FILE: power_dynamics/koa/capsules-federation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 5f7141814fdd72fb928797af1a01609474e4c9238dae5814f1b5d139160a6da8 CONTENT_BYTES: 748 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Capsules and Federation" source_basis: - S16 - S25 --- # Capsules and Federation Capsules and federation create **infrastructural autonomy puissance**: local deployment, signed packages, verification, rollback, self-hosting, offline operation, and independent continuity. Their political importance is counterpower. A system is less terminal when communities can continue operating, substitute a deployment, verify artifacts, or form branches without permanent permission from one remote operator. The technical power audit should inspect signing keys, registries, update channels, compatibility contracts, and recovery procedures. ================================================================================================ FILE: power_dynamics/koa/founder-power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 429a699d468fda6f72f3ae55cab9302a4cd07221040f89acae6d9c65365b6ec7 CONTENT_BYTES: 1704 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Founder Power" source_basis: - S18 - S25 --- # Founder Power Founder power can include authorship and vocabulary, repository and infrastructure control, domains and brand, signing/release keys, unique architectural knowledge, relationships and narrative authority, and public-identity optionality. The question is not whether an early founder has concentrated puissance, but how that dependence changes over time. `Founder capability → encoded architecture → documentation → distributed mastery → maintainer pluralism → independent reproducibility` ## Founder power can be converted into ecosystem capability The desired trajectory is not merely to constrain founder power after it exists. It is to **convert founder-specific assets into shared capability**: > **Founder-powered → Architecture-powered → Protocol-powered → Ecosystem-powered** Koali duplicability, open specifications, reproducible deployments, branch mobility, and public ethical self-binding are examples of this transition. ## Founder fallibility as a power condition Long-lived systems should assume that a founder will eventually be wrong about something. Founder resilience therefore has two separate tests: 1. **absence test** — can the system continue without the founder? 2. **opposition test** — can the system reject the founder's proposal while the founder remains influential? The second test matters because symbolic or reputational authority can survive technical decentralization. A founder-independent protocol with a founder-dependent culture remains partially centralized. ================================================================================================ FILE: power_dynamics/koa/know-choose-act-remember.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 19d458a56e5a45596e10a640842ecf2a6cdf0768d88cb7464326141ed86e8366 CONTENT_BYTES: 851 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Know → Choose → Act → Remember" source_basis: - S13 - S25 --- # Know → Choose → Act → Remember The kOA loop is a capability-regeneration cycle. ### Know Transform dispersed contributions into structured, provenance-preserving knowledge without prematurely erasing ambiguity. ### Choose Transform knowledge into legible orientation while preserving reasons, options, disagreement, and multiple readings. ### Act Transform orientation into responsibilities, tasks, routing, validation, escalation, and outcomes. ### Remember Transform experience into reusable memory that lowers the cost of future action. The political value lies in the **transitions**, because each transition can become a bottleneck or locus of power. ================================================================================================ FILE: power_dynamics/koa/koali-ekoh.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 3b3a2be42815858d6a082e336531f8b45035da456a7943162ddebb273ccd3304 CONTENT_BYTES: 1264 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Koali / EkoH" source_basis: - S15 - S17 - S26 - S28 --- # Koali / EkoH Koali and EkoH address a problem of **latent competence**: people may possess valuable experience or expertise that is difficult for others to discover, verify, or mobilize. The intended transformation is: `competence evidence → legibility → credibility signal → discoverability → opportunity → participation` The constitutional limit is explicit: > **Score ≠ person ≠ competence ≠ truth ≠ sovereignty.** Signals should be domain-bounded, evidence-linked, versioned, contestable, and portable. Multiple distributions or policies can coexist around common interoperability, supporting **plurality without fragmentation**. ## Power-sharing direction A credibility layer becomes politically dangerous if useful recognition is inseparable from one owner, one operator, or one permanent scoring policy. The current design direction is therefore to make Koali **duplicable, shareable, branchable, and capable of plural distributions** rather than a terminal proprietary credibility authority. See [`koali-protocolization.md`](koali-protocolization.md). ================================================================================================ FILE: power_dynamics/koa/koali-protocolization.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 18bc122c87356df1b913e2398358bfffdb479f929d9efa2de24a351591a5201f CONTENT_BYTES: 3208 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "USER-CONFIRMED-DESIGN" scope: "kOA" version: "6.0" title: "Koali: From Property to Protocol" source_basis: - S15 - S17 - S25 - S26 - S28 --- # Koali: From Property to Protocol Koali is a critical test of whether kOA merely creates a new credibility center or **shares the capacity to organize credibility**. The current architect-confirmed design intention is explicit: > **Koali should not remain an exclusive personal property on which everyone else must depend. Its useful capability should be duplicable, shareable, branchable, and capable of plural distributions.** This design intent is recorded here separately from source-derived implementation claims. A canonical Koali distribution specification should eventually replace this note as the primary technical evidence. ## Why this matters Credibility infrastructure can influence: - discoverability; - standing; - opportunity; - certification; - access; - trust; - collaboration; - advisory influence. If one actor permanently owns the only meaningful credibility layer, a mechanism designed to recognize contribution can become a new gatekeeper. ## Protocolization target ```text founder-created concept → explicit kernel / contracts → portable evidence and history → policy identity → multiple distributions → interoperability → independent operation → branch comparison and evolution ``` The political transformation is: > **Personal ownership of a capability → stewardship of an interoperable protocol ecology** ## What can remain distinct Power sharing does not require one universal Koali. Different distributions may legitimately use different criteria for different domains or communities, provided that their policies are explicit enough to interpret. Examples might include academic, engineering, local-community, professional, artistic, or project-specific credibility distributions. This is the intended meaning of: > **Plurality without fragmentation.** ## Minimum power-sharing properties A mature Koali architecture should make the following possible where technically appropriate: 1. **Reimplementation** — another actor can implement the common logic. 2. **Distribution plurality** — multiple operators can run different credibility policies. 3. **Policy legibility** — a score or signal identifies the policy under which it was produced. 4. **Evidence portability** — underlying evidence can be reused without recreating a person's entire history from zero. 5. **Contestability** — signals can be challenged or corrected. 6. **Interoperability** — distributions can exchange or compare structured evidence without pretending they are identical. 7. **Discoverability of alternatives** — one dominant distribution does not become the only socially visible one by default. 8. **Branch mobility** — an improved distribution can gather adoption and become viable. ## Constitutional limit > **Credibility signal ≠ person ≠ competence ≠ ethics ≠ truth ≠ sovereignty.** Koali is strongest as infrastructure when it helps other actors make informed judgments while refusing to become the unique owner of social legitimacy. ================================================================================================ FILE: power_dynamics/koa/konnaxion.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 8074805970509a45962d51579ceb2d1e28871ec215760bc161089881e9e7283f CONTENT_BYTES: 660 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Konnaxion" source_basis: - S15 - S18 - S25 --- # Konnaxion Konnaxion creates **associative, communicative, discovery, and coordination puissance** by making people, projects, knowledge, deliberation, and actions visible and connectable. Power relations may arise through moderation, ranking, recommendation, search, routing, identity, access controls, default feeds, and institutional recognition. Because discoverability is governance, Konnaxion should be analyzed as a pre-political mediation infrastructure, not merely a social interface. ================================================================================================ FILE: power_dynamics/koa/kristal.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 13435ad31e387e5c3d62725fc271107d961833f0ced0f9ce537bb80a83df1acd CONTENT_BYTES: 1578 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.1" title: "Kristal" source_basis: - S13 - S16 - S25 --- # Kristal Kristal creates **epistemic and mnemonic puissance** by structuring claims, provenance, status, versioning, lineage, validation, and reusable artifacts. Potential power relations arise around authority registries, trust roots, validation thresholds, canonical/reference promotion, reader policies, release/version selection, and federation/import rules. Plurality is constitutionally important: competing or complementary Kristals can preserve different evidence, interpretations, scopes, policies, or even incompatible worldview axioms. The system should make lineage and differences legible rather than silently declaring one permanent universal truth. This includes three distinct branch types that should not be conflated: - **reference branches** — maintained as broadly useful encyclopedic or institutional references; - **worldview branches** — intentionally adapt assumptions or interpretations to a community's beliefs; - **fictional / experimental branches** — alter world axioms for narrative, simulation, or adversarial testing. Forkability does not imply equal evidentiary support. A system can permit a branch to exist while still making provenance, contradiction, uncertainty, validation policy, and source independence visible. The strongest technical audit still requires direct current specifications for trust roots, policies, registries, signatures, and federation behavior. ================================================================================================ FILE: power_dynamics/koa/multilingualism.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 0c4a5f1f643ef572ee43abc049aa8d300b760eca8a8e56132d1f317bdadb963a CONTENT_BYTES: 737 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Multilingualism, Reach, and Semantic Participation" source_basis: - S16 - S22 --- # Multilingualism, Reach, and Semantic Participation Multilingualism creates two distinct capacities. **Reach puissance** expands geographic and linguistic participation. **Semantic participation puissance** lets communities participate without abandoning their language, categories, and local meaning structures. Translation is therefore political. A system can claim global reach while imposing one dominant ontology through translation defaults. Traceability, uncertainty, local revision, and plural mappings are important safeguards. ================================================================================================ FILE: power_dynamics/koa/orgo.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: bc94b509262a72041622b41c58312043e208541f0d55c1680f525a8ac4de85ec CONTENT_BYTES: 730 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Orgo" source_basis: - S13 - S21 - S25 --- # Orgo Orgo creates **operational and administrative puissance** by transforming signals and decisions into cases, tasks, owners, routing, escalation, time windows, closure, and operational memory. Administrative power appears because control over workflow can alter timing, workload, access, escalation, completion, and practical implementation. Key audit questions: who creates/closes cases, who assigns roles, who controls escalation, what deadlines/defaults exist, how conflicts are appealed, and whether administration can silently redefine the underlying mandate. ================================================================================================ FILE: power_dynamics/koa/propagation-adoption.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 3374d9d890488aefb3529717d0e73ddb74bc0d10283440f5d258c4decd396201 CONTENT_BYTES: 2690 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "kOA Propagation and Adoption" source_basis: - S13 - S15 - S16 - S18 - S21 - S25 - S28 - S29 --- # kOA Propagation and Adoption kOA does not need one universal acquisition channel. Its architecture supports multiple entry paths that can converge on the same knowledge-to-action infrastructure. ## Adoption path ```text entry surface → contextual understanding → inspectable evidence → bounded trial → local value → operational continuity → independent mastery → optional federation ``` ## Entry surfaces - technical code / documentation; - public-good / sovereignty framing; - SmartVote / collective judgment; - Kintsugi integration; - cultural provenance / Kreative; - multilingual access / SemantiK; - education / UCKK; - concrete operational workflow / Orgo; - Worlds / scenario-specific demonstrations; - cultural narrative and media. ## Why local value matters The propagation model is strongest when an instance can be useful before network scale. ```text local value → independent adoption → reproducible instance → compatibility → optional exchange → network value ``` This avoids making federation a prerequisite for first usefulness. ## Why existing systems can strengthen kOA Kintsugi-oriented integration changes the competitive geometry. A capable external tool can become: - a preserved authority; - an annexed sidecar; - a data / artifact source; - a Kompendio reference; - a complementary capability. The desired gravity is therefore **articulation by usefulness**, not forced replacement. ## Why SmartVote can strengthen adoption SmartVote can act as a system-wide discoverability primitive. As more evaluable objects, domains, evidence, and contribution histories exist, the platform can potentially generate more useful contextual rankings. That creates a candidate loop: `objects → evaluation → discovery → reuse → more objects`. The loop remains legitimate only if raw participation remains visible, expertise is bounded, and ranking policy is inspectable and contestable. ## Why the movement is a test environment Once multiple independent contributors exist, using kOA to coordinate kOA can test the architecture under real conditions. The important threshold is not a label such as “movement.” It is **multi-actor autonomous capacity**: - people can initiate work; - coordinate; - preserve memory; - challenge decisions; - operate infrastructure; - train successors; - continue during founder absence. That threshold is both an adoption milestone and a founder-decentering milestone. ================================================================================================ FILE: power_dynamics/koa/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 44d066857b307ebfe64f3fe58ed41aa32688494fc604353fca05aa03f9a44f6d CONTENT_BYTES: 2694 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "kOA as a Capability and Power Ecology" source_basis: - S13 - S25 --- # kOA as a Capability and Power Ecology This directory is the **systems core of the Power Show**. kOA is analyzed first as an architecture that can make actors more capable, then as an architecture whose successful capabilities can create consequential relations of power. The operative loop is: > **Know → Choose → Act → Remember → Know better** The Power Show asks: 1. **What new capability does each subsystem create?** 2. **How does that capability compose with other subsystems?** 3. **What returns does successful action preserve?** 4. **How does the result increase later capability?** 5. **Can those returns activate capability in another branch, actor, deployment, or community?** Power Dynamics then asks: 6. **What power relations arise around successful use?** 7. **What conversion, stacking, capture, or dependency risks appear?** 8. **What counterpowers exist?** 9. **Can alternative branches remain viable and evolve?** ## kOA capability stack - **SemantiK / SenTient** — semantic puissance; - **Kristal** — epistemic and mnemonic puissance; - **Konnaxion** — collective, network, communication, and discoverability puissance; - **Koali / EkoH** — credibility legibility; - **SmartVote** — comparative and deliberative puissance; - **Orgo** — operational and administrative puissance; - **AI** — cognitive amplification under governance; - **Capsules / federation** — deployment, substitution, replication, and branch puissance; - **brand / narrative** — recognition, affiliation, transmission, and economic conversion; - **multilingual layer** — semantic access and distribution across languages. The primary system map is [`system-map.md`](system-map.md). The broader showcase is [`../POWER-SHOW.md`](../POWER-SHOW.md). - [`koali-protocolization.md`](koali-protocolization.md) — Koali as a power-sharing test: from personal property toward plural interoperable distributions. ## Power-surface reading kOA should also be read across domains rather than only by component. The same component can generate epistemic, political, economic, administrative, narrative, or infrastructural effects through conversion. See [`../POWER-SURFACE.md`](../POWER-SURFACE.md) and [`../domains/README.md`](../domains/README.md). - [`propagation-adoption.md`](propagation-adoption.md) — how local value, demonstrations, deployment tooling, human replication, integration, multilingual access, and cross-branch returns can combine into an adoption and propagation ecology. ================================================================================================ FILE: power_dynamics/koa/returns-compounding.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 097ef104342a19dfa62307c58c3117784f6a107c24c0cd930a12f6e59bcd560b CONTENT_BYTES: 843 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "kOA Returns and Compounding" source_basis: - S13 - S25 - S26 --- # kOA Returns and Compounding kOA can produce returns in several domains: validated knowledge, reusable Kristals, code, operational experience, contributor credibility, network connections, institutional memory, brand recognition, economic resources, standards, and interoperability. These returns can feed other systems and lower future coordination cost, creating a **power ecology of compounding capability**. The same loop can create concentration. Recognition can generate visibility, visibility opportunity, and opportunity more recognition. Power Dynamics therefore tracks who receives returns and whether alternatives can accumulate comparable assets. ================================================================================================ FILE: power_dynamics/koa/semantik-sentient.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f3c3247eac7a2b9a5882c346abd57a717981b6b2976cf582cf50c78bbedfed07 CONTENT_BYTES: 774 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "SemantiK Architect and SenTient" source_basis: - S13 - S16 - S22 --- # SemantiK Architect and SenTient SemantiK Architect concerns the architecture of meaning: concepts, categories, relations, contexts, and multilingual mappings. SenTient concerns reconciliation of ambiguous or uncertain propositions, entity relations, and semantic interpretation. These functions create semantic puissance but can also create **constitutive power** if their categories become mandatory or opaque. Semantic sovereignty therefore requires versioned ontologies, explicit uncertainty, local control where appropriate, traceable transformations, and meaningful alternatives. ================================================================================================ FILE: power_dynamics/koa/smartvote.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f92a7961e46d6ce73fcde78b30d2540a15f63e919f2988ba71b1590cf5a76849 CONTENT_BYTES: 1839 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.2" title: "SmartVote" source_basis: - S15 - S17 - S28 --- # SmartVote SmartVote creates **comparative judgment and discoverability puissance** by preserving multiple readings of support rather than hiding evaluation inside one opaque score. A critical separation is between baseline/raw democratic readings and expertise/ethics or other advisory readings. The political baseline is not silently superseded by advisory weight. Domain-bounded credibility informs rather than automatically governs. Power relations arise through lens selection, defaults, criteria, discoverability, ranking, and institutional interpretation of weighted results. Those elements require explicit registries, versioning, auditability, and branch alternatives. ## Academic constraints The external-research layer documents several constraints directly relevant to SmartVote: - expert performance is strongly domain- and task-bounded; - nonexperts need evidence for deciding which experts to trust; - calibrated / contribution-sensitive weighting can improve some aggregates; - diversity can add problem-solving value that is lost by selecting only individually high-scoring participants; - social-choice systems face manipulation and impossibility constraints under broad conditions; - any reputation or weighting metric becomes a gaming surface once it affects opportunity or authority. See [`../Academic-Lineage/06-expertise-smartvote-and-collective-judgment.md`](../Academic-Lineage/06-expertise-smartvote-and-collective-judgment.md) and [`../Academic-Lineage/07-metrics-reputation-and-gaming.md`](../Academic-Lineage/07-metrics-reputation-and-gaming.md). These references constrain the design; they do not validate a particular SmartVote formula. ================================================================================================ FILE: power_dynamics/koa/system-map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 9c151ee921ca860734ab06a1d9cc39797bff7b360f0efb23b400dad378ca9392 CONTENT_BYTES: 3032 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "kOA System Map" source_basis: - S13 - S15 - S16 - S18 - S21 - S25 --- # kOA System Map The high-level capability chain is: > **Contribution → Resolution of meaning → Structured knowledge → Discovery / credibility → Collective choice → Governed work → Coordinated action → Experience → Reusable memory → New cycle** ## Capability map ```text SemantiK / SenTient semantic structure ↓ Kristal knowledge + provenance + memory ↓ Konnaxion circulation + people + discovery ↓ Koali / EkoH credibility context ↓ SmartVote comparison + advice + choice ↓ Orgo routing + responsibility + execution ↓ Outcomes ↓ Kristal / operational memory reusable learning ↺ ``` Cross-cutting layers: - **AI** — cognitive amplification; - **Capsules / federation** — portability, deployment, substitution, branch formation; - **brand / narrative** — recognition, affiliation, transmission; - **multilingual semantics** — linguistic access and semantic participation. ## Power overlay Each capability surface can also become a power surface: | Capability surface | Possible relational power | |---|---| | semantic structuration | classification / framing / ontology power | | knowledge validation | epistemic authority / standard-setting | | discoverability | ranking / visibility / agenda power | | credibility interpretation | recognition / standing / opportunity power | | decision support | default / weighting / advisory influence | | workflow | routing / timing / escalation / closure power | | memory | precedent / institutional-memory power | | federation infrastructure | signing / update / compatibility / registry power | | AI | hidden interpretation / prioritization power | | brand | attention / affiliation / legitimacy-by-association | The constitutional problem is therefore not whether kOA should be powerful. Its purpose is to generate capability. The problem is whether the relations created by successful capability remain **scoped, inspectable, contestable, substitutable, and evolvable**. ## Cross-domain overlay The same system can be read as a multi-domain power surface: ```text Semantics / knowledge → credibility / discoverability → political judgment → allocation → administrative execution → returns / memory → economic + institutional compounding ``` Cross-cutting economic, political, and monetary questions should therefore be audited separately: - **political** — who gains standing, agenda, mandate, and decision influence? - **economic** — who controls or receives scarce resources and returns? - **monetary** — who controls exchange rails, liquidity, credit, settlement, or transaction access where those functions exist? - **routing** — who receives capability, authority, returns, and optionality? See [`../POWER-SURFACE.md`](../POWER-SURFACE.md). ================================================================================================ FILE: power_dynamics/LICENSE.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 266e240dcb7657e8290e0cea2f8115617834c7a20b8db11a61c033bf0a8a0ea7 CONTENT_BYTES: 336 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "SOURCE-DERIVED" scope: "GENERAL" version: "6.0" title: "License" source_basis: - S01 --- # License This repository is provided as a research and conceptual framework. Individual source documents retain their own licenses and rights. Source inclusion or citation does not transfer ownership. ================================================================================================ FILE: power_dynamics/POWER-ROUTING.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 88caf4a93bbbdd6daedb0b46411ecd0c7fa9a23e49165acceabbd35eeb9e1a06 CONTENT_BYTES: 5814 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.1" title: "Power Routing, Sharing, and Devolution" source_basis: - S02 - S14 - S15 - S16 - S17 - S18 - S21 - S22 - S25 --- # Power Routing, Sharing, and Devolution Power Dynamics does not stop at **how much power kOA can generate**. It asks: > **Where does the capability, leverage, authority, return, and optionality created by kOA actually go?** A system can empower users while still making its operator indispensable. Power routing therefore examines four destinations separately: ```text CAPABILITY → who can do more? AUTHORITY → who can decide or control more? RETURNS → who receives reusable value? OPTIONALITY→ who can refuse, leave, reproduce, fork, or wait? ``` ## Core routing mechanisms | Source of leverage | Concentrating default | Routing / sharing mechanism | Intended destination | |---|---|---|---| | Founder knowledge | permanent founder dependency | documentation, schemas, protocolization, tests | maintainers, branches, independent operators | | Founder / persona authority | deference becomes policy or truth immunity | published fallibility, contestation, opposition rehearsal | independent public judgment | | Reference knowledge branch | reference becomes truth monopoly | forkability, lineage, evidence comparison | plural epistemic capacity | | Narrative attention | founder/persona centrality | explicit ethics, self-critique, attribution, anti-domination | public principles, procedures, critical readers | | Brand | trademark becomes protocol sovereignty | brand stewardship separated from protocol | protocol commons + bounded official brand | | Koali credibility infrastructure | one owner defines standing | plural distributions, portable evidence, explicit policy identity | communities, domains, alternative operators | | Expertise | expert becomes ruler | baseline + bounded advisory readings | informed public judgment | | Knowledge validation | one owner of truth | provenance, reader policies, competing Kristals | plural epistemic capability | | Infrastructure | operator becomes unavoidable | self-hosting, capsules, federation, rollback, substitution | local operators / communities | | Money | wealth buys rule | one-member-one-vote / allocation firewalls | common funding without pay-to-rule | | Workflow control | administrator becomes policymaker | scoped mandate, audit, appeal, revocability | execution without mandate capture | | AI capability | model becomes hidden sovereign | explicit role boundaries, provenance, human authority | cognitive amplification without institutional sovereignty | | Dominant branch | incumbency becomes final | branch mobility, lineage, recombination | viable alternatives | ## Ethical fiction as power routing The fiction is not only a vehicle for symbolic puissance. It also publishes limits on that puissance. The source corpus includes explicit commitments around: - clarity of intention; - respect for living beings; - vigilance against monopoly, domination, and manipulation; - recognition of contributors and sharing merit; - self-mockery and refusal to sanctify the Klown; - revision, criticism, adaptation, and transmission rather than dogma. Power Dynamics calls this **narrative self-binding**. ```text symbolic power → public ethical commitments → stable grounds for criticism → reduced freedom for arbitrary reinterpretation ``` Self-binding is not proof of compliance. It makes the exercise of power **more legible and criticizable**. ## Koali: from property to protocol ecology Current architect-confirmed design direction: > **Koali should not remain a terminal personal credibility authority. Its useful capability should be duplicable, shareable, branchable, and operable through plural distributions around interoperable structures.** The desired transition is: ```text founder-created capability → explicit kernel / contracts → portable evidence and history → explicit policy identity → multiple distributions → interoperability → independent operation → branch mobility ``` This is not founder erasure. It is **ownership decoupling**: the useful function can outgrow exclusive ownership of the first implementation. ## Power sharing is not flatness The goal is not to make everyone equally expert, equally responsible, or equally authoritative. The goal is: > **Useful asymmetry without terminal dependency.** A maintainer may have more technical authority within a defined scope. An expert may have more epistemic relevance in a defined domain. A coordinator may have routing authority for a workflow. None of those roles should silently acquire unrelated sovereignty. ## Routing and conversion firewalls Routing is strongest when paired with conversion limits: ```text expertise → advice ✓ expertise → sovereign vote weight ✗ money → funding ✓ money → political standing ✗ brand → attention ✓ brand → truth ✗ infrastructure → capability ✓ infrastructure → captivity ✗ execution → implement mandate ✓ execution → redefine mandate ✗ ``` ## Canonical routing test For every important kOA mechanism: 1. What puissance does it create? 2. Where would that puissance naturally concentrate? 3. What relational power does that concentration create? 4. What capability can be routed outward instead? 5. What authority must remain scoped? 6. Who receives the returns? 7. Who receives exit / substitution / fork optionality? 8. What evidence proves that the routing is practical rather than merely formal? See [`assessment/power-routing-audit.md`](assessment/power-routing-audit.md). ================================================================================================ FILE: power_dynamics/POWER-SHOW.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 430ec4f29fab36df9d43d02f9d0c199b411226d4766c09c64bcf272d9c30d1d3 CONTENT_BYTES: 8643 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "The kOA Power Show" source_basis: - S02 - S10 - S13 - S14 - S15 - S16 - S17 - S18 - S21 - S22 - S25 - S26 --- # The kOA Power Show The first purpose of this repository is simple: > **Show all the ways kOA can make people, groups, organizations, institutions, and federations more capable.** Then ask what happens when those capabilities become socially consequential. ## The one-paragraph answer kOA is immensely powerful because it can connect **meaning, knowledge, AI, discovery, credibility, networks, deliberation, political choice, economic allocation, coordination, execution, memory, infrastructure, federation, and institutional evolution** inside a recursive loop. The result is not merely more information. It is the possibility of turning distributed resources into collective agency, preserving the returns of action, reinvesting them, reproducing the capability elsewhere, and routing important forms of leverage away from terminal ownership. > **Breadth × Composition × Closure × Memory × Compounding × Propagation × Replication × Routing** ## 1. Breadth — many forms of puissance kOA can generate or amplify: - semantic puissance; - epistemic puissance; - cognitive / AI-mediated puissance; - information and distribution puissance; - attention / discoverability puissance; - credibility / reputation puissance; - network and affiliation puissance; - collective puissance; - political / deliberative / decision puissance; - economic and allocation puissance; - monetary / liquidity capability where monetary infrastructure exists; - administrative and operational puissance; - technical and infrastructural puissance; - narrative / symbolic / brand puissance; - mnemonic and temporal puissance; - federation, exit, substitution, fork, and evolutionary puissance. See [`POWER-SURFACE.md`](POWER-SURFACE.md). ## 2. Composition — the whole can exceed the sum ```text SemantiK / SenTient → meaning Kristal → knowledge + provenance + memory Konnaxion → discovery + network + circulation Koali / EkoH → credibility legibility SmartVote → comparative judgment + decision support Orgo → operational execution AI → cognitive amplification Capsules / federation→ replication + substitution Brand / narrative → transmission + affiliation Economic rails → funding + material capability ↓ compose ↓ coordinated collective puissance ``` A capable population is not automatically a capable collective. Composition creates the ability to use distributed capabilities **together**. ## 3. Closure — knowledge reaches action > **Know → Choose → Act → Remember → Know better** Many systems stop at one stage. kOA attempts to connect the stages. ```text knowledge → judgment → decision → governed work → execution → result → memory ``` This turns intelligence into agency. ## 4. Memory — the past remains usable kOA can preserve: - evidence; - provenance; - definitions; - decisions; - reasons; - workflows; - failures; - outcomes; - contribution history; - branch lineage. Without memory, a collective repeatedly pays the cost of rediscovery. With memory, past action becomes infrastructure for future action. ## 5. Compounding — action creates future capability ```text Puissance → Action → Result → Return → Asset → Reinvestment → Greater Future Puissance ``` Returns can include knowledge, code, tools, data, credibility, network, reputation, money, infrastructure, access, and optionality. This is the **compounding engine**. ## 5A. Propagation — returns can activate capability elsewhere A system can compound internally without becoming easier for anyone else to reproduce or adopt. Propagation begins when reusable returns cross boundaries: ```text revenue → development capacity pilot → evidence → credibility → institutional access training → operator → independent deployment documentation → lower review cost → external feedback integration → broader capability → new integration demand ``` When several such loops exchange returns, kOA can exhibit **coupled propagation**. See [`PROPAGATION.md`](PROPAGATION.md) and [`showcase/15-propagation-engine.md`](showcase/15-propagation-engine.md). ## 6. Cross-domain conversion — one capability unlocks another ```text knowledge → credibility → visibility → opportunity money → infrastructure → reach → influence brand → affiliation → revenue → development network → collaborators → execution → results memory → lower coordination cost → faster action ``` Conversion is one reason kOA can become extremely powerful. It is also one reason it can become dangerous. > **Functional Control → Cross-Domain Power** See [`framework/10-cross-domain-power-conversion.md`](framework/10-cross-domain-power-conversion.md). ## 7. Political power — before, during, and after the vote kOA touches: > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** That means political power is not confined to SmartVote or formal governance. Semantic definitions, search, ranking, credibility, workflow, and memory can all shape political possibility. ## 8. Economic power — resources become action kOA can help convert: ```text money / property / funding / labor / infrastructure → usable economic capacity → projects / services / coordination / production ``` It can also route economic resources through democratic allocation mechanisms rather than allowing wealth to automatically buy more political standing. ## 9. Monetary power — control of exchange rails Monetary power concerns issuance, liquidity, settlement, payment rails, reserves, credit, debt conditions, and transaction access. The legacy KingCoin material shows why this domain is so constitutionally sensitive: monetary control can stack with taxation, allocation, sanctions, and administration into highly terminal power. The evolved doctrine is therefore not “centralize monetary power well,” but: > **If powerful monetary functions exist, keep their authority scoped, contestable, separable, and substitutable.** ## 10. Scaling — individual to federation ```text individual → team → organization → institution → federation ``` At each scale, kOA can add shared knowledge, coordination, decision, execution, memory, and infrastructure. The design target is: > **Capability can scale without sovereignty scaling at the same rate.** ## 11. Replication — capability can leave the center Self-hosting, capsules, portability, federation, and branchability can transform: ```text use a central service ``` into: ```text possess / reproduce / operate the function locally ``` That is a major transfer of effective possibility. ## 12. Power routing — kOA can equip others instead of only itself The project includes mechanisms intended to redirect the power it creates: ```text expertise → advice, not sovereignty money → funding, not more votes narrative → mobilization + ethical self-binding Koali → plural distributions, not terminal personal ownership Kristal → portable knowledge, not one owner of truth infrastructure → self-hosting / federation, not captivity dominance → branch mobility, not final authority ``` This is why **power sharing** is part of the Power Show, not merely a later defensive layer. ## 13. The constitutional paradox The stronger the Power Show becomes, the more necessary constitutional design becomes. ```text more knowledge capability → more validation power more discovery capability → more agenda power more credibility capability → more standing power more workflow capability → more administrative power more infrastructure capability → more dependency power ``` Therefore: > **The constitution exists because the Power Show succeeds.** ## 14. The mature doctrine > **Generate immense puissance.** > **Compose it.** > **Close the loop.** > **Preserve the returns.** > **Compound future capability.** > **Make cross-domain conversions visible.** > **Route capability outward.** > **Block automatic conversion into unrelated sovereignty.** > **Preserve verification, contestation, substitution, exit, and forkability.** > **Allow the whole system to evolve.** In compressed form: > **Strong distributed puissance. Weak sovereignty.** ================================================================================================ FILE: power_dynamics/POWER-SURFACE.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 1181145076011b3b1fcccf9ebfe7e44dc3862aa04451969be28540b80047491d CONTENT_BYTES: 6573 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "The kOA Power Surface" source_basis: - S02 - S10 - S13 - S14 - S15 - S16 - S17 - S18 - S21 - S22 - S25 - S26 - S28 --- # The kOA Power Surface A **power surface** is any function, interface, role, registry, workflow, standard, narrative, resource rail, or infrastructural boundary through which control can materially alter effective possibility. The kOA Power Show is strongest when it makes the whole surface visible at once. > **kOA is powerful because it can create capability across many domains and connect those domains into conversion and feedback loops.** ## Master map | Domain | Generated puissance | Relational power that may emerge | Typical conversion outward | kOA routing / firewall direction | |---|---|---|---|---| | Epistemic | validate, compare, preserve, reuse knowledge | validation, canon, trust-root | knowledge → credibility | portable artifacts, provenance, competing Kristals | | Semantic | structure concepts, categories, translation, ambiguity | classification, framing, admissibility | meaning → agenda / enforcement | versioned semantics, local governance, contestation | | Cognitive / AI | reasoning, synthesis, modeling, translation | hidden framing, prioritization, dependency | cognition → judgment / execution | AI under explicit governance, bounded authority | | Information / attention | publish, search, rank, distribute, amplify | visibility, agenda, moderation | attention → affiliation / legitimacy / funding | explicit discovery policies, alternatives, export | | Credibility / reputation | make evidence of competence/contribution legible | standing, certification, opportunity | credibility → visibility / access | domain-bounded signals, plural models, contestation | | Network / affiliation | association, brokerage, recruitment, diffusion | inclusion, exclusion, access | network → execution / opportunity | portable identity/relationships where feasible, plural networks | | Political / constitutional | deliberate, decide, authorize, amend, govern | mandate, veto, legitimacy, decision | political → administrative / allocation | political equality, scoped authority, contestation | | Economic | mobilize scarce resources, assets, labor, funding | bargaining, ownership, allocation | money → infrastructure / reach | democratic allocation, anti-pay-to-rule firewalls | | Monetary | liquidity, exchange, payment, credit, settlement | issuance, rail, reserve, access | monetary → economic / political dependency | treat high-stack monetary designs as constitutional risk | | Administrative / operational | assign, route, schedule, escalate, close | timing, workload, approval, closure | administration → de facto policy | explicit workflows, audit, appeal, revocability | | Technical / infrastructural | build, deploy, verify, operate, reproduce | compatibility, update, identity, dependency | infrastructure → standards / access | self-hosting, capsules, federation, substitution | | Narrative / symbolic / brand | memory, attention, affiliation, transmission | framing, legitimacy-by-association, gatekeeping | brand → attention → revenue / adoption | ethical self-binding, brand ≠ truth, protocol separation | | Mnemonic / temporal | preserve reasons, outcomes, precedent, timing | precedent, delay, succession | memory → future agenda / legitimacy | provenance, versioning, alternative histories | | Evolutionary / counterpower | fork, substitute, recombine, replace | displacement of incumbents | alternative → support → dominance | branch mobility, lineage, interoperability | ## Why breadth matters A system that is powerful in one domain can still be constrained by other systems. A system that touches many domains can create much larger **cross-domain leverage**. For example: ```text semantic control → epistemic interpretation → credibility → visibility → agenda → political influence ``` or: ```text money → infrastructure → distribution → attention → affiliation → political leverage ``` or: ```text technical control → defaults → dependency → administrative necessity → de facto governance ``` The same breadth that makes kOA capable is therefore the reason it needs explicit constitutional design. ## Political surface kOA can influence political capacity through: - issue formation and semantic framing; - discoverability and agenda formation; - credibility and advisory signals; - deliberation and proposal comparison; - voting / reading mechanisms; - resource allocation; - workflow and execution; - memory and precedent; - branch evolution and institutional alternatives. Political power therefore begins **before the vote** and continues **after the vote**. ## Economic surface Economic puissance includes the ability to mobilize: - money; - property; - productive assets; - labor and time; - infrastructure; - funding; - contracts; - procurement; - philanthropy; - bargaining position. kOA can increase economic capability by improving coordination, credibility, discoverability, resource pooling, allocation, execution, and compounding. ## Monetary surface Monetary power is narrower than economic power. It concerns control over: - issuance; - units of account; - liquidity; - payment rails; - settlement; - reserves; - credit and debt conditions; - convertibility; - transaction access. A monetary layer can become extraordinarily powerful because it conditions other domains. This is why the legacy KingCoin proposals are useful as a **stacking stress test**, not as current constitutional doctrine. ## The core constitutional question For every surface, ask: 1. **Who gains capability?** 2. **Who gains authority?** 3. **Who receives returns?** 4. **Who gains optionality?** 5. **What other domain can this convert into?** 6. **What prevents that conversion from becoming arbitrary?** 7. **Can affected actors verify, contest, substitute, exit, or fork?** The desired architecture is not flatness. It is a **governable ecology of strong capabilities and non-terminal asymmetries**. ## Continue - [`showcase/12-cross-domain-power-surface.md`](showcase/12-cross-domain-power-surface.md) - [`showcase/13-political-economic-monetary-power.md`](showcase/13-political-economic-monetary-power.md) - [`framework/10-cross-domain-power-conversion.md`](framework/10-cross-domain-power-conversion.md) - [`POWER-ROUTING.md`](POWER-ROUTING.md) - [`domains/README.md`](domains/README.md) ================================================================================================ FILE: power_dynamics/PRINCIPLES.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6533284462887d2515c96f69e764ce3bb7e4691bd231fc85a7d8b688517efa97 CONTENT_BYTES: 10732 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Principles" source_basis: - S01 - S02 - S13 - S14 - S15 - S16 - S17 - S18 - S21 - S22 - S25 - S28 --- # Principles Power Dynamics begins from an affirmative premise: **people and collectives should be able to become dramatically more capable**. The constitutional problem is how to preserve that capability without allowing successful functions to harden into arbitrary, cross-domain, or terminal sovereignty. ## Generate immense but usable puissance 1. **Increase effective possibility.** expand what actors can realistically understand, choose, build, coordinate, refuse, preserve, and accomplish. 2. **Turn dispersed resources into mobilizable capability rather than merely accumulating resources.** 3. **Collective puissance can be generated.** coordinated capability can exceed the sum of isolated capabilities. 4. **Infrastructure should crystallize past effort into reusable future capacity.** 5. **Knowledge, memory, tools, and institutional learning should become cumulative.** 6. **Capability should scale from individual to federation without requiring sovereignty to scale at the same rate.** 7. **Composition does not require ownership.** interoperating functions need not collapse into one owner or authority. ## Keep domains explicit 8. **Political power, economic power, and monetary power are distinct even when they convert into one another.** 9. **Political power begins before formal decision.** meaning, visibility, credibility, and agenda are political surfaces. 10. **Economic puissance concerns mobilization of scarce resources.** economic power concerns relational effects of that control. 11. **Monetary power concerns the infrastructure and conditions of exchange.** issuance, rails, liquidity, settlement, reserves, credit, and access. 12. **Administrative power can alter outcomes without changing formal policy.** 13. **Semantic and epistemic power can shape the field in which later political decisions become intelligible.** 14. **Every domain analysis should name resources, capability, relation, conversion paths, duration, and counterpowers.** ## Maintain ontological discipline 15. **Resource ≠ Potential ≠ Capacity ≠ Puissance ≠ Power.** 16. **A resource is not automatically power.** 17. **Puissance is effective mobilizable capacity under real conditions.** 18. **Power is relational and domain-specific.** 19. **Power to / with / through are primarily capability questions.** power over is primarily a relational question. 20. **Stock, reservoir, flow, reach, influence, authority, legitimacy, and sovereignty are not synonyms.** ## Expose conversion and stacking 21. **Different forms of puissance should remain composable without automatically converting into unrelated authority.** 22. **Expertise may inform.** it does not automatically govern. 23. **Money may fund.** it does not automatically buy political standing. 24. **Brand may attract attention.** it does not become truth. 25. **Technical administration may maintain infrastructure.** it does not silently inherit political authority. 26. **Credibility may improve discoverability.** it does not become unquestionable legitimacy. 27. **Execution may carry out a mandate.** it does not silently redefine the mandate. 28. **Infrastructure may create capability.** it does not thereby own its users. 29. **Power stacking must be assessed across domains, not function by function.** 30. **Capture is a conversion problem.** Functional Control → Cross-Domain Power. ## Route and share power deliberately 31. **Power should be routed, not merely constrained after concentration.** 32. **Generated capability should preferentially become reusable capability for participants and communities where feasible.** 33. **Public ethical commitments can be a self-binding mechanism.** they do not prove compliance but create stable grounds for criticism. 34. **Narrative power should carry its own limits through explicit anti-domination, attribution, humility, and revision principles.** 35. **Protocolization is power sharing.** tacit founder mastery should become explicit, testable, documented, and independently reproducible. 36. **Useful functions should be decoupled from exclusive ownership where feasible.** 37. **Koali is a key ownership-decoupling test.** credibility capability should be duplicable, shareable, branchable, and capable of plural distributions. 38. **Returns are part of power routing.** who receives knowledge, money, reputation, network, code, memory, and infrastructure is constitutional. 39. **Exit, substitution, self-hosting, and forkability distribute optionality.** 40. **Sharing capability does not require flatness.** the target is non-terminal asymmetry. 41. **The strongest center is one that can create capability beyond itself.** ## Make emerging power legible 42. **Architecture is governance before governance is written.** 43. **Every technical boundary is also a potential political boundary.** 44. **Every mechanism that distributes capability creates a new locus of power.** 45. **Dependency is a gradient.** formal choice is not effective choice when switching costs are prohibitive. 46. **Terminal power is a primary constitutional risk.** 47. **Functional centrality is not automatically domination, but centrality plus dependency plus weak counterpower can become domination.** 48. **Instance capture must not imply system capture.** ## Preserve counterpower 49. **Verification + Contestation + Substitution + Exit are foundational counterpowers.** 50. **Formal exit is insufficient.** exit must be effective. 51. **Formal forkability is insufficient.** branch mobility matters. 52. **Revocability and reversibility are distinct.** 53. **Strong hubs are compatible with distributed capability when the whole remains independently reproducible.** 54. **Portability must include the artifacts, history, provenance, evidence, and configuration needed for meaningful continuity.** ## Preserve epistemic humility 55. **No measure of competence, ethics, credibility, contribution, or legitimacy should be treated as perfectly complete or permanently final.** 56. **Score ≠ person ≠ competence ≠ ethics ≠ truth.** 57. **Support is not evidence.** 58. **Dominance is not truth, quality, or final legitimacy.** 59. **Uncertainty, disagreement, and competing representations must remain representable.** 60. **Plurality is useful when it adds evidence, context, method, function, challenge, translation, or synthesis.** ## Make capability regenerative 61. **Action should leave assets behind.** 62. **Who receives the returns matters.** 63. **Returns can compound future puissance.** 64. **Compounding can also compound concentration and must be audited.** 65. **Shared infrastructure should convert collective activity into broader future capability where feasible.** 66. **Memory is a production factor, not merely an archive.** ## Keep the system evolvable 67. **Imperfection is permanent.** authority need not be. 68. **Variation is normal institutional experimentation, not only an emergency response to capture.** 69. **Complementarity can be superior to convergence.** 70. **The stable kernel should protect evolution, not freeze outcomes.** 71. **A better branch should be able to demonstrate value, gather support, remain interoperable, and influence or replace a dominant branch.** 72. **Improvement claims should state the dimension, beneficiaries, conditions, evidence, and trade-offs.** ## kOA constitutional orientation 73. **Strong distributed puissance.** Weak sovereignty. 74. **StrongHub + DistributedCapability + ReplicableWhole.** 75. **AI assists under governance.** AI does not silently inherit institutional sovereignty. 76. **Semantic sovereignty requires practical control, not merely formal openness.** 77. **Founder independence is a resilience criterion, not a requirement to erase the founder.** 78. **Brand stewardship and protocol governance are distinct.** 79. **The system should remain capable of learning from its own alternatives.** ## Adversarial resilience 80. **Founder fallibility is expected.** A durable system must survive both founder absence and founder error. 81. **Counterpower should be rehearsable.** Formal opposition rights are weaker than practiced, socially legitimate opposition pathways. 82. **Forkability does not imply epistemic equivalence.** Incompatible worldviews may coexist while evidence, provenance, contradiction, uncertainty, and lineage remain comparable. 83. **Apparent multiplicity is not independent confirmation.** Source and credibility systems should distinguish surface count from causal independence where provenance permits. 84. **A reference branch must remain a reference, not a monopoly on reality.** Stewardship can maintain coherence without eliminating the right to branch, contest, reinterpret, or simulate alternatives. ## Propagate capability without propagating dependency - **Compounding and propagation are distinct.** A system can become more capable without making capability easier to activate elsewhere. - **Reusable returns should cross branch boundaries when doing so increases common capability without silently transferring unrelated authority.** - **Healthy propagation lowers activation barriers for other actors.** It should not merely increase dependence on a central operator. - **Cross-loop coupling must be legible.** If revenue, credibility, evidence, brand, tooling, or standards feed another domain, the conversion path should be inspectable. - **Positive feedback requires governors.** Growth in expertise, brand, money, integration, federation, AI output, or founder recognition must not automatically become terminal sovereignty. - **Founder absence is a capability test.** A mature system should continue to operate, reproduce, teach, contest, and evolve without requiring continuous founder intervention. - **Simulation and demonstration are not adoption evidence.** Worlds, scenarios, and cinematic tours must remain epistemically separate from real use. - **Contact is not endorsement.** Outreach may create future recognition, but `contacted ≠ read ≠ familiar ≠ supportive ≠ partner`. - **Multiplicity at the periphery; simplicity at the center.** Many cultural, technical, linguistic, or institutional entry paths should converge on the same inspectable architecture and evidence. - **The goal is not maximum acceleration.** The system should preserve the ability to pause, remain local, defer federation, fork, or operate at a sustainable pace. ================================================================================================ FILE: power_dynamics/PROPAGATION.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 70bac184193365bf8c050a6232c2dff1cd4467fcd3c3333681b30074e676f0b4 CONTENT_BYTES: 9810 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Propagation and Coupled Compounding" source_basis: - S02 - S13 - S15 - S16 - S18 - S21 - S25 - S28 - S29 --- # Propagation and Coupled Compounding Power Dynamics already explains how capability is formed, mobilized, composed, converted, preserved, compounded, routed, contested, and replicated. This page adds the missing systems-level question: > **How does capability in one branch make capability elsewhere easier to activate, and what happens when several such loops reinforce one another?** ## 1. Compounding is not propagation **Compounding** means that action leaves returns that increase later capability in the same actor, branch, or system. ```text A capability → action → result → reusable return → greater future A capability ``` **Propagation** means that capability or returns from one locus reduce the activation cost, increase the expected value, or supply resources for capability to emerge elsewhere. ```text A capability → reusable return → lower activation barrier for B → B capability emerges or strengthens ``` **Coupled propagation** appears when several loops exchange returns: ```text A strengthens B B strengthens C C returns assets to A ``` The system can then grow by **conversion between loops**, not only by repetition inside one loop. ## 2. The kOA propagation thesis kOA is unusually propagation-oriented because different branches can generate different reusable returns: - software and tooling; - knowledge and documentation; - credibility and evidence; - relationships and institutional access; - money and service revenue; - operators and teaching capacity; - language coverage; - integrations and compatibility; - content and demonstrations; - reputation and brand recognition; - machine-readable context; - deployment experience and operational memory. The important property is not simply that each branch can grow. > **Returns generated in one branch can often be routed into another branch.** Examples: ```text service revenue → development capacity → better tooling → lower deployment cost → more deployments → more service revenue ``` ```text successful pilot → evidence → credibility → institutional access → additional pilots → more evidence ``` ```text new operator → independent deployment → reduced founder dependency → more simultaneous deployments → more training cases → better operator formation ``` ```text new integration → broader capability surface → more useful deployments → more reasons for other systems to integrate ``` ## 3. The propagation stack The current kOA design exposes several distinct scale surfaces. | Scale surface | Primary mechanism | Main returned asset | |---|---|---| | Construction | AI-assisted engineering + internal tooling | code, methods, automation | | Qualification | diagnostics, tests, explicit contracts | confidence, lower regression cost | | Contextualization | Worlds / scenario seeding | legibility, domain-specific demonstration | | Explanation | cinematic tours, multi-format media | understanding, attention, recall | | Deployment | Capsule Manager / Koali | lower activation and operations cost | | Local value | offline / self-host / local governance | usefulness before federation | | Discovery | SmartVote + EkoH + Kompendio | higher-signal ranking and attention | | Ecosystem integration | Kintsugi / annexation / explicit boundaries | added capability without rebuilding | | Human replication | UCKK / documentation / operator formation | independent operators | | Linguistic expansion | SemantiK / GF-oriented tooling | new communities and semantic reach | | Machine comprehension | structured docs / context packs / `llms.txt`-style surfaces | lower due-diligence cost | | Economic continuity | public good + paid responsibility | operating revenue without permission tolls | | Cultural diffusion | books, music, podcasts, fiction, public essays | multi-audience entry paths | | Federation | portable artifacts + independent instances | network value without mandatory centralization | S29 records the architect-confirmed current tooling and design directions behind the rows that are not fully represented in the earlier source corpus. ## 4. Coupling matters more than the number of loops A list of fourteen independent flywheels is not yet a propagation architecture. The stronger condition is **cross-loop convertibility**. ```text TECHNICAL CAPABILITY ↓ useful product ↓ WORLD / DEMO ↓ understanding ↓ pilot ↓ real evidence ↙ ↘ credibility operational demand ↓ ↓ access managed service ↓ ↓ new pilots revenue ↘ ↙ greater development capacity ↓ greater technical capability ↺ ``` A second loop can attach: ```text pilot → documented method → UCKK / operator formation → independent operator → additional deployment → more cases for training ``` A third can attach: ```text deployment → more objects / judgments / evidence → SmartVote signal → better discovery → higher utility → more deployment interest ``` The multiplication effect comes from **shared returns**. ## 5. Branch asymmetry: local failure, exportable success A modular branch ecology can create a useful asymmetry: ```text branch failure → primarily local loss branch success → potentially exportable returns (money, evidence, code, credibility, users, methods, integrations) → benefits elsewhere ``` This is only true when boundaries remain real. Hidden coupling can turn local failure into systemic failure. Propagation therefore depends on the same constitutional requirements as the rest of Power Dynamics: - explicit authority boundaries; - portable evidence and artifacts; - no automatic cross-domain sovereignty; - substitutability and exit; - local operational autonomy where practical; - inspectable conversion paths. ## 6. Reflexive propagation: kOA can be used to develop kOA A special case is **movement / ecosystem self-use**. If a multi-actor kOA initiative uses its own systems for proposals, ranking, work routing, knowledge preservation, training, and publication, then the deployment environment becomes a continuous integration test for the sociotechnical architecture. ```text contributors → Konnaxion / SmartVote → priorities → Orgo → work → results → Kristal / documentation → UCKK → new operators → more contributors → better kOA → more capable collaboration ↺ ``` This loop is not evidence until multiple actors use it in practice. It is nevertheless a particularly strong falsifiable design target. ## 7. Founder decentering is part of propagation, not only governance Founder-specific knowledge can be converted into shared capability: ```text founder knowledge → documentation / schemas / tests / protocols → independent mastery → more parallel work → less founder bottleneck ``` The decisive resilience property is not pseudonymity. A persona or pseudonym can manage exposure and preserve narrative optionality. It does **not** make the system independent. System independence requires: - other maintainers; - independent deployment; - portable keys / governance where appropriate; - explicit protocols; - reproducible builds and recovery; - documentation sufficient for outsiders; - legitimate disagreement and fork paths. A useful test is: > **Can the founder become temporarily unavailable without halting operation, interpretation, deployment, governance, or transmission?** ## 8. Positive feedback must have governors Propagation without damping becomes capture, runaway growth, noise, or fragility. Important governors include: ```text expertise grows → keep expertise domain-bounded credibility grows → credibility ≠ sovereignty money grows → funding ≠ political standing brand grows → brand ≠ protocol authority integration grows → preserve system authority boundaries AI throughput grows → AI remains bounded and non-authoritative content grows → provenance / validation / publication gates federation grows → local exit / fork / autonomy remain practical founder recognition grows → founder ≠ constitutional authority ``` The target is not maximum acceleration. > **Healthy propagation increases distributed capability faster than it increases terminal dependency.** ## 9. Evidence ladder Propagation claims should move through explicit evidence levels. ```text DESIGNED → DEMONSTRATED → USED → REPEATED → INDEPENDENTLY REPLICATED → FEDERATED / CROSS-BRANCH ``` A World is evidence that a context can be represented. It is not proof of adoption. A cinematic tour is evidence that a demonstration can be generated. It is not proof that a viewer understood or converted. A pilot is evidence of bounded use. It is not proof of independent replication. The strongest propagation evidence appears when another actor reproduces useful capability without founder mediation. ## 10. Canonical propagation tests For any proposed loop, ask: 1. What is the input asset? 2. What conversion occurs? 3. What reusable return is produced? 4. Who receives that return? 5. Which other loop can consume it? 6. Does the return lower activation cost elsewhere? 7. Does the loop reduce or increase dependency? 8. What damping mechanism prevents runaway conversion? 9. What observation would falsify the loop? 10. Can the loop close without founder intervention? See [`propagation/`](propagation/README.md) and [`assessment/propagation-audit.md`](assessment/propagation-audit.md). ================================================================================================ FILE: power_dynamics/propagation/00-field-definition.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 60293d166de5a94feeeb77e9d68d358d64fa33f13d75d51d8b3d847f07fb9bf7 CONTENT_BYTES: 2117 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Propagation: Field Definition" source_basis: - S13 - S18 - S21 - S25 - S29 --- # Propagation: Field Definition ## Compounding > **A return from prior action increases later capability in the same actor, branch, or system.** `A(t) → action → return → A(t+1)` ## Propagation > **A return generated in one locus lowers the activation cost, raises the expected value, supplies resources, or improves the viability of capability elsewhere.** `A → return → lower barrier / greater possibility for B → B` ## Coupled propagation > **Two or more feedback loops exchange returns such that progress in one loop increases the closure probability or throughput of another.** `A → B → C → A` ## Propagation asset A **propagation asset** is a reusable return that can cross an actor, branch, domain, deployment, language, or institutional boundary. Examples: - code; - protocol; - deployment automation; - evidence; - credibility; - documentation; - money; - trained operators; - templates; - integrations; - language resources; - brand recognition; - source corpora; - standards; - institutional relationships. ## Activation barrier An **activation barrier** is any requirement that must be crossed before a new actor can obtain useful capability. Examples: - inability to understand the system; - lack of relevant local data; - deployment complexity; - lack of trust; - language mismatch; - lack of trained operators; - perceived lock-in; - insufficient economic resources; - integration friction; - founder dependence. Propagation mechanisms matter when they reduce one or more of these barriers without merely relocating dependency to a new center. ## Healthy propagation Healthy propagation satisfies two conditions simultaneously: 1. more actors become effectively capable; 2. terminal dependency does not grow faster than distributed capability. A system can spread rapidly while becoming more centralized. That is diffusion, not necessarily empowering propagation. ================================================================================================ FILE: power_dynamics/propagation/01-coupled-feedback-loops.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ae4c5be6081bd065829b70b1d7445d1b7b0be9c949f02ab0df175fc619f0f6de CONTENT_BYTES: 2382 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Coupled Feedback Loops" source_basis: - S18 - S21 - S25 - S29 --- # Coupled Feedback Loops A single flywheel can compound one asset. A propagation ecology exists when multiple loops exchange assets. ## Basic form ```text Loop A produces return X ↓ X is usable by Loop B ↓ Loop B produces return Y ↓ Y raises the throughput of Loop A ``` The coupling can be stronger than either loop alone because each removes a bottleneck for the other. ## Common coupling classes ### Economic ↔ technical `revenue → development capacity → better product → more operational demand → revenue` ### Evidence ↔ institutional access `pilot → evidence → credibility → evaluation access → more pilots` ### Human capacity ↔ deployment `training → operator → independent deployment → real cases → better training` ### Integration ↔ adoption `integration → broader usefulness → adoption → demand for more integration` ### Knowledge ↔ execution `structured knowledge → better action → observed result → better knowledge` ### Discovery ↔ contribution `better ranking → more useful discovery → more participation → more evaluation data → better ranking` ### Documentation ↔ independent review `structured documentation → lower review cost → external feedback → better documentation` ## Coupling strength A loop is more strongly coupled when: - the returned asset is portable; - another loop can consume it with low conversion cost; - the asset retains provenance; - the asset is not locked behind one operator; - the conversion is repeatable; - the return is not exhausted by reuse. Knowledge, software, standards, templates, and reputation can therefore propagate very differently from scarce physical assets. ## Coupling risk The same property can create systemic fragility. If every loop depends on one identity provider, one signer, one hosting company, one founder, one ranking policy, or one funding source, apparent compounding can hide a single point of failure. Every coupled-loop analysis should therefore model: - positive feedback; - dependency concentration; - failure propagation; - conversion firewalls; - exit / substitution paths; - decay and saturation. ================================================================================================ FILE: power_dynamics/propagation/02-adoption-stack.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: e1532570915cc74098ad544a6e636d5f75c5115441389e2fb4c701be6c72f237 CONTENT_BYTES: 2082 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "kOA Adoption Stack" source_basis: - S13 - S16 - S18 - S25 - S29 --- # kOA Adoption Stack Adoption is not one event. It is a sequence of barriers. ```text NOTICE → UNDERSTAND → TRUST ENOUGH TO EXAMINE → SEE LOCAL RELEVANCE → TRY → DEPLOY → GET LOCAL VALUE → REPEAT → OPERATE INDEPENDENTLY → CONNECT / FEDERATE IF USEFUL ``` Different kOA mechanisms attack different barriers. | Barrier | Candidate mechanism | Intended effect | |---|---|---| | Notice | books, music, podcasts, public essays, targeted outreach | create an entry path | | Complexity | progressive documentation, cinematic tours, concise briefs | reduce explanation cost | | Abstractness | Worlds / scenario seeding | make the system legible in a familiar context | | Trust | public code, tests, provenance, explicit limitations | reduce belief dependence | | Local relevance | Scenario Mosaic / domain patterns | connect general architecture to a real workflow | | Deployment | Capsule Manager / Koali tooling | reduce technical activation cost | | Lock-in fear | self-hosting, export, fork, local authority | preserve optionality | | Language | SemantiK / multilingual tooling | reduce semantic access barriers | | Operator scarcity | UCKK / runbooks / documentation | reproduce human capability | | Integration cost | Kintsugi boundaries / annexation | reuse existing systems instead of replacing them | | Ongoing operations | managed service | sell responsibility rather than permission | The strongest adoption architecture does not require every actor to pass through the same corridor. A researcher may enter through knowledge infrastructure. A language organization may enter through multilingual capability. A municipality may enter through a concrete workflow. A developer may enter through code. A cultural institution may enter through provenance and stewardship. These paths should converge on the same inspectable core rather than becoming disconnected narratives. ================================================================================================ FILE: power_dynamics/propagation/03-cross-branch-returns.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 7d9fec4487567b496cf3993b74449c4a751e4a1c87693be51cd668263245b974 CONTENT_BYTES: 2014 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "Cross-Branch Returns" source_basis: - S18 - S25 - S29 --- # Cross-Branch Returns A modular ecosystem becomes strategically unusual when branch returns can cross branch boundaries. ## Return classes | Return | Example origin | Example destination | |---|---|---| | Money | managed hosting / support / merchandise | engineering, documentation, public-good infrastructure | | Code | internal tooling | multiple repositories | | Evidence | institutional pilot | credibility for another branch | | Credibility | academic / technical validation | institutional access elsewhere | | Relationships | one sector | introductions into another sector | | Knowledge | operational use | documentation, Kristal, training | | Operators | UCKK / apprenticeship | deployments, support, integration | | Language assets | SemantiK work | Konnaxion, UCKK, public communication | | Integrations | Kintsugi | wider system capability | | Content | Worlds / scenarios | demos, education, tests | | Brand attention | cultural layer | discovery of technical assets | | Technical legitimacy | public repositories / tests | confidence in nontechnical initiatives | ## Strategic asymmetry A desirable branch architecture tries to make: ```text failure costs local success returns portable ``` This is never automatic. Shared infrastructure, brand, funding, identity, or governance can make failure systemic. The audit question is therefore: > **Which branch dependencies are intentionally shared, and which are only accidentally shared?** ## Cross-subsidy without capture Cross-branch funding can be productive: `Branch A revenue → shared infrastructure → Branch B capability` But economic return should not silently purchase unrelated authority. `funding → capability` can be legitimate. `funding → political or epistemic sovereignty` requires an explicit constitutional basis and should normally be blocked. ================================================================================================ FILE: power_dynamics/propagation/04-distribution-surfaces.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 43847c9dc78f08d43be3b8f9fcb86722af8dbbe99a4c3ed6ac8eefbf20ade510 CONTENT_BYTES: 2415 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "Distribution Surfaces" source_basis: - S02 - S22 - S29 --- # Distribution Surfaces A complex infrastructure can fail to propagate even when it is technically useful because explanation itself does not scale. kOA uses or proposes several distinct **distribution surfaces**. ## Human-facing surfaces - institutional briefs; - public websites; - technical repositories and wikis; - Medium-style essays and academic articles; - books; - albums / songs; - podcasts; - fictional / symbolic narrative; - scenario mosaics; - seeded Worlds; - deterministic cinematic demonstrations. The purpose of multiple surfaces is not to repeat the same pitch everywhere. It is to let different audiences enter through a format they can parse while preserving a shared factual spine. ## Machine-facing surfaces - structured Markdown; - explicit source maps; - context packs; - stable schemas; - machine-readable indexes; - `llms.txt`-style entry points or equivalent concise machine-oriented maps. These can reduce the cost for a third party to use its own AI system to inspect the corpus. ## Distribution loop ```text structured corpus → lower explanation / due-diligence cost → more independent examination → more criticism / questions / evidence → better corpus → lower future explanation cost ``` ## Worlds and cinematic demonstrations Architect-confirmed current tooling includes seeded Worlds and a cinematic demonstration pipeline. Their propagation role is specific: ```text real sources → structured World → populated environment → scripted interaction → understandable demonstration ``` A World can solve the **empty-platform demonstration problem** by showing a context already populated with recognizable objects. A cinematic pipeline can reduce the marginal cost of explaining that World to many audiences. Neither mechanism proves adoption. Their value is measured by downstream conversion: `demo → examination → pilot → deployment`. ## Convergence requirement Many entry points create a maze risk. The communication architecture should therefore follow: > **Multiplicity at the periphery; simplicity and traceability at the center.** Every narrative or media corridor should make it possible to reach the canonical architecture, evidence, status, and limitations. ================================================================================================ FILE: power_dynamics/propagation/05-autonomy-and-founder-absence.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 75089851dbc09f16e85d7f64a2527f855a26aeb22c2fad07c1d11cf6d20ce269 CONTENT_BYTES: 1904 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "Autonomy and Founder Absence" source_basis: - S18 - S25 - S29 --- # Autonomy and Founder Absence Founder decentering is both a constitutional requirement and a throughput mechanism. If every deployment, interpretation, integration, conflict, or public explanation requires one founder, growth increases bottleneck pressure faster than capacity. ## Founder-to-protocol conversion ```text founder skill → method → documentation → schema / test / tool → independent operator → parallel capability ``` The objective is not founder disappearance. It is to make founder participation **optional rather than structurally mandatory**. ## Absence test A strong propagation system should eventually answer yes to questions such as: - Can another person install it? - Can another person restore it? - Can another person explain its core model accurately? - Can another person train the next operator? - Can governance continue without founder voting or interpretation? - Can a branch reject a founder preference? - Can an institution leave without founder permission? - Can development continue during founder inactivity? ## Persona / pseudonym distinction An architect may use a pseudonym or narrative persona to preserve creative freedom, manage exposure, or create a separate cultural surface. That does **not** by itself make the system resilient to criticism or personal attack. Resilience comes from: - independent evidence; - distributed maintainership; - forkability; - source availability; - explicit authority boundaries; - reproducible operations; - plural interpretation; - continued function during founder absence. The useful separation is therefore: ```text persona → exposure / narrative optionality protocolization → technical and institutional autonomy ``` ================================================================================================ FILE: power_dynamics/propagation/06-damping-and-runaway-prevention.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 1ae882df0d831935de3df2294a1cf2a0c6ded85f5442d9f83840499da80c5267 CONTENT_BYTES: 2449 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Damping and Runaway Prevention" source_basis: - S15 - S16 - S17 - S18 - S21 - S25 - S28 - S29 --- # Damping and Runaway Prevention Positive feedback is not automatically desirable. Without damping, compounding can become: - incumbency; - lock-in; - metric gaming; - prestige reproduction; - founder centrality; - monopolistic standards power; - misinformation amplification; - administrative overreach; - uncontrolled complexity; - operational overload. ## Governor pattern A propagation mechanism should be paired with at least one countervailing mechanism. | Positive loop | Runaway risk | Governor | |---|---|---| | SmartVote recognition | prestige becomes permanent authority | domain bounds, time decay, raw baseline, audit | | Managed-service revenue | money buys unrelated control | authority separation; funding ≠ votes | | Brand attention | persona becomes truth source | traceability to evidence; brand ≠ protocol | | Kintsugi integration | interface layer becomes mandatory choke point | replaceable adapters, explicit boundaries, direct exit | | Federation | de facto center dominates local nodes | local authority, optional federation, forkability | | AI production | quantity overwhelms validation | provenance, tests, human review, publication gates | | Documentation growth | information overload | canonical entry points, progressive disclosure | | Founder recognition | personal interpretation becomes constitutional | founder decentering, opposition, maintainer pluralism | | Language expansion | nominal support outruns quality | conformance tiers, native review, published coverage | | World generation | simulation mistaken for evidence | explicit simulation/reconstruction/live labels | | Outreach | contact mistaken for endorsement | evidence-state tracking | ## Pace is also a control surface A healthy architecture does not require continuous acceleration. Branches can pause, remain local, defer federation, or allow the founder or maintainers to step back temporarily. This is a resilience feature when the system can preserve state and continue safely without constant central intervention. ## Canonical condition > **The system should be able to accumulate capability without requiring the same rate of accumulation in centralized authority, dependency, or founder attention.** ================================================================================================ FILE: power_dynamics/propagation/07-metrics-and-falsification.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6092320596edd86bfdb49bf450a9f098702f9750ade4370ce803c7c04b64807a CONTENT_BYTES: 2876 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Propagation Metrics and Falsification" source_basis: - S21 - S25 - S29 --- # Propagation Metrics and Falsification Propagation should be measured as a set of transitions, not asserted from architecture alone. ## Activation metrics - time to first locally useful state; - time from first exposure to qualified examination; - World / demo → evaluator conversion; - evaluator → bounded pilot conversion; - pilot → deployment conversion; - deployment → repeated use; - deployment → referral / routing to another organization. ## Replication metrics - installation time for a non-founder operator; - founder minutes required per new instance; - restore / migration time; - time to second independent instance; - percentage of deployments completed without founder intervention; - number of operators able to train another operator. ## Cross-branch metrics - percentage of revenue reinvested into shared capability; - number of branches consuming an asset produced by another branch; - reuse count per internal tool / integration / template; - credibility spillover: one branch's validated result leading to qualified review of another; - integration reuse across domains. ## Network / discovery metrics - number of objects evaluable by SmartVote; - number of active domains with meaningful expertise data; - ranking usefulness / downstream selection quality; - percentage of high-ranked items later reused, funded, taught, or deployed; - disagreement between baseline and advisory lenses and how users interpret it. ## Multilingual metrics - languages by conformance tier; - test coverage per language; - native-review status; - population / institutions actually reached, not merely nominal language count; - contribution rate from newly supported language communities. ## Independence metrics - founder intervention per month / deployment / governance cycle; - number of maintainers with release capability; - number of independently operated instances; - number of successful exits / migrations / forks; - proportion of core decisions reproducible from public rules rather than private interpretation. ## Falsification examples A proposed propagation loop is weakened when: - demonstrations generate views but not examinations; - examinations generate no pilots; - pilots require permanent founder operation; - revenue does not reduce future deployment cost; - integrations increase maintenance faster than utility; - more SmartVote data decreases decision quality or increases gaming; - language count rises while usable quality or adoption does not; - federation increases dependency on one central service; - documentation volume increases due-diligence time. The objective is to discover **which loops actually close in practice**. ================================================================================================ FILE: power_dynamics/propagation/08-koa-loop-catalog.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 640c5e590f57e1842a0ee5151823fa44b962c3b1ead52d6c62dba5e7e390d71d CONTENT_BYTES: 3494 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "kOA Propagation Loop Catalog" source_basis: - S13 - S15 - S16 - S18 - S21 - S25 - S28 - S29 --- # kOA Propagation Loop Catalog This catalog is a map of **candidate and partially evidenced loops**, not a claim that all loops are already active at scale. | Loop | Core sequence | Primary governor | |---|---|---| | Build | tools → faster building → better tools | test / architecture discipline | | Knowledge | use → result → memory → better next cycle | provenance / plurality | | Economic | public software → adoption → paid responsibility → revenue → common capability | money ≠ authority | | Credibility | real result → evidence → credibility → access → more real tests | evidence-state discipline | | Demonstration | sources → World → cinematic demo → examination → pilot → better World | simulation ≠ evidence | | SmartVote | objects → evaluations → signal → discovery → utility → more objects | domain bounds / raw baseline | | Kintsugi | integration → capability → adoption → integration demand | replaceability / sidecar boundaries | | Replication | packaging → independent instance → operational learning → easier next instance | local autonomy / no mandatory center | | Human capacity | training → operator → deployment → experience → better training | independent assessment | | Multilingual | language support → community access → contribution → better language resources | conformance tiers | | Narrative | architecture → cultural form → understanding → technical exploration → new evidence/story | narrative ≠ factual authority | | Machine-readable review | structured docs → AI-assisted review → questions / critique → better docs | source / status discipline | | Movement self-use | contributors → kOA workflow → results → better kOA → more capable contributors | counterpower / fork / founder decentering | | Founder decentering | founder work → protocol / docs / tools → autonomous operators → lower founder bottleneck | opposition + independent reproduction | | Federation | local value → independent instances → interoperable exchange → network value → more local adoption | optional federation / exit | | Cross-branch subsidy | branch return → shared asset → another branch → new return | conversion firewalls | ## High-value couplings ### Economic × Build × Deployment `managed service → revenue → tooling → lower operating cost → more managed service` ### Credibility × Demonstration × Institutional Access `pilot → evidence → credibility → better-targeted demonstration → qualified institutional review → pilot` ### UCKK × Capsule × Founder Decentering `training → operator → reproducible deployment → less founder labor → more deployments → training cases` ### Kintsugi × SmartVote × Kompendio `more connected objects/systems → more objects to compare → better contextual discovery → more integration utility` ### SemantiK × Community × Knowledge `language support → new contributors → new knowledge / validation → more multilingual value → stronger language support` The next stage for Power Dynamics is not to add more loops indefinitely. It is to instrument these transitions and determine which couplings materially alter adoption, replication, and autonomy. ================================================================================================ FILE: power_dynamics/propagation/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 317384fb5a41ca692c33e37de7432d8feb0ee4485da5d8c6e0f3d7e027b427c8 CONTENT_BYTES: 1748 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Propagation" source_basis: - S13 - S15 - S18 - S21 - S25 - S28 - S29 --- # Propagation This directory studies how capability becomes easier to activate **elsewhere**. Power Dynamics already treats returns and reinvestment as sources of compounding. Propagation adds a different question: > **When can a return generated in one actor, branch, domain, or deployment increase the effective possibility of capability in another?** ## Reading order 1. [`00-field-definition.md`](00-field-definition.md) — compounding vs propagation vs coupled propagation. 2. [`01-coupled-feedback-loops.md`](01-coupled-feedback-loops.md) — why cross-loop links matter. 3. [`02-adoption-stack.md`](02-adoption-stack.md) — activation barriers from understanding to operation. 4. [`03-cross-branch-returns.md`](03-cross-branch-returns.md) — money, evidence, code, credibility, people, and access moving between branches. 5. [`04-distribution-surfaces.md`](04-distribution-surfaces.md) — Worlds, cinematic demonstrations, narrative, machine-readable docs, and multiple entry paths. 6. [`05-autonomy-and-founder-absence.md`](05-autonomy-and-founder-absence.md) — growth that lowers rather than deepens founder dependency. 7. [`06-damping-and-runaway-prevention.md`](06-damping-and-runaway-prevention.md) — negative feedback, firewalls, optionality, and local sovereignty. 8. [`07-metrics-and-falsification.md`](07-metrics-and-falsification.md) — what to measure. 9. [`08-koa-loop-catalog.md`](08-koa-loop-catalog.md) — current kOA-specific loop map. The top-level canonical summary is [`../PROPAGATION.md`](../PROPAGATION.md). ================================================================================================ FILE: power_dynamics/puissance/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f5f93e33c679cb57cde5f24f1390492ed0c38e2c298bcaf1b6312a57c0846aee CONTENT_BYTES: 2425 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Forms of Puissance" source_basis: - S01 - S02 - S13 - S16 - S18 - S21 - S22 - S25 --- # Forms of Puissance This directory names the **positive capability side of the Power Show**. **Puissance** is effective mobilizable capacity. Before asking who controls whom, Power Dynamics asks what an actor, group, institution, or infrastructure can actually do. ## Agency and cognitive puissance Choose, refuse, learn, reason, synthesize, model, plan, create, evaluate, and use governed AI assistance. ## Epistemic and semantic puissance Produce, structure, validate, compare, translate, preserve, contest, and evolve knowledge and meaning. ## Collective, network, and coordination puissance Find people, combine distributed expertise, form groups, coordinate roles, synchronize action, and create capability no participant possessed alone. ## Deliberative and decision puissance Compare alternatives, preserve reasons, incorporate advisory expertise, and choose through explicit procedures. ## Operational and administrative puissance Route work, assign responsibility, manage timing, escalate, execute, review, and close loops. ## Mnemonic puissance Preserve provenance, decisions, actions, failures, outcomes, and lineage so the next cycle starts from reusable memory. ## Economic and allocation puissance Mobilize material resources, funding, productive assets, and allocation mechanisms. ## Technical and infrastructural puissance Build, inspect, modify, test, reproduce, repair, deploy, self-host, and maintain systems that lower future coordination costs. ## Distribution, brand, and affiliation puissance Transmit knowledge, make people or projects discoverable, create public recognition, affiliation, and reach across communities and languages. ## Federation, exit, and evolutionary puissance Operate independently, substitute dependencies, fork, gather support, preserve interoperability, recombine, and replace dominant branches. These forms can compose. They become **power relations** only when their exercise materially changes another actor's access, options, standing, visibility, allocation, authority, dependency, interpretation, or ability to act. See [`../showcase/01-capability-spectrum.md`](../showcase/01-capability-spectrum.md) for the kOA-facing presentation. ================================================================================================ FILE: power_dynamics/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: e571ff7aaf4cbdc39e5157d2dcae586d274755fabf4f62a10814b7fc8a26aeca CONTENT_BYTES: 16514 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Power Dynamics" source_basis: - S01 - S02 - S10 - S13 - S14 - S15 - S16 - S17 - S18 - S21 - S22 - S25 - S26 - S28 --- # Power Dynamics **The kOA Power Show — and a systems theory of how capability becomes power, compounds across domains, and can be deliberately redistributed.** ## Why is kOA immensely powerful? > **Because kOA does not amplify one human capability. It connects almost the entire lifecycle by which distributed resources become collective agency, reusable assets, and greater future capability.** The shortest formula is: > **Breadth × Composition × Closure × Memory × Compounding × Propagation × Replication × Routing** ```text People + knowledge + AI + networks + credibility + money + tools ↓ STRUCTURE + CONNECT ↓ Meaning → Knowledge → Discovery → Credibility → Judgment ↓ Decision → Allocation ↓ Coordination → Execution ↓ Results → Memory → Returns ↓ Reinvestment ↓ Greater future puissance ↓ Replication / federation ↓ Sharing / contestation / evolution ``` kOA is therefore not best understood as a collection of apps. It is an attempt to build a **full-stack capability infrastructure** for the cycle: > **Know → Choose → Act → Remember → Know better** A collective that can reliably close that cycle can become more capable **because it has acted before**. ## The kOA power surface kOA can generate or amplify capability across many domains at once: | Domain | What kOA can make more possible | Power relation that can emerge | |---|---|---| | **Epistemic** | validate, compare, preserve, reuse knowledge | validation / canon / trust-root power | | **Semantic** | define, relate, translate, version meaning | classification / framing / admissibility power | | **Cognitive / AI** | reason, synthesize, model, translate, plan | hidden framing / prioritization / dependency power | | **Information / attention** | publish, discover, rank, distribute | visibility / agenda / amplification power | | **Credibility / reputation** | make demonstrated expertise and contribution legible | standing / certification / opportunity power | | **Network / affiliation** | find people, collaborators, institutions, audiences | brokerage / inclusion / affiliation power | | **Political / constitutional** | deliberate, advise, decide, amend, organize public standing | agenda / decision / mandate / legitimacy power | | **Economic** | mobilize money, assets, labor, funding, infrastructure | bargaining / property / allocation power | | **Monetary** | organize liquidity, payment rails, settlement, credit or currency functions | issuance / access / settlement / reserve power | | **Administrative / operational** | assign, route, escalate, execute, close | timing / workload / approval / closure power | | **Technical / infrastructural** | build, deploy, verify, self-host, reproduce | compatibility / access / update / dependency power | | **Narrative / symbolic / brand** | make systems memorable, transmissible, affiliative | attention / legitimacy-by-association / mobilization power | | **Mnemonic / temporal** | preserve reasons, precedent, failure, history, timing | precedent / memory / delay / succession power | | **Evolutionary / counterpower** | contest, fork, substitute, recombine, replace | incumbent displacement / branch mobility / exit power | See [`POWER-SURFACE.md`](POWER-SURFACE.md) for the full map. ## Political, economic, and monetary power are not the same Power Dynamics now separates these explicitly. ### Political power Political power concerns **standing, agenda, mandate, decision rights, legitimacy, representation, amendment, veto, and collective self-government**. kOA touches political power before and after formal voting: > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** A system can preserve one-person-one-vote while still concentrating enormous power upstream in classification, discovery, credibility, defaults, or agenda formation. That is why kOA treats the pre-political chain as part of governance. ### Economic power Economic power concerns **money, property, productive assets, funding, labor, infrastructure, bargaining position, and resource allocation**. Money is not identical to power. It is a highly convertible resource that can become economic puissance and then relational leverage. ```text money → economic puissance → purchasing / bargaining / allocation effects ``` ### Monetary power Monetary power is narrower and more infrastructural. It concerns control over **units of account, issuance, payment rails, settlement, reserves, liquidity, credit conditions, convertibility, and access to exchange**. ```text monetary infrastructure → conditions of exchange → dependency / access / allocation effects ``` KingCoin is retained as a **LEGACY-PROPOSAL / stress test** precisely because it demonstrates how monetary, economic, administrative, and political functions can stack into terminal power if they are fused. See [`showcase/13-political-economic-monetary-power.md`](showcase/13-political-economic-monetary-power.md). ## The real multiplication effect: composition The power of kOA is not the sum of independent modules. ```text SemantiK / SenTient → semantic structuration Kristal → structured knowledge + provenance + memory Konnaxion → circulation + association + discoverability Koali / EkoH → credibility / expertise legibility SmartVote → comparative judgment + decision support Orgo → governed execution AI → cognitive amplification Capsules / federation→ portability + replication + substitution ↓ composition ↓ Know → Choose → Act → Remember → Know better ``` When outputs from one capability become inputs to another, the system can create **generated collective puissance** that no component or participant possesses alone. See [`showcase/03-composition-engine.md`](showcase/03-composition-engine.md). ## The second multiplication effect: compounding Action can leave behind reusable assets: ```text experience knowledge code tools documentation data provenance credibility reputation relationships money infrastructure institutional memory ``` Those returns can feed the next cycle: > **Puissance → Action → Result → Return → Reinvestment → Greater Future Puissance** This is why kOA can become more capable over time instead of resetting after each project. See [`showcase/04-compounding-engine.md`](showcase/04-compounding-engine.md). ## The propagation effect: returns can activate capability elsewhere Compounding is not the same as propagation. ```text compounding: A acts → A receives a reusable return → A becomes more capable propagation: A acts → a reusable return lowers the activation barrier for B coupled propagation: A strengthens B → B strengthens C → C returns capability to A ``` This matters for kOA because different branches can return different assets — money, evidence, credibility, code, tools, operators, integrations, language resources, documentation, and institutional access — and those assets can be reused by other branches. The result can be a network of coupled loops rather than one growth flywheel. See [`PROPAGATION.md`](PROPAGATION.md) and [`showcase/15-propagation-engine.md`](showcase/15-propagation-engine.md). ## The third multiplication effect: cross-domain conversion Power rarely stays in one domain. ```text knowledge → credibility → visibility → opportunity money → infrastructure → reach → political leverage brand → attention → affiliation → revenue technical control → defaults → dependency → governance leverage network → collaborators → execution → results → credibility ``` This is where successful capability can become dangerous. A legitimate function can acquire leverage outside its mandate. > **Capture = Functional Control → Cross-Domain Power** Power Dynamics therefore studies both **conversion paths** and **Power Conversion Firewalls**. See [`framework/10-cross-domain-power-conversion.md`](framework/10-cross-domain-power-conversion.md). ## The fourth multiplication effect: power routing and sharing The strongest version of the project is not: > **kOA becomes immensely powerful.** It is: > **kOA generates immense puissance while deliberately routing much of that capability, optionality, authority, and return outward.** Examples: - **ethical fiction as self-binding** — publish anti-domination, attribution, revision, humility, and ethical principles inside the same symbolic channel that generates attention; - **protocolization** — convert founder mastery into explicit schemas, contracts, documentation, tests, and independently reproducible behavior; - **Koali ownership decoupling** — design credibility capability to be duplicable, shareable, branchable, and capable of plural distributions rather than terminal personal ownership; - **expertise → advice, not sovereignty** — preserve political equality while exposing bounded informed readings; - **money → funding, not more votes** — let economic resources increase common capability without automatically purchasing political authority; - **knowledge → portable artifacts, not ownership of truth** — lineage, provenance, competing Kristals, reader policies; - **infrastructure → self-hosting / federation, not captivity** — portability, capsules, rollback, substitution, local continuity; - **dominance → branch mobility** — alternatives can demonstrate value, accumulate support, coexist, merge, or replace incumbents. The canonical sequence becomes: > **Generate → Compose → Close → Preserve → Compound → Propagate → Convert → Route → Share → Bind → Contest → Fork → Evolve** See [`POWER-ROUTING.md`](POWER-ROUTING.md). ## Academic lineage and external challenge Power Dynamics now includes a structured [`Academic-Lineage/`](Academic-Lineage/README.md) layer connecting the framework to established work on relational power, dependency, polycentric governance, institutional grammar, modularity, standards lock-in, path dependence, exit / voice, open-source governance, network power, expertise, collective judgment, metric gaming, classification, infrastructure, social epistemology, and cybernetics. The purpose is **not** to claim endorsement or retrospective influence. The literature is used to name known failure modes, supply established mechanisms, expose impossibility constraints, and sharpen the tests that kOA must survive. A recurring result is that the architecture must distinguish: - capability from dependency; - expertise from political sovereignty; - compatibility from constitutional subordination; - decentralization from absence of hidden standards power; - reputation from truth; - forkability from practical exit; - provenance from epistemic authority. See [`Academic-Lineage/README.md`](Academic-Lineage/README.md) and [`Academic-Lineage/BIBLIOGRAPHY.md`](Academic-Lineage/BIBLIOGRAPHY.md). ## Power must survive adversarial use A non-dominating architecture should not depend on benevolent actors, perfect founders, or honest knowledge producers. Power Dynamics now makes three resilience tests explicit: - **founder opposition** — can participants reject a founder-backed proposal without abandoning the whole system? - **epistemic corruption** — can misleading authority signals, dependent sources, and false consensus be exposed through provenance and comparison? - **plural worldview branching** — can incompatible Kristals coexist without turning forkability into a claim of equal evidentiary support? These are treated as power questions because symbolic authority, credibility, and reference stewardship can all convert into leverage outside their intended domain. See [`cases/founder-opposition-rehearsal.md`](cases/founder-opposition-rehearsal.md) and [`cases/epistemic-authority-corruption.md`](cases/epistemic-authority-corruption.md). ## Power Conversion Firewalls kOA's constitutional goal is not to prevent useful forms of puissance from interacting. It is to prevent useful capability from silently becoming unrelated sovereignty. | Legitimate conversion | Blocked automatic conversion | |---|---| | expertise → advice | expertise → political sovereignty | | money → funding | money → more votes | | brand → attention | brand → truth | | credibility → discoverability | credibility → unquestionable authority | | narrative → mobilization | narrative → legitimacy | | technical administration → maintenance | technical control → political outcome control | | execution → mandate implementation | execution → mandate redefinition | | infrastructure → capability | infrastructure → ownership of users | > **Composition without automatic conversion.** ## Why the constitution exists > **The constitution exists because the Power Show succeeds.** If kOA can structure meaning, knowledge, discovery, credibility, deliberation, decisions, allocation, execution, memory, infrastructure, and social transmission, then it can also create serious relations of power. The normative target is: > **Maximize distributed puissance while constraining arbitrary, cross-domain, and terminal power.** The compressed doctrine is: > **Strong distributed puissance. Weak sovereignty.** > **Stable interoperability. Evolving branches.** > **Plurality without fragmentation.** > **Verification + Contestation + Substitution + Exit.** > **Instance capture ≠ system capture.** ## Start here 1. [`showcase/00-why-koa-is-immensely-powerful.md`](showcase/00-why-koa-is-immensely-powerful.md) — the shortest complete answer. 2. [`POWER-SURFACE.md`](POWER-SURFACE.md) — every major domain of capability and power. 3. [`POWER-SHOW.md`](POWER-SHOW.md) — the guided kOA power show. 4. [`showcase/03-composition-engine.md`](showcase/03-composition-engine.md) — why the whole can exceed the sum. 5. [`showcase/04-compounding-engine.md`](showcase/04-compounding-engine.md) — how power regenerates. 6. [`showcase/13-political-economic-monetary-power.md`](showcase/13-political-economic-monetary-power.md) — political, economic, and monetary distinctions. 7. [`POWER-ROUTING.md`](POWER-ROUTING.md) — how generated power is redirected and shared. 8. [`constitution/README.md`](constitution/README.md) — how the architecture constrains the power it generates. 9. [`framework/README.md`](framework/README.md) — the analytical engine. 10. [`GLOSSARY.md`](GLOSSARY.md) — canonical terminology. ## Analytical engine The broader Power Dynamics field studies how resources and capability: > **form, mobilize, compose, convert, return, compound, concentrate, capture, contest, diversify, evolve, decay, transfer, scale, and route.** Its precision ontology remains: > **Resource / Asset → Potential → Capacity → Puissance → Power Relation → Effect → Return** Its three analytical axes remain: 1. **Ontological state** — what kind of thing is this? 2. **Dynamic** — what is happening to it? 3. **Domain** — where does the capability or power operate? See [`framework/03-three-axis-model.md`](framework/03-three-axis-model.md). ## Epistemic discipline Every substantive document should distinguish: - `maturity` — current core, experimental, open question, legacy proposal, etc.; - `claim_type` — source-derived, analytical reconstruction, new concept, external research, or architect-confirmed design. A powerful claim is not treated as an implemented fact merely because it is architecturally desirable. Koali protocolization, for example, remains an architect-confirmed design direction until the required technical evidence exists. See [`sources/epistemic-rules.md`](sources/epistemic-rules.md) and [`sources/technical-evidence-map.md`](sources/technical-evidence-map.md). ================================================================================================ FILE: power_dynamics/relations/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: cc74e02ab75c34bb299cdbe65ec037f5a1404ddb8992fdf9b9bda95993833b7b CONTENT_BYTES: 2479 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Power Relations" source_basis: - S01 - S10 - S14 - S15 - S16 - S18 - S21 - S22 - S28 --- # Power Relations The Power Show maps **what actors become able to do**. This directory maps the next question: > **Whose possibilities change because that capability exists or is controlled?** Power is relational: mobilized puissance becomes power when it changes another actor's effective possibilities. ## Enabling and coordination power Relations that expand possibilities by granting access, recognition, coordination, legal standing, interoperability, or infrastructure use. Even enabling relations can become dependency when one actor becomes the only viable gateway. ## Access, gatekeeping, and allocation power Control over entry conditions and distribution of scarce resources, opportunities, credentials, services, funding, identity, or platform access. ## Visibility, ranking, agenda, and framing power Pre-political relations that shape what becomes seen, prominent, discussable, interpretable, fundable, reusable, or adoptable. ## Recognition, standing, and certification power Relations that affect who is treated as competent, trustworthy, qualified, legitimate, or institutionally relevant. ## Semantic, constitutive, and standard-setting power Definitions, classifications, ontologies, thresholds, translations, formats, trust roots, interoperability contracts, and admissibility rules. ## Authority, administration, and enforcement power Mandates, routing, assignment, timing, escalation, closure, sanctions, compulsion, and denial of consequences. ## Dependency, bottleneck, lock-in, and terminal power Relational leverage created when alternatives are costly, slow, non-portable, unrecognized, or unavailable. Terminal power is the limiting case where capture or failure cannot be effectively verified, contested, substituted, reversed, or exited. ## Veto, blocking, and delay power Preventing, slowing, queuing, withholding approval, or increasing procedural cost. Time is a political variable. Power relations are not automatically illegitimate. Assessment depends on mandate, scope, proportionality, transparency, alternatives, dependency, counterpower, and reversibility. See [`../showcase/07-component-power-matrix.md`](../showcase/07-component-power-matrix.md) for how these relations emerge around kOA components. ================================================================================================ FILE: power_dynamics/research/disciplinary-map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: e391e0dd2b7de8023a0122696574c11c3e394277e05bb981db1074a6693c5127 CONTENT_BYTES: 1092 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Disciplines That Study Power" source_basis: --- # Disciplines That Study Power Power Dynamics is interdisciplinary. Relevant fields include political science and political theory, sociology, sociology of organizations, political economy, institutional economics, law, public administration, organizational theory, network science, game theory, social choice, media and communication, information science, knowledge management, social epistemology, science and technology studies, infrastructure studies, platform governance, cybernetics, systems theory, complexity science, anthropology, social psychology, social movement theory, diffusion research, capability theory, finance, and monetary studies. The distinctive ambition of this repo is to connect **capability formation, relational power, feedback, conversion, and constitutional evolution** across these domains. The structured cross-disciplinary map now lives in [`../Academic-Lineage/README.md`](../Academic-Lineage/README.md). ================================================================================================ FILE: power_dynamics/research/literature-roadmap.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 14e86349571c627e90abee058a1226eb6a259a79f3d4ac9ccb63c9083334daa9 CONTENT_BYTES: 2247 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Literature Roadmap" source_basis: --- # Literature Roadmap The initial literature roadmap has been promoted into a structured academic lineage. Start with: - [`../Academic-Lineage/README.md`](../Academic-Lineage/README.md) — crosswalk from academic problem to Power Dynamics mechanism; - [`../Academic-Lineage/BIBLIOGRAPHY.md`](../Academic-Lineage/BIBLIOGRAPHY.md) — selective bibliography; - [`../Academic-Lineage/06-expertise-smartvote-and-collective-judgment.md`](../Academic-Lineage/06-expertise-smartvote-and-collective-judgment.md) — SmartVote / expertise lineage; - [`../Academic-Lineage/03-modularity-standards-and-path-dependence.md`](../Academic-Lineage/03-modularity-standards-and-path-dependence.md) — protocol power, installed-base power, lock-in and ossification; - [`../Academic-Lineage/01-power-dependence-and-domination.md`](../Academic-Lineage/01-power-dependence-and-domination.md) — relational power, dependency, resource dependence and non-domination. ## Next research priorities 1. **Domain-scoped expertise** — expand empirical literature on transfer limits, calibration, forecasting, and expert-selection mechanisms. 2. **Protocol / standards governance** — standards bodies, Internet ossification, backwards compatibility, migration governance, and interface control. 3. **Metric gaming** — Goodhart/Campbell effects, reputation markets, adversarial optimization, sybil resistance, and cumulative advantage. 4. **Epistemic democracy** — expertise, political equality, cognitive diversity, deliberation, and institutional design. 5. **Platform power** — ranking, moderation, recommender systems, identity, app stores, payment rails, and infrastructural dependency. 6. **Digital commons** — Ostrom-inspired governance of software, data, compute, schemas, models, and shared registries. 7. **AI-mediated authority** — when model outputs, defaults, summaries, or agentic execution become hidden decision rights. Future work should continue asking: > **What does each theory explain that Power Dynamics misses, and what does Power Dynamics connect that each theory usually treats separately?** ================================================================================================ FILE: power_dynamics/research/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 804a646584375d90c0244945e7e71d6570d343a99bd6ef37e41d153b52cfce5f CONTENT_BYTES: 812 ================================================================================================ --- maturity: "OPEN-QUESTION" claim_type: "EXTERNAL-RESEARCH" scope: "GENERAL" version: "6.2" title: "Research Layer" source_basis: --- # Research Layer This directory is the entry point for external scholarship that can challenge, refine, or situate Power Dynamics. The structured academic inventory now lives in [`../Academic-Lineage/`](../Academic-Lineage/README.md). External literature is deliberately separated from the supplied kOA corpus so the repository does not silently replace source-derived concepts with general academic knowledge. The governing rule is: > **Academic correspondence is not endorsement, historical influence, or implementation validation.** Use the literature to identify known failure modes, established mechanisms, impossibility results, and useful comparative vocabulary. ================================================================================================ FILE: power_dynamics/resources/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b37b3f776c012b5887ba1c8ab3e12304ba9c2d88619e4c8bba9090a7231767bf CONTENT_BYTES: 2348 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Resources and Stocks" source_basis: - S01 - S02 - S04 - S07 - S10 - S13 - S15 - S16 - S21 - S25 - S26 --- # Resources and Stocks Resources are inputs, not power by definition. A stock becomes politically significant only through the capacities, conversions, dependencies, and relations it supports. ## Material, financial, and time resources Money, property, energy, equipment, housing, physical infrastructure, and time are foundational because many other capacities depend on them. Time is especially political: formal rights can be unusable when work, debt, bureaucracy, care burdens, or procedure consume the time needed to exercise them. Financial resources are unusually convertible because they can purchase labor, infrastructure, attention, expertise, legal support, mobility, or time. ## Knowledge, expertise, and memory Knowledge can be shared without consuming the original resource, which makes it strongly generative. Expertise is not identical to credentials or reputation; it includes accumulated practice, methods, understanding, and evidence. Memory includes decisions, reasons, failures, outcomes, and operational traces. When made reusable, memory lowers the cost of future action. ## Networks, reputation, and brand Relationships, trust, reputation, affiliations, and brand recognition can lower coordination cost and open pathways to attention, collaboration, funding, and institutional access. They are not automatically authority. These resources are especially prone to positive feedback and incumbency effects. ## Technical, data, and infrastructure Code, schemas, hardware, APIs, data, keys, registries, protocols, and operational knowledge can be small artifacts with large systemic effects. Their significance depends on custody, reproducibility, substitution, recovery, and whether others must pass through them. ## Identity, rights, and optionality Identity, privacy, credentials, legal rights, licenses, and preserved choices condition future action. Optionality is valuable because action has not yet been irreversibly committed. A private identity or unpublished corpus can preserve future timing and strategy. Optionality is potential until it becomes effectively usable. ================================================================================================ FILE: power_dynamics/showcase/00-why-koa-is-immensely-powerful.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 0a1fccf6b937e23151c8aaea09bd8911006d7283d77784e0e0ffce55933e5d0f CONTENT_BYTES: 3009 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "Why kOA Is Immensely Powerful" source_basis: - S13 - S15 - S16 - S18 - S21 - S22 - S25 - S26 --- # Why kOA Is Immensely Powerful > **kOA is immensely powerful because it connects the full lifecycle of collective capability and makes the outputs of one cycle usable as inputs to the next.** ## Seven multipliers ### 1. Breadth kOA touches many domains at once: meaning, knowledge, cognition, discovery, credibility, networks, politics, economics, coordination, execution, memory, infrastructure, narrative, federation, and evolution. ### 2. Composition Those capabilities can strengthen one another. ```text structured knowledge + AI + credibility + discoverability + decision + workflow + memory = generated collective puissance ``` ### 3. Closure kOA attempts to close the loop: > **Know → Choose → Act → Remember → Know better** Information can become judgment; judgment can become action; action can become reusable memory. ### 4. Memory The system can preserve reasons, evidence, provenance, decisions, failures, outcomes, and implementation history instead of forcing every cycle to restart. ### 5. Compounding Action can leave assets behind: > **Action → Return → Asset → Reinvestment → Greater Future Puissance** ### 6. Replication Portability, self-hosting, capsules, federation, and branchability can transform one functioning capability into many independently operated capabilities. ### 7. Routing kOA does not only ask how to generate leverage. It also creates mechanisms to redirect it: - expertise → advice rather than sovereignty; - money → funding rather than more votes; - narrative → mobilization plus ethical self-binding rather than unquestionable legitimacy; - Koali → plural distributions rather than one terminal credibility owner; - infrastructure → self-hosting and substitution rather than captivity; - dominance → branch mobility rather than final authority. ## The master loop ```text Distributed resources → meaning → structured knowledge → discovery → credibility → deliberation → decision / allocation → coordination → execution → results → memory / returns → reinvestment → greater capability → federation / replication → contestation / evolution ``` This is why the system can become more capable **because it has already acted**. ## The central warning The same architecture that increases collective capability can also create: - semantic power; - agenda power; - political power; - economic and monetary leverage; - administrative power; - infrastructural dependency; - narrative capture; - founder power; - standards and registry power. Therefore: > **The Power Show and the Power Constitution are the same project viewed from opposite directions.** The first asks how much capability can be generated. The second asks whether those capabilities remain governable. ================================================================================================ FILE: power_dynamics/showcase/01-capability-spectrum.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 35b55929ff2b0c72fa186e621f04f28252d3ab6b7212764d60a24e567666c02e CONTENT_BYTES: 5041 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "The kOA Capability Spectrum" source_basis: - S13 - S15 - S16 - S18 - S21 - S25 --- # The kOA Capability Spectrum The Power Show begins by separating **what kOA helps actors do** from **what authority any actor has over others**. The first category is **puissance**: effectively mobilizable capacity. ## Epistemic puissance Create, structure, compare, verify, preserve, cite, derive, and reuse knowledge. Kristal is the primary architectural locus. ## Semantic puissance Make categories, meanings, relations, ambiguity, translation, and ontology explicit enough to inspect and evolve. SemantiK / SenTient are central here. ## Cognitive puissance Reason, synthesize, model, plan, generate, evaluate, and learn at greater throughput. AI can amplify this capability, but its outputs remain subordinate to explicit governance and provenance. ## Individual agency Understand options, make informed choices, refuse, exit, learn, publish, organize, and preserve personal or institutional optionality. ## Collective puissance Combine people who individually possess only partial knowledge, time, skills, resources, and relationships into coordinated capability. ## Network puissance Find expertise, collaborators, communities, institutions, supporters, customers, contributors, or alternative branches. Network capability changes what can be attempted. ## Discoverability puissance Make relevant knowledge, people, needs, proposals, branches, and evidence findable. Discoverability is empowering before it becomes a ranking or agenda relation. ## Credibility puissance Make evidence of contribution, expertise, reliability, or domain-bounded competence legible enough to be used. `Score ≠ competence`; credibility signals are governed readings, not persons. ## Deliberative and decision puissance Compare alternatives, preserve baseline equality, add advisory expertise without silently replacing the baseline, and make reasons inspectable. ## Political and constitutional puissance Form agendas, organize public standing, deliberate, decide, authorize, amend, contest mandates, and connect collective judgment to binding action without reducing politics to the final vote. ## Coordination puissance Sequence actors and information so that many partial capabilities produce coherent action. ## Operational puissance Route work, create ownership, set escalation paths, manage time windows, review outcomes, and close loops. ## Mnemonic puissance Preserve reasons, provenance, decisions, actions, failures, outcomes, versions, and lineage so future action begins with memory rather than amnesia. ## Economic puissance Mobilize money, property, funding, labor, contracts, productive assets, and infrastructure for action. Economic resources become power when their control materially changes others' options or bargaining positions. ## Allocation puissance Pool, prioritize, and direct resources toward people, projects, institutions, or goals. Economic contribution can support collective action without automatically purchasing political authority. ## Monetary and liquidity puissance Create, access, move, settle, convert, intermediate, or finance value through payment, credit, liquidity, settlement, or currency infrastructure. Monetary capability is distinct from general economic capability and carries unusually high dependency risk when rails become unavoidable. ## Technical puissance Build, inspect, modify, test, reproduce, repair, deploy, integrate, and maintain systems. ## Infrastructural puissance Create shared capability that lowers the cost of future action for many actors: protocols, schemas, identity contracts, deployment mechanisms, knowledge formats, workflow primitives. ## Distribution puissance Move knowledge and coordination across languages, communities, institutions, and geographic boundaries. ## Brand and affiliation puissance Create recognition, public signaling, identity, community affiliation, and transmission. Brand can create attention and funding without becoming truth or sovereignty. ## Federation puissance Operate local instances while preserving interoperability, lineage, portability, and the possibility of alternative governance. ## Exit and substitution puissance Leave, replace a dependency, preserve assets, self-host, migrate, or continue through another implementation. ## Forking puissance Create an alternative implementation, policy, ontology, credibility model, reader policy, governance model, or knowledge representation. ## Evolutionary puissance Do more than fork: demonstrate improvement, gather support, remain interoperable, recombine useful ideas, and allow dominant branches to change or be replaced. ## The key distinction A capability is not automatically a relation of power. > **The Power Show maps what actors become able to do. Power Dynamics then asks whose possibilities change because they can do it.** ================================================================================================ FILE: power_dynamics/showcase/02-individual-to-federation.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 290c6243729f0a72c2aaa460f2ab40d650cfc1caffcb3b902665eaab4277289a CONTENT_BYTES: 2040 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "From Individual to Federation" source_basis: - S13 - S16 - S18 - S25 --- # From Individual to Federation kOA's power show is also a **scale show**. The same architecture can increase capability at different social scales without assuming that every scale requires the same center. ## Individual Potential gains include: - better access to structured knowledge; - stronger personal memory and provenance; - AI-assisted cognition; - better discovery of expertise and opportunities; - easier publication and reuse; - more informed choice; - greater exit and optionality. ## Group A group can gain capabilities no member has alone: - shared context; - distributed expertise; - collective comparison; - task routing; - explicit ownership; - coordination; - reusable memory; - stronger network reach. This is **generated collective puissance**. ## Organization At organizational scale, the architecture adds: - roles and mandates; - governed workflows; - escalation; - decision records; - institutional memory; - auditability; - repeatable operating patterns; - succession and continuity. ## Federation A federation can add: - local sovereignty over local operation; - shared interoperability contracts; - portable knowledge; - distributed deployment; - branchable governance; - independent continuity; - cross-instance learning; - substitution of providers or implementations. The target architecture is: > **StrongHub + DistributedCapability + ReplicableWhole** This permits useful centrality without making the center the sole source of truth, continuity, identity, or capability. ## Scaling without scaling sovereignty The important design challenge is: > **Can capability scale faster than dependency on any single sovereign node?** That is why portability, federation, explicit authority scope, provenance, branch mobility, and local operation belong inside the power show rather than being afterthoughts. ================================================================================================ FILE: power_dynamics/showcase/03-composition-engine.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 21484ccca187161d98d85a37863b2e2f75a62727a5346f9edaa1ff5456c2360c CONTENT_BYTES: 2656 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "The Composition Engine" source_basis: - S13 - S15 - S18 - S21 - S25 --- # The Composition Engine kOA becomes significantly more powerful when distinct capabilities **compose**. Composition means that one subsystem's output becomes another subsystem's usable input without requiring one subsystem to own the others. > **Composition does not require ownership.** ## The chain ```text Contribution → semantic resolution → structured knowledge → discoverability → credibility context → deliberation / comparison → collective choice → governed work → coordinated action → outcome → reusable memory → new cycle ``` Each step removes a different failure mode. ## Why the whole can exceed the parts A large knowledge base without discovery can remain unused. A network without credible information can coordinate noise. Credibility without deliberation can become status hierarchy. A good decision without workflow can remain aspirational. Execution without memory can repeatedly pay the same learning cost. Memory without provenance can fossilize error. Forkability without interoperability can fragment. The composition engine matters because it joins these functions while preserving the possibility that each function remains governed separately. ## Generated collective puissance Suppose ten people each have: - incomplete knowledge; - limited time; - different skills; - different contacts; - different resources. Without coordination, their resources remain partly latent. With shared artifacts, discovery, explicit credibility context, a choice mechanism, task routing, and persistent memory, the group can perform actions unavailable to any individual participant. That capability is **generated**, not merely transferred. ## Multiplicative intuition A useful heuristic is: ```text collective effectiveness ≈ knowledge quality × discoverability × coordination × decision quality × execution × memory reuse ``` This is not a literal universal formula. It expresses a systems insight: a severe failure in one necessary transition can suppress the value of strong capabilities elsewhere. ## Constitutional consequence Because composition increases capability, the seams among components become political boundaries. Who controls: - discovery; - identity; - credibility interpretation; - defaults; - routing; - signatures; - update channels; - authority registries; - memory; - migration? Every composition seam is therefore both a capability interface and a possible power interface. ================================================================================================ FILE: power_dynamics/showcase/04-compounding-engine.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ad794216140bce451fdd6a6aa1097b07c72ec8b3beea0911cad5917f1413fad2 CONTENT_BYTES: 2187 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "The Compounding Engine" source_basis: - S02 - S13 - S18 - S25 - S26 --- # The Compounding Engine The strongest form of capability is not one-time capability. It is capability that leaves behind assets that lower the cost or raise the quality of future action. ## Core loop > **Action → Result → Return → Asset → Reinvestment → Greater Future Puissance** Possible returns include: - knowledge; - experience; - code; - tools; - infrastructure; - documentation; - provenance; - reputation; - credibility; - network relationships; - data; - institutional access; - financial resources; - memory; - optionality. ## Why memory matters Without reusable memory: ```text Act → learn → forget → pay again ``` With reusable memory: ```text Act → learn → preserve → reuse → start higher ``` This is why Kristal and operational memory are not passive archives. They are future capability infrastructure. ## Tools as crystallized past puissance A tool records prior effort in a form that can be reused. ```text past time + knowledge + experimentation → code / procedure / infrastructure → lower future effort → greater future capacity ``` The same applies to documentation, standards, schemas, trusted relationships, and institutional routines. ## Regenerative vs extractive loops An extractive loop looks like: ```text collective activity → value → narrow owner → more owner capacity ``` A regenerative loop looks like: ```text collective activity → value → participants + shared assets + common infrastructure → more distributed capability ``` The constitutional question is therefore: > **Who receives the returns generated by an exercise of collective puissance?** ## kOA transition A founder can bootstrap an ecosystem through concentrated effort. Long-term resilience requires a transition from: > **Founder-powered → System-powered ecosystem** The test is whether accumulated assets become usable, maintainable, forkable, and improvable by others without requiring unique founder knowledge or permission. ================================================================================================ FILE: power_dynamics/showcase/05-conversion-chains.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 685e187411bf0031df6a2448c701da8bbbec180ba64abf73bc7a571151c64769 CONTENT_BYTES: 1962 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Capability and Power Conversion Chains" source_basis: - S01 - S10 - S13 - S18 - S25 - S26 --- # Capability and Power Conversion Chains Power rarely remains in one domain. Resources and forms of puissance can be converted into other resources, opportunities, and relations of power. ## Common chains ```text knowledge → credibility → visibility → opportunity → resources → better tools → more knowledge ``` ```text brand → attention → affiliation → sales / funding → infrastructure → reach → stronger brand ``` ```text network → collaborators → execution → results → reputation → broader network ``` ```text technical control → control of defaults → user dependence → agenda influence ``` ```text money → infrastructure → distribution → attention → political influence ``` ## Conversion is not automatically illegitimate Systems need conversion. Expertise should influence advice. Money should fund work. Reputation can help discovery. Technical administration is needed to maintain infrastructure. The danger is **automatic cross-domain conversion**. Examples: - expertise becoming political sovereignty; - money becoming more votes; - brand becoming truth; - technical maintenance becoming control of political outcomes; - credibility becoming unquestionable authority; - infrastructure becoming ownership of users. That is why Power Dynamics uses **conversion firewalls** rather than trying to eliminate conversion itself. ## Power stacking When one actor controls several conversion points, legitimate functions can stack into cross-domain leverage. ```text finance + identity + certification + platform access + philanthropy → high cross-domain leverage ``` The issue is not that any one function is illegitimate. The issue is what the combined position makes possible. ================================================================================================ FILE: power_dynamics/showcase/06-pre-political-chain.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 79880e420eb4dad94ae0f356e33737d89bac6d0bf40a21fb79e85ac463faead4 CONTENT_BYTES: 1879 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "The Pre-Political Chain" source_basis: - S15 - S16 - S18 - S21 - S22 - S25 --- # The Pre-Political Chain Power begins before formal voting or command. > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** kOA touches nearly every step. ## Meaning Categories determine what can be described, compared, included, or excluded. Semantic infrastructure can create semantic puissance; control over definitions can create semantic power. ## Knowledge What becomes structured, provenance-bearing, canonical, disputed, or reusable affects later reasoning. ## Visibility What is discoverable has a higher chance of being cited, funded, reused, adopted, or debated. Discoverability is therefore both capability and governance. ## Credibility Signals about expertise or contribution can help groups navigate complexity. They can also affect opportunity and standing. ## Agenda What is surfaced repeatedly becomes more likely to be treated as worthy of collective attention. ## Deliberation and decision Decision tools can expand comparative capacity. Defaults, lenses, weighting, and presentation can also shape the decision environment. ## Execution Routing, ownership, time, escalation, and closure determine whether a nominal decision becomes an effective outcome. ## Memory What is preserved becomes precedent, evidence, training data, institutional learning, and the starting point for future decisions. ## Why this belongs in the Power Show The impressive capability of kOA is precisely that it links these stages. The governance challenge is that a system spanning these stages could also accumulate pre-political leverage if the same node controls too many transitions. ================================================================================================ FILE: power_dynamics/showcase/07-component-power-matrix.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 03f8ba9c591f24548dda658e517bd6c1f41101d2356bf824212eb509b7f41008 CONTENT_BYTES: 3864 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "kOA Component Power Matrix" source_basis: - S02 - S13 - S14 - S15 - S16 - S17 - S18 - S21 - S25 --- # kOA Component Power Matrix Every component should be read across five questions: 1. What resource does it organize? 2. What puissance does it generate? 3. In which domain does relational power emerge? 4. Into what other domains can that power convert? 5. How is capability routed or counterpower preserved? | Component | Primary domains | Generated / amplified puissance | Possible relational power | Cross-domain conversion | Routing / counterweights | |---|---|---|---|---|---| | SemantiK / SenTient | semantic, epistemic | classification, ambiguity resolution, translation | framing, admissibility, ontology power | meaning → agenda / enforcement | explicit ontologies, provenance, local governance, alternatives | | Kristal | epistemic, mnemonic | structured knowledge, provenance, reusable memory | validation, canon, trust-root, standard-setting | knowledge → credibility → visibility | portability, lineage, competing Kristals, reader-policy plurality | | Konnaxion | information, attention, network | circulation, association, discoverability | ranking, moderation, visibility, agenda, access | attention → affiliation / opportunity / politics | explicit policies, export, federation, alternative discovery paths | | Koali / EkoH | credibility, reputation | evidence and expertise legibility | standing, certification, opportunity | credibility → visibility / funding / influence | domain bounds, portable evidence, plural distributions, contestation | | SmartVote | political, deliberative | comparative judgment, multiple readings | lens, default, weighting, agenda influence | expertise → political interpretation | baseline preservation, explicit lenses, deterministic calculation | | Orgo | administrative, operational | assignment, routing, escalation, execution, closure | timing, workload, approval, closure | administration → de facto policy | scoped roles, audit, appeal, revocability, mandate boundary | | Capsules / federation | technical, infrastructural, evolutionary | deployment, replication, local continuity, substitution | signing, update, registry, compatibility | infrastructure → standards / dependency | verifiable packages, rollback, self-hosting, multiple operators | | AI | cognitive, epistemic | reasoning, synthesis, translation, modeling | hidden framing, prioritization, interpretive dependency | cognition → judgment / execution | bounded roles, provenance, human/institutional authority | | Brand / narrative | narrative, attention, network, economic | recognition, affiliation, transmission, fundraising | symbolic legitimacy, gatekeeping, attention | brand → affiliation → revenue / adoption | ethical self-binding, brand ≠ truth, protocol/brand separation | | Multilingual layer | semantic, distribution | cross-language access, translation, reach | language inclusion/exclusion, translation framing | language → discoverability / standing | explicit source links, review, local semantic control | | Zero-Skim mechanisms | economic, allocation, political | pooling and allocating resources | allocation, donor/funder leverage | money → projects / infrastructure | one-member-one-vote style safeguards, capital ≠ political standing | | Koali protocolization | technical, credibility, evolutionary | reproducible credibility capability | registry / compatibility / standing power | founder control → protocol ecology | ownership decoupling, interoperability, branchability | ## The design goal > **Increase generated puissance aggressively, expose cross-domain conversion, route capability deliberately, and keep resulting power contestable and non-terminal.** ================================================================================================ FILE: power_dynamics/showcase/08-governance-after-capability.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: ff1fc042f49f177f186981568bc76ffcb466e0cd2b4e84ad5c7c70ecf7b4ab4f CONTENT_BYTES: 3019 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Governance After Capability" source_basis: - S16 - S18 - S21 - S25 --- # Governance After Capability Power Dynamics does not treat governance as the mechanism that prevents kOA from becoming powerful. It treats governance as the mechanism that allows kOA to become **very capable without making successful capability terminal**. ## The sequence ```text Generate puissance → compose puissance → amplify and preserve it → observe emerging power relations → constrain arbitrary conversion → preserve counterpower → keep alternatives viable → let governance itself evolve ``` ## Governance can redirect power before constraining it The constitutional architecture has two jobs: 1. **redirect useful leverage toward distributed capability where possible;** 2. **preserve counterpower where concentration still occurs.** Examples include protocolizing founder knowledge, making Koali plural and reproducible, publishing ethical constraints in narrative, separating expertise from sovereignty, and turning central infrastructure into self-hostable local capability. See [`11-power-routing-and-sharing.md`](11-power-routing-and-sharing.md) and [`../constitution/power-redirection-sharing.md`](../constitution/power-redirection-sharing.md). ## Four core counterpowers > **Verification + Contestation + Substitution + Exit** ### Verification Can affected actors independently inspect the claim, rule, calculation, provenance, signature, workflow, or authority? ### Contestation Can they challenge it through a meaningful process? ### Substitution Can another provider, branch, reader, model, implementation, institution, or workflow perform the function? ### Exit Can participants leave without disproportionate loss of identity, history, knowledge, reputation, data, rights, or continuity? ## Non-terminal architecture No architecture can guarantee that capture never occurs. The more realistic objective is: > **Instance Capture ≠ System Capture** A captured organization, deployment, branch, registry, or brand should not automatically capture the whole capability ecology. ## Conversion firewalls Useful functional control should not silently become unrelated sovereignty. ```text expertise → advice yes expertise → permanent rule no automatic path money → contribution yes money → more political votes no automatic path technical administration → upkeep yes technical administration → policy no automatic path ``` ## Evolutionary governance Even the constitution is an approximation. Forks and branches are not only emergency escape valves. They are normal mechanisms of institutional experimentation. The final safeguard is therefore not a perfect center. It is the preservation of a system in which alternatives can remain viable enough to challenge, recombine with, or replace dominant implementations. ================================================================================================ FILE: power_dynamics/showcase/09-why-this-is-not-just-software.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 6c0ee039801c0a22660b0434583316f625eae068a7cdc4a460e26f956fda1c39 CONTENT_BYTES: 1632 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "Why kOA Is Not Just Software" source_basis: - S13 - S16 - S18 - S25 --- # Why kOA Is Not Just Software Software is one layer of kOA's capability architecture. The broader system combines: - knowledge structures; - semantic conventions; - provenance; - credibility interpretations; - coordination rules; - decision procedures; - workflows; - institutional memory; - identity and affiliation; - deployment infrastructure; - governance; - branching and federation; - human and AI cognition. That means kOA can affect not only computation but **what a collective can know, notice, compare, decide, coordinate, preserve, and reproduce**. ## Capability infrastructure A useful definition is: > **kOA is capability infrastructure for converting knowledge into governed collective action and action back into reusable knowledge.** Its deeper loop is: ```text knowledge → orientation → choice → execution → experience → memory → better knowledge ``` ## Why infrastructure matters politically Infrastructure disappears into normality when it works. Once widely adopted, technical defaults and interfaces can become de facto political boundaries. A powerful infrastructure may therefore create: - standard-setting power; - compatibility power; - identity gatekeeping; - discoverability power; - administrative power; - mnemonic power; - dependency and lock-in. The objective is not to avoid infrastructure. It is to make infrastructural puissance **governable, portable, inspectable, and non-terminal**. ================================================================================================ FILE: power_dynamics/showcase/10-counterpower-and-optionality.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 8b0b9d1f41d7da968e241220d2ca8e23c20e76e2f9c56fe0d623f596fd476541 CONTENT_BYTES: 2279 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Counterpower and Optionality as Capability" source_basis: - S01 - S16 - S18 - S25 --- # Counterpower and Optionality as Capability The Power Show includes not only the ability to **do more**, but also the ability to **depend less**. A system that can coordinate, rank, certify, route, or preserve memory is powerful. A participant who can verify, contest, substitute, exit, fork, or wait also possesses important capability. ## Verification puissance Ability to independently inspect claims, provenance, signatures, rules, calculations, policies, and technical behavior. ## Contestation puissance Ability to challenge a decision, score, category, workflow, authority, branch, or interpretation through a process capable of producing change. ## Substitution puissance Ability to replace a provider, implementation, trust root, reader policy, workflow, branch, or institution with a viable alternative. ## Exit puissance Ability to leave while preserving enough identity, history, knowledge, reputation, data, rights, relationships, and continuity for departure to be meaningful. ## Forking puissance Ability to create an alternative rather than accept the existing implementation as terminal. ## Branch mobility Ability to move beyond a symbolic fork: attract maintainers, preserve interoperability, gain discoverability, gather support, and become institutionally viable. ## Optionality puissance Ability to preserve future choices rather than commit them prematurely. Examples include: - retained financial reserves; - unpublished knowledge; - unused deployment capacity; - privacy and unrevealed identity; - multiple providers; - portable credentials; - branchable software; - independent infrastructure. Optionality is important because **unexercised capability can still change future strategic position**. ## The inversion Traditional power analysis often asks who can compel whom. Power Dynamics also asks: > **Who can refuse? Who can leave? Who can reproduce? Who can create an alternative? Who can preserve the option to act later?** These are central forms of practical freedom and therefore belong inside the Power Show itself. ================================================================================================ FILE: power_dynamics/showcase/11-power-routing-and-sharing.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 70a24e3ef1ff1216276eccec6fcae8cf62af4e5cf8115942ec8046348c9d1152 CONTENT_BYTES: 6924 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "Power Routing and Sharing" source_basis: - S02 - S14 - S15 - S16 - S17 - S19 - S21 - S22 - S25 --- # Power Routing and Sharing The strongest version of the kOA Power Show is not: > **kOA accumulates enormous power.** It is: > **kOA can generate enormous collective puissance while deliberately routing much of the resulting capability, leverage, optionality, and authority outward.** This is a distinct design achievement. Many systems empower users while quietly increasing the terminal power of the operator. Power Dynamics therefore asks two separate questions: 1. **What new puissance does the system create?** 2. **Where does the resulting leverage go?** ## Four things can be routed ### Capability Who gains practical ability to know, build, decide, execute, remember, reproduce, and evolve? ### Authority Who gains rights to validate, rank, approve, route, certify, update, moderate, or decide? ### Returns Who receives the reusable assets generated by action — knowledge, money, reputation, network, code, data, memory, infrastructure, and opportunity? ### Optionality Who gains the practical ability to refuse, leave, substitute, self-host, fork, wait, or build an alternative? A system may distribute one while concentrating another. For example, it may distribute information while centralizing authority, or distribute software while centralizing identity and discoverability. A power-sharing audit must inspect all four. ## Core mechanisms ### 1. Narrative self-binding Narrative and brand can create enormous attention and affiliation puissance. One kOA mechanism is to publish ethical limits **inside the same fiction that carries symbolic power**. This is not a guarantee of good conduct. It is a public self-binding mechanism: ```text symbolic influence → explicit ethical commitments → public expectations → criticism / citation / contestation → reduced interpretive freedom for arbitrary drift ``` The source corpus explicitly frames its ethical code around clarity of intention, respect for living beings, vigilance against monopoly and domination, recognition of contributors, self-mockery, revision, criticism, and a living code rather than dogma. The important Power Dynamics insight is that **the narrative channel carries not only the message, but also constraints on how the message should be used**. ### 2. Protocolization Founder knowledge can be converted into a dependency or into shared capability. ```text founder insight → architecture → explicit interfaces → schemas / documentation / testable behavior → independent implementation → distributed mastery ``` Protocolization redirects founder-centric puissance toward maintainers, institutions, branches, and users who can reproduce the function without unique personal permission. > **Founder → Architecture → Distributed Mastery** ### 3. Koali ownership decoupling The current design intention is that Koali should **not remain an exclusive personal property that others must depend on**. Its useful logic should be capable of duplication, sharing, variation, and plural operation around compatible structures. That means credibility infrastructure should tend toward: ```text common / interoperable kernel + plural distributions + portable evidence / history + explicit policy identity + alternative operators = plurality without fragmentation ``` This redirects recognition power from a single credibility owner toward an ecology of communities and distributions. This design intent is architect-confirmed and should be backed by a canonical Koali distribution specification as the implementation matures. ### 4. Advice without sovereignty EkoH and SmartVote illustrate a different redirection: ```text expertise / credibility → informed advice not → automatic political supremacy ``` A baseline political reading can remain visible while advisory readings expose competence or ethics under explicit policies. Expertise gains influence without silently inheriting sovereignty. ### 5. Portable epistemic capability Kristal can redirect epistemic leverage away from a platform owner by making knowledge artifacts portable, attributable, versioned, auditable, and capable of lineage. Competing Kristals and reader policies make disagreement representable rather than requiring one final representation to own the whole epistemic field. ### 6. Infrastructure → local autonomy Self-hosting, offline operation, capsules, federation, rollback, verification, and substitution convert infrastructure from a potential dependency into a source of local capability. ```text central service → reproducible package / protocol → local operation → independent continuity ``` ### 7. Capital → democratic allocation The Zero-Skim design separates contribution from political standing. Money can supply resources without automatically purchasing more votes over allocation. This is a direct power-redirection pattern: > **Economic contribution → common resource pool → democratic allocation power** rather than: > **Economic contribution → proportional political authority** ### 8. Dominance → evolutionary alternatives Forkability, competing Kristals, branch mobility, and recombination redirect some of the power of incumbency toward challengers. The system does not need to assume that the dominant branch is permanently best. It needs viable pathways through which a better or complementary branch can demonstrate value and gather support. ## Power sharing is not equalization Power sharing does not mean every actor must have identical capability, expertise, responsibility, or authority. It means that **useful asymmetries do not silently become terminal dependencies**. The objective is therefore not flatness. It is a governable ecology in which generated capability can circulate and where important functions can be learned, reproduced, challenged, substituted, or evolved. ## Canonical sequence The Power Show can now be summarized as: > **Generate → Compose → Close the loop → Preserve returns → Compound → Route → Share → Bind → Contest → Fork → Evolve** This is how the repository reconciles two ambitions that can otherwise appear contradictory: > **Make kOA immensely powerful.** > > **Make that power increasingly usable by others rather than terminally owned by one center.** ## Continue - [`07-component-power-matrix.md`](07-component-power-matrix.md) - [`08-governance-after-capability.md`](08-governance-after-capability.md) - [`../constitution/power-redirection-sharing.md`](../constitution/power-redirection-sharing.md) - [`../koa/koali-protocolization.md`](../koa/koali-protocolization.md) - [`../cases/ethical-fiction-self-binding.md`](../cases/ethical-fiction-self-binding.md) ================================================================================================ FILE: power_dynamics/showcase/12-cross-domain-power-surface.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: f547049898911bc48d4926ead1552d86a78cd86031b2086d28928f14110f9701 CONTENT_BYTES: 2753 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "Cross-Domain kOA Power Surface" source_basis: - S10 - S13 - S14 - S15 - S16 - S17 - S18 - S21 - S22 - S25 - S26 --- # Cross-Domain kOA Power Surface kOA's largest effects appear when capability crosses domain boundaries. ## Cross-domain graph ```text SEMANTIC ↓ EPISTEMIC → CREDIBILITY → VISIBILITY → AGENDA → POLITICAL ↓ ↓ ↓ ↓ COGNITIVE NETWORK NARRATIVE ALLOCATION ↓ ↓ ↓ ↓ DECISION ← COLLECTIVE ← AFFILIATION ← BRAND ECONOMIC ↓ ↓ ADMINISTRATIVE → EXECUTION → RETURNS → MEMORY → COMPOUNDING ↓ ↓ TECHNICAL / INFRASTRUCTURAL ← FUNDING ← MONETARY / ECONOMIC ↓ FEDERATION → SUBSTITUTION → FORK → EVOLUTION ``` No arrow means automatic legitimacy. Each arrow is a **possible conversion path** that must be made explicit and governed. ## High-leverage conversion chains ### Knowledge to political influence ```text knowledge → credibility → visibility → agenda access → political influence ``` ### Money to political leverage ```text money → infrastructure → reach → attention → organizational capacity → political leverage ``` ### Brand to economic capacity ```text brand → attention → affiliation → purchases / funding → infrastructure → development capacity ``` ### Technical control to de facto governance ```text technical administration → defaults → compatibility → dependency → inability to substitute → quasi-sovereign leverage ``` ### Memory to future power ```text institutional memory → precedent → lower coordination cost → faster action → stronger results → greater credibility ``` ## Why the map matters A component can be perfectly legitimate inside its original function and still become dangerous through conversion. This is the basis of **Power Stacking** and **Capture**: > **Functional Control → Cross-Domain Power** The appropriate question is not merely “is this component democratic?” but: > **What other domains can control of this component buy?** ## Routing layer The kOA response is to combine: - function separation; - conversion firewalls; - scoped authority; - protocolization; - self-hosting; - portable evidence; - baseline/advisory separation; - explicit ethics; - branch mobility; - verification, contestation, substitution, and exit. See [`14-power-conversion-and-routing-map.md`](14-power-conversion-and-routing-map.md). ================================================================================================ FILE: power_dynamics/showcase/13-political-economic-monetary-power.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 729a6d1736bf24e898c8fe6badbb9005c91d8cc54d8dcf64cccdfb950882a304 CONTENT_BYTES: 4044 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "Political, Economic, and Monetary Power" source_basis: - S09 - S10 - S11 - S14 - S15 - S17 - S18 - S21 - S25 --- # Political, Economic, and Monetary Power These domains interact strongly but should not be collapsed. ## Political power Political power concerns who can shape: - political standing; - agenda; - deliberation; - decision rights; - representation; - mandates; - amendment; - vetoes; - legitimacy; - allocation decisions; - execution of public decisions. kOA touches political power across the full chain: > **Meaning → Knowledge → Visibility → Credibility → Agenda → Deliberation → Decision → Execution → Memory** This means a system can preserve formal equality at the ballot and still create major political asymmetries upstream. ### kOA mechanisms - SemantiK / Kristal: what becomes intelligible and evidentially stable; - Konnaxion: what becomes discoverable and discussable; - Koali / EkoH: which competence or contribution becomes legible; - SmartVote: how alternative readings of a decision become visible; - Orgo: how a decision becomes implementation; - memory: what becomes precedent; - branch ecology: how institutional alternatives emerge. ## Economic power Economic power concerns control or mobilization of scarce resources: - money; - property; - productive assets; - labor and time; - infrastructure; - funding; - procurement; - contracts; - philanthropy; - access to markets. Money is a resource stock. When mobilizable, it becomes economic puissance. When used to alter another actor's options, bargaining position, access, or allocation, it becomes relational economic power. ```text money → purchasing / funding / bargaining puissance → access / allocation / dependency effects ``` ### kOA mechanisms - Zero-Skim: common resource pooling and democratic allocation; - brand / merchandise: symbolic → economic conversion; - credibility: opportunity and funding access; - networks: collaborators, customers, institutions, opportunities; - execution: turning funding into actual capability; - compounding: returns become future assets. ## Monetary power Monetary power concerns the infrastructure and rules of exchange itself: - issuance; - unit of account; - liquidity; - settlement; - payment rails; - reserves; - convertibility; - credit and debt conditions; - access to transaction systems. This domain can create exceptional leverage because nearly every economic actor depends on exchange infrastructure. ### Legacy KingCoin as stress test The older KingCoin material proposes highly centralized functions including monetary coordination, taxation, redistribution, sanctions, settlement, and public investment. In the current repository these are **LEGACY-PROPOSAL** material. Their analytical value is to show the danger of: ```text monetary authority + taxation + allocation + sanctions + governance + transaction infrastructure = extreme power stacking ``` The evolution of Power Dynamics moves away from “design a sufficiently just center” toward: > **Design powerful functions that do not become terminal arbitrary authority.** ## Conversion firewalls between the three domains | Conversion | Status | |---|---| | money → funding | desirable | | funding → infrastructure | desirable | | infrastructure → broader capability | desirable | | money → proportional political standing | blocked by principle | | credibility → informed advice | desirable | | credibility → sovereign decision right | blocked by principle | | monetary infrastructure → arbitrary exclusion | constitutional risk | | administrative execution → mandate redefinition | blocked by principle | ## The key question > **How can material and monetary capability increase collective agency without converting wealth, rails, or administration into unaccountable political sovereignty?** That is a core Power Dynamics question, not a side topic. ================================================================================================ FILE: power_dynamics/showcase/14-power-conversion-and-routing-map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 23b45d217d5ec37956edddffe04f707613e262cdae073260fbb81bd99a381bfd CONTENT_BYTES: 3572 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.0" title: "Power Conversion and Routing Map" source_basis: - S02 - S10 - S13 - S14 - S15 - S16 - S17 - S18 - S25 - S26 --- # Power Conversion and Routing Map The central constitutional problem can be expressed as a routing problem: ```text RESOURCE / CAPABILITY ↓ LEGITIMATE FUNCTION ↓ NEW LEVERAGE ↓ ┌─────────────────────┬─────────────────────────┐ │ governed conversion │ silent conversion │ │ │ │ │ advice │ sovereignty │ │ funding │ vote buying │ │ attention │ truth │ │ maintenance │ political control │ │ execution │ mandate capture │ │ local capability │ user captivity │ └─────────────────────┴─────────────────────────┘ ↓ ROUTING / FIREWALL / COUNTERPOWER ``` ## Main conversion firewalls | Source | Allowed / useful destination | Automatic destination to resist | Mechanisms | |---|---|---|---| | Expertise | advice, interpretation, warning | political sovereignty | domain bounds, parallel readings, baseline preservation | | Money | funding, procurement, infrastructure | more votes / standing | democratic allocation rules | | Brand | attention, affiliation, commerce | truth / legitimacy | architecture-first references, brand ≠ protocol | | Narrative | translation, mobilization, memory | unquestionable authority | ethical self-binding, criticism, self-mockery | | Credibility | discovery, trust cues | final authority | contestable evidence, plural distributions | | Technical administration | maintenance, implementation | political outcome control | scoped roles, audit, revocability | | Execution | carrying out mandate | redefining mandate | explicit decision-to-work boundary | | Infrastructure | capability, continuity | captivity | self-hosting, substitution, federation | | Incumbency | demonstrated reliability | permanent dominance | branch mobility, lineage, recombination | ## Main routing destinations ### Toward users - portability; - local operation; - usable evidence; - exit; - substitution; - personal optionality. ### Toward communities - shared knowledge; - local semantic governance; - democratic allocation; - collective memory; - community-run distributions. ### Toward protocols - explicit contracts; - schemas; - testable behavior; - interoperability; - independent implementations. ### Toward branches - lineage; - variation; - comparison; - discoverability; - support accumulation; - replacement capacity. ### Away from terminal founder ownership - documentation; - distributed mastery; - protocolization; - independent operation; - separation of persona, brand, protocol, and governance; - succession and maintainer plurality. ## Routing quality A mechanism is not genuinely power-sharing merely because the license says “open” or because export exists in theory. Power sharing should be evaluated by **effective possibility**: > Can another actor actually reproduce, operate, understand, contest, substitute, or evolve the function under real conditions? This is the difference between formal openness and effective counterpower. ================================================================================================ FILE: power_dynamics/showcase/15-propagation-engine.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 542797cb657ea8785d4b15c3633537f06b5e649c2ea4e50d65b9682fb23bd332 CONTENT_BYTES: 1877 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "The Propagation Engine" source_basis: - S13 - S15 - S18 - S21 - S25 - S29 --- # The Propagation Engine kOA does not rely on one flywheel. It can contain several partially independent loops whose outputs become one another's inputs. ```text BUILD ↓ USEFUL CAPABILITY ↓ WORLD / DEMONSTRATION ↓ UNDERSTANDING ↓ PILOT ↓ EVIDENCE ├────────→ CREDIBILITY ───────→ INSTITUTIONAL ACCESS │ ↓ │ MORE PILOTS │ └────────→ OPERATIONAL DEMAND ─→ MANAGED SERVICE ↓ REVENUE ↓ DEVELOPMENT ↓ GREATER CAPABILITY ↺ ``` Other loops attach: ```text pilot → training material → operator → independent deployment → more pilots ``` ```text integration → more capability → more usefulness → demand for integration ``` ```text objects → SmartVote signal → better discovery → reuse → more objects ``` ```text new language → new community → contribution → better language resources ``` ```text founder work → protocols / tools / documentation → autonomous operators → lower founder bottleneck → more parallel work ``` The most important property is therefore not “many mechanisms.” > **The mechanisms share returns.** The constitutional requirement is equally important: > **Positive feedback must increase distributed capability faster than it increases terminal dependency.** See [`../PROPAGATION.md`](../PROPAGATION.md). ================================================================================================ FILE: power_dynamics/showcase/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: d0922f1c0084a093282f0cddc37714f525338e4abeebf3b6c8a48526ab9591fd CONTENT_BYTES: 2496 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "kOA" version: "6.3" title: "kOA Power Show" source_basis: - S13 - S15 - S16 - S18 - S21 - S25 --- # kOA Power Show This directory is the **front stage** of Power Dynamics. It answers three questions in order: 1. **Why is kOA immensely powerful?** 2. **What kinds of power can that capability create across domains?** 3. **How is that power routed, constrained, shared, contested, and evolved?** ## Guided sequence 0. [`00-why-koa-is-immensely-powerful.md`](00-why-koa-is-immensely-powerful.md) — the shortest complete answer. 1. [`01-capability-spectrum.md`](01-capability-spectrum.md) — the capability spectrum. 2. [`02-individual-to-federation.md`](02-individual-to-federation.md) — capability across scale. 3. [`03-composition-engine.md`](03-composition-engine.md) — why the whole can exceed the sum. 4. [`04-compounding-engine.md`](04-compounding-engine.md) — how action creates greater future capability. 5. [`05-conversion-chains.md`](05-conversion-chains.md) — how resources and forms of puissance convert. 6. [`06-pre-political-chain.md`](06-pre-political-chain.md) — power before formal decision. 7. [`07-component-power-matrix.md`](07-component-power-matrix.md) — component-by-component power surfaces. 8. [`08-governance-after-capability.md`](08-governance-after-capability.md) — why success creates a constitutional problem. 9. [`09-why-this-is-not-just-software.md`](09-why-this-is-not-just-software.md) — kOA as capability infrastructure. 10. [`10-counterpower-and-optionality.md`](10-counterpower-and-optionality.md) — verification, contestation, substitution, exit. 11. [`11-power-routing-and-sharing.md`](11-power-routing-and-sharing.md) — how leverage is redirected outward. 12. [`12-cross-domain-power-surface.md`](12-cross-domain-power-surface.md) — the multi-domain power map. 13. [`13-political-economic-monetary-power.md`](13-political-economic-monetary-power.md) — explicit separation of political, economic, and monetary power. 14. [`14-power-conversion-and-routing-map.md`](14-power-conversion-and-routing-map.md) — conversion firewalls and routing destinations. 15. [`15-propagation-engine.md`](15-propagation-engine.md) — how returns cross branches and couple adoption, evidence, revenue, tooling, operators, language, integration, and founder decentering. The canonical full-surface summary is [`../POWER-SURFACE.md`](../POWER-SURFACE.md). ================================================================================================ FILE: power_dynamics/sources/architect-confirmed-design-notes.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 1ffe789263ea505063407bd8d0586203a7611e99806f0137f45bd564ffac6301 CONTENT_BYTES: 4305 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "USER-CONFIRMED-DESIGN" scope: "kOA" version: "6.3" title: "Architect-Confirmed Design Notes" source_basis: --- # Architect-Confirmed Design Notes This file records current design intentions that have been explicitly confirmed during repository development but are not yet backed by a canonical technical specification in the supplied corpus. They should not be cited as if they were already implemented facts. ## Koali ownership and distribution Current intention: > Koali should not remain the exclusive personal property or terminal credibility authority of its founder. Its useful capability should be duplicable, shareable, branchable, and capable of plural distributions around interoperable structures. Technical evidence still needed: - kernel / interoperability specification; - evidence portability model; - distribution identity; - policy versioning; - branch / fork procedure; - registry / discovery design; - brand / trademark relationship to protocol implementations. ## Ethical principles inside fiction Current intention and source-backed practice: > The narrative layer explicitly publishes ethical principles rather than leaving them as private founder intent. S02 provides direct source support for a living ethical code, vigilance against monopoly and domination, public recognition, self-mockery, revision, and non-dogmatic transmission. ## Reference Kristal stewardship and worldview forks Current intention: > A principal encyclopedic Kristal is envisioned as an institutionally stewarded reference corpus, including a proposed UNESCO stewardship role, while remaining forkable into incompatible worldview, cultural, religious, fictional, or experimental branches. This records an intended stewardship model, **not an existing UNESCO agreement, endorsement, or deployment**. The intended constitutional distinction is: ```text reference stewardship ≠ ownership of truth forkability ≠ equal evidentiary support ``` Technical evidence still needed: - reference-branch governance specification; - fork and lineage rules; - reader-policy model; - evidentiary comparison across branches; - institutional stewardship / handoff mechanism. ## Founder opposition rehearsal Current intention: > kOA should not only permit disagreement with its founder; it should establish a practiced precedent for organized, legitimate opposition to a founder-backed proposal. A proposed civic resilience drill uses an otherwise coherent political platform containing one conspicuously abusive tattoo-prohibition / compulsory-removal policy. The intended output is a reusable counterpower pathway, not adoption of the policy. The design objective is to test whether symbolic founder authority can be prevented from becoming truth or policy immunity. ## Epistemic authority corruption drill Current intention: > A deliberately false flat-Earth Kristal branch should be used as an adversarial epistemic stress test to study how weak, dependent, misleading, or fabricated authority signals can accumulate into apparent credibility and consensus. The primary intended output is a postmortem taxonomy of corruption patterns and detection failures. This note records the threat-model direction, not an operational procedure for deceiving external institutions or audiences. ## Propagation and coupled loops Current intention: > kOA should be analyzed not only as a set of compounding capabilities but as a network of partially independent propagation loops whose returns can be reused across branches. Examples include: - revenue → shared development capacity; - evidence → credibility → institutional access; - training → independent operator → more deployments; - integration → wider capability → more integration demand; - language support → community access → contribution → improved language assets; - documentation → lower review cost → feedback → better documentation; - founder knowledge → protocol / tools / documentation → reduced founder bottleneck. The design requirement is that positive feedback increase distributed capability without automatically increasing terminal authority or dependency at the same rate. See `sources/propagation-design-notes.md` for the current detailed record. ================================================================================================ FILE: power_dynamics/sources/concept-origin-map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 10f8496b1e4bef109ddbb3e72239130eff4c883d5442a85d64459b4e75577a22 CONTENT_BYTES: 4085 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.2" title: "Concept Origin Map" source_basis: --- # Concept Origin Map | Concept | Main basis | Status | |---|---|---| | kOA Power Show | S13, S15, S18, S21, S25 + presentation synthesis | NEW-CONCEPT / presentation layer | | Capability spectrum | corpus + Power Dynamics synthesis | NEW-CONCEPT | | Capability surface / power surface | corpus + Power Dynamics synthesis | NEW-CONCEPT | | Composition engine / composition gain | S13, S18, S21, S25 + synthesis | NEW-CONCEPT | | Closed capability loop | S13, S25 + synthesis | NEW-CONCEPT | | Compounding engine | S13, S21, S25, S26 + synthesis | NEW-CONCEPT | | Effective possibility / dependency | S01, S16 | ANALYTICAL-RECONSTRUCTION | | Resource → Potential → Capacity → Puissance → Power | S01, S13, S16, S18, S21, S25 + synthesis | NEW-CONCEPT / ontological refinement | | Three-axis ontology × dynamics × domains | corpus + Power Dynamics synthesis | NEW-CONCEPT | | Stock → Capacity → Flow → Return | S13, S21, S25, S26 + synthesis | ANALYTICAL-RECONSTRUCTION | | Reservoir → Release → Flow → Mediation | S13, S15, S18, S21, S22 + synthesis | NEW-CONCEPT / mobilization model | | Generated / collective puissance | S13, S18, S21, S25 | ANALYTICAL-RECONSTRUCTION | | Pre-political power | S15, S18, S21, S22 | NEW-CONCEPT / synthesis | | Discoverability as governance | S15 | SOURCE-DERIVED | | Epistemic capital / compounding collective capacity | S26 | SOURCE-DERIVED analytical concept | | Returns / reinvestment / compounding puissance | S13, S21, S25, S26 + synthesis | NEW-CONCEPT | | Power Conversion Firewalls | S15, S17, S21, S22, S28 + synthesis | NEW-CONCEPT | | Power Stacking | S10 + synthesis | NEW-CONCEPT | | Capture as cross-domain conversion | corpus + prior kOA coherence work | ANALYTICAL-RECONSTRUCTION | | Verification + Contestation + Substitution + Exit | S16, S19, S21, S25 + prior coherence work | ANALYTICAL-RECONSTRUCTION | | Instance Capture ≠ System Capture | federation principles + synthesis | NEW-CONCEPT | | Branch Mobility | S16, S19, S25 + synthesis | NEW-CONCEPT | | Evolutionary Governance | S13, S16, S22 + synthesis | NEW-CONCEPT | | Complementarity / anti-dogma | S13, S16, S22 + synthesis | NEW-CONCEPT | | Mnemonic power | S13, S21, S25 + synthesis | NEW-CONCEPT | | Recognition loop risk | S15, S28 + synthesis | NEW-CONCEPT | | Founder decentering | S18, S25 + synthesis | ANALYTICAL-RECONSTRUCTION | | Strong distributed puissance / weak sovereignty | S16, S18, S21 + synthesis | NEW-CONCEPT | | Power Routing / Power Redirection | S02, S14–S17, S19, S21, S22, S25 + synthesis | NEW-CONCEPT | | Power Sharing / Power Devolution | federation, advisory separation, democratic allocation + synthesis | NEW-CONCEPT | | Narrative self-binding | S02, S19, S21, S22 + synthesis | ANALYTICAL-RECONSTRUCTION | | Protocolization as power sharing | founder decentering + interoperability / reproducibility principles | NEW-CONCEPT | | Ownership decoupling | Koali architect-confirmed design + protocol commons principles | USER-CONFIRMED-DESIGN / synthesis | | Power Surface Map | corpus + domain synthesis | NEW-CONCEPT / presentation + audit layer | | Political / Economic / Monetary separation | S09, S10, S11, S14, S15, S17, S18 + synthesis | ANALYTICAL-RECONSTRUCTION | | Cross-Domain Power Conversion | S10, S14, S15, S18, S26 + synthesis | NEW-CONCEPT / framework refinement | | Breadth × Composition × Closure × Memory × Compounding × Replication × Routing | corpus + Power Dynamics synthesis | NEW-CONCEPT / v6 summary formula | | Academic lineage layer | external literature used for comparison / challenge, not presumed historical influence | EXTERNAL-RESEARCH / NON-ORIGINATING | | Installed-Base Power | standards / network-effects literature + Power Dynamics synthesis | PROPOSED-CONCEPT / external-research-informed | | Interface power | modularity / standards literature + Power Dynamics synthesis | PROPOSED-CONCEPT / external-research-informed | ================================================================================================ FILE: power_dynamics/sources/corpus-map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: aba8e13c36dc5bb2eb34b31ff744fd4774b6b71777bda34d49e2ea34476b347f CONTENT_BYTES: 6276 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Corpus Map" source_basis: --- # Corpus Map The repository uses stable source IDs. Source IDs identify provenance; they do not imply endorsement or current status. | ID | File | Status | Relevance | |---|---|---|---| | S01 | `Abuser l'humanité v5 KDP.pdf` | FOUNDATIONAL | Critique of modern dependency, debt, time capture, procedural opacity, merit, justice and effective freedom. | | S02 | `Hacking Reality_ practical guide for the next Christ_26-05-2026_17_15_42(2).md` | FOUNDATIONAL | Language, narrative, symbols, recognition, alliances, transmission, learning and collective agency. | | S03 | `Bank Management, instructions v3.docx` | EXPLORATORY-LEGACY | Bank-management and financial-institution design proposals. | | S04 | `branding gold, high-value collectibles(1).docx` | EXPLORATORY-LEGACY | Conversion of material value into symbolic, scarcity, narrative and brand value. | | S05 | `Business Plan_ Gold and Precious Metals Trading Business(1).docx` | EXPLORATORY-LEGACY | Precious-metals business, storage, trading and financial-capacity design. | | S06 | `charities through your more efficient system, you can greatly reduce administrative costs.docx` | EXPLORATORY-LEGACY | Early philanthropy, administrative-efficiency and allocation ideas. | | S07 | `Contre l’Abus Financier Systémique _ Le Manifeste Stratégique du Mouvement kOA.docx` | FOUNDATIONAL-ECONOMIC | Financial abuse, dependency, redistribution and institutional redesign. | | S08 | `Copie de Abus financier, inégalité.docx` | FOUNDATIONAL-ECONOMIC | Inequality, access, invention, entrepreneurship and economic dependency. | | S09 | `Debt management using King Koin as a stable reserve during currency oscillations, technical mechanisms.docx` | LEGACY-PROPOSAL | King Koin reserve/debt-management mechanisms. | | S10 | `Desjardins_ Projet complet de transformation coopérative.docx` | EXPERIMENTAL-PROPOSAL | Member governance, allocation, identity, certification and cooperative financial infrastructure. | | S11 | `Economic method.docx` | LEGACY-PROPOSAL | Global redistribution, KingCoin, automated enforcement, sanctions and public investment. | | S12 | `Outline redistib richesses et territoires.docx` | LEGACY-PROPOSAL | Redistribution of wealth, territory, migration and international sharing. | | S13 | `kOA Digital Ecosystem — Connaître, choisir, agir, se souvenir(20260902-205259).md` | CURRENT-CORE | Know → Choose → Act → Remember; controlled transformations and collective capability. | | S14 | `Zero-Skim Philanthropy Blueprint(20260902-205251).md` | CURRENT-EXPERIMENTAL | Cooperative donation rail, one-member-one-vote allocation, auditability and structural leakage reduction. | | S15 | `SmartVote _ un « like » de niveau gouvernance qui fait émerger les meilleurs contenus dans Konnaxion(20260902-205251).md` | CURRENT-EXPERIMENTAL | Discoverability as governance; raw and weighted readings; domain-bounded expertise. | | S16 | `Semantic Sovereignty and Non-Domination_ Toward an Offline, Governable Knowledge Infrastructure.docx(20260902-205250).md` | CURRENT-CORE | Non-domination, semantic sovereignty, offline operation, auditability, determinism and multilinguality. | | S17 | `Democracy with Informed Advice_ A Merit-Based, Ethics-Governed Parallel Channel(20260902-205251).md` | CURRENT-EXPERIMENTAL | Parallel advisory channel: expertise informs without replacing political equality. | | S18 | `L’intelligence collective comme nouveau pôle du pouvoir V3 (Roussin)(20260902-205250).md` | CURRENT-CORE | Collective intelligence as infrastructural power; mediation, visibility, credibility, execution and memory. | | S19 | `Jourdain_Toward_a_Governable_Civic_Infrastructure_Thesis_Draft_March_2026 (Benkler)(20260902-205251).md` | CURRENT-ANALYTICAL | Governable civic infrastructure, semantic sovereignty, bounded expertise, recourse and soft-technocracy risks. | | S20 | `Francois_Jourdain_Governable_Civic_Infrastructure_Thesis_Draft_March_2026(Beth)(20260902-205252).md` | CURRENT-ANALYTICAL | Public capacity, civic infrastructure, pilot criteria and institutional governability. | | S21 | `COLLECTIVE INTELLIGENCE AS DEMOCRATIC GOVERNANCE INFRASTRUCTURE(Fung)(20260902-205251).md` | CURRENT-ANALYTICAL | Power, legitimacy, non-domination, execution, memory and advisory safeguards. | | S22 | `Francois_Jourdain_Thesis_Draft_Forming_Publics_Governing_Meaning_March_2026(Marres)(20260902-205251).md` | CURRENT-ANALYTICAL | Meaning, classification, mediation, publics, narrative self-limitation and semantic power. | | S23 | `Rapport sur l'Empire de Réjean McCormick(20260902-205251).md` | EXTERNAL-ANALYTICAL | External-style synthesis of the project's institutional, symbolic and political ambitions; not canonical by itself. | | S24 | `L’ampleur réelle _ pas un projet, mais une architecture du monde social(20260902-205251).md` | ANALYTICAL-RECONSTRUCTION | Macro map of kOA as socio-technical, symbolic and institutional architecture. | | S25 | `kOA_ A Governable Knowledge-to-Action Ecosystem for the Commons(20260902-205251).md` | CURRENT-CORE | Commons-facing account of kOA, collective capability, portability, auditability and non-enclosure. | | S26 | `Analyse Stratégique et Socio-Technique _ La Mutation de la Vérité et le Capital Épistémique(20260902-205251).md` | ANALYTICAL-RECONSTRUCTION | Epistemic capital, compounding collective capacity, EkoH and SmartVote. | | S27 | `A Technosocial Architecture for Knowledge-to-Action.docx(20260902-205258).md` | CURRENT-ANALYTICAL | Integrated knowledge-to-action architecture, open knowledge, validation, collaboration and governance. | | S28 | `FINAL Domain-Bounded Collective Intelligence_ Merit, Safety, and Scale(5).md` | CURRENT-EXPERIMENTAL | Domain-bounded expertise weighting, evidence, time decay, ethics multipliers, audit and human oversight. | | S29 | `sources/propagation-design-notes.md` | CURRENT-DESIGN-NOTES | Architect-confirmed propagation mechanisms: cross-branch returns, Worlds, cinematic demonstrations, machine-readable documentation, multilingual scale, cultural diffusion, pre-exposure discipline, founder optionality, and movement self-use. | ================================================================================================ FILE: power_dynamics/sources/epistemic-rules.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 5996d25b1b9a2a16439ca79d252937c7cd02f50191958e5554cf2725cb537a95 CONTENT_BYTES: 1330 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Epistemic Rules for the Repository" source_basis: --- # Epistemic Rules for the Repository 1. Preserve source terminology when summarizing a source. 2. Label reconstructions and new concepts explicitly. 3. Do not silently convert legacy proposals into current principles. 4. Preserve disagreements among current documents. 5. Treat technical claims about current implementation as provisional unless supported by direct specifications or code. 6. Avoid treating analytical thesis drafts as canonical technical specifications. 7. Do not infer perfect measurement of competence, ethics, credibility, legitimacy, or truth from the presence of a scoring mechanism. 8. Use source IDs for provenance and technical evidence for implementation claims. ## Architect-confirmed design notes `USER-CONFIRMED-DESIGN` may be used for a current design intention explicitly confirmed by the project architect in the working process but not yet supported by a canonical source document or technical specification. Rules: - do not present it as source-derived; - identify missing technical evidence; - replace or supplement it with canonical documentation when available; - distinguish design intention from deployed implementation. ================================================================================================ FILE: power_dynamics/sources/propagation-design-notes.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: a9bbe85f3df1f51870ab1d2562f7da4939e19f68be3b30ea9c83b3db429dcd6b CONTENT_BYTES: 4892 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "USER-CONFIRMED-DESIGN" scope: "kOA" version: "6.3" title: "Propagation Design Notes — 2026-09-21" source_basis: --- # Propagation Design Notes — 2026-09-21 This source records current architect-confirmed mechanisms relevant to propagation and adoption that are not all fully represented in the earlier supplied source corpus. It records **current capability claims and design intention**, not independent validation of scale or effectiveness. ## Cross-branch returns Current intention: > Successful branches should be able to return money, credibility, evidence, code, methods, relationships, operators, or other reusable assets to shared infrastructure and other branches. A branch may therefore finance or de-risk another branch without requiring all branches to share the same business model. ## Tools that build tools Current reported practice: > AI-assisted development methods and internal development / diagnostic / deployment tooling are used to increase the speed and quality with which additional kOA tooling can be built. Evidence needed for external claims: - comparable effort measurements; - repeatability by non-founder operators; - regression / quality metrics; - documented automation reuse across repositories. ## Worlds Current reported capability: > Konnaxion can be seeded with structured simulated or reconstructed Worlds derived from public sources, allowing a demonstration environment to begin with realistic actors, questions, positions, sources, and relationships rather than an empty platform. Required epistemic distinction: ```text source material ≠ reconstruction ≠ simulation ≠ live contribution ``` A World demonstrates representational and demonstration capacity. It does not by itself prove adoption or real-world impact. ## Cinematic demonstration pipeline Current reported capability: > A cinematic demonstration engine, combined with interface tooling and browser automation, can generate repeatable high-quality product demonstrations from scripted tours. Propagation hypothesis: > Lowering the marginal cost of contextual demonstrations can lower the explanation barrier for new audiences. Evidence needed: - production time per demonstration; - viewer → evaluator conversion; - evaluator → pilot conversion; - repeatability across languages / countries / domains. ## Machine-readable documentation Current reported practice / intention: > Documentation is increasingly optimized for AI-assisted reading through structured Markdown, indexes, context packs, and `llms.txt`-style concise machine entry surfaces. Propagation hypothesis: > If external reviewers can use their own AI systems to navigate the corpus, due-diligence and explanation costs may fall. ## Multilingual scale Current reported milestone: > A complete Albanian implementation has been produced in a Grammatical Framework-oriented language architecture, strengthening the plausibility of systematic expansion toward much broader language coverage. The 300-language target remains a scale objective, not a claim of current equal-quality support. Recommended evidence model: - language conformance tiers; - compile / grammar tests; - gold corpus metrics; - native-speaker review; - human hours and AI-assisted hours; - coverage across language families and scripts. ## Cultural and narrative diffusion Current assets include multiple books, albums, podcasts, web material, essays, and narrative surfaces intended to explain complex architecture through different cognitive entry modes. These assets should remain optional to operational adoption. `Narrative usefulness ≠ factual authority.` ## Pre-exposure / outreach Current strategy includes earlier outreach to people and institutions in several sectors before later deployment phases. Epistemic rule: `contacted ≠ received ≠ read ≠ familiar ≠ supportive ≠ partner` The only defensible propagation claim without stronger evidence is that prior contact can create a possibility of later recognition. ## Founder exposure and pseudonymity Current practice uses a public architect identity and a separate narrative persona / pseudonym. The persona can provide creative and exposure optionality. It must not be treated as the reason the system is resilient. System resilience depends on independent reproducibility, distributed mastery, public artifacts, explicit authority, branchability, and continuity during founder absence. ## Movement self-use Current design intention: > When multiple independent participants exist, the kOA initiative can use kOA tooling to coordinate parts of its own work, allowing the movement / community to become a real operational test environment. The relevant threshold is not a branding declaration that a “movement” exists. It is evidence of multi-actor independent capability. ================================================================================================ FILE: power_dynamics/sources/README.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: 201f82c96bf093f036c5fe3d1c6c169333099ad57745e67e3a51a3aaa32acea0 CONTENT_BYTES: 694 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Sources and Provenance" source_basis: --- # Sources and Provenance The supplied corpus is the repository's primary evidence base. Source IDs are stable references to the 28 supplied files. They identify provenance, not endorsement or current status. The repo distinguishes: - **FOUNDATIONAL / CURRENT-CORE** source material; - **CURRENT-EXPERIMENTAL** designs; - **ANALYTICAL** thesis drafts and reconstructions; - **LEGACY-PROPOSAL** material preserved for genealogy and stress testing. The source corpus contains real internal tensions. These should not be silently reconciled. ================================================================================================ FILE: power_dynamics/sources/source-status.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: b23eac9463b2ad1aaea717986127110ca02978e5aa4367916e8fe0b5e7427b38 CONTENT_BYTES: 804 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Source Status" source_basis: --- # Source Status `CURRENT-CORE` and `CURRENT-EXPERIMENTAL` describe recent design direction. `CURRENT-DESIGN-NOTES` records architect-confirmed current mechanisms or intentions that still require independent technical or adoption evidence. `LEGACY-PROPOSAL` identifies earlier proposals retained for historical and stress-test value. `ANALYTICAL-RECONSTRUCTION` identifies synthesis rather than primary architecture. Status is not truth ranking. A legacy proposal can still expose a useful mechanism, and a recent analytical document is not automatically a canonical technical specification. See [`corpus-map.md`](corpus-map.md) for per-source classification. ================================================================================================ FILE: power_dynamics/sources/technical-evidence-map.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: eee327112e5ff10c27eb4d204670b31e83f14b2994cd4148f3d5e56566da2b9f CONTENT_BYTES: 3056 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.0" title: "Technical Evidence Map" source_basis: - S13 - S15 - S16 - S18 - S21 - S25 --- # Technical Evidence Map The 28-file corpus is strong on philosophy, architecture summaries, institutional proposals, and analytical reconstructions. A rigorous next-stage audit should add direct technical specifications for the exact loci where **capacity becomes puissance and puissance becomes relational power**. ## Highest-priority evidence to import 1. **Civilizational Coherence — power/capture chapters**: capture, lock-in, verification, contestation, substitution, exit. 2. **kOA Digital Ecosystem Layer Model / Layer 0**: separation of functions and mandate boundaries. 3. **Kristal authority registry, trust roots, reader policies, federation/versioning**: epistemic puissance, authority, branch lineage. 4. **EkoH ScoreConfiguration, ScoreHistory, visibility/access policies**: who defines credibility readings and how those readings affect opportunity. 5. **SmartVote lens registry, defaults, raw/weighted storage, version governance**: decision puissance, discoverability, advisory power. 6. **Orgo RBAC, routing, escalation, closure, override rules**: operational puissance and execution power. 7. **Konnaxion moderation, discovery, identity, ranking policies**: collective puissance, attention, agenda power. 8. **Capsule Manager signing, registry, update, rollback, deployment profiles**: deployment puissance, infrastructural dependency, choke points. 9. **Koali distribution specification**: credibility portability, alternative distributions, interoperability. 10. **Brand / trademark governance and founder-control inventory**: symbolic assets, domains, repos, release keys, registries, marks, current relational control. ## Audit rule A normative statement such as “EkoH is non-sovereign” is not sufficient technical evidence. The audit must identify the configuration, permission, key, role, registry, default, or protocol boundary that explains: 1. what resource and potential exist; 2. what becomes usable capacity; 3. what becomes effective puissance; 4. where that puissance creates relational power; 5. which counterpowers constrain that relation. ## Mobilization / mediation evidence Also inspect release permissions, publication gates, queueing, rate limits, ranking, recommendation, translation, summarization, distribution dependencies, analytics feedback, alternative channels, moderation controls, update keys, and bottlenecks. ## Koali protocolization / ownership-decoupling evidence To validate the current design intention that Koali be duplicable, shareable, branchable, and plural, collect: - common-kernel / protocol specification; - distribution identity and versioning; - evidence / history portability; - policy interchange contracts; - alternative distribution discovery; - fork / branch procedure; - registry and signing governance; - trademark / brand separation from protocol implementation. ================================================================================================ FILE: power_dynamics/STATUS.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: c944106b9870c900b46757d4ac267f5557db0bd0216c5d14c0de49d4947e065a CONTENT_BYTES: 5798 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Repository Status" source_basis: - S01 - S02 - S13 - S14 - S15 - S16 - S18 - S21 - S25 --- # Repository Status Version 6.3 retains the **kOA Power Show** and cross-domain Power Surface while strengthening adversarial resilience around founder authority, epistemic credibility, and plural Kristal branches. ## Presentation architecture > **Why kOA is powerful → Power Surface → Composition → Closure → Compounding → Propagation → Cross-Domain Conversion → Power Routing → Constitution → Evolution** The analytical engine remains: > **ontology × dynamics × domains** ## Major v6.3 changes - added `PROPAGATION.md` as the canonical map for propagation and coupled feedback loops; - formally separated **compounding** from **propagation**; - added `propagation/` with adoption barriers, coupled loops, cross-branch returns, distribution surfaces, founder-absence tests, damping, metrics, and a kOA loop catalog; - added `dynamics/13-propagation-and-coupled-loops.md`; - added `koa/propagation-adoption.md` and `showcase/15-propagation-engine.md`; - added `assessment/propagation-audit.md`; - added `feedback-loop` and `coupled-loop` schemas; - recorded architect-confirmed propagation tooling / design notes as S29, including Worlds, cinematic demonstrations, machine-readable documentation, multilingual scale, cross-branch returns, movement self-use, and founder exposure optionality; - made the epistemic distinction `contacted ≠ familiar ≠ supportive`, `simulation ≠ evidence`, and `persona optionality ≠ system resilience` explicit; - added the canonical propagation condition: **healthy propagation increases distributed capability faster than terminal dependency**. ## Major v6.2 changes - added `Academic-Lineage/` as a structured external-research layer; - connected relational power and dependency to Dahl, Emerson, Cook et al., and Resource Dependence Theory; - connected federation and institutional structure to Ostrom and the institutional-grammar tradition; - added standards / compatibility failure modes from modularity, network-effects, excess-inertia, and path-dependence research; - connected forkability and founder decentering to exit / voice, open-source governance, and peer-production research; - added network-power, brokerage, social-capital, and cumulative-advantage lineages; - added a dedicated SmartVote / expertise lineage covering domain-specific expertise, calibrated expert judgment, select crowds, diversity, and social-choice impossibility / manipulation results; - added classification, infrastructure, code-as-governance, epistemic injustice, argumentation, belief revision, and cybernetic feedback references; - added collective-action, diffusion, threshold, capability, concerted-power, and legibility lineages; - explicitly distinguished **academic correspondence** from endorsement, historical influence, or implementation validation; - proposed **Installed-Base Power** and **interface power** as explicit audit targets for future framework integration. ### Retained v6.1 adversarial-resilience additions - added founder opposition as a distinct resilience test beyond founder absence; - introduced **rehearsed counterpower**: practiced opposition pathways can be stronger than merely formal rights; - added a founder-backed civic fire-drill case and reusable **Tattoo Protocol** concept; - added an epistemic authority corruption case using a known-false worldview as a stress test; - distinguished apparent source multiplicity from causal independence; - clarified that Kristal forkability permits incompatible worldviews without implying equal evidentiary support; - added reference-stewardship firewalls: maintained reference ≠ monopoly on truth; - recorded architect-confirmed directions for proposed UNESCO stewardship, worldview forks, and adversarial resilience drills without presenting them as implemented facts. ## Current core - `Resource → Potential → Capacity → Puissance → Power Relation → Effect → Return`; - `Know → Choose → Act → Remember → Know better`; - Breadth × Composition × Closure × Memory × Compounding × Propagation × Replication × Routing; - political power as a pre-political-through-execution chain; - economic puissance and allocation power; - monetary power as rail / issuance / liquidity / settlement / credit power; - cross-domain conversion, stacking, and capture; - Power Conversion Firewalls; - deliberate routing of capability, authority, returns, and optionality; - narrative self-binding; - Koali ownership decoupling as an architect-confirmed direction; - verification, contestation, substitution, and exit; - branch mobility and evolutionary governance; - `Strong distributed puissance. Weak sovereignty.` ## Important maturity distinction KingCoin remains **LEGACY-PROPOSAL** material. It is retained as a monetary and cross-domain power-stacking stress test, not as current kOA constitutional doctrine. Koali plural distributions / ownership decoupling remain **architect-confirmed design direction** until current technical specifications demonstrate the intended kernel, portability, policy identity, branchability, and interoperability. ## Technical evidence still required A concrete current-state power audit still needs direct evidence for authority registries, reader policies, trust roots, scoring configuration, SmartVote defaults/lenses, Orgo RBAC and escalation, Konnaxion ranking/moderation, signing/update keys, deployment registries, brand/trademark governance, domains, maintainer controls, and operational topology. See [`sources/technical-evidence-map.md`](sources/technical-evidence-map.md). ================================================================================================ FILE: power_dynamics/TREE.md AUTHORITY: reference CONTENT_ROLE: knowledge CONTENT_SHA256: eb595d93a25a6fb4e94653359ae16f6a282b5e95aa94ed044d332ed3b32e4b74 CONTENT_BYTES: 8828 ================================================================================================ --- maturity: "CURRENT-CORE" claim_type: "ANALYTICAL-RECONSTRUCTION" scope: "GENERAL" version: "6.3" title: "Repository Tree" --- # Repository Tree The v6.3 reading hierarchy is intentionally different from the filesystem hierarchy: > **Why kOA is powerful → Power Surface → Composition → Compounding → Propagation → Conversion → Routing → Constitution → Evolution → Audit** ```text Power-Dynamics-v6/ ├── .github/ │ ├── ISSUE_TEMPLATE/ │ │ ├── concept-proposal.md │ │ ├── power-audit.md │ │ └── power-surface-audit.md │ └── PULL_REQUEST_TEMPLATE.md ├── Academic-Lineage/ │ ├── 01-power-dependence-and-domination.md │ ├── 02-polycentric-governance-and-institutions.md │ ├── 03-modularity-standards-and-path-dependence.md │ ├── 04-open-source-exit-fork-and-peer-production.md │ ├── 05-network-power-and-social-capital.md │ ├── 06-expertise-smartvote-and-collective-judgment.md │ ├── 07-metrics-reputation-and-gaming.md │ ├── 08-classification-infrastructure-and-code.md │ ├── 09-epistemic-power-provenance-and-plurality.md │ ├── 10-systems-cybernetics-and-adaptation.md │ ├── 11-collective-action-mobilization-and-diffusion.md │ ├── 12-capabilities-concerted-power-and-legibility.md │ ├── BIBLIOGRAPHY.md │ └── README.md ├── assessment/ │ ├── analysis-method.md │ ├── branch-comparison.md │ ├── capability-show-profile.md │ ├── constitutional-tests.md │ ├── dependency-exit-audit.md │ ├── flow-conversion-capture-audit.md │ ├── power-balance-sheet.md │ ├── power-routing-audit.md │ ├── power-surface-audit.md │ ├── propagation-audit.md │ ├── README.md │ ├── system-profile.md │ └── temporal-evolution.md ├── branch-ecology/ │ ├── branch-mobility.md │ ├── complementarity-and-antidogma.md │ ├── improvement-support-dominance.md │ ├── lineage-and-competing-kristals.md │ ├── README.md │ └── recombination-replacement.md ├── cases/ │ ├── ai-hidden-sovereignty.md │ ├── bootstrap-koa.md │ ├── brand-merchandise-affiliation.md │ ├── competing-kristals.md │ ├── desjardins-stacking.md │ ├── epistemic-authority-corruption.md │ ├── ethical-fiction-self-binding.md │ ├── founder-identity-optionality.md │ ├── founder-opposition-rehearsal.md │ ├── kingcoin-legacy-stress-test.md │ ├── media-and-state.md │ ├── README.md │ ├── recognition-loop.md │ ├── smartvote-discoverability.md │ ├── unpublished-corpus-reservoir.md │ └── zero-skim-philanthropy.md ├── constitution/ │ ├── authority-architecture.md │ ├── branch-evolution.md │ ├── conversion-firewalls.md │ ├── counterpowers-and-legibility.md │ ├── federation-subsidiarity.md │ ├── founder-decentering.md │ ├── non-domination-terminality.md │ ├── power-redirection-sharing.md │ ├── README.md │ └── revocability-exit-portability.md ├── domains/ │ ├── 01-political-constitutional.md │ ├── 02-economic-allocation.md │ ├── 03-monetary-credit.md │ ├── 04-epistemic-semantic.md │ ├── 05-information-attention-media.md │ ├── 06-credibility-reputation.md │ ├── 07-network-affiliation.md │ ├── 08-administrative-operational.md │ ├── 09-technical-infrastructural.md │ ├── 10-narrative-symbolic-brand.md │ ├── 11-cognitive-ai.md │ ├── 12-mnemonic-temporal.md │ ├── 13-evolutionary-counterpower.md │ ├── 14-property-territorial.md │ └── README.md ├── dynamics/ │ ├── 01-formation.md │ ├── 02-mobilization.md │ ├── 03-composition-generated-puissance.md │ ├── 04-conversion-and-firewalls.md │ ├── 05-returns-reinvestment-compounding.md │ ├── 06-concentration-stacking-capture.md │ ├── 07-counterpower-contestation-exit.md │ ├── 08-diversification-and-evolution.md │ ├── 09-decay-dissipation-and-loss.md │ ├── 10-transfer-succession-and-inheritance.md │ ├── 11-externalities-and-scale.md │ ├── 12-routing-sharing-and-devolution.md │ ├── 13-propagation-and-coupled-loops.md │ └── README.md ├── framework/ │ ├── 00-field-definition.md │ ├── 01-core-ontology.md │ ├── 02-effective-possibility.md │ ├── 03-three-axis-model.md │ ├── 04-power-ecology.md │ ├── 05-pre-political-chain.md │ ├── 06-stock-capacity-flow-return.md │ ├── 07-imperfection-and-plurality.md │ ├── 08-constitutional-thesis.md │ ├── 09-power-routing-and-sharing.md │ ├── 10-cross-domain-power-conversion.md │ └── README.md ├── history/ │ ├── central-correction-to-nondomination.md │ ├── dependency-to-empowerment.md │ ├── founder-to-protocol.md │ └── README.md ├── koa/ │ ├── ai.md │ ├── brand-narrative.md │ ├── capsules-federation.md │ ├── founder-power.md │ ├── know-choose-act-remember.md │ ├── koali-ekoh.md │ ├── koali-protocolization.md │ ├── konnaxion.md │ ├── kristal.md │ ├── multilingualism.md │ ├── orgo.md │ ├── README.md │ ├── returns-compounding.md │ ├── propagation-adoption.md │ ├── semantik-sentient.md │ ├── smartvote.md │ └── system-map.md ├── propagation/ │ ├── 00-field-definition.md │ ├── 01-coupled-feedback-loops.md │ ├── 02-adoption-stack.md │ ├── 03-cross-branch-returns.md │ ├── 04-distribution-surfaces.md │ ├── 05-autonomy-and-founder-absence.md │ ├── 06-damping-and-runaway-prevention.md │ ├── 07-metrics-and-falsification.md │ ├── 08-koa-loop-catalog.md │ └── README.md ├── puissance/ │ └── README.md ├── relations/ │ └── README.md ├── research/ │ ├── disciplinary-map.md │ ├── literature-roadmap.md │ └── README.md ├── resources/ │ └── README.md ├── schemas/ │ ├── assertion.schema.yaml │ ├── authority-scope.schema.yaml │ ├── branch-comparison.schema.yaml │ ├── branch-lineage.schema.yaml │ ├── capability-show.schema.yaml │ ├── conversion.schema.yaml │ ├── dynamic-event.schema.yaml │ ├── mobilization-flow.schema.yaml │ ├── ontology.schema.yaml │ ├── power-domain.schema.yaml │ ├── power-relation.schema.yaml │ ├── power-return.schema.yaml │ ├── power-routing.schema.yaml │ ├── power-surface.schema.yaml │ ├── feedback-loop.schema.yaml │ ├── coupled-loop.schema.yaml │ └── system-profile.schema.yaml ├── showcase/ │ ├── 00-why-koa-is-immensely-powerful.md │ ├── 01-capability-spectrum.md │ ├── 02-individual-to-federation.md │ ├── 03-composition-engine.md │ ├── 04-compounding-engine.md │ ├── 05-conversion-chains.md │ ├── 06-pre-political-chain.md │ ├── 07-component-power-matrix.md │ ├── 08-governance-after-capability.md │ ├── 09-why-this-is-not-just-software.md │ ├── 10-counterpower-and-optionality.md │ ├── 11-power-routing-and-sharing.md │ ├── 12-cross-domain-power-surface.md │ ├── 13-political-economic-monetary-power.md │ ├── 14-power-conversion-and-routing-map.md │ ├── 15-propagation-engine.md │ └── README.md ├── sources/ │ ├── architect-confirmed-design-notes.md │ ├── concept-origin-map.md │ ├── corpus-map.md │ ├── epistemic-rules.md │ ├── README.md │ ├── source-status.md │ └── technical-evidence-map.md ├── .gitignore ├── CHANGELOG.md ├── CONTRIBUTING.md ├── GLOSSARY.md ├── LICENSE.md ├── POWER-ROUTING.md ├── PROPAGATION.md ├── POWER-SHOW.md ├── POWER-SURFACE.md ├── PRINCIPLES.md ├── README.md ├── STATUS.md └── TREE.md ```