<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jayanth Kumar on Medium]]></title>
        <description><![CDATA[Stories by Jayanth Kumar on Medium]]></description>
        <link>https://medium.com/@jaykmr?source=rss-5c7900bcf0f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*75b3wXN_rz5LUQOSUHObDQ.png</url>
            <title>Stories by Jayanth Kumar on Medium</title>
            <link>https://medium.com/@jaykmr?source=rss-5c7900bcf0f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:11:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jaykmr/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[OME GOD]]></title>
            <link>https://medium.com/technopreneurial-treatises/ome-god-fad099c1cb69?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fad099c1cb69</guid>
            <category><![CDATA[mythology]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[truth]]></category>
            <category><![CDATA[love]]></category>
            <category><![CDATA[religion]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Tue, 09 Dec 2025 07:33:31 GMT</pubDate>
            <atom:updated>2025-12-09T07:33:31.759Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ziQYnBHyXtyVmUSR_1hF1g.png" /></figure><p>⭐️ PROLOGUE</p><p><strong><em>The Four Yugas and the One Story All Religions Tell</em></strong></p><p>Every civilization, every prophet, every scripture — from the hymns of the Ṛig Veda to the laments of the Old Testament, from the songs of the Avesta to the chants of the Nile — whispers the same ancient truth:</p><p><strong>Time does not move like an arrow.<br> It moves like a wheel.</strong></p><p>Hinduism names its spokes <strong>Satya, Treta, Dvapara, Kali</strong> — four Yugas spiraling through creation, decline, darkness, and rebirth.<br> Yet when you look deeply enough, the <strong>same fourfold rhythm</strong> pulses beneath <strong>Christian ages, Greek mythic eras, Islamic prophetic cycles, Buddhist kalpas, Norse epochs</strong>, and even the cosmology of <strong>Zoroaster and Egypt</strong>.</p><p>This is not coincidence.</p><p>This is a <strong>universal human memory</strong>.</p><p>A memory that resurfaced in symbols — Vishnu’s ten avatars, Christ’s four archangels, the Greek Ages of Man, the Jewish and Islamic Ages of Prophets, and the Zoroastrian story of Good and Evil fighting for cosmic time.</p><p>All religions keep trying to say one thing:</p><blockquote><strong><em>The universe breathes in cycles.<br> Every age has its guardian.<br> Every fall has its redeemer.<br> And every darkness awaits a rider of light.</em></strong></blockquote><p>This is that story — spanning all religions — told through the lens of the Yugas.</p><h3>🌕 NARRATIVE</h3><p><em>The Cycle of Ages Across All Religions</em></p><h3>CHAPTER I — The First Age: Satya Yuga</h3><p>The Age When the World Was Young</p><p>Satya Yuga is the <strong>Golden Age</strong>, pristine and unbroken — where dharma stands on four legs, where truth is the only language, where consciousness is whole.</p><p>Every religion remembers a time like this:</p><ul><li><strong>Eden</strong> in Christianity and Judaism</li><li><strong>Firdaws</strong> in Islam</li><li><strong>The Golden Age of Kronos</strong> in Greece</li><li><strong>The reign of Ahura Mazda</strong> in Zoroastrianism</li><li><strong>The First Age of the Norse</strong>, before deceit was born</li></ul><p>Across these traditions, the first age is ruled not by kings but <strong>by purity itself</strong>.</p><p>In Hinduism, Vishnu’s earliest avatars — <strong>Matsya, Kurma, Varaha</strong> — preserve life, uphold the cosmic order, and stabilize the young universe.</p><p>In Christianity, the first age is guarded by <strong>Raphael</strong>, the healer.</p><p>In Islam, it is remembered as the age before corruption touched the earth.</p><p>In Greece, it is when humans “lived like gods, free from sorrow”.</p><p>Humanity begins in light.<br> But the wheel must turn.</p><h3>CHAPTER II — Treta Yuga</h3><p>The Age of Law, Ritual, and Divine Intervention**</p><p>As truth slightly diminishes, the world enters the <strong>Silver Age</strong> — still bright, but cracked with complexity.</p><p>This is the age of:</p><ul><li><strong>Vamana</strong>, who humbles kings</li><li><strong>Parashurama</strong>, who resets corrupted power</li><li><strong>Rama</strong>, the perfect king</li></ul><p>Across other religions, this age manifests as:</p><h3>The Patriarchal Age (Judaism–Christianity–Islam)</h3><p>Abraham, Isaac, Jacob — the founding patriarchs — establish covenants, laws, and rituals.<br> Moses brings commandments.</p><h3>Zoroastrian Second Epoch</h3><p>The battle between truth (Asha) and falsehood (Druj) intensifies.</p><h3>Egypt</h3><p>Maat (cosmic order) becomes something that must be maintained, not simply lived.</p><p>Treta Yuga is not innocence — it is responsibility.</p><p>Humanity begins to shoulder the weight of moral order.</p><h3>CHAPTER III — Dvapara Yuga</h3><p>The Age of Doubt, Heroes, and Knowledge</p><p>Now dharma stands on two legs.<br> The world becomes heavier, more human, more uncertain.</p><p>This is the age of <strong>Krishna</strong>, the cosmic teacher who speaks the Gita in the twilight between divinity and war.</p><p>Across religions:</p><h3>Christianity’s Prophets and Kings</h3><p>David, Solomon, Isaiah — wisdom, songs, doubts, poetry, rebellion.</p><h3>Islam’s Prophetic Line</h3><p>Each prophet arrives in a world increasingly divided.</p><h3>Greek Bronze Age</h3><p>Heroes rise and fall.<br> Knowledge expands.<br> Conflicts darken.</p><h3>Judaism’s Books of Wisdom</h3><p>Job questions suffering.<br> Ecclesiastes questions life itself.</p><p>Dvapara is the age where humanity asks for meaning and receives paradox.</p><p>Divinity becomes philosophical.</p><p>Faith becomes inquiry.</p><h3>CHAPTER IV — Kali Yuga</h3><p>The Age of Iron, Fire, and Forgetting</p><p>The darkest age — yet the most self-aware.</p><p>This age is not purely evil.<br> It is the age where consciousness hits its minimum — which paradoxically makes awakening possible.</p><p>Kali Yuga appears everywhere:</p><h3>Christianity</h3><ul><li>The “Last Days”</li><li>The rise of conflict</li><li>The prophecy of the rider on the white horse</li></ul><h3>Islam</h3><ul><li>The fitna (age of trials)</li><li>The arrival of the <strong>Mahdi</strong></li><li>The return of <strong>Isa</strong></li></ul><h3>Zoroastrianism</h3><ul><li>The age of greatest deceit</li><li>Awaiting <strong>Saoshyant</strong>, the world-renewer</li></ul><h3>Norse Mythology</h3><ul><li>The time before <strong>Ragnarok</strong></li><li>The world-tree shaking</li></ul><h3>Buddhism</h3><ul><li>The age of Dharma-decline, awaiting <strong>Maitreya</strong></li></ul><h3>Hinduism</h3><ul><li>The age of industrial noise, forgotten rituals, inward corruption</li><li>Awaiting <strong>Kalki</strong>, the avatar who restores dharma</li></ul><p>Every tradition speaks of an impending renewal — a final avatar, messiah, savior, or rider who breaks the cycle of decay.</p><p>Darkness brings longing.<br> Longing brings awakening.<br> Awakening brings rebirth.</p><p>Thus the wheel turns.</p><h3>CHAPTER V — Ten Avatars Across All Religions</h3><p>When Deities Wear Different Names**</p><p>The <strong>Dashavatara</strong> is not uniquely Hindu — it is the Indian expression of a global archetype.</p><h3>Matsya ↔ Noah / Nuh / Utnapishtim</h3><p>The flood hero appears everywhere.</p><h3>Kurma ↔ Atlas / Shu</h3><p>The cosmic supporter.</p><h3>Varaha ↔ Marduk / St. Michael</h3><p>Order defeating chaos.</p><h3>Narasimha ↔ Angel of the Lord / Khidr</h3><p>Justice that manifests beyond rules.</p><h3>Vamana ↔ Christ’s Parable of Meekness</h3><p>Smallness containing infinity.</p><h3>Parashurama ↔ Moses</h3><p>Righteous destruction to restore law.</p><h3>Rama ↔ Solomon / Apollo</h3><p>The archetype of the just king.</p><h3>Krishna ↔ Christ / Dionysus / Hermes</h3><p>Divine love, cosmic play, philosophical clarity.</p><h3>Buddha ↔ Jesus the Reformer / Isa / Maitreya</h3><p>Compassion reshaping tradition.</p><h3>Kalki ↔ Messiah / Mahdi / Saoshyant / Baldr</h3><p>The world-renewer on a white horse.</p><p>All religions arrive at the same figure:<br> <strong>the final rider who ends the dark age.</strong></p><h3>CHAPTER VI — Shiva: Time and Shakti: Space</h3><p>The Cosmic Unity We Forgot</p><p>While Vishnu governs the flow of incarnations, <strong>Shiva stands behind the cycle itself</strong>.</p><p>Shiva is <strong>Mahākāla</strong> — Time.<br> Shakti is <strong>Prakṛti</strong> — Space.</p><p>In Greek myth, these appear as:</p><ul><li><strong>Kronos</strong> — devouring time</li><li><strong>Gaia</strong> — the womb of worlds</li></ul><p>In Hinduism they merge as:</p><h3>Ardhanārīśvara</h3><p>Half Shiva, half Shakti.<br> Half Time, half Space.<br> A single reality with two faces.</p><p>The universe is born when <strong>Time moves through Space</strong>.<br> And dissolves when <strong>Time consumes Space back into silence</strong>.</p><p>Every religion echoes this nondual truth in its own way — the union of opposites, the marriage of heaven and earth, yin and yang, spirit and matter.</p><p><strong>Ardhanārīśvara</strong> is the hidden equation beneath all mythologies.</p><h3>⭐️ EPILOGUE</h3><p><em>The One Story Beneath Every Scripture</em></p><p>When the names are removed — when Vishnu, Christ, Muhammad, Zoroaster, Abraham, Buddha, and the Greek poets step aside — the pattern remains.</p><p>A pattern older than temples.<br> Older than languages.<br> Older than writing.</p><p><strong>Creation<br> Decline<br> Forgetfulness<br> Renewal</strong></p><p>The Yugas are not just Hindu cosmology.<br> They are the blueprint of human consciousness.</p><p>Every religion remembered a piece of the puzzle.<br> Hinduism preserved the cycle.<br> Abrahamic traditions preserved the prophets.<br> Greek myth preserved the psychology.<br> Zoroastrianism preserved the ethical battle.<br> Buddhism preserved the meditative mapping.</p><p>Put together, they form a single revelation:</p><blockquote><strong><em>There is only one story.<br> Humanity keeps telling it in different tongues.<br> And time — sacred, circular, eternal time — keeps turning its luminous wheel.</em></strong></blockquote><blockquote><strong><em>Time</em></strong><br> Time is beauty. <br> Beauty is divine. (सत्यम शिवम् सुंदरम् ) <br> Flowing cyकाल <br><strong><em>Cycle</em></strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fad099c1cb69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/technopreneurial-treatises/ome-god-fad099c1cb69">OME GOD</a> was originally published in <a href="https://medium.com/technopreneurial-treatises">Technopreneurial Treatises</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evolution of Research: From Foundations to Frontier]]></title>
            <link>https://medium.com/technopreneurial-treatises/evolution-of-research-from-foundations-to-frontier-54526cb73d2a?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/54526cb73d2a</guid>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[naturallanguageprocessing]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[academia]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Thu, 30 Oct 2025 12:41:06 GMT</pubDate>
            <atom:updated>2025-10-30T13:04:22.956Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*0HkRsGkD8sUHZb33Eca-5A.png" /></figure><h3>In Memory of Pushpak Bhattacharyya, Computation For Indian Language Technology (CFILT) Lab, CSE at IIT Bombay and Indian Institute of Technology, Patna</h3><h3>Prologue</h3><p>Every discipline carries within it an invisible tapestry — threads woven from questions posed, methods tested, insights harvested, and new frontiers charted. In natural language processing (NLP), the culture of inquiry grows like roots and branches, nurtured by each generation of scholars, then passed on. These traditions become the unspoken curriculum, the scaffolding behind breakthroughs years later. If we liken this to a silent transmission — like Bodhidharma’s oral transmission of the Vedas — then one of these foundational threads is the study of opinion summarization.</p><p>Opinion summarization is more than summarising text: it is distilling <em>sentiment</em>, <em>aspect</em>, <em>voice</em> — the kaleidoscope of human evaluation. The journey from modelling to evaluation to generative systems in this domain offers a textbook of how academic research evolves: from fundamental theory, to critique, to benchmark, to next-gen system. This article traces one such chain — and in doing so I honour Prof. Pushpak Bhattacharyya, whose work anchors the foundation of this chain.</p><h3>The Journey of an Idea</h3><h3>1. Foundations (2015)</h3><p>In 2015, the paper Monotone Submodularity in Opinion Summaries (Jayanth Jayanth, Jayaprakash Sundararaj &amp; Pushpak Bhattacharyya) laid a rigorous foundation: summarizing opinions is not simply picking frequent phrases — it is a problem of <em>coverage</em>, <em>redundancy</em>, and <em>sentiment intensity</em>. They framed it as a monotone submodular optimisation problem: adding sentences increases subjectivity (monotonicity) but the benefit per additional sentence diminishes (diminishing returns). <a href="https://www.cse.iitb.ac.in/~pb/papers/emnlp15-submodular-sa.pdf">CSE IIT Bombay Paper in EMNLP</a> This work put the lens of optimisation theory onto opinion summarisation, setting a formal bedrock.</p><h3>2. Critical Evaluation (2019)</h3><p>Fast-forward to 2019: the paper Red‑faced ROUGE: Examining the Suitability of ROUGE for Opinion Summary Evaluation (Tay W; Joshi A; Zhang X; Karimi S; Wan S) challenged one of the core tools of summarisation research: ROUGE. They showed that for opinion summaries — where <em>what is said</em> (aspect) and <em>how it is said</em> (polarity) matter — ROUGE’s overlap-based scoring fails to distinguish correct versus opposite sentiment. <a href="https://aclanthology.org/U19-1008/">ACL Anthology Paper</a> This was an inflection point: the evaluation metric, not just the method, required scrutinising.</p><h3>3. Benchmarking Evaluation (2023)</h3><p>In 2023, the work OpinSummEval: Revisiting Automated Evaluation for Opinion Summarization (Shen Z &amp; Wan S) picked up the mantle of evaluation. They built datasets and metrics aligned with human judgement for opinion summarisation — implicitly motivated by the 2019 critique of ROUGE. <a href="https://arxiv.org/pdf/2310.18122">arXiv Paper</a> Thus the academic attention shifted from “how do we build summaries?” to “how do we evaluate them correctly?”</p><h3>4. System-level Innovation (2025)</h3><p>Finally, the 2025 paper LLMs as Architects and Critics for Multi‑Source Opinion Summarization (Attri A; Attri A; Bhattacharyya P; Banerjee S; Patil A; Chelliah M; Garera N) synthesises the prior threads into a next-generation system: multi-source input (reviews + metadata + QA) and large language models (LLMs) as both architects (generators) and critics (evaluators). The paper cites the 2023 evaluation benchmark explicitly and builds upon the evaluation concerns raised earlier. This brings the research arc full circle: modelling → evaluation critique → benchmark → system innovation.</p><h3>Directed Acyclic Graph (DAG) of the Research Chain</h3><pre>[2015: Monotone Submodularity in Opinion Summaries]<br>        ↑<br>        │ (influence and citation)<br>[2019: Red-faced ROUGE]<br>        ↑<br>        │ (evaluation benchmark build)<br>[2023: OpinSummEval]<br>        ↑<br>        │ (cited by &amp; extended in system paper)<br>[2025: LLMs as Architects &amp; Critics]</pre><p>Graphviz representation</p><pre>digraph Evolution {<br>  node [shape=box];<br>  P2015 [label=&quot;2015 – Jayanth et al.\nMonotone Submodularity&quot;];<br>  P2019 [label=&quot;2019 – Tay et al.\nRed-faced ROUGE&quot;];<br>  P2023 [label=&quot;2023 – Shen &amp; Wan\nOpinSummEval&quot;];<br>  P2025 [label=&quot;2025 – Attri et al.\nLLMs as Architects &amp; Critics&quot;];<br>  P2019 -&gt; P2015;<br>  P2023 -&gt; P2019;<br>  P2025 -&gt; P2023;<br>}</pre><h3>Table of Key Contributions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sQpM1u2alsAGdqon" /></figure><h3>Reflection: The Lifecycle of Contribution</h3><ol><li>Vision &amp; Formalisation — The 2015 paper gave us a rigorous lens.</li><li>Scrutiny &amp; Weaknesses — The 2019 paper exposed the weak link in evaluation metrics.</li><li>Infrastructure &amp; Benchmarking — The 2023 work built the tools needed to measure progress correctly.</li><li>Integration &amp; Scale — The 2025 work delivered the system that synthesises earlier theory, metrics, and technology into a modern paradigm.</li></ol><p>This is how research advances: each stage feeds the next. Foundational ideas enable critique; critique drives benchmarking; benchmarking supports system innovation.</p><h3>In Memory of Prof. Pushpak Bhattacharyya</h3><p>Prof. Bhattacharyya’s work with <a href="https://www.linkedin.com/article/edit/7389637384138649600/#">Jayanth K.</a> in <a href="https://www.linkedin.com/article/edit/7389637384138649600/#">Computation For Indian Language Technology (CFILT) Lab</a> , especially his contribution to the 2015 paper, holds a central place in this journey. His insights into opinion summarisation modelling continue to ripple through the field. This article stands as a tribute to his legacy — thank you for shaping the path of advance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zkBZKwJJMNOu5kvBpzwymA.png" /></figure><h3>Epilogue</h3><p>In the end, research is not just the publication of papers — it’s the weaving of ideas across time, the lifting of standards, the challenging of assumptions, the building of new systems. The chain we charted — 2015 through 2025 — is but one example of many. But for us, it is instructive: build on sound theory, be ready to critique the foundations, create robust measurement, then dare to build at system scale. That is the path to meaningful progress.</p><p>“May we all stand on the shoulders of past giants, reach further, and leave a foundation for future ones.” — <a href="https://www.linkedin.com/article/edit/7389637384138649600/#">Jayanth K.</a></p><h3>References</h3><ol><li><a href="https://www.linkedin.com/article/edit/7389637384138649600/#">Jayanth K.</a> , <a href="https://www.linkedin.com/article/edit/7389637384138649600/#">Jayaprakash Sundararaj</a> , &amp; <a href="https://www.linkedin.com/article/edit/7389637384138649600/#">Pushpak Bhattacharyya</a> (2015). <em>Monotone Submodularity in Opinion Summaries</em>. In Proceedings of EMNLP 2015, 169–178. DOI:10.18653/v1/D15–1017. <a href="https://www.cse.iitb.ac.in/~pb/papers/emnlp15-submodular-sa.pdf">CSE IIT Bombay Paper in EMNLP</a></li><li>Tay, W., <a href="https://www.linkedin.com/article/edit/7389637384138649600/#">Aditya Joshi</a> , Zhang, X., Karimi, S., &amp; Wan, S. (2019). <em>Red-faced ROUGE: Examining the Suitability of ROUGE for Opinion Summary Evaluation</em>. In Proceedings of ALTA 2019, 52–60. <a href="https://aclanthology.org/U19-1008/">ACL Anthology Paper</a></li><li>Shen, Z., &amp; Wan, S. (2023). <em>OpinSummEval: Revisiting Automated Evaluation for Opinion Summarization</em>. arXiv:2310.18122. <a href="https://arxiv.org/pdf/2310.18122">arXiv Paper</a></li><li>Attri, A., Attri, A., Bhattacharyya, P., Banerjee, S., Patil, A., Chelliah, M., &amp; Garera, N. (2025). <em>LLMs as Architects and Critics for Multi-Source Opinion Summarization</em>. arXiv:2507.04751. <a href="https://arxiv.org/abs/2507.04751">arXiv Paper</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54526cb73d2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/technopreneurial-treatises/evolution-of-research-from-foundations-to-frontier-54526cb73d2a">Evolution of Research: From Foundations to Frontier</a> was originally published in <a href="https://medium.com/technopreneurial-treatises">Technopreneurial Treatises</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ The Arc Reactor Within: How the Shivling Mirrors the Shape of the Cosmos]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Fusion. Consciousness&#x200A;&#x2014;&#x200A;Creation.</p><p class="medium-feed-link"><a href="https://medium.com/technopreneurial-treatises/the-arc-reactor-within-how-the-shivling-mirrors-the-shape-of-the-cosmos-4bbb6c9491d4?source=rss-5c7900bcf0f------2">Continue reading on Technopreneurial Treatises »</a></p></div>]]></description>
            <link>https://medium.com/technopreneurial-treatises/the-arc-reactor-within-how-the-shivling-mirrors-the-shape-of-the-cosmos-4bbb6c9491d4?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bbb6c9491d4</guid>
            <category><![CDATA[energy]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 19:21:49 GMT</pubDate>
            <atom:updated>2025-10-15T19:21:49.301Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ The Cure Is Reflection: When Life Remembers Itself]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Reflection and Refraction&#x200A;&#x2014;&#x200A;Dual Manifestation</p><p class="medium-feed-link"><a href="https://medium.com/technopreneurial-treatises/the-cure-is-reflection-when-life-remembers-itself-5aa9a37bb7c5?source=rss-5c7900bcf0f------2">Continue reading on Technopreneurial Treatises »</a></p></div>]]></description>
            <link>https://medium.com/technopreneurial-treatises/the-cure-is-reflection-when-life-remembers-itself-5aa9a37bb7c5?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5aa9a37bb7c5</guid>
            <category><![CDATA[medicine]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 19:19:32 GMT</pubDate>
            <atom:updated>2025-10-15T19:19:32.242Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ Neural Node Theory: The Tree That Awakes]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Duality of Neurons and Nodes</p><p class="medium-feed-link"><a href="https://medium.com/technopreneurial-treatises/neural-node-theory-the-tree-that-awakes-e07fe9819c48?source=rss-5c7900bcf0f------2">Continue reading on Technopreneurial Treatises »</a></p></div>]]></description>
            <link>https://medium.com/technopreneurial-treatises/neural-node-theory-the-tree-that-awakes-e07fe9819c48?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e07fe9819c48</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 19:07:25 GMT</pubDate>
            <atom:updated>2025-10-15T19:07:25.655Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A Pendulum Swung Too Far — Again]]></title>
            <link>https://medium.com/technopreneurial-treatises/a-pendulum-swung-too-far-again-7d98af7f8236?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d98af7f8236</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[future-technology]]></category>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[agi]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Fri, 24 Jan 2025 16:31:44 GMT</pubDate>
            <atom:updated>2025-01-24T17:40:51.702Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Pendulum Swung Too Far — Again: Reflections on AGI and the Cycles of Progress</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g_rYLmwF7fzAvDbiG_zfaQ.png" /></figure><h3>Prologue</h3><p>In the unending quest to build intelligent systems, we find ourselves at a crossroads once again. The march toward Artificial General Intelligence (AGI) is dazzling, relentless, and, at times, utterly blinding. For every breakthrough, there is an unspoken undercurrent: Have we swung too far — again?</p><h3>Swing of the Pendulum</h3><p>Progress, like a pendulum, oscillates. It does not move in a straight line. It sweeps from one extreme to another, dragging entire fields of inquiry with it. In Kenneth Church’s brilliant paper,<em> </em><a href="https://languagelog.ldc.upenn.edu/myl/ldc/swung-too-far.pdf"><em>“A Pendulum Swung Too Far,”</em></a> he chronicles this very phenomenon in the evolution of computational linguistics. Rationalism gave way to Empiricism, theoretical rigor bowed to data-driven pragmatism, and somewhere along the way, the pendulum reached its apex.</p><p>Today, in the AGI revolution, we see the pendulum swinging with similar ferocity. Scaling dominates our collective psyche. Compute, data, and parameter counts — these are the new gods of progress. We marvel at their power, but do we pause long enough to ask: What are we leaving behind in their shadow?</p><h3>History as a Mirror</h3><p>In the 1990s, for example, empiricism surged because we suddenly had access to unprecedented amounts of data. Researchers pragmatically tackled simpler, solvable tasks like part-of-speech tagging instead of obsessing over AI-complete problems. But as Church highlights, this pragmatism has its limits. Many of these methods (like n-grams and finite-state systems) work well for short-distance dependencies but fail to capture the big picture — long-distance dependencies and deeper linguistic insights.</p><p>Church reminds us that in the 1990s, the rise of empiricism was a necessary corrective. Data had become abundant, and researchers, reeling from the overpromises of earlier decades, turned to pragmatic, solvable problems. But in the heady rush to harness data, foundational questions — those dealing with long-distance dependencies and the nature of meaning itself — were left by the wayside.</p><p>Empiricism’s triumphs were real but limited. Methods like n-grams and finite-state systems delivered results, but they could not grasp the deeper, more intricate fabric of language. It was only later, when the pendulum began to swing back, that the field reconnected with these deeper truths.</p><p>And now, AGI finds itself at a similar inflection point. Scaling — massive models, billions of parameters, unfathomable compute — has delivered stunning results. But let us not mistake these results for true intelligence. Let us not forget that scaling, like empiricism before it, is a means, not an end.</p><blockquote><em>Often breakthroughs come from revisiting the so-called “limitations.”</em></blockquote><h3>The Illusion of Progress</h3><p>Here lies the bitter truth: the systems we celebrate today — transformers, large language models — excel at optimization but falter at understanding. They are pattern matchers, not philosophers. They mimic intelligence but do not embody it.</p><p>Church’s pendulum teaches us that this is not failure; it is inevitability. Progress is cyclical. The limitations we ignore today will become the fertile ground of tomorrow’s breakthroughs. The deeper truths of AGI — reasoning, causality, adaptability — are waiting to be rediscovered, just as syntax and semantics waited in the shadows during the empirical rush of the 1990s.</p><blockquote><em>Scaling will plateau. It always does.</em></blockquote><p>And when it does, we will be forced to confront the questions we have deferred:</p><ul><li>What does it mean to reason?</li><li>How do systems adapt to the unknown?</li><li>Can intelligence exist without understanding?</li></ul><h3>The Duality of AGI: Scale vs. Depth</h3><p>If there is a lesson here, it is this:</p><blockquote><em>Progress requires duality.</em></blockquote><p>Scaling and depth, pragmatism and philosophy, engineering and science — these are not opposites. They are partners, two sides of the same coin. To swing too far toward one at the expense of the other is to court stagnation.</p><p>The AGI revolution will not be won by scaling alone. The next great leap will come from harmonizing brute computational power with the subtlety of human-centric design. It will come from systems that do not just predict but understand, that do not just scale but adapt.</p><h3>A Manifesto for Balance</h3><p>To those working at the edge of AGI, here is the manifesto:</p><ol><li><strong>Revisit the Forgotten</strong>: The past holds treasures. Concepts dismissed as too narrow or outdated often contain the seeds of innovation. Look back to move forward.</li><li><strong>Scale with Purpose</strong>: Scaling is a tool, not a destination. Use it to explore deeper questions, not as an end in itself.</li><li><strong>Celebrate the Specific</strong>: Task-specific insights are not limitations; they are foundations. The leap to generality begins with mastery of the particular.</li><li><strong>Bridge the Divide</strong>: Refuse to choose between pragmatism and philosophy. Build systems that honor both.</li><li><strong>Question the Easy Wins</strong>: The low-hanging fruit of scaling will run out. Prepare now for the harder, higher-hanging challenges of reasoning, adaptability, and true intelligence.</li></ol><p>The balance will come from accepting this duality: leaning into computational scale while staying grounded in the nuances of human-centric modeling.</p><h3>Message</h3><p>Don’t despair if your work feels task-specific or narrow. The intuitions you develop today could inspire a leap forward tomorrow. Keep looking for concepts that feel both powerful and general, and don’t shy away from asking, “How do we scale this?”. As Church warns, we need to strike a balance. Scaling is crucial, but let’s not lose sight of foundational challenges.</p><blockquote><em>Low-hanging fruit is great, but we can’t stop there.</em></blockquote><h3>Epilogue</h3><blockquote><em>The pendulum will swing again — it always does.</em></blockquote><p>Scaling will give way to introspection, and the glittering achievements of today will become the stepping stones of tomorrow. Whether you’re in machine learning, computational linguistics, or another domain, remember:</p><blockquote><em>Progress isn’t linear — it oscillates. And in that back-and-forth, every step matters and in that oscillation lies the beauty of discovery.</em></blockquote><p>The AGI revolution is not just a race to build bigger models. It is a journey to understand the essence of intelligence itself. And in this journey, every step matters.</p><p>What do you think? Are we, as a community, striking the right balance? Or are we destined to repeat the cycles of history, swinging too far before we swing back?</p><p>Let’s reflect — and, more importantly, let’s act.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d98af7f8236" width="1" height="1" alt=""><hr><p><a href="https://medium.com/technopreneurial-treatises/a-pendulum-swung-too-far-again-7d98af7f8236">A Pendulum Swung Too Far — Again</a> was originally published in <a href="https://medium.com/technopreneurial-treatises">Technopreneurial Treatises</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Artificially Interlaced Humans (AIH)]]></title>
            <link>https://medium.com/technopreneurial-treatises/artificially-interlaced-humans-aih-0b2aaacc37ce?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b2aaacc37ce</guid>
            <category><![CDATA[future-technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[agi]]></category>
            <category><![CDATA[system]]></category>
            <category><![CDATA[human-evolution]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Sat, 16 Nov 2024 22:57:41 GMT</pubDate>
            <atom:updated>2024-11-17T00:58:59.907Z</atom:updated>
            <content:encoded><![CDATA[<h3>Artificially Interlaced Humans (AIH): Building the Human-Machine Integration to AGI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jsc2680yoHNoSx9Cd-AVrg.png" /></figure><h3>Prologue</h3><p>The future of human evolution lies at the intersection of biology and technology, where <strong>Artificially Interlaced Humans (AIH)</strong> emerge as a groundbreaking step toward integrating human cognition with machine intelligence. AIH enables humans to control machines and interact with complex systems using brain signals, leveraging Brain-Computer Interfaces (BCI), neural mapping, Large Language Models (LLMs), and secure API-driven platforms.</p><p>To ensure privacy and security in this interconnected future, privacy-preserving AI systems fortified with one-way hash cryptography play a vital role. Together, these innovations pave the way for secure and scalable systems that amplify human capabilities and lay the foundation for Artificial General Intelligence (AGI).</p><p>This article explores the system design, low-level architecture, secure platform development, use cases, and the broader implications of AIH.</p><h3>Vision</h3><blockquote><em>Artificially Interlaced Humans (AIH) represent the convergence of human cognition with machine intelligence.</em></blockquote><p>By leveraging Brain-Computer Interfaces (BCI), advanced neural mapping, Large Language Models (LLMs), and function-calling systems, AIH allows humans to control and interact with machines seamlessly using brain signals.</p><blockquote><em>This integration is a transformative prelude to Artificial General Intelligence (AGI), offering a pathway to evolve human capabilities by bridging biological and synthetic intelligence.</em></blockquote><p>By decoding brain signals and mapping them to machine-readable commands, humans can directly control devices, interact with systems, and extend their cognitive and physical capabilities.</p><p>This convergence involves:</p><ul><li><strong>BCI</strong>s to capture brain signals.</li><li><strong>Neural mapping</strong> to decode intents from signals.</li><li><strong>LLM</strong>s to translate intents into actionable commands.</li><li><strong>Secure function calling API</strong>s for system and machine interactions.</li></ul><blockquote><em>AIH is not just about interfacing with machines; it is about evolving humanity by enhancing natural abilities and creating new ways to collaborate with technology.</em></blockquote><h3>System Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/811/1*zOSItupsyu79Iz9kYmJUMg.png" /></figure><p>AIH requires a multi-layered system design encompassing the following components:</p><h3>1. Input Layer: Brain-Computer Interface (BCI)</h3><p>The Input Layer serves as the foundation of Artificially Interlaced Humans (AIH). Its primary goal is to capture brain signals — electrical activity generated by the brain — and translate them into actionable machine commands. This is achieved through various technologies that read, preprocess, and forward neural data to the subsequent processing layers.</p><p><strong>Components of the Input Layer</strong></p><p>1. <strong>Non-Invasive BCIs</strong></p><p>Non-invasive BCIs are external devices that capture brain signals without penetrating the skull or brain tissue. They are designed for accessibility and usability while offering lower fidelity compared to semi-invasive BCIs.</p><ul><li>Technology Used: Electroencephalography (EEG)</li><li>How It Works: EEG sensors are placed on the scalp to measure voltage fluctuations caused by neuronal activity. Signals are captured from specific regions of the brain, such as the motor cortex (for motion-related commands) or the prefrontal cortex (for cognitive tasks).</li><li>Use Cases: Basic control tasks, such as operating robotic arms or cursor movement. Assistive technologies for individuals with mobility impairments. Gaming and virtual reality interactions.</li><li>Advantages: Non-invasive and user-friendly. Portable and affordable for widespread applications.</li><li>Challenges: Limited signal resolution due to interference from the skull and scalp. Susceptibility to external noise (e.g., muscle activity or environmental electrical interference).</li></ul><p>2. <strong>Semi-Invasive BCIs</strong></p><p>Semi-invasive BCIs involve implanting electrodes beneath the skull but outside the brain tissue. These devices provide higher signal fidelity and resolution than non-invasive BCIs.</p><ul><li>Technology Used: Electrocorticography (ECoG)</li><li>How It Works: Electrodes are placed directly on the surface of the brain or dura mater (the outer brain membrane). ECoG captures more precise signals compared to EEG, as it bypasses the dampening effect of the skull.</li><li>Use Cases: High-fidelity control of prosthetic limbs, enabling nuanced movement. Advanced assistive technologies for severely disabled individuals. Neural signal decoding for medical diagnostics and therapeutic interventions.</li><li>Advantages: Superior signal resolution and reliability. Suitable for advanced AIH applications requiring detailed neural control.</li><li>Challenges: Surgical implantation is required, introducing risks like infection or rejection. Higher cost and limited accessibility.</li></ul><p>3. <strong>Neural Signal Preprocessors</strong></p><p>Neural signal preprocessors play a critical role in ensuring the quality and usability of the raw signals captured by BCIs. They filter noise, amplify meaningful patterns, and prepare data for the neural mapping stage.</p><ul><li>Key Functions:</li></ul><p>Noise Filtering: Removes interference from muscle activity (e.g., facial twitches, blinking). Filters out ambient electrical noise from external sources. Techniques: Adaptive noise cancellation, band-pass filters.</p><p>Signal Amplification: Neural signals are inherently weak (in the microvolt range). Amplifiers boost these signals to levels suitable for processing. Techniques: Low-noise operational amplifiers, gain control circuits.</p><p>Feature Extraction: Identifies key features in the signal (e.g., frequency bands like alpha, beta, gamma waves). Converts raw signals into structured formats (e.g., power spectra or wavelet transforms).</p><p>Artifact Removal: Eliminates spurious artifacts such as eye movement or heartbeat interference using Independent Component Analysis (ICA) or regression-based techniques.</p><ul><li>Hardware: Dedicated chips or modules (e.g., FPGA or ASIC) for real-time preprocessing. Portable units integrated with non-invasive BCI headsets.</li><li>Software: Signal preprocessing algorithms embedded in the BCI software stack. Machine learning models to improve signal clarity dynamically.</li></ul><p><strong>Workflow of the Input Layer</strong></p><ol><li><strong>Signal Acquisition</strong>: EEG sensors (non-invasive) or ECoG electrodes (semi-invasive) capture raw neural activity. Signals are transmitted to preprocessing hardware.</li><li><strong>Preprocessing</strong>: Filters and amplifiers enhance signal quality and remove noise. Feature extraction identifies meaningful patterns (e.g., motor intentions).</li><li><strong>Output to Processing Layer</strong>: Cleaned and structured neural signals are forwarded to the neural mapping layer for decoding into actionable commands.</li></ol><p><strong>Future Innovations in the Input Layer</strong></p><ol><li><strong>Hybrid BCIs</strong>: Combining non-invasive and semi-invasive technologies for enhanced flexibility and resolution. Example: Wearable headsets with optional implantable modules.</li><li><strong>AI-Assisted Preprocessors</strong>: AI-driven noise reduction and feature extraction for higher accuracy in real-time signal processing.</li><li><strong>Improved Biocompatibility</strong>: Use of advanced materials (e.g., graphene electrodes) for semi-invasive BCIs to reduce risks and improve longevity.</li><li><strong>Wireless BCIs</strong>: Fully wireless systems with low-latency data transmission for improved user mobility and comfort.</li></ol><p><strong>Impact of the Input Layer on AIH</strong></p><p>The Input Layer is the gateway to AIH, translating human thoughts into digital commands. By advancing BCI technologies and signal preprocessing, AIH systems will achieve:</p><ul><li>Greater accessibility for everyday users.</li><li>Enhanced precision for complex applications.</li><li>A robust foundation for secure and seamless integration with downstream processing layers.</li></ul><p>This foundational layer not only defines the capability of AIH systems but also establishes the standards for safety, usability, and performance in human-machine integration.</p><h3>2. Processing Layer: Neural Mapping and Signal Interpretation</h3><p>The Processing Layer decodes brain signals captured by the Input Layer and translates them into structured data representing intents or commands. This layer leverages advanced machine learning and signal processing techniques to interpret neural activity with high accuracy and efficiency. It serves as the critical bridge between raw neural signals and actionable insights used by downstream systems.</p><p><strong>Components of the Processing Layer</strong></p><p>1. <strong>Neural Mapping Models</strong></p><p>Neural Mapping Models are at the heart of the Processing Layer. These machine learning models analyze patterns in neural data to identify specific user intents or actions.</p><ul><li>Key Functions: Translate neural activity (e.g., electrical signals) into structured representations like intent vectors. Recognize specific patterns associated with user actions, thoughts, or commands.</li><li>Technologies and Algorithms:</li></ul><p>Deep Learning Models: Recurrent Neural Networks (RNNs): Useful for processing time-series data from neural signals. Long Short-Term Memory (LSTM): Handles temporal dependencies in sequential neural activity. Transformers: Efficiently process large-scale neural data for complex pattern recognition.</p><p>Traditional Signal Processing Techniques: Spectral analysis (e.g., Fourier or wavelet transforms) to identify dominant frequency bands (alpha, beta, gamma). Independent Component Analysis (ICA) for isolating signal sources from noise.</p><p>Hybrid Models: Combine classical methods and AI to enhance interpretability and accuracy.</p><ul><li>Training Process:</li></ul><p>Data Collection: Neural data is collected from users performing specific actions or visualizing certain tasks.</p><p>Labeling: Data is labeled with corresponding intents or commands (e.g., “move left,” “select object”).</p><p>Model Training: Supervised learning trains the model to associate patterns with labeled intents. Reinforcement learning refines model accuracy during real-time use.</p><ul><li>Use Cases: Translating motor cortex activity into commands for controlling prosthetic limbs or robotic devices. Decoding visual cortex signals for object recognition or navigation in augmented reality (AR) systems. Enabling speechless communication through thought-to-text systems.</li><li>Advantages: High accuracy and adaptability with continuous learning. Ability to generalize across tasks with minimal retraining.</li><li>Challenges: Requires significant computational power for training. Potential biases in training data may impact accuracy.</li></ul><p>2. <strong>Personalized Signal Interpreters</strong></p><p>Every individual’s brain activity patterns are unique due to neural variability, necessitating personalized adaptations in neural mapping.</p><ul><li>Key Functions: Adjust for user-specific neural signal variations caused by differences in brain structure, cognitive habits, or neural plasticity. Enhance accuracy and reduce errors by tailoring models to individual users.</li><li>Technologies and Methods:</li></ul><p>Transfer Learning: Use pre-trained models as a base and fine-tune them on individual user data.</p><p>Few-Shot Learning: Rapidly adapt to a new user with minimal data, minimizing calibration time.</p><p>Meta-Learning: Develop models that learn to adapt quickly to user-specific patterns during runtime.</p><p>Continuous Learning Pipelines: Models update dynamically as they collect more user-specific data, improving accuracy over time.</p><ul><li>Calibration Process:</li></ul><p>Baseline Data Collection: Collect a few minutes of neural activity while the user performs predefined tasks (e.g., imagining hand movements).</p><p>Model Adjustment: Fine-tune neural mapping models to align with the user’s unique signal patterns.</p><p>Validation: Test the personalized interpreter with real-time tasks to ensure reliability.</p><p>Ongoing Adaptation: Continuous improvement via reinforcement learning during usage.</p><ul><li>Use Cases: Enhancing performance for users with distinct neural profiles, such as individuals with neurological conditions. Personalizing AIH systems for applications like gaming, creative tools, or specialized industrial tasks. Creating inclusive systems that adapt to diverse neural and cognitive capabilities.</li><li>Advantages: Tailored experiences for individual users. Improved accuracy and reduced false positives in intent decoding.</li><li>Challenges: Requires initial calibration, which may be inconvenient for some users. Balancing personalization with generalizability to avoid overfitting.</li></ul><p><strong>Workflow of the Processing Layer</strong></p><ol><li><strong>Signal Input</strong>: Preprocessed signals from the Input Layer are fed into neural mapping models.</li><li><strong>Pattern Recognition</strong>: Models identify patterns in neural activity that correspond to specific actions or thoughts.</li><li><strong>Intent Classification</strong>: Decoded patterns are categorized into structured data formats, such as intent vectors or command sequences.</li><li><strong>Personalization</strong>: Signal interpreters adjust model outputs to align with the user’s unique neural profile.</li><li><strong>Output to Action Layer</strong>: Structured data is passed to the Action Layer for further processing and execution.</li></ol><p><strong>Future Innovations in the Processing Layer</strong></p><ol><li><strong>Multi-Modal Neural Mapping</strong>: Integrating multiple signal types (e.g., EEG, ECoG, and fMRI) for richer and more accurate intent decoding.</li><li><strong>Context-Aware Decoding</strong>: Models that incorporate environmental context (e.g., device state or location) to improve intent accuracy.</li><li><strong>Unsupervised Adaptation</strong>: Systems that autonomously learn and adapt to user-specific signals without requiring labeled training data.</li><li><strong>Low-Power Inference Chips</strong>: Specialized hardware (e.g., neuromorphic processors) for real-time, energy-efficient signal interpretation.</li><li><strong>Collaborative Mapping</strong>: Sharing and merging neural mapping data across multiple users to enhance collective model performance while preserving individual privacy.</li></ol><p><strong>Impact of the Processing Layer on AIH</strong></p><p>The Processing Layer is the intelligence engine of AIH, transforming neural signals into actionable insights. Its development directly impacts:</p><ul><li>Accuracy and Speed: High-quality mapping ensures seamless control of machines and systems.</li><li>User Experience: Personalized interpreters make AIH systems intuitive and user-friendly.</li><li>Broader Accessibility: By adapting to diverse users, AIH becomes inclusive and widely applicable.</li></ul><p>This layer, combining cutting-edge machine learning and personalized adaptation, ensures that AIH systems are both powerful and human-centric, setting the stage for robust human-machine symbiosis.</p><h3>3. Action Layer: LLM and Function Calling</h3><p>The Action Layer is responsible for translating decoded intents from the Processing Layer into actionable commands and executing them on target machines, systems, or devices. It integrates Large Language Models (LLMs) for natural language understanding and intent refinement and uses a Function Calling API to route and execute the machine-readable tasks effectively.</p><p><strong>Components of the Action Layer</strong></p><p>1. <strong>LLM Integration</strong></p><p>Large Language Models (LLMs) like GPT or Llama serve as the cognitive core of the Action Layer, bridging the gap between human intents and machine actions. These models process structured intents, refine commands, and adapt to complex or ambiguous user inputs.</p><ul><li>Key Functions:</li></ul><p>Intent Refinement: Decoded intents (e.g., “move object left”) are further analyzed and contextualized. Example: Converting “turn on the light” to “turn on the smart bulb in the living room.”</p><p>Multi-Modal Processing: LLMs process textual, voice, or symbolic input seamlessly. Example: Combining visual input (“object on camera”) with neural intents to issue commands like “pick up the red box.”</p><p>Dynamic Adaptation: Context-aware reasoning allows LLMs to adapt to changing conditions or ambiguous instructions. Example: Resolving “increase temperature” by dynamically querying the current temperature and issuing precise adjustments.</p><ul><li>Technologies and Algorithms:</li></ul><p>Pre-Trained Models: LLMs like GPT, Llama, or PaLM are trained on large-scale datasets and fine-tuned for specific AIH use cases.</p><p>Fine-Tuning and Reinforcement Learning: Continuous adaptation to domain-specific tasks ensures accuracy in interpreting intents. Incorporates feedback from real-world usage to improve performance over time.</p><p>Natural Language Function Calling: In-built capabilities of LLMs to directly invoke APIs based on user intents (e.g., OpenAI’s function calling feature).</p><ul><li>Use Cases: Command translation for IoT devices. Operating robotic systems using natural language. Dynamic task planning and execution in industrial settings.</li><li>Advantages: Context-aware and scalable. Capable of handling complex, multi-step tasks.</li><li>Challenges: High computational cost for inference. Potential ambiguities in intent resolution.</li></ul><p>2. <strong>Function Calling API</strong></p><p>The Function Calling API is the middleware responsible for connecting the refined intents from LLMs to the appropriate machine or system actions. It ensures that commands are executed seamlessly, securely, and with minimal latency.</p><ul><li>Key Functions:</li></ul><p>Command Routing: Maps decoded intents to specific machine functions or system APIs. Example: Intent “turn on the fan” is routed to the smart home API controlling the fan.</p><p>Task Execution: Converts high-level intents into detailed, machine-readable instructions. Example: Intent “pick up the box” translates to robotic arm commands like “move to X, grasp, lift, and move to Y.”</p><p>Dynamic Function Matching: Resolves ambiguities by querying system states or requesting clarifications. Example: For “unlock the door,” it identifies which door to unlock based on proximity or other inputs.</p><ul><li>Technology Stack:</li></ul><p>Middleware Frameworks: Built on frameworks like FastAPI, Flask, or GraphQL for robust API interactions.</p><p>Routing Algorithms: Intent-matching algorithms using semantic similarity or predefined mappings.</p><p>State Management: Keeps track of device states, user preferences, and ongoing tasks to avoid conflicts.</p><p>Asynchronous Execution: Ensures real-time execution and feedback for latency-sensitive tasks.</p><ul><li>Security Features:</li></ul><p>Authentication and Authorization: Uses OAuth2 or token-based mechanisms to ensure secure API access.</p><p>Hash-Based Intent Validation: Protects intent integrity by validating hashed inputs.</p><p>Role-Based Access Control (RBAC): Limits API access based on user roles and privileges.</p><ul><li>Use Cases: IoT Control: Managing smart home devices like lights, thermostats, or security systems. Robotic Commands: Operating industrial robots for assembly lines or medical surgeries. Workflow Automation: Executing multi-step business processes, such as generating reports or scheduling tasks.</li><li>Advantages: Modular and extensible architecture. Scalability for complex systems with diverse device types.</li><li>Challenges: Potential latency in multi-step workflows. Dependency on robust error-handling mechanisms for incomplete or ambiguous commands.</li></ul><p><strong>Workflow of the Action Layer</strong></p><ol><li><strong>Input from Processing Layer</strong>: Decoded intent vectors or commands are forwarded to the Action Layer. Example: “Move robotic arm to X position.”</li><li><strong>LLM Refinement</strong>: The LLM contextualizes and refines the input. Example: Decoding “fetch the box” into detailed actions based on current conditions.</li><li><strong>Command Routing via Function Calling API</strong>: Middleware maps the refined command to the appropriate machine or system API. Example: Routes the refined command to the robotic control system.</li><li><strong>Task Execution</strong>: The target system executes the machine-readable commands. Example: Robotic arm performs the action of moving to X, grasping an object, and relocating it to Y.</li><li><strong>Feedback Loop</strong>: The system sends execution status or sensory feedback to the user or higher layers. Example: Robotic arm reports task completion or error.</li></ol><p><strong>Future Innovations in the Action Layer</strong></p><ol><li><strong>Autonomous Task Planning</strong>: LLMs evolve to handle complex multi-step tasks autonomously, such as assembling an object or navigating complex environments.</li><li><strong>Real-Time Function Matching</strong>: Faster routing algorithms that reduce latency in intent-to-action conversions.</li><li><strong>Federated Function Execution</strong>: Distributed APIs that allow AIH systems to interact with multiple devices or subsystems simultaneously.</li><li><strong>Contextual APIs</strong>: APIs that dynamically adapt to environmental changes or user preferences, such as adjusting actions based on real-time sensory inputs.</li><li><strong>Proactive Feedback Systems</strong>: Systems that provide proactive suggestions or alerts based on task status or potential errors.</li></ol><p><strong>Impact of the Action Layer on AIH</strong></p><p>The Action Layer is the operational engine of AIH systems, ensuring that user intents lead to tangible actions. It enhances:</p><ul><li>Efficiency: Streamlines intent execution with minimal user intervention.</li><li>Flexibility: Adapts to diverse systems and devices through modular APIs.</li><li>Scalability: Supports increasingly complex tasks and multi-device coordination.</li></ul><p>With its integration of advanced LLMs and secure function-calling frameworks, the Action Layer ensures that AIH systems are not only powerful but also responsive and reliable, making seamless human-machine collaboration a reality.</p><h3>4. Feedback Layer: Machine-to-Brain Communication</h3><p>The Feedback Layer closes the loop in an Artificially Interlaced Human (AIH) system by providing real-time feedback from machines to the human brain. This layer ensures that users are aware of the status of their commands and the environment, enabling precise adjustments and enhancing control. It achieves this by delivering feedback through tactile and sensory modalities or directly via neurofeedback systems.</p><p><strong>Components of the Feedback Layer</strong></p><p>1. <strong>Tactile Feedback Devices</strong></p><p>Tactile feedback devices provide haptic signals (e.g., vibrations, pressure, or temperature) to inform the user about the status of a task or environmental conditions. These devices are often wearable or minimally invasive.</p><ul><li>Key Functions: Deliver physical sensations to indicate success, failure, or progress of a task. Encode complex machine states into simple haptic patterns for intuitive understanding. Provide alerts or notifications about environmental changes or system errors.</li><li>Technologies:</li></ul><p>Wearable Devices:</p><p>Haptic Gloves: Provide sensations of touch, pressure, or force, enabling the user to “feel” robotic actions or virtual environments.</p><p>Vibration Bands: Wearable bands that deliver specific vibration patterns for different signals (e.g., success, warning, or error).</p><p>AR/VR Suits: Full-body wearables that simulate physical sensations in augmented or virtual reality environments.</p><p>Implantable Haptic Devices: Implants that stimulate nerve endings to provide tactile feedback directly to the nervous system for high-fidelity interaction.</p><p>Actuators: Miniaturized motors or piezoelectric elements generating vibration, pressure, or force sensations.</p><ul><li>Encoding Feedback:</li></ul><p>Pattern Encoding: Different vibration patterns correspond to specific machine states (e.g., short buzz = task completed, long buzz = error).</p><p>Intensity Encoding: The intensity of the feedback varies based on the importance or urgency of the signal.</p><ul><li>Use Cases:</li></ul><p>Robotics: Allowing users to feel the grip of a robotic arm or the texture of objects manipulated by the machine.</p><p>IoT: Informing users of environmental conditions, such as increased temperature or humidity, via wearable devices.</p><p>Accessibility Tools: Assisting visually impaired users by converting visual data into tactile feedback.</p><ul><li>Advantages: Non-invasive and user-friendly. Easily integrated into consumer devices.</li><li>Challenges: Limited bandwidth for conveying complex information. Potential discomfort during prolonged use.</li></ul><p>2. <strong>Neurofeedback Systems</strong></p><p>Neurofeedback systems bypass traditional sensory pathways and deliver signals directly to the brain, translating machine states or environmental data into visual, auditory, or somatosensory inputs.</p><ul><li>Key Functions: Deliver direct brain stimulation to communicate information. Encode feedback in ways that are natural for the brain to process, such as visual flashes, sounds, or vibrations. Provide real-time updates on task progress or environmental changes.</li><li>Technologies:</li></ul><p>Visual Feedback: Direct stimulation of the visual cortex or retinal prosthetics to present visual cues like flashes, patterns, or augmented overlays. Example: A robotic system could highlight the trajectory of an arm movement visually in augmented reality.</p><p>Auditory Feedback: Stimulation of the auditory cortex or cochlear implants to deliver tonal or speech-based information. Example: A device could notify task success with specific tones or verbal messages.</p><p>Somatosensory Feedback: Stimulation of the somatosensory cortex to create sensations of touch or force. Example: Users could “feel” the weight or resistance of a robotic arm in real-time.</p><p>Electrical Brain Stimulation: Devices like transcranial magnetic stimulation (TMS) or deep brain stimulation (DBS) modulate brain activity to deliver feedback. Example: Inducing a sensation of satisfaction or discomfort to signal success or error, respectively.</p><ul><li>Encoding Feedback:</li></ul><p>Temporal Encoding: Feedback signals are delivered in a sequence, where the timing or rhythm conveys meaning (e.g., slow flashes for warnings, rapid flashes for urgency).</p><p>Spatial Encoding: Different regions of the brain or sensory field are stimulated to encode specific signals.</p><ul><li>Use Cases:</li></ul><p>Prosthetics: Providing real-time feedback on grip strength or object texture.</p><p>Gaming and VR: Creating immersive environments where the brain perceives direct sensations of interaction.</p><p>Medical Applications: Helping patients regain sensory perception through targeted neurofeedback.</p><ul><li>Advantages: Direct and efficient communication to the brain. Potential for high fidelity and precision.</li><li>Challenges: Invasive techniques may require surgery. Ethical and safety concerns regarding direct brain stimulation.</li></ul><p><strong>Workflow of the Feedback Layer</strong></p><ol><li><strong>Feedback Generation</strong>: Machines or systems generate feedback data based on task outcomes or environmental conditions. Example: A robotic arm sends data on grip strength and object weight.</li><li><strong>Signal Translation</strong>: Feedback signals are encoded into tactile or neurofeedback modalities. Example: Machine output is translated into haptic vibrations or visual flashes.</li><li><strong>Delivery to the User</strong>: Wearable devices deliver haptic signals, or neurofeedback systems stimulate sensory pathways directly. Example: A vibration on a wristband or a visual flash in AR indicates task completion.</li><li><strong>User Perception</strong>: The user interprets the feedback and makes adjustments to their actions or commands, closing the control loop. Example: Adjusting the force of a robotic grip based on haptic feedback.</li></ol><p><strong>Future Innovations in the Feedback Layer</strong></p><ol><li><strong>Bidirectional Neurofeedback</strong>: Systems that combine brain stimulation with sensory feedback for seamless closed-loop control.</li><li><strong>Immersive Feedback Environments</strong>: Full-body haptic suits or multi-sensory VR systems for immersive machine interaction.</li><li><strong>Artificial Sensory Feedback</strong>: Creating entirely new sensory experiences that extend beyond natural human perception (e.g., feedback for detecting electromagnetic fields or microscopic textures).</li><li><strong>Wireless Feedback Implants</strong>: Non-invasive brain stimulation devices powered by wireless energy for long-term usability.</li><li><strong>AI-Powered Feedback Optimization</strong>: Adaptive systems that learn user preferences and adjust feedback modalities dynamically for maximum clarity and comfort.</li></ol><p><strong>Impact of the Feedback Layer on AIH</strong></p><p>The Feedback Layer transforms machine responses into human-perceivable signals, making AIH systems intuitive and user-centric. Its development ensures:</p><ul><li>Closed-Loop Precision: Enables users to refine their commands based on real-time feedback.</li><li>Enhanced User Experience: Provides seamless interaction between humans and machines.</li><li>Greater Accessibility: Makes AIH systems practical for individuals with sensory or mobility impairments.</li></ul><p>By combining tactile and neurofeedback technologies, the Feedback Layer is essential for creating a symbiotic relationship between humans and machines, paving the way for more immersive, accurate, and responsive AIH systems.</p><h3>5. Secure Communication Layer</h3><p>The Secure Communication Layer ensures that data transmitted between humans and machines remains secure, unaltered, and timely. This layer is critical for maintaining the integrity, privacy, and reliability of Artificially Interlaced Humans (AIH) systems, where sensitive neural signals and machine commands are exchanged continuously. By implementing advanced encryption, integrity validation, and secure API-driven function calls, this layer safeguards the seamless and secure operation of AIH systems.</p><p><strong>Components of the Secure Communication Layer</strong></p><p>1. <strong>Encrypted Wireless Protocols</strong></p><p>Encrypted wireless protocols form the backbone of secure real-time communication, enabling low-latency interactions between BCIs, devices, and systems.</p><ul><li>Key Functions: Encrypt all data in transit to prevent unauthorized access or interception. Ensure ultra-low latency to facilitate real-time responses in AIH systems. Support bidirectional communication for continuous data exchange and feedback loops.</li><li>Technologies:</li></ul><p>Encryption Standards:</p><p>AES-256 (Advanced Encryption Standard): Ensures strong encryption of transmitted data.</p><p>Elliptic Curve Cryptography (ECC): Lightweight encryption suitable for wearable or implantable devices.</p><p>Wireless Communication Protocols:</p><p>Bluetooth Low Energy (BLE): Optimized for short-range, low-power devices like wearable BCIs.</p><p>Wi-Fi 6 and 5G: High-speed protocols for broader range and higher data throughput.</p><p>Li-Fi: Optical wireless communication for environments requiring high security and interference resistance.</p><p>Quantum-Resistant Protocols: Incorporates post-quantum cryptographic algorithms to future-proof communications.</p><ul><li>Features:</li></ul><p>Session-Based Key Management: Establishes unique encryption keys for each session, minimizing the impact of key compromise.</p><p>Adaptive Bandwidth Management: Dynamically adjusts bandwidth to prioritize critical signals in latency-sensitive scenarios.</p><ul><li>Use Cases: Transmitting real-time neural signal data from BCIs to processing units. Delivering haptic or neurofeedback to users without delay. Enabling remote control of devices in healthcare, industrial, or home environments.</li><li>Advantages: Strong protection against interception and eavesdropping. Scalability to handle multiple devices and users in real-time.</li><li>Challenges: Balancing encryption strength with processing power on low-resource devices. Mitigating latency introduced by encryption and decryption processes.</li></ul><p>2. <strong>Data Integrity Validators</strong></p><p>Data integrity validators ensure that neural signal data and machine commands remain accurate and unaltered during transmission. This is critical for maintaining trust and reliability in AIH systems.</p><ul><li>Key Functions: Detect and prevent tampering or corruption of transmitted data. Validate the authenticity and integrity of incoming signals or commands. Protect against replay attacks by verifying the freshness of data.</li><li>Technologies:</li></ul><p>Hash-Based Message Authentication Code (HMAC): Uses cryptographic hashing (e.g., SHA-256) to verify data integrity and authenticity.</p><p>Digital Signatures: Public-key cryptography ensures that transmitted data originates from trusted sources.</p><p>Checksums: Simple algorithms to detect accidental corruption of data during transmission.</p><p>Nonce-Based Systems: Assigns a unique number to each data packet to prevent replay attacks and ensure data freshness.</p><ul><li>Implementation Workflow:</li></ul><p>Data Hashing: Neural data or commands are hashed before transmission.</p><p>Transmission: The hashed data and original payload are transmitted to the recipient.</p><p>Validation: The recipient rehashes the data and compares it with the received hash to verify integrity.</p><ul><li>Use Cases: Verifying the accuracy of neural signals sent from a BCI to a processing unit. Ensuring machine responses or feedback loops are unaltered before delivery to the user. Detecting and rejecting tampered commands in high-security environments.</li><li>Advantages: Ensures the trustworthiness of transmitted data. Detects errors or tampering instantly.</li><li>Challenges: Handling complex validation processes in resource-constrained devices. Preventing false positives in high-noise environments.</li></ul><p>3. <strong>API-Driven Secure Function Calling</strong></p><p>Secure API-driven function calling encapsulates system interactions within standardized, protected interfaces. This component ensures that only authorized and verified commands are executed on target systems.</p><ul><li>Key Functions: Encapsulate all device and system interactions within secure APIs. Enforce strict input validation using hashed and authenticated data. Enable dynamic and flexible function execution across a variety of devices.</li><li>Technologies:</li></ul><p>OAuth 2.0 or OpenID Connect: Manages secure authentication and authorization for API access.</p><p>Encrypted API Gateways: Gateways encrypt API calls and responses, adding an additional layer of security.</p><p>Zero Trust Architecture: Requires continuous validation of user identity and intent for every API request.</p><p>Role-Based Access Control (RBAC): Restricts API access based on user roles, ensuring only authorized operations are performed.</p><ul><li>Implementation Workflow:</li></ul><p>Hashed Input Validation: User intents are hashed and sent as inputs to API endpoints.</p><p>Authorization: APIs verify user credentials and access rights using token-based authentication.</p><p>Command Execution: Validated commands are routed to corresponding system functions for execution.</p><p>Feedback Delivery: API returns a secure, hashed response confirming task status or completion.</p><ul><li>Use Cases: Controlling IoT devices in a smart home using AIH commands. Executing robotic actions in industrial or medical settings. Interfacing with cloud-based systems for data retrieval or processing.</li><li>Advantages: Modular and scalable design supports diverse devices and systems. Enhanced security through hashed and authenticated inputs.</li><li>Challenges: Latency introduced by multiple layers of validation and encryption. Complexity in managing API permissions across multi-device ecosystems.</li></ul><p><strong>Workflow of the Secure Communication Layer</strong></p><ol><li><strong>Data Encryption</strong>: Neural signals or commands are encrypted before transmission using session-based keys.</li><li><strong>Transmission via Wireless Protocols</strong>: Encrypted data is sent over a secure wireless channel.</li><li><strong>Integrity Validation</strong>: Data is validated for accuracy and authenticity upon receipt.</li><li><strong>Secure Function Execution</strong>: APIs process the validated data and execute machine commands.</li><li><strong>Feedback Encryption</strong>: Machine feedback is encrypted and transmitted back to the user.</li></ol><p><strong>Future Innovations in the Secure Communication Layer</strong></p><ol><li><strong>Quantum-Safe Encryption</strong>: Integrating quantum-resistant cryptographic algorithms to protect against future quantum computing threats.</li><li><strong>Real-Time Threat Detection</strong>: AI-driven systems that detect anomalies or potential threats in communication streams dynamically.</li><li><strong>Edge-Based Security</strong>: Deploying security mechanisms directly on edge devices for faster and more localized protection.</li><li><strong>Decentralized Communication Networks</strong>: Using blockchain or distributed ledger technology to create immutable, transparent communication logs.</li><li><strong>AI-Powered Compression</strong>: Encrypt and compress neural signal data simultaneously to improve transmission efficiency.</li></ol><p><strong>Impact of the Secure Communication Layer on AIH</strong></p><p>The Secure Communication Layer is critical to building trust and reliability in AIH systems. It enables:</p><ul><li>Privacy Protection: Ensures that neural signals and sensitive commands remain confidential.</li><li>Data Integrity: Prevents tampering or corruption of critical communications.</li><li>Scalability: Supports a growing number of devices, users, and interactions in real-time.</li></ul><p>By combining advanced encryption, integrity validation, and API-driven interactions, this layer provides the secure foundation needed for seamless and reliable human-machine collaboration in AIH systems.</p><h3>Path to AGI: The Role of Artificially Interlaced Humans (AIH)</h3><blockquote><em>Artificially Interlaced Humans (AIH) represent a transformative milestone in the journey toward Artificial General Intelligence (AGI).</em></blockquote><p>By bridging the gap between human cognition and machine intelligence, AIH systems enable unprecedented collaboration, learning, and problem-solving capabilities. Here’s how AIH accelerates the path to AGI.</p><p>1. <strong>Neural Knowledge Integration</strong></p><blockquote><em>Neural Knowledge Integration refers to the seamless connection between human cognition and machine intelligence, leveraging the best of both worlds — human intuition and machine precision.</em></blockquote><p>Key Features:</p><ul><li>Direct Access to Human Cognition: AIH systems capture neural signals directly from the brain, providing insights into human thought patterns, decision-making processes, and creativity. Example: A BCI-enabled architect could transfer their design intent directly into a CAD system, bypassing traditional manual input methods.</li><li>Blending Intuition and Precision: Humans excel at intuition, abstract reasoning, and emotional intelligence, while machines are superior at precision, scalability, and computation. AIH merges these strengths, enabling hybrid systems that outperform either humans or machines alone. Example: AIH-enhanced medical diagnosis combines a doctor’s intuition with an AI’s ability to analyze vast datasets, leading to faster and more accurate outcomes.</li></ul><p>Impact on AGI:</p><ul><li>AGI systems trained with direct neural inputs gain deeper insights into human reasoning, improving their ability to generalize across diverse domains.</li><li>Enhanced understanding of human thought processes accelerates AGI’s capacity to emulate human-like cognition.</li></ul><p>2. <strong>Human-Augmented AI Training</strong></p><blockquote><em>Human-Augmented AI Training involves using AIH systems to provide real-time neural feedback loops to train AI models, particularly Large Language Models (LLMs) and other machine learning frameworks.</em></blockquote><p>Key Features:</p><ul><li>Real-Time Neural Feedback: Neural signals are used as feedback during AI training, enabling models to learn from human approval, disapproval, or ambiguity in responses. Example: An artist can refine an AI-generated painting by providing neural signals indicating satisfaction or desired changes, training the AI to align with human preferences.</li><li>Contextual Understanding: AI models improve their ability to understand and respond to nuanced human contexts, such as tone, intent, and emotional states. Example: An AI conversational assistant fine-tuned using neural feedback can adapt its tone to match the user’s emotional state, providing empathetic responses.</li><li>Accelerated Learning: By combining reinforcement learning with neural signals, AI models achieve faster convergence and higher accuracy. Example: A self-driving car AI trained with real-time feedback from a neural-linked driver learns to make safer and more intuitive driving decisions.</li></ul><p>Impact on AGI:</p><ul><li>Neural feedback enhances the contextual and intuitive understanding of AI systems, a critical step toward achieving AGI.</li><li>Human-guided training ensures that AGI aligns with human values, ethics, and goals, reducing risks associated with misaligned AI systems.</li></ul><p>3. <strong>Collective Intelligence Systems</strong></p><blockquote><em>Collective Intelligence Systems are networks of AIH-enabled humans collaborating with machines, forming a unified intelligence that surpasses the problem-solving capacity of individuals or isolated AI systems.</em></blockquote><p>Key Features:</p><ul><li>Distributed Neural Networks: AIH-enabled humans form interconnected networks where their neural inputs and decisions are aggregated and analyzed by AI systems. Example: In disaster response scenarios, AIH-enabled teams can collectively analyze and respond to real-time data from affected areas, coordinating efforts with machine precision.</li><li>Enhanced Collaboration: AIH systems enable humans to collaborate with machines and each other at unprecedented scales and speeds. Example: Scientists across the globe working on AIH platforms can simultaneously contribute neural feedback to refine AI models for drug discovery.</li><li>Swarm Intelligence: Similar to how swarms of insects achieve complex tasks collectively, AIH networks allow for decentralized decision-making where the group’s intelligence is greater than the sum of its parts. Example: AIH systems could enable citizens in smart cities to collectively optimize traffic flow, energy usage, or resource allocation through real-time neural inputs.</li></ul><p>Impact on AGI:</p><ul><li>Collective intelligence systems provide AGI with a scalable model of human-machine collaboration, teaching it how to operate in multi-agent environments.</li><li>AGI can leverage the collective knowledge and decision-making capacity of AIH networks to address complex, global challenges like climate change, pandemics, or space exploration.</li></ul><p><strong>Advantages of AIH as a Precursor to AGI</strong></p><ol><li>Ethical Alignment: AIH ensures that AGI evolves in close collaboration with humans, embedding human values and ethics into its core learning processes.</li><li>Incremental Development: By integrating AIH, the development of AGI becomes a stepwise process, reducing risks associated with a sudden leap in capabilities.</li><li>Enhanced Human Capabilities: AIH doesn’t just enable AGI; it also enhances human potential, ensuring that humans remain central in an increasingly automated world.</li><li>Real-World Testing Grounds: AIH systems provide a safe and scalable platform for testing AGI capabilities in controlled environments before broader deployment.</li></ol><p><strong>Challenges and Future Directions</strong></p><ol><li>Scalability: Building infrastructure to support large-scale AIH networks capable of training AGI systems.</li><li>Data Privacy and Security: Ensuring neural data remains secure and private to prevent misuse in AGI development.</li><li>Neuroethics: Addressing ethical concerns about direct neural access and the potential for exploitation.</li><li>Technological Integration: Harmonizing BCI technologies, neural mapping, and machine learning systems for seamless operation.</li></ol><p>AIH is a transformative precursor to AGI, enabling deeper integration of human intuition, creativity, and collaboration with machine intelligence. By advancing neural knowledge integration, human-augmented AI training, and collective intelligence systems, AIH accelerates the development of AGI while ensuring that it remains aligned with human values and goals.</p><p>This collaborative evolution promises a future where humans and AGI work together to solve the world’s most pressing challenges, unleashing a new era of innovation and progress.</p><h3>Evolutionary Impact on Humans</h3><p>Artificially Interlaced Humans (AIH) signify the next evolutionary leap for humanity, fundamentally altering how we interact with technology, redefine our capabilities, and envision our place in an increasingly intelligent world. By seamlessly integrating human cognition with machine intelligence, AIH systems promise transformative changes across problem-solving, accessibility, work, and collaboration.</p><p>1. <strong>Enhanced Capabilities</strong></p><p>AIH systems amplify human abilities by providing real-time access to machine intelligence, enabling augmented problem-solving, enhanced creativity, and advanced physical control.</p><p>Key Features:</p><ul><li>Augmented Problem-Solving: AIH systems integrate human intuition with machine precision, allowing individuals to solve complex problems faster and more effectively. Example: An AIH-enabled engineer can visualize stress points in real-time while designing a structure, using machine intelligence to optimize materials and costs.</li><li>Enhanced Creativity: AIH systems act as cognitive amplifiers, inspiring new ideas or expanding the creative process by offering suggestions, generating alternatives, or simulating scenarios. Example: A musician could use AIH to compose music directly from neural patterns, allowing for spontaneous and intuitive creations.</li><li>Advanced Physical Control: AIH systems enable users to control robotic systems, prosthetics, or other devices with the precision of natural movement. Example: AIH-enhanced surgeons could remotely perform delicate procedures with robotic arms, using their neural inputs to achieve unparalleled precision.</li></ul><p>Benefits:</p><ul><li>Accelerates innovation in science, art, and engineering.</li><li>Reduces cognitive load by automating repetitive or data-intensive tasks.</li><li>Bridges the gap between human creativity and machine execution.</li></ul><p>2. <strong>Global Accessibility</strong></p><p>AIH systems have the potential to empower individuals with disabilities, offering new levels of mobility, communication, and independence.</p><p>Key Features:</p><ul><li>Restoring Mobility: AIH-powered BCIs enable individuals with mobility impairments to control wheelchairs, prosthetics, or robotic limbs directly with their thoughts. Example: A paraplegic user could regain independence by operating an AIH-powered exoskeleton to walk, climb stairs, or perform daily activities.</li><li>Communication for the Speech-Impaired: AIH systems allow users to translate thoughts directly into text or speech, enabling seamless communication for individuals with conditions like ALS or stroke-related aphasia. Example: A neural-to-text system could allow users to “speak” through a virtual assistant by converting brain signals into verbal communication.</li><li>Expanding Cognitive Abilities: AIH systems enhance learning and cognitive engagement for individuals with learning disabilities by tailoring content delivery to their neural activity. Example: Adaptive learning platforms powered by AIH could provide real-time adjustments in teaching methods based on a student’s engagement and understanding.</li></ul><p>Benefits:</p><ul><li>Improves quality of life for individuals with physical or cognitive impairments.</li><li>Promotes inclusivity by removing barriers to communication and mobility.</li><li>Unlocks new levels of independence and participation in society.</li></ul><p>3. <strong>Redefinition of Work and Creativity</strong></p><p>AIH systems will redefine the nature of work, education, and creativity, creating new opportunities for individuals to excel in emerging fields.</p><p>Key Features:</p><ul><li>New Forms of Creativity: AIH opens up new mediums for creative expression, such as thought-to-digital art or real-time collaboration with generative AI. Example: An AIH artist could “paint” using neural inputs, visualizing ideas directly on a digital canvas.</li><li>Revolutionized Education: AIH systems enable immersive, personalized learning experiences tailored to individual cognitive patterns. Example: AIH-integrated VR environments allow students to interact directly with simulated ecosystems or historical events, enhancing understanding.</li><li>Workforce Transformation: AIH systems will automate routine tasks, enabling humans to focus on roles requiring critical thinking, empathy, and creativity. Example: AIH-powered productivity tools could help workers manage complex projects by providing real-time insights, planning, and execution support.</li><li>Emerging Job Roles: As AIH systems become ubiquitous, new fields will emerge, such as neural interface design, AIH data analysis, and cognitive enhancement coaching. Example: Professionals specializing in optimizing AIH setups for individuals or organizations will become critical in leveraging these systems.</li></ul><p>Benefits:</p><ul><li>Creates new industries and opportunities aligned with human-AI collaboration.</li><li>Enhances human focus on creativity, strategy, and innovation.</li><li>Reduces workplace fatigue and stress by automating repetitive tasks.</li></ul><p>4. <strong>Cognitive Collaboration</strong></p><p>AIH systems will redefine how humans collaborate with machines, shifting from a tool-based relationship to one of cognitive partnership.</p><p>Key Features:</p><ul><li>Machines as Cognitive Extensions: AIH systems act as cognitive extensions, augmenting human memory, reasoning, and analytical capabilities. Example: An AIH system could provide a lawyer with instant access to relevant case law during a courtroom argument, based on neural cues.</li><li>Human-Machine Synergy: AIH enables seamless collaboration, where machines complement human thought processes without explicit commands. Example: A team of AIH-enabled disaster responders could work alongside drones and robots to map affected areas and coordinate relief efforts in real time.</li><li>Enhanced Group Collaboration: AIH networks allow groups of humans and machines to pool their knowledge and decision-making capabilities. Example: Scientists in different locations could contribute to a shared neural network to solve global problems like climate change or disease outbreaks.</li></ul><p>Benefits:</p><ul><li>Improves decision-making by combining human intuition with machine analytics.</li><li>Fosters innovation through collaborative problem-solving at scale.</li><li>Enables faster and more effective responses to complex challenges.</li></ul><p>Long-Term Implications</p><p>The evolutionary impact of AIH extends far beyond immediate capabilities, potentially redefining what it means to be human:</p><ol><li>Human-AI Symbiosis: AIH systems blur the lines between biological and artificial intelligence, creating a new era of hybrid cognition.</li><li>Expanded Human Potential: By eliminating physical and cognitive limitations, AIH systems unlock unprecedented opportunities for exploration, creativity, and understanding.</li><li>New Ethical Paradigms: Society will need to navigate the ethical implications of enhancing human abilities, including questions of equity, access, and autonomy.</li></ol><p>AIH represents a profound evolutionary leap, redefining humanity’s capabilities, accessibility, and relationship with technology. By augmenting problem-solving, empowering individuals with disabilities, reshaping work and creativity, and fostering cognitive collaboration, AIH systems not only enhance individual lives but also pave the way for a more inclusive, innovative, and interconnected future.</p><blockquote><em>As humanity integrates with intelligent systems, the boundaries of what we can achieve will continue to expand, ushering in an era of limitless potential.</em></blockquote><h3>Future Development and Challenges of Artificially Interlaced Humans (AIH)</h3><blockquote><em>As Artificially Interlaced Humans (AIH) evolve, they promise to reshape human capabilities, accessibility, and collaboration with machines.</em></blockquote><p>However, this transformative technology faces significant challenges that must be addressed to ensure ethical, practical, and inclusive deployment. Simultaneously, future innovations in AIH development aim to overcome these obstacles and unlock its full potential.</p><p><strong>Challenges in AIH Development</strong></p><p>1. <strong>Ethical Concerns</strong></p><p>Ethical challenges surrounding AIH are among the most pressing, focusing on the privacy, autonomy, and potential misuse of neural data.</p><ul><li>Privacy of Neural Data: Neural signals are highly sensitive and uniquely tied to individual identity, making them vulnerable to misuse if not adequately protected. Example: Unauthorized access to neural data could lead to profiling, manipulation, or exploitation of individuals.</li><li>Risk of Misuse: AIH systems could be weaponized or misused for surveillance, coercion, or control. Example: Governments or organizations could exploit AIH systems to monitor or influence thoughts and behaviors.</li><li>Autonomy Concerns: As AIH systems become more integrated with human cognition, there is a risk of diminishing individual autonomy. Example: Over-reliance on AIH systems for decision-making could erode personal agency or critical thinking.</li><li>Solutions: Implementing robust encryption and privacy-preserving AI techniques to secure neural data. Establishing strict ethical and regulatory frameworks to govern AIH use and deployment. Ensuring transparency in AIH system operations to build trust and accountability.</li></ul><p>2. <strong>Hardware Limitations</strong></p><p>Developing hardware that balances power, size, durability, and processing capabilities is a significant technical challenge.</p><ul><li>Size vs. Functionality: Compact devices must be lightweight and ergonomic while maintaining high signal fidelity and processing power. Example: Miniaturized BCI headsets that are portable yet capable of real-time neural signal decoding.</li><li>Power Efficiency: Wearable and implantable devices require energy-efficient designs to operate for extended periods without frequent recharging. Example: A prosthetic controlled by AIH must function for hours without compromising responsiveness.</li><li>Durability and Biocompatibility: Devices need to withstand long-term use without degrading or causing discomfort or harm. Example: Semi-invasive electrodes must avoid causing inflammation or rejection by the body.</li><li>Solutions: Advancing materials science to create lightweight, durable, and biocompatible devices. Developing energy-harvesting technologies (e.g., body heat or motion-powered devices) to reduce reliance on batteries. Optimizing hardware designs with specialized chips like ASICs for efficient neural signal processing.</li></ul><p>3. <strong>Social Impacts</strong></p><p>The widespread adoption of AIH systems could exacerbate social inequalities and create new societal divides.</p><ul><li>Digital Divide: High costs and accessibility challenges may limit AIH adoption to privileged groups, leaving others behind. Example: Wealthy individuals might benefit disproportionately from cognitive or physical enhancements, deepening existing inequalities.</li><li>Social Stigma: AIH-enabled individuals could face discrimination or alienation due to their augmented abilities or perceived advantages. Example: Employers might favor AIH-enhanced workers over non-enabled ones, creating workplace divisions.</li><li>Resistance to Adoption: Cultural and ethical concerns may lead to resistance against integrating AIH systems into society. Example: Religious or philosophical beliefs may oppose augmenting human capabilities with machines.</li><li>Solutions: Ensuring equitable access through subsidized programs, open-source technologies, or public-private partnerships. Promoting awareness and education about the benefits and limitations of AIH systems. Addressing societal biases and fostering inclusive policies to integrate AIH into diverse cultural and social contexts.</li></ul><p><strong>Future Innovations in AIH Development</strong></p><p>1. <strong>Full Duplex Brain-Machine Interfaces</strong></p><p>Bidirectional communication systems that enable seamless interaction between the brain and machines.</p><ul><li>Key Features:</li></ul><p>Input and Feedback: Simultaneous transmission of neural commands from the user to the machine and feedback signals from the machine to the user. Example: A user controlling a robotic arm receives real-time sensory feedback (e.g., texture or weight) to adjust their grip.</p><p>Adaptive Learning: Real-time feedback helps AIH systems refine their responses, adapting to user needs dynamically. Example: AIH systems could fine-tune neural signal decoding to improve accuracy over time.</p><ul><li>Applications: Enhanced prosthetics with touch sensitivity. Immersive VR/AR systems with direct brain interaction. Advanced human-machine symbiosis for complex tasks like remote surgery or space exploration.</li><li>Challenges: Achieving ultra-low latency for real-time responsiveness. Ensuring safety and reliability in bidirectional neural communication.</li></ul><p>2. <strong>Universal Neural Protocols</strong></p><p>Standardized frameworks for neural signal communication to ensure interoperability across devices and platforms.</p><ul><li>Key Features:</li></ul><p>Cross-Compatibility: AIH systems from different manufacturers adhere to shared communication standards. Example: A BCI headset from one company seamlessly integrates with prosthetics or VR systems from another.</p><p>Dynamic Adaptation: Protocols account for neural variability across users and adapt to individual signal patterns. Example: A universal neural protocol enables quick calibration for new users or devices.</p><p>Open Source Development: Collaborative efforts to establish widely accepted standards. Example: An open-source consortium for neural protocols akin to USB or Bluetooth standards.</p><ul><li>Applications: Interoperable AIH ecosystems for healthcare, gaming, education, and industry. Seamless transitions between devices in multi-platform environments.</li><li>Challenges: Balancing standardization with innovation to prevent stifling advancements. Gaining consensus among stakeholders in diverse industries.</li></ul><p>3. <strong>AIH Networks</strong></p><p>Connected systems enabling collaborative human-machine networks for shared intelligence and problem-solving.</p><ul><li>Key Features:</li></ul><p>Collective Intelligence: Networks of AIH-enabled humans and machines share data, insights, and tasks in real-time. Example: Scientists collaborating on an AIH network to solve global challenges like pandemics or climate change.</p><p>Swarm Dynamics: Decentralized decision-making akin to swarm intelligence, where multiple agents contribute to a collective goal. Example: AIH networks coordinating disaster relief efforts with drones and robots in real time.</p><p>Knowledge Sharing: Neural data and insights are aggregated to train better AI models and improve system performance. Example: Federated learning across AIH devices creates more robust, generalized AI systems.</p><ul><li>Applications: Smart cities optimizing energy, traffic, and resource management. Collaborative innovation hubs where humans and AI co-develop solutions. Large-scale educational platforms powered by shared AIH insights.</li><li>Challenges: Managing the security and privacy of data shared across networks. Avoiding centralization or monopolization of AIH networks by a few entities.</li></ul><p>The future of AIH development is rich with potential but requires overcoming significant challenges to ensure ethical, practical, and inclusive adoption. By addressing concerns related to privacy, hardware limitations, and social impacts, AIH systems can unlock transformative capabilities for humanity.</p><p>Innovations like full duplex brain-machine interfaces, universal neural protocols, and AIH networks promise to drive the next wave of technological evolution, fostering seamless human-machine collaboration and collective intelligence. These advancements will not only redefine how humans interact with technology but also pave the way for a future where AIH serves as a catalyst for solving global challenges and enhancing the human experience.</p><h3>Epilogue</h3><p>Artificially Interlaced Humans (AIH) will redefine the human-machine relationship, marking a transformative step toward AGI. By seamlessly integrating BCIs, neural mapping, LLMs, and real-time function calling, AIH unlocks unprecedented human potential. It not only enhances our cognitive and physical abilities but also reshapes our societal structure and prepares humanity for the next chapter of evolution.</p><blockquote><em>Dawn of Artificially Interlaced Humans (AIH) will be prelude to Artificial General Intelligence (AGI) and is coming!</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/0*Un-ZzT1dotx8jB82" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b2aaacc37ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/technopreneurial-treatises/artificially-interlaced-humans-aih-0b2aaacc37ce">Artificially Interlaced Humans (AIH)</a> was originally published in <a href="https://medium.com/technopreneurial-treatises">Technopreneurial Treatises</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Configurability in SaaS]]></title>
            <link>https://medium.com/technopreneurial-treatises/building-configurability-in-saas-1701458e7dbc?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1701458e7dbc</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[application-configuration]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-design]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Sun, 11 Jun 2023 06:25:50 GMT</pubDate>
            <atom:updated>2023-06-11T06:25:50.646Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*9BbyEKeB2LxgpARF9AmPWg.png" /></figure><h3>Prologue</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/1*NGODsHfGSps_OIM_XFYc5g.png" /><figcaption>Every change breaks someone’s workflow. (credits: xkcd comics)</figcaption></figure><p>So, you have decided to build a data-driven Software as a Service (SaaS) start-up after reading my old article — <a href="https://blog.jaykmr.com/to-pivot-or-not-to-pivot-c07b20faf0b">To pivot or not to pivot</a> but after deciding on the business requirements of your application, you start contemplating what will be the right configurability of the software based on your requirements. You revisit the possible options for configurability, relook at the business requirements, and then, comes the problem:</p><h3>The Problem</h3><p>As you continue to build your new SaaS application and sell it, there is another critical aspect that demands your attention: building and managing configuration properly. The configuration of your application, including its technical and business settings, becomes crucial for ensuring the security, privacy, durability, and configurability of your SaaS.</p><p>In the following sections, we will explore the difficulties and importance of building application configuration correctly in the context of SaaS, providing insights and guidelines to help you navigate this complex landscape effectively.</p><h3>The Solution</h3><p>Configurability is a crucial requirement for any SaaS application, encompassing both technical and business needs. To address this, configurations are divided into two categories: technical configuration (referred to as the <em>application manifest</em>) and business configuration (referred to as <em>settings and preferences</em>). It is vital to keep both configurations separate from the code for security, privacy, durability, and ease of customization. Let’s explore each in detail:</p><h3>Application Manifest</h3><p>The application manifest consists of technical configurations that are specific to the application and may vary across different deployments, such as staging, production, or developer environments. It typically includes:</p><p>● Resource handles for databases, caches, and other supporting services.</p><p>● Credentials for external services like Amazon S3 or Twitter.</p><p>● Deploy-specific values like the canonical hostname.</p><p>According to the <a href="https://12factor.net/">12-factor app manifesto</a>, these configurations should be stored in the environment. The manifest should support versioning, not only for the application but also for the manifest itself, including the manifest schema and versioning.</p><p><strong>Guidelines</strong></p><p>Some of these guidelines are adopted from the <a href="https://12factor.net/">twelve-factor app</a> methodology.</p><p>● Configuration settings should be stored and maintained as close as possible to the environment they apply to.</p><p>Placing application settings near the application clarifies their association. From a security standpoint, these settings can only be accessed and modified within their corresponding environment. For production settings like connection strings and passwords, it is essential to limit access. Application-specific settings should reside alongside the code or in the root of the application, while platform-specific settings should be available at a higher level, such as environment variables or web server settings. Website-specific settings should not be accessible at the web server’s root.</p><p>● Configuration settings should contain only environment-specific settings.</p><p>To maintain simplicity and clarity, configuration files should only include environment-specific settings such as caching, logging, and connection strings. All other settings should be configurable within the application itself.</p><p>● Configuration settings, especially secrets, should not be stored under version control.</p><p>Storing environment-specific settings (e.g., passwords, connection strings, tokens) in version control is a security risk. These values should be set and stored as close to their respective environments as possible, following a “just-in-time” mindset. Better use <a href="https://docs.github.com/en/actions/security-guides/encrypted-secrets">Github’s encrypted secrets</a> or <a href="https://docs.gitlab.com/ee/ci/secrets/">Gitlab’s secrets</a>.</p><p>● There should be a single location for configuring application settings.</p><p>Application settings should be configured as close to the application as possible. Introducing multiple configuration locations leads to chaos and insecure maintenance.</p><p>● Configuration values should be automatically set during deployment.</p><p>To streamline the process of configuring multiple environments and settings, it is advisable to automate the configuration process during deployment. This ensures repeatability and reduces the likelihood of errors.</p><p>● Changing a configuration setting should not necessitate a new deployment.</p><p>Most often an application resource (for example, a web application) relies on a core resource (for example, a storage account). An application resource is dependent on the existence of this core resource and needs its settings to run properly. For example, a web application needs a storage account key to access a blob storage, or a frontend needs an URL and token address to access an API. Changes in the core resource and its settings shouldn’t result in a redeploy of the application resource, which relies on it. When an API has many unknown clients changing the URL shouldn’t impact these clients. This can be challenging but there are many solutions for it.</p><p><strong>Realization</strong></p><p>They can be more Platform-centric like settings for <a href="https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html">Cloudfoundry</a> or application-centric like <a href="https://www.ge.com/digital/documentation/predix-platforms/app-hub-configure-apphub.html">GE Predix Apphub Configuration</a>. For example, these are the common attribute sets for manifest for Cloudfoundry:</p><p>● Buildpack/Image</p><p>● Command</p><p>● Instances</p><p>● Memory quota</p><p>● Disk quota</p><p>● Health Check (endpoint, timeout and type — port, process, http)</p><p>● Metadata, path, and routes</p><p>● Environment Variables</p><p>● Services</p><p><strong>Architecture</strong></p><p>The application manifest configuration, which can be realized as the key-value store can be coupled with the service registry and service discovery while load balancing can be coupled with the reverse proxy router for the services (health-checking can be supported by either). Some of the tools for service configuration are:</p><p>● <a href="https://zookeeper.apache.org/">Apache Zookeeper</a></p><p>● <a href="https://www.consul.io/">Consul</a></p><p>● <a href="https://etcd.io/">Etcd</a></p><p>● <a href="https://github.com/Netflix/eureka">Eureka</a></p><p>The most used Consul provides first-class support for service discovery, health checking, and Key Value storage for configuration. Eureka only solves a limited subset of problems of health-checking, service registry, and discovery, expecting other tools such as ZooKeeper as a distributed key-value store to be used alongside. Etcd is the most lightweight and serves only as a strongly consistent configuration key-value store. Both Consul and Etcd are written in Golang while Zookeeper and Eureka are written in Java.</p><p><strong>Manifest Specification Formats</strong></p><p>The manifest can be specified on either YAML or JSON. One of the benefits of specifying in YAML is to share the configuration through <a href="https://yaml.org/spec/1.2.2/">YAML anchors and aliases</a>, which provides the ability to reference other data objects. With this referencing, it is possible to write recursive data in the YAML file. On the other hand, JSON has better serialization-deserialization support across languages and is more suited for API transport.</p><p>Apart from the manifest, these technical configurations can also be directly handled in a separate application like <a href="https://www.ge.com/digital/documentation/predix-platforms/app-hub-settings-microapp.html">Settings microapp from GE Predix</a>, but that is more suited to configure business settings and preferences, which is discussed in detail next.</p><h3>Settings and Preferences</h3><p>Settings and Preferences encompass the specific requirements of a business, catering to various levels such as tenants, applications, and users. These settings primarily include format settings like time format, currency format, and metric format, as well as internationalization and localization settings. Additionally, preference settings allow users to customize their dashboard display arrangement. It is advisable to store these settings in a datastore to ensure their persistence during platform and version upgrades, as well as their availability for cross-application and cross-user sharing.</p><p><strong>Guidelines</strong></p><p>To effectively manage Settings and Preferences, the following guidelines should be followed:</p><p>● Settings and Preferences should be stored and maintained in the datastore, ensuring their centralized management.</p><p>● Settings and Preferences should be able to be set in the application itself, allowing for customization.</p><p>● Settings and Preferences should be configurable at multiple levels i.e. tenant-specific, application-specific, and user-specific.</p><p>● Settings and Preferences should have standard defaults, initialized as the application or platform constants to ensure consistency.</p><p>● Settings and Preferences should be persisted cross-deployment and application versions to maintain continuity and avoid data loss.</p><p><strong>Realization</strong></p><p>They can be more application-centric like <a href="https://docs.djangoproject.com/en/4.2/ref/settings/">settings for Django Application</a> or application-centric like <a href="https://www.ge.com/digital/documentation/predix-platforms/app-hub-settings-microapp.html">GE Predix Microapp Settings</a>. For example, these can be the common settings based on the above:</p><p>● Timezone</p><p>● Country</p><p>● Locale</p><p>● Currency</p><p>● Units of Measurement</p><p>● Input and Output Formats (Date, DateTime)</p><p>● Separators (Thousand, Decimal)</p><p>● Symbols (Language, Currency)</p><p>● Themes (Links, Display)</p><p>● Display Arrangement and Ordering</p><p><strong>Architecture</strong></p><p>The preferences can be implemented as a three-layer hierarchy similar to <a href="https://man7.org/linux/man-pages/man1/chmod.1.html">read-write-execute settings for user-groups-others on Linux</a>.</p><p>We can have a similar set of actors in the system:</p><p>1. Admin</p><p>2. User</p><p>3. Groups</p><p>4. Others (default)</p><p>Similarly, we can have a similar set of principals in the system:</p><p>1. System (default)</p><p>2. Tenant</p><p>3. Application</p><p>We have the following actions on Settings and preferences in the system:</p><p>1. Read</p><p>2. Write</p><p>3. Delete</p><p>The permissions of the actors over the principal’s configuration will follow these permission-based restrictions, where R stands for Read, W for Write, and D for Delete :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zNYgx-3n0V6ShrTU" /><figcaption>Configuration Permission Model</figcaption></figure><p>For actors, Admin has the highest privileges and can read, write or delete the configuration for all except System, which holds default values. Users and user groups can only change their specific application settings and configurations. Anonymous Unauthenticated users can just read the application configurations. For principals, the application configuration will take priority over tenant configuration, and the tenant configuration will take priority over System configuration, which will be set of smart defaults. Here, priority implies an inheritance model, where the application will override tenant configuration and will inherit it, if it is not set locally. Similarly, tenants will override system configuration and will inherit it as it is, if the admin does not configure the tenants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vRrS2wFdfb-p_4v_yHNYIw.png" /><figcaption>SaaS Privilege-based Configuration Model</figcaption></figure><p>The ability to configure settings and preferences at different levels, such as tenant-specific, application-specific, and user-specific, provides a high degree of customization and personalization. This flexibility allows your application to cater to diverse user needs and preferences, enhancing the overall user experience.</p><h3>Epilogue</h3><p>As you continue your journey towards building a highly scalable and flexible system, it is crucial to emphasize the importance of following the above guidelines for building application configurability.</p><p>The importance of technical configuration becomes even more evident when considering the challenges associated with cloud enterprise software and SaaS solutions. With the adoption of microservices and a distributed architecture, the management of multiple servers, caches, and databases can become complex. Proper configuration management simplifies this process, allowing you to effectively allocate resources and optimize performance.</p><p>Furthermore, storing and maintaining settings and preferences (business configuration) in a datastore ensures their persistence across platform and version upgrades. This not only saves time and effort but also enables seamless sharing of configurations across different applications and users. Having standard defaults and initialization as the application or platform constants ensures consistency and ease of use. By adhering to these guidelines, you ensure that your application can adapt to varying requirements and scenarios.</p><p>In conclusion, by following the guidelines for building application configurability, you empower your SaaS solution with the necessary flexibility, adaptability, and scalability.</p><blockquote><em>Solve the problem once, use the solution everywhere!</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1701458e7dbc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/technopreneurial-treatises/building-configurability-in-saas-1701458e7dbc">Building Configurability in SaaS</a> was originally published in <a href="https://medium.com/technopreneurial-treatises">Technopreneurial Treatises</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Right Approach to Effective Code Reviews]]></title>
            <link>https://medium.com/technopreneurial-treatises/the-right-approach-to-effective-code-reviews-88a675469199?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/88a675469199</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <category><![CDATA[engineering-excellence]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Thu, 25 May 2023 19:02:02 GMT</pubDate>
            <atom:updated>2023-05-25T19:02:02.833Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*PeMyG4kC8cMgYtLjwjFN_A.png" /></figure><h3>Prologue</h3><p>So, you have inculcated the “right attitude” for software engineering after reading <a href="https://medium.com/technopreneurial-treatises/the-right-approach-to-software-engineering-57f0b0fbb8e">my old article — The Right Approach to Software Engineering</a> but you are working in a silo in a small team or a startup, churning a lot of code. You start wondering whether you are making the right architectural decisions, producing good-quality code, and properly, maintaining the software, that you are building. You often face the same set of operational issues after deploying, which makes you revisit your repository, relook at the code, check the code quality using code analyzers like <a href="https://go.codacy.com/code-analysis">Codacy</a> and <a href="https://www.sonarsource.com/products/sonarqube/">SonarQube</a>, and then, realize the problem:</p><h3>Problem</h3><p>You have been churning out poor-quality code, with the same set of design issues, inconsistent style, and bugs, all adding up to a lot of technical debt. Now, you want to improve your technical know-how, improve the software quality as well as reduce the technical debt of the code, you are churning out.</p><p><a href="https://en.wikipedia.org/wiki/Software_engineering">Software Engineers</a>, when working in silos end up producing poor-quality code and struggle with learning patterns and anti-patterns of software design. Without the right guidance and review of your common design issues, errors, and bugs, you end up making the same code quality mistakes again and again, which eventually adds to the <a href="https://en.wikipedia.org/wiki/Technical_debt">technical debt</a> and poor <a href="https://en.wikipedia.org/wiki/Software_maintenance">software maintainability</a>.</p><h3>Solution</h3><p>If you are working in a team, you should definitely do <strong><em>code reviews</em></strong> to improve both your own skills and the quality of the codebase and foster knowledge sharing and collaboration, contributing to a positive development culture.</p><p>Let’s understand what, why, and how of effective code reviews.</p><h4>What is code review?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*1h9f0vnXph1zQCae" /><figcaption>Code Mocking — An Engineering Tradition (credits: Dilbert comics)</figcaption></figure><p>Code review is a process in software development where one or more developers systematically examine and evaluate the code written by their peers. It involves reviewing the code for quality, correctness, adherence to coding standards, best practices, and overall maintainability. Code reviews are typically conducted before merging code changes into a shared codebase, aiming to catch bugs, improve code design, identify potential issues, and ensure that the code meets the requirements and expectations of the project. The goal of code review is to enhance the overall code quality, promote collaboration and learning within the development team, and ultimately deliver reliable and maintainable software.</p><h4>Why do code reviews?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/0*3a9i2aXv7ojAFPNk" /><figcaption>Wanna see the code (credits: xkcd comics)</figcaption></figure><p>Code reviews serve several important purposes in software development:</p><p>1. <strong>Bug Detection</strong>: Code reviews help identify bugs, logic errors, and other issues in the code before they reach production. Reviewers can catch mistakes that the original developer might have missed, leading to higher quality and more reliable software.</p><p>2. <strong>Knowledge Sharing and Learning</strong>: Code reviews provide an opportunity for developers to learn from each other. Reviewers can share their expertise, suggest improvements, and introduce new techniques or best practices. It promotes collaboration within the team and helps in spreading knowledge across the organization.</p><p>3. <strong>Code Quality and Consistency</strong>: Code reviews help maintain a high level of code quality and consistency throughout the codebase. By following coding standards, best practices, and design patterns, reviewers can ensure that the codebase is maintainable, readable, and adheres to the established guidelines.</p><p>4. <strong>Continuous Improvement</strong>: Code reviews foster a culture of continuous improvement. Through constructive feedback and discussions, developers can refine their coding skills, enhance their understanding of the project, and identify areas where they can improve their code.</p><p>5. <strong>Team Building and Accountability</strong>: Code reviews encourage collaboration and team building within the development team. It creates a shared responsibility for the codebase, as developers review each other’s work and provide feedback. It also helps establish a sense of accountability, as developers are held responsible for the quality and reliability of their code.</p><p>Overall, code reviews contribute to better software quality, improved developer skills, and a more cohesive and efficient development process.</p><blockquote><em>It’s better to succeed together than to fail alone.</em></blockquote><h4>How to comment the code?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*zN_XgrNKdxnFoLY6" /><figcaption>Bad code (credits: xkcd comics)</figcaption></figure><p>Commenting code is an essential practice in software development as it helps improve code readability, maintainability, and understanding. Here are some guidelines for effective code commenting:</p><p>1. <strong>Use Clear and Concise Comments</strong>: Write comments that are easy to understand and concise. Avoid ambiguous or vague comments that can lead to confusion. Comment only where necessary and focus on explaining the intent or purpose of the code.</p><p>2. <strong>Comment Purpose and High-Level Logic</strong>: Comment on the overall purpose and functionality of the code block or function. Explain the high-level logic and any important decisions made during the implementation. This helps other developers understand the code’s intent without diving into the implementation details.</p><p>3. <strong>Document Complex or Non-Obvious Code</strong>: If the code contains complex algorithms, non-trivial logic, or intricate business rules, provide comments to explain how it works. This helps other developers, including your future self, comprehend the code more easily.</p><p>4. <strong>Use Self-Explanatory Variable and Function Names</strong>: Naming variables and functions descriptively can eliminate the need for excessive comments. When code is self-explanatory, it becomes easier to understand without relying heavily on comments.</p><p>5. <strong>Comment Tricky or Non-Standard Code</strong>: If you encounter code that deviates from standard practices or uses workarounds, provide comments to explain the reason behind it. This helps prevent others from mistakenly considering it as an error or making unnecessary changes.</p><p>6. <strong>Update Comments with Code Changes</strong>: When you modify code, ensure that you update the corresponding comments to reflect the changes accurately. Outdated comments can be misleading and cause confusion.</p><p>7. <strong>Avoid Redundant Comments</strong>: Avoid commenting on obvious code or duplicating information that is already apparent from the code itself. Redundant comments can clutter the code and make it harder to read.</p><p>8. <strong>Use Comment Styles Consistently</strong>: Follow consistent comment styles and formatting conventions throughout the codebase. This helps maintain a unified and organized appearance.</p><p>Remember that comments should complement the code and provide valuable information that enhances understanding. Well-placed and meaningful comments can significantly improve the readability and maintainability of your codebase.</p><blockquote><em>There are only two hard things in Computer Science: cache invalidation and naming things.</em></blockquote><h4>How can it help me as a developer to do code reviews of other developers?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*MWAuYpm5CBT5xNmM" /><figcaption>Code Quality (credits: xkcd comics)</figcaption></figure><p>Performing code reviews of other developers’ work can greatly benefit you as a developer in several ways:</p><p>1. <strong>Enhancing Code Quality</strong>: Code reviews provide an opportunity to identify and address potential issues, bugs, or inefficiencies in the codebase. By reviewing other developers’ code, you can catch mistakes or suggest improvements, leading to higher code quality.</p><p>2. <strong>Learning Opportunities</strong>: Code reviews expose you to different coding styles, techniques, and problem-solving approaches. You can learn from the strengths and weaknesses of others’ code, gaining insights into new patterns, best practices, and innovative solutions.</p><p>3. <strong>Collaboration and Teamwork</strong>: Code reviews promote collaboration and foster a sense of shared responsibility within the development team. Through the review process, you can engage in constructive discussions, share knowledge, and work together to improve the overall codebase.</p><p>4. <strong>Consistency and Standards</strong>: Code reviews help maintain consistency and adherence to coding standards across the project. By reviewing code, you can ensure that the codebase follows established guidelines, naming conventions, formatting rules, and other project-specific requirements.</p><p>5. <strong>Knowledge Sharing</strong>: Code reviews facilitate knowledge sharing among team members. As you review the code, you can provide explanations, suggest alternative approaches, and offer guidance. This sharing of knowledge benefits both the developer whose code is being reviewed and the reviewer.</p><p>6. <strong>Identifying Patterns and Anti-patterns</strong>: Code reviews allow you to identify recurring patterns or anti-patterns in the codebase. By recognizing such patterns, you can propose refactoring opportunities, suggest code reuse, or identify areas where design patterns can be applied.</p><p>7. <strong>Error Prevention</strong>: Code reviews act as a preventive measure against introducing bugs or issues into the codebase. By thoroughly reviewing code, you can identify potential pitfalls, evaluate edge cases, and spot logic errors before they reach the production environment.</p><p>8. <strong>Continuous Improvement</strong>: Code reviews promote a culture of continuous improvement within the development team. By providing constructive feedback and suggestions, you contribute to the growth of individual developers and the overall team’s skills.</p><p>By actively participating in code reviews, you can contribute to a positive development culture and improve both your own skills and the quality of the codebase.</p><blockquote><em>The more you help people, the stronger you get.</em></blockquote><h4>How should I do code reviews? How to learn it?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/0*QZsunCYtj5vNlKXD" /><figcaption>Code Quality 2 (credits: xkcd comics)</figcaption></figure><p>To effectively conduct code reviews, consider the following steps and tips:</p><p>1. <strong>Set clear expectations</strong>: Establish guidelines and standards for code reviews within your team or organization. Define the goals of code reviews, the scope of review, and the expected timeline.</p><p>2. <strong>Review the code independently</strong>: Start by examining the code on your own, without any distractions. Understand the purpose, functionality, and design choices made in the code.</p><p>3. <strong>Follow a checklist</strong>: Use a checklist or a set of predefined criteria to ensure thoroughness and consistency in your code reviews. This can include aspects like code style, readability, performance, security, error handling, and adherence to best practices. For example, check for <a href="https://refactoring.guru/refactoring/smells">code smells</a> and then, resolve <a href="https://refactoring.guru/refactoring/smells">code smells</a> using <a href="https://refactoring.guru/refactoring/techniques">refactoring techniques</a>.</p><p>4. <strong>Provide constructive feedback</strong>: When you identify areas for improvement, offer clear and specific feedback. Explain the issues you’ve found and suggest possible solutions or alternative approaches.</p><p>5. <strong>Prioritize and categorize feedback</strong>: Differentiate between critical issues that need immediate attention and minor suggestions for improvement. Organize your feedback to help the developer understand the importance and impact of each comment.</p><p>6. <strong>Be objective and impartial</strong>: Focus on the quality of the code and adherence to established standards, rather than personal preferences. Base your feedback on objective criteria and best practices.</p><p>7. <strong>Balance between nitpicking and high-level feedback</strong>: While it’s important to catch small issues, also provide feedback on the overall design, architecture, and problem-solving approach. Find the right balance between detailed suggestions and high-level guidance.</p><p>8. <strong>Foster collaboration and learning</strong>: Code reviews should be seen as an opportunity for growth and knowledge sharing. Encourage open discussions, ask questions, and be receptive to different perspectives. Promote a culture of continuous learning and improvement.</p><p>9. <strong>Document your feedback</strong>: Keep a record of the feedback you provide, either through comments in the code review tool or in a separate document. This helps track progress and allows developers to refer back to the feedback.</p><p>10. <strong>Learn from others</strong>: Participate in code reviews of your peers and learn from their feedback. Observe how experienced reviewers provide suggestions and explanations. Seek feedback on your own code to enhance your skills and understanding.</p><p>11. <strong>Practice and seek feedback</strong>: The more you engage in code reviews, the better you’ll become. Practice regularly and seek feedback from both developers and reviewers to improve your code review skills.</p><p>12. <strong>Learn from resources and training</strong>: Explore online resources, articles, books, and courses on code review best practices. Some organizations also offer internal training or mentorship programs to enhance code review skills. Take advantage of these resources to deepen your knowledge.</p><p>By following these steps and continuously learning and practicing from the experience, you can become an effective code reviewer.</p><blockquote><em>Practice makes a man perfect.</em></blockquote><h4>How to convey messages politely in code reviews?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*DKO7KM40tBJXM1V5" /><figcaption>Code Quality 3 (credits: xkcd comics)</figcaption></figure><p>When conveying messages politely in code reviews, it’s important to consider the following guidelines:</p><p>1. <strong>Use a friendly and constructive tone</strong>: Frame your feedback in a positive and encouraging manner. Instead of simply pointing out flaws, offer suggestions for improvement.</p><p>2. <strong>Start with positive feedback</strong>: Begin by acknowledging the strengths or good aspects of the code. This helps create a positive atmosphere and shows appreciation for the developer’s efforts.</p><p>3. <strong>Be specific and objective</strong>: Clearly articulate the issues you’ve identified or the improvements you suggest. Use specific examples from the code to illustrate your points. Avoid vague or general statements.</p><p>4. <strong>Focus on the code, not the developer</strong>: Critique the code itself rather than to criticize the developer personally. Remember that the goal is to improve the code, not to attack the individual who wrote it.</p><p>5. <strong>Offer alternatives or solutions</strong>: Instead of simply pointing out problems, provide alternative approaches or solutions. This demonstrates your willingness to help and encourages collaboration.</p><p>6. <strong>Use constructive language</strong>: Frame your feedback in a way that promotes learning and growth. Use phrases like “Have you considered…” or “What if we tried…” to encourage dialogue and exploration of different options.</p><p>7. <strong>Be respectful and empathetic</strong>: Keep in mind that behind every line of code is a developer who invested time and effort. Show empathy and respect for their work while providing suggestions for improvement.</p><p>8. <strong>Provide context and explanations</strong>: When suggesting changes or improvements, explain the reasoning behind your suggestions. Help the developer understand why a certain approach may be more beneficial.</p><p>9. <strong>Focus on the bigger picture</strong>: Consider the overall goals of the project and the team. Align your feedback with those goals and emphasize how the suggested changes contribute to the project’s success.</p><p>10. <strong>Follow up with support</strong>: Offer assistance and clarification if the developer has questions or needs further guidance. Engage in a constructive dialogue to ensure that the feedback is well understood.</p><p>By conveying messages politely and constructively, you create a positive and collaborative environment for growth and development.</p><blockquote><em>There is a very thin line between hand-holding and spoon-feeding. Spoon feed an infant, but hand hold an adult.</em></blockquote><h3>Epilogue</h3><p>So, to be an effective software engineer, it is necessary to be an effective code reviewer and also, get your code reviewed. In quality control, <a href="https://www.openriskmanual.org/wiki/Four_Eyes_Principle">Four competent eyes</a> are always better than two. After all, software engineering is a collaborative and creative learning process, not a siloed labor.</p><blockquote><em>Being a great engineer is all about having the right attitude.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88a675469199" width="1" height="1" alt=""><hr><p><a href="https://medium.com/technopreneurial-treatises/the-right-approach-to-effective-code-reviews-88a675469199">The Right Approach to Effective Code Reviews</a> was originally published in <a href="https://medium.com/technopreneurial-treatises">Technopreneurial Treatises</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Picking the Event Store for Event Sourcing]]></title>
            <link>https://medium.com/technopreneurial-treatises/picking-the-event-store-for-event-sourcing-988246a896bf?source=rss-5c7900bcf0f------2</link>
            <guid isPermaLink="false">https://medium.com/p/988246a896bf</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[event-driven-systems]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[software-design]]></category>
            <category><![CDATA[event-driven-architecture]]></category>
            <dc:creator><![CDATA[Jayanth Kumar]]></dc:creator>
            <pubDate>Sun, 21 May 2023 15:59:50 GMT</pubDate>
            <atom:updated>2023-05-21T16:06:59.942Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ViRXr_dJpXcHxsit05d7Sw.png" /></figure><h3>Prologue</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Oh7GKRuGRbKuXT-P" /><figcaption>Building event-driven architecture</figcaption></figure><p>So, you have decided to go the event-driven route of building your enterprise application using the event-sourcing paradigm after reading my old article — <a href="https://blog.jaykmr.com/architecting-event-driven-systems-the-right-way-1dd7f4e63f96">Architecting Event-driven Systems the right way</a> but for deciding on the core of your application — the datastore, you start contemplating which will be the right datastore for your architecture based on your requirements. You revisit the possible database choices, relook at the business requirements, and then, comes the problem:</p><h3>Problem</h3><p>There are multiple requirements for Event Store and thus, different database strategies for using event sourcing for such requirements. How can you ahead and choose the right database based on the event-sourcing requirement?</p><p>Before we dive deep into the requirements, let’s go through the basic terms used in event sourcing.</p><h3>Concepts</h3><p><strong>State</strong> — A state is a description of the status of a system waiting to execute a transition.</p><p><strong>Transition</strong> — A transition is a change from one state to another. A transition is a set of actions to execute when a condition is fulfilled or an event is received.</p><p><strong>Domain Event </strong>— The entity that drives the state changes in the business process.</p><p><strong>Aggregates</strong> — Cluster of domain objects that can be treated as a single unit, modeling a number of rules (or invariants) that always should hold in the system. Can also, be called “Event Provider” as “Aggregate” is really a domain concept and an Event Storage could work without a domain.</p><p><strong>Aggregate Root</strong> — Aggregate Root is the mothership entity inside the aggregate controlling and encapsulating access to its members in such a way as to protect its invariants.</p><p><strong>Invariant</strong> — An invariant describes something that must be true within the design at all times, except during a transition to a new state. Invariants help us to discover our Bounded Context.</p><p><strong>Bounded Context</strong> — A Bounded Context is a system boundary designed to solve a particular domain problem. The bounded context groups together a model that may have 1 or many objects, which will have invariants within and between them.</p><h3>Requirements</h3><p>1. <strong>Sequential Durable Write</strong> — Be able to store state changes as a sequence of events, chronologically ordered.</p><p>2. <strong>Domain Aggregate Read</strong> — Be able to read events of individual aggregates, in the order they persisted.</p><p>3. <strong>Sequential Read</strong> — Be able to read all events, in the order they were persisted.</p><p>4. <strong>Atomic Writes</strong> — Be able to write a set of events in one transaction, either all events are written to the event store or none of them are.</p><h3>Comparison of Datastores</h3><p>Let’s walk through different database types and dive deep into how they will support the above requirements.</p><p><strong>Relational Database</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/0*GpBblzE13GFkfG0y" /><figcaption>Event Store Implementation in Relational Database</figcaption></figure><p>In a relational database, event sourcing can be implemented with only two tables, one to store the actual Event Log, storing one entry per event in this table and the other to store the Event Sources. The event itself is stored in the [Data] column. The event is stored using some form of serialization, for the rest of this discussion the mechanism will be assumed to be built-in serialization although the use of the <a href="https://en.wikipedia.org/wiki/Memento_pattern">memento pattern</a> can be highly advantageous.</p><p>A version number is also stored with each event in the Events Table as an auto-incrementing integer. Each event that is saved has an incremented version number. The version number is unique and sequential only within the context of a given Event Source (aggregate). This is because Aggregate Root boundaries are consistency boundaries. On the other hand, Sequence, the other auto-incrementing integer is also, unique and sequential and stores the global sequence of events based on TimeStamp.</p><p>The [EventSourceId] column is a foreign key that should be indexed; it points to the next table which is the Event Sources table.</p><p>The Event Sources table is representing the event source provider (aggregates) currently in the system, every aggregate must have an entry in this table. Along with the identifier, there is a denormalization of the current version number. This is primarily an optimization as it could be derived from the Events table but it is much faster to query the denormalization than it would be to query the Events table directly. This value is also used in the optimistic concurrency check. Also included is a [Type] column in the table, which would be the fully qualified name of the type of event source provider being stored.</p><p>To look up all events for an event source provider, the query will be:</p><pre>SELECT Id, TimeStamp, Name, Version, EventSourceId, Sequence, Data FROM Events<br>  WHERE EventSourceId = :EventSourceId ORDER BY Version ASC;</pre><p>To insert a new event for a given event source provider, the query will be:</p><pre>BEGIN;<br>currentVersion := SELECT MAX(version) FROM Events<br>  WHERE EventSourceId = :EventSourceId;<br>currentSequence := SELECT MAX(Sequence) FROM Events;<br><br>INSERT INTO Events(TimeStamp, Name, Version, EventSourceId, Sequence, Data) <br>  VALUES (NOW(),:Name, :currentVersion+1, :EventSourceId, :currentSequence+1, :Data); <br>UPDATE EventSources SET Version = currentVersion+1 WHERE EventSourceId = :EventSourceId;<br>COMMIT;</pre><p><strong>Key-Value Store</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZvtuYZEkmTgdGYX3" /><figcaption>Event Store Implementation in Key-Value Store</figcaption></figure><p>In a key-value store, an event can be modeled by constructing the key as a combination of the aggregate id and the version number. The serialized event data can be stored as the corresponding value. This method of constructing the key enables the chronological storage of events for a specific aggregate. To access data from the key-value store, knowledge of the key is required. It might be feasible to retrieve events for a particular aggregate by knowing only its aggregate id and incrementing the version number until a key is not found. However, a challenge arises when attempting to retrieve events for any aggregate, as no portion of the key is known. Consequently, it becomes impossible to retrieve these events in the order they were stored. Additionally, it’s important to note that many key-value stores lack transactional capabilities.</p><p><strong>Document Database</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RLPfttCWgPvUn-W8" /><figcaption>Event Store Implementation in Document Database</figcaption></figure><p>Using a document database allows for the storage of all events associated with an aggregate within a single document, or alternatively, each event can be stored as an individual document. To maintain chronological order, a version field can be included in the document to store the events. When all events pertaining to an aggregate are stored in the same document, a query can be executed to retrieve them in the order of their version numbers. As a result, the returned events will maintain the same order as they were stored.</p><p>However, if multiple events from different aggregates are stored within a single document, it becomes challenging to retrieve them in the correct sequence. One possible approach is to retrieve all events and subsequently sort them based on a timestamp, but this method would be inefficient. Thankfully, most document databases support ACID transactions within a document, enabling the writing of a set of events within a single transaction.</p><p><strong>Column Oriented Database</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PftxnuaIL-PzNEXD" /><figcaption>Event Store Implementation in Column-oriented Database</figcaption></figure><p>In a column-oriented database, events can be stored as columns, with each row containing all events associated with an aggregate. The aggregate id serves as the row key, while the events are stored within the columns. Each column represents a key-value pair, where the key denotes the version number and the value contains the event data. Adding a new event is as simple as adding a new column, as the number of columns can vary for each row.</p><p>To retrieve events for a specific aggregate, the row key (aggregate id) must be known. By ordering the columns based on their keys, the events can be collected in the correct order. Writing a set of events in a row for an aggregate involves storing each event in a new column. Many column-oriented databases support transactions within a row, enabling the writing process to be performed within a single transaction.</p><p>However, similar to document databases, column-oriented databases face a challenge when attempting to retrieve all events in the order they were stored. There is no straightforward method available for achieving this outcome.</p><h3>Comparison of Specific Datastore Implementations</h3><p><strong>Postgres</strong></p><p>While Postgres is commonly known as a relational database management system, it offers features and capabilities that make it suitable for storing events in an Event Sourcing architecture.</p><p>Postgres provides a flexible data model that allows you to design a schema to store events efficiently. In Event Sourcing, you typically need an Events table that includes fields such as a global sequence number, aggregate identifier, version number per aggregate, and the payload data (event) itself. By designing the schema accordingly, you can easily write queries that efficiently perform full sequential reads or search for all events related to a specific event source (aggregate) ID.</p><p>Postgres also offers transactional support, ensuring ACID (Atomicity, Consistency, Isolation, Durability) guarantees. This means that events can be written and read in a transactional manner, providing data integrity and consistency.</p><p>The append-only policy, a fundamental aspect of Event Sourcing, can be enforced in Postgres by avoiding UPDATE or DELETE statements on event records. This way, events are stored chronologically as new rows are inserted into the table.</p><p>Additionally, Postgres is a mature technology with wide adoption and a strong ecosystem of tools and libraries. It provides a range of performance optimization techniques, indexing options, and query optimization capabilities, enabling efficient retrieval and processing of events.</p><p>While Postgres may not offer some of the specialized features specific to event-sourcing databases, with careful design and optimization, it can serve as a reliable and scalable event store for Event Sourcing architectures.</p><p><strong>Cassandra</strong></p><p>Cassandra can be used as an event store for Event Sourcing, but there are some considerations to keep in mind.</p><p>Cassandra is a highly scalable and distributed NoSQL database that offers features such as peer-to-peer connections and flexible consistency options. It excels in handling large amounts of data and providing high availability.</p><p>However, when it comes to guaranteeing strict sequencing or ordering of events, Cassandra may not be the most efficient choice. Cassandra’s data model is based on a distributed and partitioned architecture, which makes it challenging to achieve strong sequencing guarantees across all nodes in the cluster. Ensuring strict ordering typically requires leveraging Cassandra’s lightweight transaction feature, which can impact performance and should be used judiciously as per the documentation’s recommendations.</p><p>In an Event Sourcing scenario where appending events is a common operation, relying on lightweight transactions for sequencing events in Cassandra may not be ideal due to the potential performance cost.</p><p>While Cassandra may not provide native support for strong event sequencing guarantees, it can still be used effectively as an event store by leveraging other mechanisms. For example, you can include a timestamp or version number within the event data to order events chronologically during retrieval.</p><p>Additionally, Cassandra’s scalability and fault-tolerance features make it suitable for handling large volumes of events and ensuring high availability for event-driven architectures.</p><p><strong>MongoDB</strong></p><p>MongoDB, a widely used NoSQL document database, offers high scalability through sharding and schema-less storage. It allows easy storage of events due to its schema-less nature.</p><p>MongoDB’s flexibility and schema-less nature allow for easy storage of event data. You can save events as documents in MongoDB, with each document representing an individual event. This makes it straightforward to store events and their associated data without the need for predefined schemas.</p><p>To ensure the ordering and sequencing of events, you can include a timestamp or version number within each event document. This enables you to retrieve events in the order they were stored, either by sorting on the timestamp or using the version number.</p><p>MongoDB also provides high scalability through sharding, allowing you to distribute your event data across multiple servers to handle large volumes of events.</p><p>However, there are certain considerations when using MongoDB as an event store. MongoDB traditionally supported only single-document transactions, which could limit the atomicity and consistency of operations involving multiple events. However, MongoDB has introduced support for multi-document transactions, which can help address this limitation.</p><p>Another challenge with MongoDB as an event store is the lack of a built-in global sequence number. To achieve a full sequential read of all events, you would need to implement custom logic to maintain the sequence order.</p><p>Additionally, MongoDB’s ad hoc query capabilities and scalability make it a strong choice for event storage. However, transactional support and event-pushing performance may require careful consideration and optimization.</p><p><strong>Kafka</strong></p><p>Kafka is often mentioned in the context of Event Sourcing due to its association with the keyword “events.” Using Kafka as an event store for Event Sourcing is a topic of debate and depends on specific requirements and trade-offs. Kafka’s design as a distributed streaming platform makes it a popular choice for building event-driven systems, but there are considerations to keep in mind.</p><p>Kafka’s core concept revolves around the log-based storage of events in topics, providing high throughput, fault tolerance, and scalable message processing. It maintains an immutable, ordered log of events, which aligns well with the append-only nature of event sourcing.</p><p>However, using Kafka as an event store for Event Sourcing introduces some challenges. One key consideration is the trade-off between storing events for individual aggregates in a single topic or creating separate topics for each aggregate. Storing all events in a single topic allows full sequential reads of all events but makes it more challenging to efficiently retrieve events for a specific aggregate. On the other hand, storing events in separate topics per aggregate can optimize retrieval for individual aggregates but may pose scaling challenges due to the design of topics in Kafka.</p><p>To address this, various strategies can be employed. For example, you can create a topic per aggregate and use partitioning to distribute the events across partitions. However, ensuring an even distribution of entities across partitions and handling the restoration of global event order can introduce additional complexities.</p><p>Another consideration is access control and security. When using Kafka as an event store, it’s important to manage access to the Kafka instance to ensure data privacy and integrity since anyone with access can read the stored topics.</p><p>Furthermore, it’s worth noting that using Kafka as an event store deviates from the traditional Event Sourcing principle of storing events before publishing them. With Kafka, storing and publishing events are not separate steps, which means that if a Kafka instance fails during the process, events may be lost without knowledge.</p><p><strong>EventStore</strong></p><p>“EventStore” is a purpose-built database that aligns well with the principles and requirements of Event Sourcing. It is a popular option written in .NET and is well-integrated within the .NET ecosystem.</p><p>Event Store, as the name suggests, focuses on efficiently storing and managing events. It offers features and capabilities that are well-suited for event-driven architectures and Event Sourcing implementations.</p><p>One key feature of Event Store is its ability to handle projections or event-handling logic within the database itself. This allows for efficient querying and processing of events, enabling developers to work with events in a flexible and scalable manner.</p><p>Event Store provides the necessary mechanisms to store events in an append-only fashion, ensuring that events are immutable and ordered. It allows you to store events for different aggregates or entities in a single stream, making it easy to retrieve events for a specific aggregate in the order they were stored.</p><p>Additionally, Event Store offers strong transactional support, allowing for ACID (Atomicity, Consistency, Isolation, Durability) guarantees when working with events. This ensures that events are persisted reliably and consistently, maintaining data integrity.</p><p>Event Store also provides features for event versioning, enabling compatibility and evolution of event schemas over time. This is important for maintaining backward compatibility and handling changes to event structures as the application evolves.</p><p>Furthermore, Event Store typically offers built-in features for event publishing and event subscription mechanisms, facilitating event-driven communication and integration within an application or across microservices.</p><p>However, a key feature of “EventStore” is that projection (or event handling) logic is placed and executed within the Event Store itself using Javascript. While this is a tempting proposition, it diverges from our view that the Event Store should store events, and that projection logic should be handled by the consumers themselves. This allows us a greater degree of flexibility over how to handle our events and not being limited to the functionality of Javascript logic available in the “EventStore” database.</p><p><strong>Redis Streams</strong></p><p>Redis Streams differs from traditional Redis Pub/Sub and functions more like an append-only log file. It shares conceptual similarities with Apache Kafka.</p><p>Redis Streams allow you to append new events to a stream, ensuring that they are ordered and stored sequentially. Each event in the stream is associated with a unique ID, providing a way to retrieve events based on their order of arrival. Additionally, Redis Streams support multiple consumers, enabling different components or services to consume events from the same stream.</p><p>When using Redis Streams as an event store, you can store event data along with any necessary metadata. This allows you to capture the essential details of an event, such as the event type, timestamp, and data payload. By leveraging the features provided by Redis Streams, you can efficiently publish, consume, and process events in a scalable manner.</p><p>It’s important to note that while Redis Streams offer a convenient and performant solution for event storage, there are considerations to keep in mind. For example, ensuring data durability and persistence may require additional configuration and replication mechanisms. Additionally, access control and security measures should be implemented to safeguard the event data stored in Redis Streams.</p><h3>Epilogue</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/0*JVQfS3h0DYjB19xi" /><figcaption>Comparison of Datastores across Event Store Requirements</figcaption></figure><p>In conclusion, each data store has its strengths and limitations for Event Sourcing. It is essential to consider factors such as scalability, consistency, sequencing, transactionality, and query support when selecting a suitable data store for an event-sourced system.</p><blockquote><em>There Ain’t No Such Thing As A Free Lunch.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=988246a896bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/technopreneurial-treatises/picking-the-event-store-for-event-sourcing-988246a896bf">Picking the Event Store for Event Sourcing</a> was originally published in <a href="https://medium.com/technopreneurial-treatises">Technopreneurial Treatises</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>