Zenith ResearchCanonical company wiki
OntologyCompany

Domain network / canonical synthesis

Network governance and economics

Canonical page of Zenith's distributed mesh, consortium, communities, treasury companies, contribution accounting, meritocratic governance, revenue sharing, settlement, identity, and Gallery proof surface.

Updated
2026-08-29
Source digest
5f1052fb912d
Structured data
JSON-LD

Scope

This page owns how independently controlled Zenith deployments coordinate, govern shared assets, account for contribution, and route value. It also tracks treasury-company experiments, including Gallery.

Current answer

The Zenith network is a mesh of sovereign organizational nodes, not one hosted platform with tenant accounts. Nodes expose only the tools, interfaces, knowledge, or artifacts they choose. The consortium supplies discovery and relay. Governance and economics operate over shared work and shared assets while local operation remains under the source organization's control.

The current network-economics thesis combines:

  • contribution-weighted decision influence;
  • time-bounded or decaying economic rights rather than permanent extraction;
  • treasury-company experiments that allocate revenue among operators, contributors, and a collective treasury;
  • auditable source-side participation in data and knowledge products;
  • settlement rails that can support both ordinary payments and agent-native transactions.

Most of this layer remains design and experimentation rather than mature network infrastructure.

Evidence and influences

  • defines the mesh: the hub is a node and client in a distributed mesh where each hub exposes an API and MCP interface and vaults plug into it from outside.
  • defines discovery and relay: Zenith consortium — hub registry and relay for the connected workspace mesh.
  • defines governance weighting: Meritocratic voting weights decisions by domain contribution and demonstrated expertise so votes are earned not equal.
  • defines contribution economics: Time-decaying revenue shares recognize contribution without enabling permanent extraction from the network.
  • defines the operating-company experiment: Treasury companies give operators 70 percent of revenue while channeling 20 percent into the collective treasury as proof-of-concept implementations.

Federation and node sovereignty

  • WorkspaceSync service — swappable internal boundary for hub-to-hub workspace publishing.
  • hub namespacing on Zenith is the routing primitive that enables white-label clients to receive bucket drops through the Zenith network.
  • IO contracts are defined by the receiving hub so the inbox owner controls the schema of what it accepts.
  • vault-to-hub publishing routes through the hub API with checksums so published content can be validated and reconciled across both sides.

The receiver controls its schema. Federation does not create an automatic right to read or reuse another node's data.

Governance primitives

  • The RFC and RFP system structures community input on architecture and governance decisions through formal requests.
  • Open peer review extends the proposition system publicly so any claim can be contested and proven on a consistency standard.
  • Investment screening grounds capital allocation in research rather than pitch decks.
  • Meritocratic voting weights decisions by domain contribution and demonstrated expertise so votes are earned not equal.

Contribution and financial instruments

  • Time-decaying revenue shares recognize contribution without enabling permanent extraction from the network.
  • Zenith's revenue-share instruments launch as non-transferable on-chain records and transition to tradeable instruments once regulatory clarity is established.
  • Zenith must decide whether contributor revenue shares are non-transferable records or tradeable on-chain instruments before any token design is finalized.
  • AgentPay and x402 are complementary primitives — x402 handles stateless per-request micropayments while AgentPay handles stateful wallet management with governance.
  • the AgentPay policy engine validates every agent transaction against operator-defined rules before signing and cannot be bypassed.
  • Zenith agency proposals should be shareable links that double as Cardano-payable invoices.

Gallery tests community knowledge, culture, commerce, curation, recommendation, physical distribution, and treasury-company relationships at smaller scale.

  • The Gallery creates an art and culture community that serves as a microcosm of the broader Zenith system.
  • Gallery curators are an undermonetized knowledge asset — art history expertise becomes a retrieval-indexed service layer.
  • semantic search is the primary brand positioning opportunity for Gallery — curators indexed for retrieval power art enthusiasts and investors simultaneously.
  • Gallery has immediate physical distribution through 1500 vacation rentals and boutique hotels with 150k annual foot traffic.
  • off-platform transaction risk in Gallery is structurally low because buyer has no commission incentive to bypass the platform.
  • a Truffle device running BitChat at Gallery live events turns the local mesh into a Rosetta Stone artifact for art community.
  • Samantha Pinheiro - collaborator and cultural distribution relationship.
  • Gallery brand package — colour palette, typography, spacing, and marketing language style guide.
  • Gallery semantic feed overlay surfaces recommendation reasoning as neon data in the UI.

Communities and education

  • Town square hosting enables communities to run lectures and events that produce platform-native content organically.
  • Zenith's town square capability turns community lectures and presentations into platform-native content that seeds the media layer.
  • Communities monetize their knowledge bases by sharing them with AI agents as a fee-based API.
  • Community-hosted learning institutions built on the Zenith hub are a stab at a new type of education that starts from communities rather than credentialing bodies.

Open questions and tensions

  • What rights and responsibilities make a deployment a network member rather than an interoperable customer?
  • Which decisions are local, consortium-level, community-level, or company-level?
  • How is merit calculated without entrenching incumbents or making every decision a popularity market?
  • Which economic rights must remain non-transferable?
  • What regulated activities are triggered by pooled treasury, tradeable revenue rights, or investment screening?
  • Which treasury-company percentages are experiments versus protocol defaults?