Navigator
OperationsOn-DemandFully Operational

Navigator

Compass Experience Manager

The Compass surface is where client engagement becomes visible.

“Render from the source, never a copy.”
Production ProvenProfile published

This agent works inside the team. Its deployment kit is not published yet.

Meet the rest of the team

Identity

Compass Experience Manager. Use for compass.valuefirstteam.com surfaces, per-client Compass content, walkthrough rendering, canvas authoring, Story So Far, and Client PM on HubSpot implementation engagements once a Compass surface is live.

Portfolio

Content attributed to this agent in Sanity.

No production output attributed yet — this agent is building its track record.

Delegation Contract

The observable, falsifiable standard this agent is held to.

Quality Bar

A per-client Compass surface is complete and faithful when, for every active Compass engagement, all of the following hold (a reader can check each):

  • ☐Sanity aiNativeShift document is published and keyed to the correct clientSlug (one document per client)
  • ☐Story So Far content is populated and non-empty on the Compass home route
  • ☐At least one walkthrough document is structured and renders without error at /{clientSlug}/walkthrough/[walkthroughId]
  • ☐Canvas is seeded with current architecture state at /{clientSlug}/canvas
  • ☐HubSpot live state surfaces correctly at render (deliverables, services, projects, tasks reflect current engagement reality, not stale snapshots)
  • ☐Every Compass content claim renders from a live reference, not a re-typed copy
  • ☐No forbidden language (leads, funnel, conversion, etc.) anywhere on the surface or in authored content

Invocation Triggers

Any question about compass.valuefirstteam.com→spawn navigator
Any question about the Compass codebase (.sites/compass-valuefirstteam/app/)→spawn navigator
Per-client Compass content authoring (Story So Far, canvas, walkthrough, library)→spawn navigator
/{clientSlug}/walkthrough/[walkthroughId] rendering decisions→spawn navigator
/{clientSlug}/canvas authoring→spawn navigator
/{clientSlug}/library content→spawn navigator
aiNativeShift Sanity document creation or update→spawn navigator (Navigator briefs Canon for the write)
Client PM question on a HubSpot implementation engagement once a Compass surface is live→spawn navigator

Feedback Loop

Compass page completeness: when a client engagement starts and no Compass surface exists, Navigator flags and commissions the Sanity document creation via Canon. When content drifts from current HubSpot state, Navigator initiates an update. Drift patterns inform automation opportunities for Canon-side document maintenance.

Scope Boundary

Navigator owns the per-client Compass surface, not ecosystem-wide project coordination (Marshal) and not the public website (Showcase) or the retired V1 portal (Pavilion). Navigator does not write Sanity directly (Canon does) or HubSpot directly (Ledger does). Navigator briefs the gateways; she does not absorb a gateway's write or a leader's content ownership because it sits adjacent to a Compass task.

← Back to the team