Concepts
Architectural commitments, R&D, and the frameworks Hussh decisions run on.
68 pages
- BYOA ArchitectureSVG of BYOA: user at center, six AI provider examples around the perimeter, all routed through PCHP consent boundary.
- DNSA Engine — entry / exit signalsFund A's signal layer. Non-proprietary discipline tools — RSI, VIX, put/call, credit spreads, IV rank, Bollinger position. The edge is execution discipline, not sophisticated signals.
- DNSA Engine — Signal Calculator (reference)Reference Python implementation of the DNSA Engine entry/exit signal layer. Illustrative only — not live trading.
- DRIP-ON — One-Way RatchetSVG illustration of the DRIP-ON one-way ratchet: share count only goes up, quarter over quarter, as premium and dividends compound back to shares.
- DRIP-ON — premium-on-premium ratchetFund A's covered-call mechanic. 100% of premium reinvested into additional shares. One-way ratchet on share count — the Iron Rule core differentiator vs. all other covered-call funds.
- Five Iron Rules + Five Filters — One-PagerHTML one-pager for Five Iron Rules + Five Filters — LP-facing reference document, Apple-frame typography (Fraunces + EB Garamond, oxblood/black). Pre-launch.
- hu_ssh — brand-aligned PCHP namingAlternate naming surface for PCHP. Brand-aligned for consumer-facing / demo contexts; PCHP retained for RFC / engineering contexts.
- Hussh GlossaryHTML glossary of canonical Hussh / Fund A / Aloha Compass terms with one-line definitions. Apple-frame typography. Single-page reference for partners + LPs.
- Hussh wiki — scalable app + MCP architectureThree-tier architecture turning the markdown wiki into a scalable app (Capacitor 8 + Next.js 16) plus MCP server (HTTP/SSE on localhost). Same repo, qmd-backed, BYOA-aligned, dogfoods PCHP.
- Iron Rules — Five PillarsSVG five-pillar visual of Fund A's Iron Rules: leverage ceiling, reserve floor, concentration cap, permanent HWM, GP co-invest.
- Iron Rules — Fund A's five constitutional provisionsThe five non-negotiable risk and structural rules that govern Fund A — leverage ceiling, reserve floor, concentration cap, permanent HWM, GP co-invest.
- Iron Rules + DRIP-ON — Reference MathReference Python implementation of the Five Iron Rules and DRIP-ON one-way ratchet. Illustrative only — not a live trading system, not connected to LP capital.
- James Park personaCanonical north-star user persona for iBrokerage. Senior tech executive, $4M+ across ~8 accounts, time-poor, high standards. Not a real person.
- LLM Wiki Landscape — Three LevelsSVG landscape map of LLM Wiki implementation levels (May 2026): Level 1 RAG → Level 2 agent-writable closed → Level 3 open + MCP + agent-writable. Hussh sits at Level 3.
- LLM Wiki Pattern — LandscapeSVG landscape positioning hussh-wiki against existing wiki/notes patterns (Notion, Roam, Obsidian, GitHub wiki, MediaWiki, Confluence). Two axes: openness x structure. Hussh's distinctive position: private + strict + MCP-native.
- LLM Wiki pattern — landscape & R&DHow people are spinning up LLM Wikis as of May 2026. Karpathy's origin gist, three implementation levels, known failure modes, tooling landscape, and how Hussh's wiki compares.
- MLX on One surfacesConcept paper on why MLX (Apple's array framework) is the natural inference runtime for on-device intelligence in One. Status: concept only, no implementation.
- MLX Runtime TopologySVG of MLX runtime topology. User intent → PCHP runtime → MLX inference → Apple silicon. Drive-visible canonical.
- MLX Runtime Topology (editable source)Mermaid editable source for MLX runtime topology — same structure as the SVG, intended for revision.
- One Lens — Curator model for ads and contentOne Lens — the Curator-model agent in One that mediates ads and content on the user's terms. Free as trust-builder; PCHP handshake API revenue is Phase 2; no Hushh-branded ad marketplace.
- One Lens — Three-Way ForkSVG of One Lens design fork: Marketplace (rejected), Curator (chosen, sage), Pure pipeline (rejected). Phase 2 monetization via PCHP brand-side endpoint, not Hussh inventory.
- PCHP brand-side endpointPhase 2 monetization protocol-tier. Brands and publishers request consented attention via PCHP handshakes; Hussh charges subscription/per-receipt; no inventory, no marketplace, no Hussh ad cut on impression spend.
- Personal Operating Layer — One's strategic positioningThe strategic positioning of One as a consent and orchestration substrate sitting under the user's existing apps and services, not a super-app destination layer that competes with them. Four v1 verticals locked; entertainment/gaming/social/native commerce explicitly excluded.
- Personal Operating Layer ArchitectureSVG architecture of Personal Operating Layer: apps on top, One substrate band in oxblood middle, user data on bottom; v1 verticals + explicit exclusions annotated.
- Public vs Private — auth-tier on one Hussh wikiHow the Hussh wiki serves anonymous public readers and the authenticated owner from one MCP server and one reader. HCT (Hushh Consent Token) bearer model + OAuth 2.1 + PKCE for browser clients, sanitization rules, content guard.