One marketing ecosystem. Every surface.
Moosewave keeps the same identity, campaign, audience, permission, approval, operation, and evidence chain connected across web, desktop, mobile, developer tools, agents, integrations, and recipient experiences.
Each interface is native to its job. The authority, action, progress, and outcome remain shared.
Shared work / native expression
Choose a surfaceCanonical work item
CampaignProduct update · revision 12- Workspace
- Northstar
- Policy
- Checked now
- Progress
- Review open
- Evidence
- Linked
Compose, compare, configure, and investigate with the full information architecture in view.
- Same campaign revision
- Live authority
- Current operation
- Linked evidence
Interactive continuity switchboard
Work moves. Context stays.
Choose a journey, then inspect how one work item moves through beginning, continuation, approval, execution, and verification. The interface changes; the resource, authority, action, and causal history remain connected.
A campaign moves from creation to review, approval, execution, and evidence without becoming five unrelated tasks.
Begin · Web
Shape the campaign
Audience, content, permission basis, and readiness attach to one saved revision.
- Resource
- Same identity
- Authority
- Checked live
- Action
- One meaning
- History
- One causal chain
What completion meansThe approved revision, the executed revision, and the reported revision remain one traceable object.
Four connected journeys
Different work. The same continuity rule.
Every journey begins with a named object and ends with evidence that can be traced back to the decision that caused it.
Campaign continuation
A campaign moves from creation to review, approval, execution, and evidence without becoming five unrelated tasks.
The approved revision, the executed revision, and the reported revision remain one traceable object.
Deliverability remediation
A placement signal becomes an investigation, a bounded decision, and a verified change rather than a detached alert.
The incident closes only when the approved change and the later evidence can be reconciled.
Connection recovery
A connection problem preserves its last known cursor, direction, scopes, and affected work while access is restored.
Resumption starts from reconciled state instead of silently replaying or dropping work.
Agent-proposed action
An agent can gather evidence and propose a change, but the action keeps the same policy, approval, and audit path as a human request.
The proposal, decision, execution, and evidence form one history that a person can explain later.
Recovery lab / truthful operations
Built for interruption, not the happy-path demo.
Offline devices, changing permissions, provider timeouts, and older clients are normal operating conditions. Moosewave keeps durable intent separate from external effect so uncertainty is visible, bounded, and recoverable.
Queued with context
The durable intent keeps its resource revision and local order. When a connection returns, Moosewave rechecks authority and conflicts before execution.
- RecordedIntent
Saved before the handoff
- CheckedAuthority
Rechecked on reconnect
- BoundedEffect
Held while offline
- ResolvedReconcile
Revision and order compared
- ReturnedEvidence
Outcome returns to the history
- Admission
- Accepted locallyThe request is durable, not yet admitted for remote execution.
- Execution
- QueuedNo server execution is implied while the device is offline.
- External effect
- NoneNo provider call has begun.
- Reconciliation
- RequiredPermission, revision, and sequence are checked after reconnect.
- Retryability
- After checksResume is allowed only from compatible state.
28 connected programs / five fabrics
Every feature knows what surrounds it.
The ecosystem connects identity, creation, collaboration, audiences, automation, delivery, analytics, integrations, agents, recipients, and operations as one operating model.
Explore the five fabrics below. Each program states the customer-visible job it performs, and the relevant field guides go deeper into the underlying marketing discipline.
01Move without losing contextIdentity, navigation, state, and help travel far enough for the next surface to continue the job.
Identity and device trust
One account and workspace boundary, with sessions scoped to each device and client.
Universal work links
Links identify the work and intent without carrying secrets or borrowed authority.
Handoff and durable drafts
Selected step, draft state, and revision survive a move between surfaces.
Live sync and offline core
Invalidation, replay, conflict handling, and offline intent share one state contract.
Notification and action centre
A notification opens the exact work and exposes the action that is valid now.
Search, commands, recents, and favourites
The same resource language makes work findable from every entry point.
Workspaces, agencies, and entitlements
Context switches are explicit, and capability follows the active workspace.
Native operating-system continuity
Share, open, capture, and resume feel native while respecting the same boundaries.
Onboarding and contextual help
Guidance points to the current object, state, and safe next action.
02Decide togetherCollaboration, approvals, background work, and recovery use one causal history instead of side-channel memory.
Collaboration and approvals
Comments, diffs, decisions, and step-up checks stay attached to the work.
Background operations
Long-running work exposes progress, cancellation, retry, and final outcome separately.
Support, operations, audit, and recovery
Operators can investigate safely without gaining invisible business authority.
Activity, provenance, history, and undo
Each important change records cause, actor, version, and reversibility.
Marketing calendar and collision control
Campaigns, journeys, channels, and limits meet in one scheduling view.
03Run the customer loopCustomer state, campaign work, delivery, revenue, and recipient choices remain connected from intent to outcome.
Customer 360 and conversations
Profile, consent, events, messages, and replies meet without erasing their sources.
Read the customer 360 guideCampaign and content continuity
Brief, content, audience, approval, execution, and report share one revision lineage.
Automation and journey control
Triggers, eligibility, exits, re-enrolment, and recovery are evaluated at the right moment.
Read the automation guideDeliverability and remediation
Authentication, transport, controlled placement evidence, and corrective work connect.
Read the deliverability guideCommerce and revenue
Cart, order, product, subscription, and attribution state can change the next action.
Read the commerce guideTransactional lifecycle
Operational and cross-channel messages keep their own purpose, permission, policy, delivery, and evidence path.
Read the transactional lifecycle guide
04Open by contractAnalytics, agents, developers, integrations, and first-party data use declared capability rather than privileged shortcuts.
Analytics and investigations
Evidence classes, attribution models, cohorts, and drill-downs keep observation distinct from interpretation.
Read the analytics guideGoverned agents
Agents receive filtered context, cite sources, propose diffs, and pass the same action gates.
Experiment registry
Hypothesis, exposure, metric definition, decision, and follow-up remain one experiment record.
Integrations, migration, and data plane
Scopes, direction, mapping, cursor, lag, reconciliation, and recovery define connection health.
Developer parity and sandbox
API, SDK, CLI, webhooks, and simulation share resource and operation contracts.
First-party events and warehouse
Event lineage and governed export keep customer data useful beyond one interface.
05Respect data truthRecipient choices and schema changes propagate as governed state, not as best-effort notes between tools.
Recipient and public lifecycle
Signup, confirmation, preferences, unsubscribe, suppression, archives, erasure, and privacy choices share one permission truth.
Read the recipient guideAudience schema governance
Field ownership, type, sensitivity, compatibility, and migration are explicit.
Connection health / capability truth
A health record, not a logo wall.
A connection declares what it can do now: scopes, direction, cursor, lag, last verified outcome, mapping, reauthorization, and reconciliation. A familiar logo never substitutes for runtime capability.
- Capability
- Supported · Conditional · Read-only · Unavailable
- Access
- Declared scopes and current authorization
- Progress
- Direction, cursor, lag, and last success
- Recovery
- Reauthorize, resume, replay, and reconcile
Agent fabric / bounded intelligence
Helpful enough to act. Governed enough to trust.
An agent receives permission-filtered context and a scoped mandate. It cites sources, shows a proposed diff, declares impact, and routes consequential work through approval and step-up authentication.
- Permission-filtered context
- Sources and assumptions
- Visible proposal and diff
- Approval, budget, and audit
Trust travels with the work. Authority does not hide inside the handoff.
Every supported action checks the current workspace, actor, permission, resource revision, and policy at execution. Links and notifications carry identity and intent—not secrets. Support access, approvals, provider outcomes, and recovery stay visible in the same evidence chain.
Questions about the Moosewave ecosystem
Short answers to the questions that define whether a multi-surface product is truly connected.
What is the Moosewave ecosystem?
The Moosewave ecosystem is the shared identity, resource, action, operation, and evidence layer that connects campaigns, audiences, automation, delivery, integrations, analytics, agents, and operations across web, desktop, mobile, developer tools, and recipient experiences.
Do I need to use every Moosewave app or surface?
No. Each surface is shaped for the work it does best. The ecosystem matters because you can use only the surfaces you need without creating a separate version of the customer, campaign, permission, or operation truth.
Can work move between a phone, desktop, and web browser?
Yes, for supported actions. A handoff carries the work item, revision, selected step, and relevant decision context. The receiving surface checks current authority rather than inheriting permission from the link or device that opened it.
What happens when a device is offline or a provider times out?
Moosewave keeps durable intent separate from external effect. Offline work is revalidated when connectivity returns, while an ambiguous provider timeout is reconciled before a retry is considered. Queued, running, completed, and provider-confirmed are not treated as synonyms.
How does Moosewave describe integration support?
Connection health is based on runtime capability, declared scopes, direction, cursor and lag, last verified outcome, mapping, and recovery path. Moosewave does not use a logo alone as proof that a connection can perform a particular action.
Can an AI agent act without approval?
Only within its explicit mandate and the policy for that action. Consequential changes can require a visible proposal, cited evidence, human approval, and step-up authentication. The activity history distinguishes the proposer, approver, executor, and external outcome.
Follow one piece of work through the whole system.
Explore the guided Moosewave workspace across desktop, mobile, AI, MCP, approvals, deliverability evidence, and analytics—then join the waitlist when you are ready to bring your own work.