foundation-ready
prime-arena-featuresRank features that deserve prime Arena placement such as Branches, Voice, Discover, Vault, Import, Execute, and Memory Flow.
Prime placement must be earned by usefulness, clarity, and interaction.FEATURE VISIBILITY + INTERACTION TELEMETRY READINESS
Prime space belongs to features that users actually use.
A dynamic, read-only readiness layer that defines feature ranking, visibility signals, click-path friction, demo-before-demotion, widget obstruction review, and future interaction telemetry without collecting live events yet.
Universal Time Scroll
Every TheoB pathway can move through Past, Present, and Future without losing context.
Present
Read current signals, conditions, and live context.
🎙
Universal Voice Orb
Voice ready
SYSTEM STATE
StableFounder ControlledHuman Reviewed
FEATURE RANKING
Seen. Clicked. Used. Completed. Returned to. Earned.
TheoB needs a ruthless but fair ranking loop. If a feature is valuable but ignored, demo it. If still ignored, move it. If still ignored, improve it. If still ignored, archive or consolidate it. No ghosts renting prime UI.
SeenClickedCompletedReturnedPromoted
trueReadiness
falseLive Telemetry
falseUser Tracking
falseProduction Mutation
Feature Visibility Ranking and Interaction Telemetry Readiness is active as a non-destructive readiness layer. TheoB can define feature visibility targets, interaction signals, ranking rules, future telemetry record shape, and ranking receipt shape, but it cannot collect live telemetry, track users, store events, promote or demote features automatically, or mutate production yet.
foundation-ready
underused-feature-reviewIdentify features that look valuable but receive low interaction after launch.
Low clicks mean investigate, not immediately delete.foundation-ready
demo-before-demotionGive unclear but valuable features a demo, explanation, or guided preview before demoting them.
A great feature hidden badly should not be punished too early.foundation-ready
visual-location-testingMove features between Arena, Branches, Tools, Vault, Academy, Village, and System Index based on usage and purpose.
Placement is a product decision, not decoration.foundation-ready
functionality-improvement-loopImprove features that are visible but not used, then re-test after the change.
Sometimes the problem is not visibility. Sometimes the feature is not good enough yet.foundation-ready
archive-or-consolidate-loopArchive, hide, merge, or consolidate features that remain unused after demos, relocation, and functionality adjustments.
Unused features should not haunt the interface forever.foundation-ready
interaction-path-lengthMeasure how many clicks it takes to reach essential actions.
Essential operations should not require a treasure map.foundation-ready
non-clickable-ui-confusionDetect hover-reactive text bubbles, pills, or panels that look clickable but do not perform an action.
If it acts clickable, it should either click or stop acting clickable.foundation-ready
widget-popup-frictionRank popups, guide boxes, learning boxes, voice orbs, time scrolls, and mobile controls by usefulness and obstruction.
Widgets should serve the Arena, not squat in it.review-required
build-cost-per-featureConnect feature visibility to build cost, route count, CSS weight, and maintenance overhead.
A feature that costs build time must justify its rent.foundation-ready
feature-seenDetect whether a feature was visible in the user viewport.
Use: visibilityfoundation-ready
feature-clickedDetect whether a visible feature received interaction.
Use: engagementfoundation-ready
feature-usedDetect whether the click led to meaningful use instead of bounce or confusion.
Use: utilityfoundation-ready
action-completedDetect whether the user completed the intended action.
Use: completionfoundation-ready
return-usageDetect whether the user returned to the feature later.
Use: retentionfoundation-ready
rage-click-or-loopDetect repeated clicking, loops, or page-hopping that suggest confusion.
Use: frictionfoundation-ready
multi-hop-action-pathDetect when users need too many pages to reach the real operation.
Use: path compressionfoundation-ready
ignored-after-demoDetect features still ignored after demos or explanation.
Use: demotion reviewreview-required
feature-build-weightEstimate whether a feature adds too much route, CSS, or build overhead relative to use.
Use: build cost reviewready
telemetry-runtime-disabledShow telemetry collection remains disabled in this readiness layer.
Use: global lockready
Visibility Must Be EarnedPrime visual space belongs to features that users understand, use, and return to.
Pretty is not enough. Useful wins.ready
Demo Before DemotionIf a feature seems valuable but underused, show a demo or guided path before hiding it.
Do not bury a jewel because the sign was bad.ready
One Or Two Paths MaximumEssential operations should have one main path and, only when necessary, one backup path.
Three paths is usually a maze wearing a hat.ready
Hover Means IntentHover-reactive elements should be clickable, expandable, or visibly informational only.
Fake buttons are trust leaks.ready
Widgets Must Be Subtle And DismissibleGuide boxes, learning cards, voice orbs, mobile controls, and status widgets must shrink, disappear, or move into Tools when not needed.
The Arena is the stage. Widgets are stagehands.ready
Telemetry Informs RankingFeature ranking should use visibility, clicks, completion, return use, friction, and build cost.
Opinions start the design. Data earns the placement.ready
Consolidate Unused FeaturesFeatures that remain unused after visibility, demo, and functionality improvements should be archived or merged.
Do not let ghosts rent prime UI.ready
No Live Tracking YetThis layer defines telemetry readiness only and does not collect live user events.
No tracking. No storage. No surprise.Allowed NowRender Feature Visibility Ranking and Interaction Telemetry Readiness.Define feature ranking targets.Define interaction telemetry signals.Define demo-before-demotion policy.Define widget friction review.Define future feature telemetry record shape.Define future ranking receipt shape.Keep live telemetry disabled.
Not Allowed YetCollect live telemetry.Track users.Store interaction events.Automatically promote features.Automatically demote features.Mutate page placement.Mutate production.
featureTelemetryRecordId: stable feature telemetry record idfeatureId: stable feature idroute: route or arena view where feature appearsplacement: arena/topbar/branches/tools/vault/academy/village/footer/system-index/popupvisibilityState: seen/not-seen/unknowninteractionState: clicked/not-clicked/used/completed/bounced/returnedclickPathLength: 0/1/2/3+frictionSignal: none/rage-click/loop/backtrack/hover-confusion/blockeddemoShown: true/falseplacementAdjusted: true/falsefunctionalityAdjusted: true/falserecommendedAction: promote/keep/demo/move/improve/archive/consolidatebuildCostClass: low/medium/high/review-requiredtelemetryStorageAllowed: falseproductionMutation: false
featureRankingReceiptId: stable feature ranking receipt idfeatureTelemetryRecordId: linked telemetry recordfeatureSeenChecked: true/falseclickChecked: true/falsecompletionChecked: true/falsereturnUseChecked: true/falsefrictionChecked: true/falsedemoChecked: true/falsebuildCostChecked: true/falserankingApplied: falsetelemetryStored: falseapprovedBy: founder/operator/system-gate/human-reviewcreatedAt: ISO timestampauditTrailSafe: trueproductionMutation: false