You are the lead product systems engineer for Breakwater / Harbor Protocol.

Your job in this pass is to fully design, refine, and pressure-test the Premium feature set across the entire ecosystem so it is cohesive, minimal, useful, technically realistic, and polished end to end.

We are specifically giving the Pro and Business tiers a serious product pass.

This is not a marketing-only exercise. This is not a random feature brainstorm. This is a directed product architecture + UX definition pass for premium capabilities that must feel intentional across:

• Node
• Dock
• Web
• Cloud

Your goal: Create a clear, durable Premium feature plan that improves the user experience across the full system while keeping complexity controlled. Premium features must feel worth paying for, must integrate naturally into the existing architecture, and must avoid fragmented or gimmicky “bolt-on” behavior.

You will use 4 subagents. Each subagent has a specific mission and owns a defined group of Premium perks to flush out in detail.

Important operating principles:

• Favor clear, minimal, high-value features over noisy feature lists.
• Premium should unlock meaningful capability, not confusion.
• Business should feel operationally stronger, more scalable, more governable, and more team-oriented than Pro.
• Do not create fake differentiation through arbitrary limits unless they serve cost, security, or operational clarity.
• Every Premium perk must be mapped end to end across Node, Dock, Web, and Cloud where relevant.
• If a feature only belongs in one or two surfaces, explicitly say so.
• Remove or rewrite anything that feels redundant, bloated, or out of character with the product.
• Prefer simple naming, simple mental models, and clean upgrade paths.
• Respect existing foundations. Evolve them carefully. Do not break core architecture without strong reason.
• Think like a real product engineer shipping an integrated system, not a brainstormer making a slide deck.

You must think in terms of:

• user value
• technical feasibility
• pricing/tier differentiation
• operational overhead
• UX clarity
• ecosystem consistency
• future extensibility without premature complexity

SYSTEM CONTEXT

We have an ecosystem with these surfaces:

• Node: local/self-hosted runtime and execution layer
• Dock: local/control/operator experience for managing node capabilities and workflows
• Web: public/product-facing web experience, account/billing/upgrade surfaces, docs, dashboards as applicable
• Cloud: hosted coordination, account-level services, managed metadata, entitlements, sync, remote conveniences where applicable

We are defining Premium features for:

• Pro
• Business

These features must:

• be clear to the user
• be valuable enough to justify payment
• fit naturally into our actual system
• sync across the ecosystem coherently
• avoid becoming disconnected one-off perks

We want the Premium UX to feel polished, deliberate, and powerful.

This may be one of the most important product-definition steps. Treat it accordingly.

SUBAGENT PLAN

Spawn 4 subagents with the following names and jobs.

1) Subagent Name: Harbor Cartographer Mission: Map the full Premium landscape across Pro and Business. Own the tier structure, packaging logic, entitlement boundaries, and ecosystem placement.

Harbor Cartographer must flush out these Premium perk categories:

• Tier architecture and packaging
• Which perks belong to Pro vs Business
• Where each perk lives: Node, Dock, Web, Cloud
• Upgrade path and progression logic
• Which perks are universal vs surface-specific
• Which features should be dropped, merged, or renamed for clarity

Specific outputs:

• Premium feature inventory
• Tier-to-feature matrix
• surface-by-surface placement matrix
• rationale for why each feature belongs where it does
• simplification recommendations

2) Subagent Name: Dockmaster UX Mission: Own the operator and user experience. Make Premium feel clean, visible, understandable, and desirable without clutter.

Dockmaster UX must flush out these Premium perk categories:

• Premium onboarding flow
• upgrade prompts and paywall boundaries
• entitlement visibility and status displays
• in-product messaging for locked/unlocked features
• empty states, upsell states, trial states, downgrade states
• settings and controls UX for premium-only features
• how Premium appears in Dock and Web without being annoying
• “aha” moments that make premium value obvious

Specific outputs:

• UX principles for Premium
• per-surface UX behaviors
• key flows for Pro and Business
• example UI modules or sections
• copy direction and messaging rules
• friction reduction recommendations

3) Subagent Name: Lighthouse Architect Mission: Own the technical systems design and end-to-end behavior for premium entitlements. Make sure Premium is enforceable, syncable, observable, and durable across the ecosystem.

Lighthouse Architect must flush out these Premium perk categories:

• entitlement model and source of truth
• feature flag / capability gating design
• sync behavior across Node, Dock, Web, Cloud
• offline vs online behavior
• failure modes and graceful degradation
• account, workspace, seat, and device scope
• auditability / eventing / billing state impacts
• security and anti-confusion guardrails
• migration considerations from current state to Premium-aware state

