AE New Project KB Bootstrap (ae-kb-bootstrap)

Purpose: when a new customer (company / caliber subject) is onboarded to AE analysis, use a two-stage flow — company onboarding (once per customer) → project onboarding (once per project) — to produce a compiled business metrics definition KB that is "query-ready". Afterwards, querying data for this project via kb-driven-data-analysis / ae-analysis reuses this caliber.

Why this skill exists (customer pain) and prerequisites

Customer pain: before a customer's metric calibers are written down, every data query re-guesses which events / fields / aggregations back a metric, so numbers drift and do not match the customer's own dashboards. This skill turns the customer's authoritative dashboards or reports into one compiled caliber library so later queries reuse a single definition instead of re-deriving it.

Prerequisites (check before starting; if any is missing, stop and ask — do not guess):

• ae-cli is authenticated and can search readable assets and read the selected report definitions (ae-cli analysis asset search and report get succeed).
• The authenticated user can create and edit company knowledge bases. If any --scope company write fails because of insufficient permission, stop, preserve the generated local files, and ask a company-KB administrator to grant access or execute the remaining commands. Never omit --scope company or silently fall back to a personal knowledge base.
• The target project_id, project name, and the authoritative caliber source are known (the user must pick the dashboard or report at gate ②).
• Company onboarding requires the metric family set and per-family default calibers to be confirmed with the user (hard gate).
• Degradation when data is unavailable: if asset search finds no readable candidate, broaden the search terms once; if it still returns empty, ask the user to grant access or provide the authoritative dashboard/report IDs. Never infer lack of access from dashboard list alone, and never guess event or field names.

Core concept: one directory, two layers

One customer = one KB directory. The directory holds both the company-level abstraction layer (reused unchanged across that customer's projects) and the project-level instance layer (appended once per project). Do not split into "company-layer directory + project directory" as two KBs.