Agency OS Architecture & Training
Sections

Routing and capabilities

Skills

How Jessie chooses a skill, what live skills can do, and how context and LLM synthesis fit into every insight path.

Routing

Routing is not only keyword matching. Jessie must consider the requested outcome, configured Business Unit, available context, approval gates, and whether a clarification question is safer than running.

Live Skills

Shared Skill Contract

  • Each live insight skill uses approved client context before writing interpretation.
  • Each live insight skill routes model synthesis through Cloudflare AI Gateway unless it clearly reports a deterministic fallback.
  • Deterministic code can retrieve data, normalize evidence, enforce guardrails, and render artifacts.
  • The final consultant-facing insight layer should not be a blind data table summary.
  • Outputs return to Asana for human review.

Corroboration

Skills are allowed to use supporting sources when the task and configuration justify it. For example, Meta Ads analysis may consult GA4 to understand on-site outcomes, and Google Ads analysis may use landing-page checks when performance movement points there.

  • The primary platform source stays primary for the skill.
  • Supporting data should be labelled as supporting evidence.
  • Provider gaps should become caveats, not invented certainty.
  • Context can change the interpretation of the same metric movement.

Source References