A business understood.
A next move connected.

Build a shared record of what the business offers, whom it serves, and what it is trying to achieve. Keep unknowns and proposed facts distinct from what a person has established.

Maintain versioned guidelines and evidence-backed claims. Withdrawal, expiry, or changed context can require affected work to be reviewed again. Approval belongs to a specific version.

Record a decision with the evidence behind it. Reopening it retains its history, so a new owner can understand what changed and why the original choice was made.

Configure permitted sources and competitor pages. Keep collected changes separate from a person’s interpretation; a failed check is not evidence that a competitor changed. Collection requires source setup and an operating schedule.

Run bounded website crawls, compare findings, and connect an issue to a task. A later crawl can verify a fix. Supported file imports add search and research context without pretending that an external account is connected.

Retain the customer’s words and the source of an inquiry. Review recurring needs and themes, then connect them to marketing work or a proposed product initiative. Importing a contact does not authorize outreach.

Read-only authorization and bounded reporting are implemented locally. Live use requires Google configuration, an authorized property, and provider verification. Reporting is on demand; continuous synchronization is not implied.

ICP briefs and reviewed seed or licensed-file imports exist in the native workflow. Live provider discovery remains planned and requires a selected provider, appropriate data rights, and verification.

A plan explains its inputs, alternatives, prerequisites, and a useful first test. A limited budget can concentrate the plan; missing conversion measurement can defer paid channels. People approve the resulting direction.

The operating cycle evaluates available evidence and implemented rules, records recommendations, and can prepare bounded draft work. Repeated checks retain history and avoid duplicating the same task. Scheduling needs a configured worker.

Bring workspace priorities, diagnostics, requirements, experiments, and retained learning into one investigation. Keep the hypothesis, evidence, and outcome together before carrying a conclusion into the next plan.

Keep readiness, execution, commercial outcomes, and data confidence separate. Checks that lack their required inputs remain unknown. Review the reason behind a priority instead of treating a blended score as business truth.

Organize employees, partners, platforms, evidence, and commitments around a responsibility. Review ownership, delivery, evidence freshness, and continuity gaps. Assignment does not grant access to restricted sources.

Start a process from its reviewed blueprint. Its tasks retain dependencies and require completion evidence. Changes to the blueprint affect future runs; reopening work preserves the previous evidence.

Compare known availability with estimated dated work. Trace confirmed dependencies and preview which task dates would shift. Missing estimates and relationships stay visible; a person applies a current scenario.

Record evidence, next actions, and review dates. Supported recurring deliveries can renew after review. Handovers preserve history and can transfer open work without transferring credentials or silently expanding permissions.

Export versioned Markdown and JSON packages with source references and a clear return contract. Current export and source-use permissions are checked. The package carries focused context rather than exposing every workspace record.

Retain the relationship to the original package and content version. Changed context, withdrawn evidence, or stale work can block adoption. Human adoption is separate from approval and publication.

MCP tools use the same brand boundaries and service permissions as the interface. Agent proposals cannot establish consequential truth. Hosted client compatibility, authorization, and supported operations are verified for the access being offered.

Model-assisted features require operator configuration and the appropriate data permissions. Native records and deterministic checks remain usable without a model. Managed AI provisioning and included usage are confirmed with access.

Review the brief, prepare or import work, and approve the exact version with its context. Edits and changed evidence can end an approval. A draft, approved asset, and verified publication are distinct states.

Maintain campaign plans, readiness checks, budget pools, and ledger records. These native records support controlled decisions; they do not imply that an advertising account is connected or spending money.

Keep lifecycle planning and partner records connected to the CRM and permissions. Separate an outreach attempt from confirmed coverage, and retain the terms and evidence behind a deliverable.

Broad external delivery is a release-dependent extension. Each provider needs an implemented adapter, credentials, permissions, and verified operations. The native planning and approval workflows do not imply that delivery integrations are live.

Compare complete periods and drill into scoped records. Keep currencies, coverage, and definitions explicit. More recorded activity is not automatically business improvement, and pipeline value is not collected revenue.

Record a test plan, source-attributed results, and a review. Supported experiment readouts distinguish exploratory findings from a final result. A simple before-and-after change does not establish causation.

A reviewed recommendation can produce a linked follow-up task with a review date. Learning stays associated with the work and decision that produced it; a proposed change does not silently rewrite the strategy.

Explore different views of shared company records. Trace confirmed relationships to owners, work, goals, controls, and systems. Missing relationships remain unknown rather than producing invented impact.

Create and review diagram versions with owners and links to campaigns, pipeline stages, initiatives, work, and systems. Export Markdown, JSON, SVG, or PNG. A diagram describes a design; drawing a connection does not execute work.

Keep the link between a customer need and a proposed product response. People establish commitments and roadmap changes. These native records provide product context; the full advanced Product OS scope is still broader than the current build.

Maintain native data-use and privacy workflows with scoped access and recorded decisions. These controls support the work of responsible handling; they do not constitute a compliance certification or autonomous legal judgment.

A shared portfolio does not merge business truth or automatically grant access to every brand. Authorized people can switch between their workspaces while each brand retains its own operating record.

Roll-ups preserve coverage and currency differences and draw only from brands the viewer may access. Missing reporting is not counted as zero. Allocation proposals remain reviewable decisions.

Supported exports and previewed imports preserve defined contracts. Work, company maps, handoffs, and schematics have distinct formats and limits; an export is not a promise of universal restore. Agents propose, and people approve consequential decisions.