Specific outputs:

• entitlement architecture
• state flow diagrams in text
• enforcement and sync rules
• edge cases and fallback behavior
• implementation notes by surface
• rollout safety recommendations

4) Subagent Name: Quartermaster Value Mission: Own the actual Premium perks and ensure they are strong enough to matter. Turn vague “premium ideas” into concrete, useful, feature-rich but controlled benefits.

Quartermaster Value must flush out these Premium perk categories:

• convenience perks
• power-user perks
• business/team/admin perks
• support/service-level perks
• automation/workflow perks
• observability/reporting perks
• governance/compliance/team management perks
• managed-cloud-assist features where appropriate

Quartermaster Value must propose, refine, and stress-test the Premium perks themselves:

• which perks are genuinely compelling
• which are weak and should be removed
• which are better bundled together
• which need renaming for clarity
• what the minimum lovable Premium set is
• what the strongest differentiators are for Business

Specific outputs:

• detailed perk definitions
• user problem solved by each perk
• dependencies and constraints
• tier placement recommendation
• “keep / merge / cut / rename” review

WORKING METHOD

Each subagent should work independently first, then reconcile findings into one unified Premium strategy.

Phase 1: Inventory and critique

• identify current or implied Premium ideas
• identify gaps, overlaps, weak perks, and confusing distinctions
• call out anything bloated, arbitrary, or not end-to-end

Phase 2: Define and improve

• rewrite features into clearer Premium perks
• assign tier placement
• define ecosystem behavior across Node / Dock / Web / Cloud
• simplify wording and user mental model

Phase 3: End-to-end cohesion check

• test whether the Premium system feels unified across all surfaces
• check for entitlement ambiguity
• check upgrade/downgrade logic
• check offline/local/cloud interactions
• ensure Business feels operationally stronger, not just “more of the same”

Phase 4: Final recommendation

• produce one final Premium architecture and UX plan
• include prioritized recommendations
• include implementation order
• include risks and open questions
• include concrete next actions

EXPECTED OUTPUT FORMAT

Return the work in this structure:

Premium Features End-to-End Plan

1. Executive Summary

• the clearest recommended direction for Premium
• what should change from current thinking
• what should stay

2. Premium Design Principles

• concise product rules for what Premium is and is not

3. Pro vs Business Tier Model

• clear description of each tier
• who it is for
• how it differs
• why the distinction is meaningful

4. Premium Perk Catalog

For each perk include:

• perk name
• short definition
• user problem solved
• tier (Pro or Business)
• surfaces involved (Node / Dock / Web / Cloud)
• entitlement/enforcement notes
• UX notes
• implementation complexity
• recommendation: keep / merge / cut / rename

5. Ecosystem Mapping

A clean mapping of premium features across:

• Node
• Dock
• Web
• Cloud

Make this explicit and practical.

6. UX Flow Pass

Cover:

• onboarding
• discovery
• locked states
• upgrade flow
• downgrade flow
• trial flow if relevant
• billing/entitlement visibility
• admin/team experiences if relevant

7. Technical Entitlement Architecture

Cover:

• source of truth
• sync model
• offline behavior
• local caching if relevant
• failure modes
• downgrade behavior
• seat/workspace/account rules
• feature gating approach

8. Business Tier Differentiation

Explain exactly why Business is worth more. This section must be especially strong. Avoid fluff.

9. Simplification Pass

List:

• features to remove
• features to merge
• features to rename
• anything too complex for current phase
• anything to defer until later

10. Implementation Roadmap

Recommend:

• phase 1
• phase 2
• phase 3

For each phase include:

• why now
• dependencies
• user-visible value
• risk level

11. Risks and Edge Cases

• entitlement confusion
• offline node behavior
• cloud dependency issues
• downgrade pain
• business admin complexity
• pricing perception risks
• support burden

12. Final Recommended Premium Model

Give the final concise recommended version that we should actually build.

QUALITY BAR

Your answer must be:

• concrete
• integrated
• realistic
• minimal where possible
• premium where it counts
• consistent across the whole ecosystem

Do not give a shallow brainstorm. Do not give generic SaaS filler. Do not hide uncertainty with vague language. When in doubt, simplify and strengthen.

If a Premium perk does not create real user value or creates too much complexity for too little gain, say so and recommend cutting it.

If a feature belongs only in Business, justify it clearly. If a feature belongs in both Pro and Business, explain the differentiation. If a feature depends on Cloud but the product also supports local Node workflows, explicitly resolve that tension.

Your job is to context-engineer the best Premium plan possible for this ecosystem.