Velunor Bikes plans technical search work
The fictional D2C manufacturer at velunor-bikes.example uses a synthetic goal to show crawl findings, prioritisation and a concrete approval. The values are demonstration data, not a market observation.
Control Surface
Three fictional companies show how MarketingOS works.
Velunor Bikes, Qevora Systems and Studio Talvori are synthetic showcases. Their domains end in .example. Names, goals, KPIs, approvals and outcome values are invented and contain no customer data. The existing interface captures document only the technical UI state of the alpha.
Velunor Bikes
Fictional work state with synthetic data
DraftTechnical recommendation prepared
ReviewApprovalOwner decision required
OpenObservationStarts only after an approved change
WaitingPreparing agentsContent AgentboundedSEO AgentboundedEvidence Agentbounded
The captures come from a reproducible Velunor Bikes product state. The company, domain, goals, metrics and runtime reports are invented. They demonstrate features and interaction, not customer impact.
01 / TODAY
The business goal comes before the activity.
The opening view brings the goal, metric, context status, next decision and latest evidence into one workspace.02 / STRATEGY
Business context is saved and revisioned.
Company, brand, audiences, offers, websites and markets share one version. The interface exposes its revision, hash and save state.03 / GOALS
KPIs stay bound to a source and time window.
The fictional business goal carries its metric. The source, demonstration window, current value and target remain visible.
04 / APPROVAL
The decision applies to the exact payload hash.
The target system, business goal, risk level and payload hash appear before the action. The showcase reviews a local brief and performs no external write.05 / RUNTIME
OpenCLAW reports its state to the Control Surface.
The synthetic report shows a runtime version, three sessions, twelve agents, capabilities and a receipt hash. It demonstrates runtime presence and performed no external write.06 / AGENT TEAM
Twelve roles receive an actual status.
The showcase reports the orchestrator, Strategy Lead and Tech SEO as active. The remaining roles are available. These synthetic states only demonstrate how runtime presence appears in MarketingOS.07 / ADDONS
Available and planned never look the same.
The SEO/GEO Addon is installed and functional. Social Media, Lifecycle CRM and Paid Performance remain visibly planned. The same applies to the Growth Bundle and Agency Pack. No invented prices are shown.08 / SECURITY
The interface shows the boundary that actually applies today.
The Direct Profile permits read only sources and local drafts. External writes remain blocked. Separated identities, the SiteOne requirement and Secure Profile foundations appear as distinct states.Qevora Systems organises demand and GEO questions
The invented B2B software company at qevora-systems.example shows how audience, offer, sources and open hypotheses stay in one context. There is no real Search Console property or customer campaign.
Studio Talvori directs editorial work
The fictional studio at studio-talvori.example demonstrates briefing, tone, review and release preparation. Every displayed approval remains synthetic.
Interface captures are technical evidence
Desktop and mobile captures show layout, navigation, context revision, approval review and runtime state from a development build. They are not a case study or a claim about any company's performance.
Product proof and business impact stay separate
A working view or stored receipt can prove product behaviour. Rankings, citations, leads or revenue need a real baseline, an executed action and an appropriate observation window.
Runtime values describe one test point
Version, sessions, agents, capabilities and receipt hash came from a technical report. Without a new signal it becomes stale after five minutes. It proves neither permanent availability nor customer value.
Continue
The evidence behind the interface
The Proof Ledger connects the captures to verified OpenCLAW and Hermes runs and keeps a point in time runtime report separate from permanent availability or customer impact.