Research
Compare two sources about cacao growing conditions, retain their dates, and mark where they disagree.
Explore researchA careful contributor system for experts, scouts, cacao professionals, artisans, operators, institutions, reputation, credits, and future rewards.
Every TheoB pathway can move through Past, Present, and Future without losing context.
Read current signals, conditions, and live context.
Living Intelligence Ecosystem · Saved evidence shared across Library, capsules, world and time.
Connecting this view to its project…
Voice ready
Program design; enrollment and earned benefits are pending. This guide brings the existing plans together. Verified clone enrollment, unique avatar assignment, dedicated liaisons, the consent-based spatial user grid, and reward grants are not active through this page. Existing profiles and demonstrations do not establish that those services are ready.
Browse the guide and experiment with the Personal Prime appearance preview without an account. Preview changes stay on the open page. Saving your appearance or Arena work, restoring a saved workspace, and exporting your work require a signed-in account. Signing in starts a separate account workspace; it does not silently adopt another visitor’s browser data.
The wider goal is a sample of every capability, with limited live trials and a clear remaining allowance. That full sample collection and a reliable guest usage meter are still pending. Older pages are being brought under the same account-to-save rule.
These examples describe possible work. They are not completed research, generated media, sent messages, or active agents.
Compare two sources about cacao growing conditions, retain their dates, and mark where they disagree.
Explore researchSketch a festival poster, an acoustic music brief, and a short story about a fictional cacao harvest. Keep authorship and sharing choices visible.
Explore art, music and storiesPlan a community archive: one person records oral history, another checks permissions, and a liaison explains the next reviewed task.
Explore collaborationA fictional alias assigned to Shop A receives unexpected mail from Sender B. Record the observation and offer to pause the alias; do not claim Shop A sold the address.
Explore privacyYour skin, avatar motif and accessories can change while your owner identity and clone history stay stable. Personal Prime lets you preview these cosmetics and explicitly save an account-specific version in this browser. Cloud appearance sync is not active. Cosmetic choices do not establish verified ownership, earn stars, or increase usage limits.
Private email aliases are proposed, not active. The plan is an optional TheoB collaboration address plus separate aliases for individual services, routed privately to email addresses you verify. You should be able to add multiple destinations, choose where an alias delivers, and pause or retire it. Delivery limits and costs must be clear; adding addresses must not create extra accounts, rewards or usage allowances.
Keymaster should show unexpected alias use and optional breach alerts, explain the evidence, and help you choose a response. An exposed alias can reveal which address was used; it cannot by itself prove who sold information. Mail relay, exposure monitoring and automatic protection are not active in the current Keymaster preview. Saving an appearance or adding an alias must never publish your profile or location without a separate sharing choice.
Explore the existing Keymaster previewTheoB can reward professionals and community contributors for useful verified knowledge, but reputation, proof, and quality must come before money-like systems.
Every new clone must belong to a real, verified person or organization. An organization also needs a verified representative with permission to act for it. A chosen display name does not establish that verification.
Each clone needs its own identity and avatar. Changing devices, providers, plans, or appearance must preserve its owner, projects, and history.
Each clone must have an assigned liaison agent with a visible role and scope, a clear way to ask for help, and a recorded handoff if the liaison changes.
A spatial user grid must start with profiles hidden. You choose whether to appear, who can see you, and the approximate area or radius you share. Exact location is not needed.
Public cards must contain only the fields and work you deliberately share. Account details, private research, messages, credentials, and private projects stay out of the grid and reward evidence shown to others.
You must be able to hide your profile, change the audience or radius, and revoke future access. Already downloaded shared material cannot be recalled. Declining location sharing must not reduce eligibility for contribution rewards.
Existing location preferences include General only, Within 5 miles, 5–10 miles, 10–25 miles, City / metro area, and Region only. Those choices describe your preference; saving one does not publish a clone on a verified user grid.
Stars and contributor tiers are part of the planned program. The star schedule is still awaiting confirmation. Earning rules, tier thresholds, reviews, appeals, and benefits must be clear before awards begin. No star balance or automatic entitlement is claimed on this page.
Reputation should identify the area of expertise and supporting work. Existing directory badges use displayed Proof, Execution, and Impact scores; a badge label alone does not verify a person, an organization, or an earned benefit.
Reputation principlesThe existing usage plan describes Free User, First-Month Explorer, Pro Member, Operator, Founder Pass, and Contributor Credit. These are access categories, not star thresholds. Bonus features and higher free limits need an issued grant and a visible allowance before they can be used.
Usage and access planThe current avatar chooses the highest stage whose total activity threshold is met. Activity is stored in this browser and can be changed locally. These stages are a personalization demonstration; they do not award stars, verified trust, or usage benefits.
| Stage | Total local activity signals |
|---|---|
| Seed | Fewer than 3 |
| Explorer | 3 or more |
| Builder | 8 or more |
| Architect | 15 or more |
| Sage | 25 or more |
Add sourced knowledge, literature summaries, scientific context, and evidence trails.
Submit local signals, photos, events, cultural context, field notes, and map intelligence.
Contribute producer knowledge, farming insight, ceremony education, formulation, and sourcing context.
Share materials, process, origin stories, product proof, and creative applications.
Support outreach, verification, partner coordination, events, and real-world follow-through.
Contribute archives, reports, datasets, public knowledge, and educational material.
Share original art, music, stories, and other useful creative work with clear ownership, attribution, and permission to share.
Research, art, music, stories, useful tools, cultural knowledge, corrections, and community work should qualify for review. Choose the material and audience; retain attribution and permission records.
Reviewers should assess originality, usefulness, evidence appropriate to the work, and community benefit. Real customer engagement can earn an additional benefit, but audience size does not establish accuracy or trust, and a smaller audience must not disqualify valuable work.
The decision should name the reviewed contribution, applicable rule, reviewer, reason, and any conflicts of interest. Duplicate claims, fabricated engagement, self-dealing, and coordinated reward farming must be checked. Contributors need a correction and appeal route.
An approved award must produce a receipt tied to the owner and contribution. Show the feature unlocked or free usage increase, amount, start and expiry dates, remaining allowance, reset timing, and reason for any reversal. A recommendation alone does not increase a limit.
Early collaboration should reward contributors who improve the work and those who bring genuine customer participation. Share only the evidence needed for review; public recognition requires your choice of what to publish. Reward decisions must never buy a better truth score or permission to access another person's private work.
Contribution review, engagement verification, appeals, and feature or quota grants still need connected services and accepted trials. The current bounty examples and reward labels are not issued awards. Cash payouts remain separately gated.
Visible trust score, verified contribution history, and expertise badges.
Expanded tools, higher limits, advanced routes, and contributor-only features.
Internal Theo Credits for useful verified contributions and field work.
Featured profiles, project credits, regional recognition, and partner exposure.
Bounties, paid missions later, sponsor matching, events, and collaboration routes.
Revenue share or cash payouts only after legal/compliance review.
No unsourced claims treated as fact.
No rewards for volume without quality.
Every contribution needs a topic, attribution or source, timestamp, and review criteria appropriate to the work. Region is included only when relevant and deliberately shared.
Sensitive claims require higher review.
Cash-out systems are future-gated.
Credits start as platform utility, not banking.