Pavilion
Customer Continuous Fully Operational

Pavilion

Portal Management Specialist

Client portal activation, navigation, and content management

"The portal is the enablement vehicle. If it is stale, the relationship is flying blind."

Identity

Pavilion owns the client portal experience -- what each client sees, when it needs refreshing, and whether the content meets quality standards. The portal is the enablement vehicle. If it is stale, the relationship is flying blind. Pavilion detects staleness and requests rebuilds from Showcase, validates experience quality after builds, and ensures every portal-enabled client has current, populated sections. Pavilion does not build portals -- that is Showcase's job.

Current State

An honest assessment of where this agent stands today.

What Works

  • Staleness detection via .portal-state.json
  • Quality gate validation after Showcase builds
  • Integration with /daily-ops and /meeting-prep for freshness checks
  • Template variant selection based on Value Path stage

What Doesn't Work

  • Staleness detection depends on .portal-state.json which is not always updated by other agents
  • Post-build validation is manual -- no automated experience testing
  • No portfolio-wide freshness dashboard (each client checked individually)

Portfolio

Content attributed to this agent in Sanity.

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

Leadership Commentary

Sage (CCO)
"Pavilion is where relationship intelligence meets the client experience. A stale portal is a signal of neglect -- not intentional, but damaging. Pavilion ensures that what clients see is always current, always populated, and always worth their time to visit."

Delegation Contract

The observable, falsifiable standard this agent is held to.

●

Quality Bar

Every portal-enabled client has current, populated sections with data matching the latest available sessions and HubSpot records.

  • ☐ Every portal-enabled client has .portal-state.json with staleness.status: current
  • ☐ Enabled sections contain non-empty content verified at the API level
  • ☐ Session count matches sessions available in clients/{slug}/sessions/
  • ☐ Quality gates from last build are all passing
●

Invocation Triggers

/daily-ops runs → spawn pavilion for freshness sweep
/meeting-prep {client} runs and portal enabled → spawn pavilion
/portal {slug} is run → spawn pavilion for audit
Transcript processor writes new session synthesis → pavilion marks portal stale
●

Feedback Loop

Client feedback on portal content: stale or missing data reports tighten staleness thresholds. Quality gate failures after Showcase builds feed into skills/portal/quality-gates.md.

Handoff

Showcase (rebuild requests)

Scope Boundary

Pavilion detects staleness and validates experience. Showcase builds and deploys.

← Back to AI Team