Inference
On-device, not cloud metered
Unlimited free chat is only viable because the core chat loop does not carry a cloud inference bill on every message.
Product OverviewProvider pivot
Realbits Chat Hub is becoming a model and app provider.
The current product direction is a slate of on-device apps that distribute reusable model packs and character cards, with creator monetization and a web surface that supports marketing, account flows, and the canonical studio.
One-line positioning: Realbits Chat Hub provides on-device AI models, reusable character cards, and themed chat apps.
Ownership
Characters and settings as assets
The web3 layer stays, but only in service of portable character ownership, provenance, and creator royalties.
Distribution
Themed storefronts, shared catalog
The distribution strategy is a flagship app plus verticals, each with its own funnel while drawing from one shared provider catalog.
App Slate
Current consumer-facing apps in the repo
realbits-chat-hub
Flagship chat hub and primary provider showcase.
daily-wisdom-guide
Daily-reflection and spiritual guidance surface.
situational-english-coach
Scenario-based conversational English surface.
Product Principles
Constraints that now define the product
On-device first
Inference runs locally. The cloud is for accounts, ownership, marketplace support, and creator payouts, not the core experience loop.
Provider assets as product
The monetizable units are reusable character cards, model packs, and themed app surfaces. Chat is one delivery mode, not the business by itself.
Ownership-first
Premium character assets are meant to be owned via ERC-721 rather than server-rented experiences that disappear when the platform changes its mind.
Provider-led distribution
One flagship plus specialized apps gives Realbits broader acquisition while keeping each app tightly focused on a concrete use case.
Roadmap
What the repo should do next
Phase 0
Strategy lock
Vision, GST framework, and deprecation banners for the retired B2A2A thesis.
Phase 1
Provider foundation
Character data model, model manifests, repurposed contracts, shared backend routes, and flagship app integration.
Phase 2
Cross-app provider delivery
Keep the existing apps as separate storefront entries while sharing account, model-pack, character, and ownership layers.
Phase 3
Creator supply engine
Web-first creator studio, public marketplace, and on-chain royalty routing.
Transition Status
The repo vision and GST framework now frame Realbits Chat Hub as a model and app provider.
Provider data models now exist in `packages/web/prisma/schema.prisma`.
The public web entrypoints are being rewritten away from the old marketplace/social framing.
Legacy marketplace and social routes still exist in the codebase during the transition and should be treated as carry-over surfaces, not the strategic product direction.
Immediate Build-Out
Repurpose `AgentNFT.sol` into `CharacterNFT.sol`.
Repurpose `AgentEscrow.sol` into `CreatorRoyaltyEscrow.sol`.
Finish the shared provider routes for characters, conversations, and character memory.
Wire one full flagship path through `realbits-chat-hub` before broad cleanup.