Domain products / canonical synthesis
Products and capabilities
Canonical page of Zenith Research's capability layers, product surfaces, agency offers, treasury-company proofs, and the distinction between platform primitives and market-facing products.
- Updated
- 2026-08-29
- Source digest
abfa01a674f3- Structured data
- JSON-LD
Scope
This page owns what Zenith Research builds and how foundational capabilities compose into products. It distinguishes capabilities, platform modules, delivery surfaces, and independent treasury-company products.
Current answer
Zenith is one platform with multiple entry points. Its core product is the owned organizational substrate: a Hub runtime operating against Vault knowledge bases, agents, tools, processes, review controls, and local interfaces. Market-facing products are composed from those primitives rather than built as unrelated SaaS applications.
zenith-capabilities is the detailed capability graph. The Zenith hub is one platform serving agency delivery, enterprise team access, AI CEO operations, community knowledge sharing, and community learning through the same document and dispatcher infrastructure is the canonical unification claim.
Evidence and influences
- defines the capability graph: zenith-capabilities.
- defines the unified-platform position: The Zenith hub is one platform serving agency delivery, enterprise team access, AI CEO operations, community knowledge sharing, and community learning through the same document and dispatcher infrastructure.
- defines the deployment boundary: A vault deployed on the node is the node vault; every other vault connecting to that hub is a client vault.
- implements the current Hub foundation: zenith-hub repo — Phase 0 architecture and stack.
- evidences the treasury-company product model: The Gallery creates an art and culture community that serves as a microcosm of the broader Zenith system.
Capability stack
Knowledge infrastructure
- The collective knowledge graph makes every contributor's knowledge part of the whole without surrendering local ownership.
- A vault deployed on the node is the node vault; every other vault connecting to that hub is a client vault.
- ai-os-publish-api - vault-to-hub and vault-to-space publication contract.
Agent and orchestration layer
- Frank orchestrates hub-side agent execution through intent recognition and skill dispatch.
- Raziel manages the business knowledge ontology while Frank manages the business information ontology — static structure vs objects in motion.
- processes are author-facing SOPs in markdown — the system derives the execution schema from declared IO without exposing it to the author.
- AI CEOs are agents that operate with enough autonomy to run a product or business within the Zenith product framework.
Dispatch and service composition
- The dispatcher routes tasks to humans or services based on declared processes and triggers.
- Product development automation applies the dispatcher to the full product lifecycle from idea to delivery.
- Property operations dispatch automates cleaning and maintenance assignments based on booking triggers and process definitions.
- Concierge dispatch applies the dispatcher to full-service hospitality giving guests hotel-level service through property management infrastructure.
- An atomic design system paired with a product framework enables non-technical operators to vibe code their own dashboards and booking sites from start to finish.
Research and governance
- Open peer review extends the proposition system publicly so any claim can be contested and proven on a consistency standard.
- The research journal publishes claims that clear the consistency bar as citable versioned documents.
- Meritocratic voting weights decisions by domain contribution and demonstrated expertise so votes are earned not equal.
Commerce, identity, and relationships
- Rolodex is the central CRM of the dispatching system — the Rails for commerce.
- Compatibility matching connects people by psychographic fit across opt-in domains including founder matching and talent supply.
- Verifiable identity uses JWT-based encryption for privacy-preserving credentialing of sensitive personal data.
- Zenith agency proposals should be shareable links that double as Cardano-payable invoices.
Current product surfaces
Zenith Hub
The primary platform surface: workspaces, repositories, assets, review, intake, agents, and locally controlled knowledge infrastructure.
- zenith-hub repo — Phase 0 architecture and stack.
- Zenith hub review surface — asset routing, capability matrix, and comment anchor model.
- zenith-research.ca serves three surfaces — review, repo display, and assets display with workspace-styled Obsidian-like Markdown rendering.
- documents rendered on zenith-research.ca inherit the styling of the workspace that produced them.
Agency delivery
Zenith Research implements client-specific systems using the same framework it is turning into a platform. See Zenith Research - operations and delivery.
Gallery
Gallery is an art and culture community and treasury-company proof surface.
- The Gallery creates an art and culture community that serves as a microcosm of the broader Zenith system.
- Gallery component library - product UI map.
- Exhibition Carousel displays the active exhibition as a main image with Back-Next navigation and a scrollable artist-labelled thumbnail row in Gallery.exe chrome.
- Gallery SUBJECT dossier card is the primary UI pattern for artist and curator profiles.
- Gallery semantic feed overlay surfaces recommendation reasoning as neon data in the UI.
- Gallery landing page needs dual entry points — contributors see curator onboarding, all other personas go straight to the feed.
Zendo
Zendo provides full hotel-level concierge to remote workers and business travelers through property management infrastructure is the hospitality dispatch proof.
Local operating environment
- the hub ships a native Mac OS transcription app that logs voice input and agent responses to a local SQLite database with PostgreSQL as the upgrade path.
- FaceTimeCapture - local capture and transcription component.
Product status boundary
| Layer | Status |
|---|---|
| Local vault methodology | Live in this vault |
| Hub and review infrastructure | Partially built |
| Frank and agent orchestration | Partially built; architecture evolving |
| Agency delivery | Active entry point |
| Data-rights and brokerage protocol | Specified direction; not yet proven end to end |
| Distributed mesh and treasury governance | Architecture and experiments; not mature platform |
Open questions and tensions
- What is the smallest deployable Zenith product that proves owned infrastructure rather than custom service?
- Which capability graph belongs in the core protocol versus optional modules?
- Which treasury-company products should remain separate companies rather than become platform features?
- What exact user journey connects documents, dispatch, review, and data rights in one product surface?
Related canonical pages
- Zenith Research - system architecture - implementation of the primitives.
- Zenith Research - operations and delivery - current delivery system.
- Zenith Research - network governance and economics - treasury-company and network mechanics.
- Zenith Research - roadmap decisions and open questions - current build sequence.