Concepts
Architectural commitments, R&D, and the frameworks Hussh decisions run on.
68 pages
- Public vs Private Surface MapSVG two-column public-vs-private surface map. When-in-doubt rule = private.
- Sell the Wall — Decision FlowMermaid flowchart of Sell the Wall RSI-based decision: overbought → calls, oversold → puts, neutral → hold. All premium DRIP-ON. Assignment triggers auto-repurchase to protect Iron Rule #1.
- Sell the Wall — RSI-based options overlay for Fund AFund A's mechanical RSI-based options overlay. Sell covered calls when Alpha Bets 27 names are overbought (RSI > 60-70+); sell cash-secured puts when oversold (RSI < 30-40+). All premium reinvested via DRIP-ON. Share-accumulation engine, not income fund.
- Seven GDP Pillars — Sector GridSVG seven-cell sector grid for the Seven GDP Pillars — the structurally indispensable categories Alpha Bets 27 sources from. Pillar VII (physical infrastructure) accented in sage as the critical foundation.
- Seven GDP Pillars — Sector UniverseSVG sector grid of the seven GDP pillars: Tech, Energy, Healthcare, Consumer, Financials, Industrials, and Critical Physical Infra (the recently-articulated 7th pillar, oxblood-banded). Universe for Alpha Bets 27.
- Signature Vault — user-owned signature pattern in OneUser-owned signature pattern in One. Stored AES-256-GCM with Secure Enclave biometric; consent-gated via Kai/Nav; cryptographic attestation block on every use (SHA-256 hash, nonce, UTC timestamp, signing platform); full audit in Transparency Log. "Sign once, use everywhere."
- Signature Vault Flow SequenceMermaid sequence of Signature Vault flow: biometric → ephemeral envelope → attestation → Transparency Log.
- T-Bill Float Engine — Three Jobs One PoolSVG visual of the T-Bill Float Engine — 22% reserve doing three jobs simultaneously: yield, CSP collateral, constitutional safety floor.
- T-Bill Float Engine — three jobs, one poolFund A's 22% T-Bill reserve doing three jobs: risk-free yield, cash-secured put collateral, constitutional safety floor. Berkshire-float analogy.
- Three-Layer ArchitectureSVG of the Hussh three-layer architecture: PCHP (inner) → One (middle) → Fund A (outer). Four PCHP primitives + tagline arc.
- Three-layer architecture — Protocol → Platform → Fund AHussh's structural thesis. Protocol (PCHP / hu_ssh) inner moat → Hussh.ai platform (One) middle layer → Fund A outer compounding engine.
- Wiki scaling — search architecture and growth pathHow Hussh wiki search works today (qmd hybrid BM25 + vector + LLM rerank), what breaks as data scales from 10² → 10³ → 10⁴ → 10⁵ pages, and the deployment path from single-user localhost to public/multi-tenant hosting.
- Wiki search — dual-audience UX + AX (R&D)Has anyone shipped a wiki search interface optimized for both humans (UX) and agents (AX)? Survey of the design space and the few existing examples.
- Wiki-as-app — Three-Tier ArchitectureSVG three-tier architecture for the Hussh wiki: clients (Capacitor + Next.js + agents) → API (HTTP reader + MCP) → store (git + Drive + qmd). Drive-visible canonical.
- Wiki-as-App — Three-Tier ArchitectureSVG of the wiki-as-app three-tier architecture. Reader/writer surfaces → hussh-wiki MCP service → git repo + Drive buckets. Same wiki page accessed by humans + LLM agents.
- Wiki-as-App (editable source)Mermaid editable source for the wiki-as-app three-tier architecture — same as the SVG, intended for revision when tiers evolve.
- Wiki-as-app Architecture (editable source)Mermaid editable source for the wiki-as-app three-tier architecture. Same structure as the SVG, intended for revision.
- World Model — user-side personal-knowledge storeUser-side encrypted store anchoring all of One's personal knowledge of the user. Two-table AES-256-GCM, BYOK biometric key derivation, domain registry, three-layer consent validation.