<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Coder Legion - Recent posts tagged sovereigntech</title>
<link>https://coderlegion.com/tag/sovereigntech</link>
<description>Powered by Question2Answer</description>
<item>
<title>🚀 SHIPPED: The Stateless Feedback Substrate (v1.0)</title>
<link>https://coderlegion.com/22831/shipped-the-stateless-feedback-substrate-v1-0</link>
<description>&lt;p&gt;Most &quot;user feedback&quot; plugins are just thinly veiled surveillance scripts. They inject heavy tracking pixels, log cursor movement, ship raw database telemetry to centralized SaaS clouds, and create a massive compliance liability.&lt;/p&gt;
&lt;p&gt;We refused to build that way.&lt;/p&gt;
&lt;p&gt;Today, my team lifted the code freeze on the Pocket Portfolio Feedback Substrate—a stateless, local-first feedback engine engineered for absolute data sovereignty.&lt;/p&gt;
&lt;p&gt;Here is the exact technical blueprint of how we solved the user-telemetry paradox on the write-path:&lt;/p&gt;
&lt;p&gt;🔹 &lt;strong&gt;Zero-Telemetry Trigger Logic&lt;/strong&gt;&lt;br&gt;
100% client-side eligibility validation. Zero telemetry is shipped on navigation just to determine if a user should see the modal.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-typescript&quot;&gt;// Local-First State Machine
const visitGate = localStorage.getItem('pp_dash_visits');
if (visitGate &amp;amp;&amp;amp; JSON.parse(visitGate).count &amp;gt; 5) {
  mountFeedbackSubstrate();
}

&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;🔹 &lt;strong&gt;Deterministic Privacy (The HMAC Decoupling)&lt;/strong&gt;&lt;br&gt;
To decouple telemetry metadata from actual user records, identity on the vault/event store uses a strict cryptographic barrier:&lt;br&gt;
&lt;code&gt;anonUserHash = HMAC-SHA256(uid, pepper)&lt;/code&gt;&lt;br&gt;
Raw user IDs and emails never touch the analytics collections. The &lt;code&gt;FEEDBACK_ANON_PEPPER&lt;/code&gt; remains locked on our server-side secure environment variables.&lt;/p&gt;
&lt;p&gt;🔹 &lt;strong&gt;Dual-Scrub Sanitization&lt;/strong&gt;&lt;br&gt;
Data is sanitized client-side before submission, and scrubbed again server-side on the API write-path. If a user accidentally pastes sensitive PII or raw transaction keys, our regex/entropy engine strips it down to anonymous context strings before it hits persistence.&lt;/p&gt;
&lt;p&gt;🔹 &lt;strong&gt;Restricted Server-Only Write Paths&lt;/strong&gt;&lt;br&gt;
We bypassed client-direct database writes. All submissions go through &lt;code&gt;POST /api/feedback/submit&lt;/code&gt; using the Firebase Admin SDK. The public &lt;code&gt;firestore.rules&lt;/code&gt; explicitly block all client-side write access:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-javascript&quot;&gt;match /feedbackSubmissions/{document} {
  allow read: if request.auth.token.admin == true;
  allow write: if false; // Server-side SDK writes only
}

&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;🔹 &lt;strong&gt;Synchronous P0 Escalation&lt;/strong&gt;&lt;br&gt;
A client reporting a critical, broken UI state (P0) triggers an immediate bypass of standard curation queues. Our API route parses the severity on-the-fly and fires a direct webhook payload alongside a verified Resend transactional dispatch straight to &lt;code&gt;*Emails are not allowed*&lt;/code&gt; for immediate triage.&lt;/p&gt;
&lt;p&gt;🔹 &lt;strong&gt;Static Compilation of Featured Receipts&lt;/strong&gt;&lt;br&gt;
Our public landing pages (&lt;code&gt;/&lt;/code&gt; and &lt;code&gt;/open&lt;/code&gt;) never query the live feedback database. Instead, they load from &lt;code&gt;featuredReceipts&lt;/code&gt;. When our team promotes a submission inside &lt;code&gt;/admin/analytics&lt;/code&gt;, we compile a sanitized, static excerpt to the public CMS. No leaks, no trace parameters, and no connection back to the &lt;code&gt;sourceSubmissionId&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The code is compiled, the rules are deployed, and the pipeline is officially live. No trackers, no third-party cookies, and no telemetry creep.&lt;/p&gt;
&lt;p&gt;If you're on our dashboard, you can force-mount the substrate and audit the network payload using &lt;code&gt;?showFeedbackModal=true&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Your Data. Your Device. Your Rules.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;#LocalFirst #SelfSovereignIdentity #EdgeComputing #SovereignTech #TypeScript&lt;/strong&gt;&lt;/p&gt;
</description>
<category>Articles</category>
<guid isPermaLink="true">https://coderlegion.com/22831/shipped-the-stateless-feedback-substrate-v1-0</guid>
<pubDate>Fri, 17 Jul 2026 08:05:00 +0000</pubDate>
</item>
</channel>
</rss>