Concepts
Architectural commitments, R&D, and the frameworks Hussh decisions run on.
77 pages
- Personal Knowledge Model (PKM) Upgrade RehearsalPublic concept page defining the zero-information-loss upgrade and rehearsal framework for Hussh Personal Knowledge Models (PKM).
- Hussh Discovery PipelineThe automated SEO, sitemap, and IndexNow discovery engine for the Hussh Search Console.
- One Systems Meta HubThe technical HOW behind 🤫 Agent One — latency, failure modes, privacy boundaries, and scale.
- One Voice Onboarding Journey — first-run setupPublic concept page defining the stages, visual map, and privacy boundaries for One's interactive first-run voice onboarding journey.
- One ADK — Agent Development Kit FrameworkThe architectural framework and runtime standard for building, orchestrating, and executing specialized personal agents under Hussh One.
- Onepoint — Drive To FlowPublic concept page defining the Drive To flow, destination-sharing, and live ETA calculation on Hussh One.
- One Goal Framework — governed action executionPublic product and conceptual overview of the One Goal Framework, which powers intent execution behind Agent One and One Voice.
- Trusted Connections — Generalized Social GraphPublic concept overview of Hussh's privacy-first, directional social graph architecture for agentic trust and recipient-scoped interactions.
- One-to-Subagent Turn Delegation over A2APublic concept page defining the One-parent to sub-agent delegation pattern over an in-process, transport-agnostic A2A contract.
- Personal Knowledge Model (PKM) Slice MarketplacePublic concept page defining the PKM slice marketplace where users can package and publish granular slices of personal context under explicit consent and ownership controls.
- AI & Search Engine Discoverability FrameworkPublic design and guidelines for Hussh One's discoverability architecture, aligning traditional SEO with Answer Engine Optimization (AEO) for LLMs and crawler-friendly discovery.
- Real-time Voice Transport — Provider-Neutral ProtocolPublic concept and protocol design for One's low-latency, full-duplex realtime voice transport, including client/server requirements, provider-neutral voice transport contract, and animated waveform visual feedback.
- Connected Systems — user-controlled integrations under PCHPThe architectural concept and design principles behind user-controlled integration surfaces (Connected Systems) managed via the central One Dashboard.
- Air-Gapped Offline Mode — local-first consent-driven architectureThe public design concept for Hussh's offline-first, air-gapped development and testing model, enabling complete local-loop execution with SQLite, zero external services, and biometric fallback simulations.
- Campaign Context Preparation — high-level customer experience consentThe high-level, least-privilege customer-experience and campaign consent loop that enables external brand agents to securely discover and request user context without exposing raw user data.
- Consent Reverse-Auction — the Intention Economy on PCHP + UCP + AP2Hussh's plan to flip the data economy: brands' agents bid for scoped, consented context and money settles to the user. Adds a bid field to the consent protocol; settles via AP2; commerce via UCP. Includes the PCHP-vs-AP2 difference report.
- Hermes Agent — the One runtime (Nous Research framework)Open-source agent framework from Nous Research that Hussh forks as the runtime for One. Provider-neutral, MCP-native, skills-driven — the concrete engine behind the BYOA commitment.
- 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.
- 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. (Slug-twin: a different diagram with the same basename lives under wiki/about/wiki-as-app-architecture/diagrams/ — disambiguate by parent folder.)
- 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.
- 1024 Club — Eight CathedralsSVG of the eight Cathedrals (Founders, Sages, Seekers, Healers, Makers, Stewards, Witnesses, Builders) with 128 portraits each = 1,024. Cathedral of Builders highlighted in oxblood as the current active production.
- 1024 Club — LP cap and book projectTwo intertwined uses of the same number. (1) Maximum 1,024 LPs across all Fund A vehicles ever. (2) The Hussh 1024 Club book — 1,024 literary portraits of historically significant deceased humans.
- 1024 Club Typography SpecimenHTML typography specimen for the 1024 Club Founder Edition: Fraunces display + EB Garamond body, oxblood + black two-color, sample portraits showing display/body-large/body/caption hierarchy.
- 1024bets ETF — Composite ScoringReference Python composite-scoring function for the 1024bets ETF universe. Four sub-scores (FCF, reinvestment ROIIC, indispensability, options-eligibility) → 0–1024 composite → AKQJ tier.
- 1024bets ETF — public-market FCF-aces vehicle (concept)Concept for the public-market sister vehicle to Fund A. Top 1024 global businesses by FCF + FCF growth + indispensability + AI-flywheel attention capture, with another 1024 in queue. Day 369 launch target. Concept-stage; methodology under review.