Run any Skill in Manus with one click

aidp-fusion-bootstrap

Stars2

Forks2

UpdatedJune 17, 2026 at 13:08

Guide and run the Oracle AIDP Fusion bundle bootstrap phase. Validates bundle/config readiness, checks AIDP/Fusion/IAM prerequisites, runs `aidp-fusion-bundle bootstrap --check-iam` or `bootstrap --refresh`, surfaces tenant variation choices pinned into the active profile YAML and evidence snapshots, and routes unresolved variation failures (`AIDPF-2010` / `AIDPF-2011`) to `/medallion-author`. Use when the user says 'bootstrap', 'pin tenant variation', 'create the profile', 'run pre-seed checks', 'missing profile', 'bootstrap --refresh', or needs the setup phase before seed/incremental. NOT for seed runs, incremental refresh, OAC dataset/workbook work, or net-new mart authoring.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ahmedawan-oracle

ahmedawan-oracle/claude-code-plugins

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

More from this repository

same repository

mart-author

ahmedawan-oracle/claude-code-plugins

Author a new medallion node (gold mart, silver dim, or additive column) when the live gold layer AND the content pack both cannot serve a business need. Takes the user's business logic, inspects the Fusion PVO SOURCE schema (not bronze) for available raw fields, and authors the lowest-cost, additive, non-destructive change as content-pack YAML + SQL in an overlay pack — never touching already-materialized (possibly terabyte-scale) bronze/silver. Then validates and hands off to seed. Use when oac-dataset-advisor reports a true GAP, or the user says 'add a metric/dimension my gold layer doesn't have', 'create a new mart for <business logic>', 'I need a column that doesn't exist'. Does NOT seed, query live data, alter existing nodes' grain/keys, or write Python dim modules.

2026-06-302

aidpf-error-triage

ahmedawan-oracle/claude-code-plugins

Read-only triage router for Oracle AIDP Fusion bundle failures. Use when the user pastes CLI output, a traceback, an `.aidp/diagnostics` path, a run id, or says bootstrap, validate, seed, incremental, dashboard, OAC, or workbook failed. Extract `AIDPF-*` codes, affected run id, dataset, layer, variation point, or diagnostic artifact; explain the failure briefly; route to the correct skill or command such as `/aidp-fusion-config`, `/aidp-fusion-bootstrap`, `/medallion-author`, `/fusion-drift-doctor`, `/aidp-fusion-seed`, `/aidp-fusion-incremental`, `/oac-dataset-setup`, or `/workbook-authoring`. Also triage non-AIDPF OAC MCP disconnect symptoms. Never run destructive seed, never edit profiles or overlays, and never bypass drift gates.

2026-06-262

fusion-drift-doctor

ahmedawan-oracle/claude-code-plugins

Diagnose and route Fusion->AIDP schema-drift / gate failures. When a run fails with a drift gate (AIDPF-2072 Fusion PVO drift, AIDPF-4070/4071 source-schema, AIDPF-2012 bronze fingerprint, AIDPF-4040 plan-hash), this read-only skill explains the code, probes the LIVE Fusion PVO, classifies each affected column, and routes the fix: bootstrap --refresh (mechanical re-pin), /medallion-author (overlay a new column name the pack never anticipated), re-seed (plan-hash drift), or human investigate. Use when an incremental/seed run reports schema drift or an AIDPF-20xx/40xx gate, when 'the Fusion PVO column changed', or as a precheck before /aidp-fusion-incremental. Does NOT fix anything itself — it diagnoses and hands off.

2026-06-252

medallion-author

ahmedawan-oracle/claude-code-plugins

Draft a content-pack overlay extending the starter pack's variation-point candidate lists when `aidp-fusion-bundle bootstrap` fails AIDPF-2010 / AIDPF-2011. Reads diagnostic artifacts under `.aidp/diagnostics/<run_id>/`, proposes new candidates from the observed bronze schema, presents a draft overlay for operator approval, and drafts a backend-aware remediation runbook (Option A/B/D/E; Option C deferred to v0.4). Use when the CLI exits 1 with AIDPF-2010 or AIDPF-2011 on a fresh tenant or after a Fusion-release upgrade. NOT for runtime drift detection or for authoring net-new silver/gold nodes; skill-authored SQL templates are forbidden.

2026-06-252

aidp-fusion-autopilot

ahmedawan-oracle/claude-code-plugins

End-to-end conductor for the Fusion to AIDP to OAC dashboard journey. Takes one high-level goal ('I want a supplier-spend vs GL-balance dashboard from Fusion') and drives the whole chain: configure, connect OAC MCP, bootstrap, seed, advise dataset, author mart if needed, create OAC dataset, author workbook, and optionally enable end-user MCP chat by detecting current state and delegating each step to the right sibling skill/command. Auto-advances on clean steps; pauses for real decisions (destructive seed, variation freeze, OAC dataset creation, ambiguous intent, gaps). Use when the user states a dashboard/analytics goal and wants it driven start-to-finish, OR on first run after installing the plugin: 'I just installed this, what now', 'get me started', 'set me up', 'set up Fusion analytics from scratch / end to end', 'autopilot this', 'take me from nothing to a dashboard'. This is the front door for a fresh install (setup scaffolds the bundle). NOT for a single known step (call that skill directly).

2026-06-172

aidp-fusion-bundle

ahmedawan-oracle/claude-code-plugins

Productized Fusion → Oracle AI Data Platform pipeline with curated BICC extracts (GL/AR/AP/PO/Suppliers/Items), bronze/silver/gold medallion in Delta, conformed dimensions (account/calendar/org/supplier/item), gold marts (AR-Aging/AP-Aging/GL-Balance/PO-Backlog/Supplier-Spend), and MCP-native OAC workbook authoring. Use when the user wants to load Fusion ERP/HCM/SCM data into AIDP, build a CFO dashboard from Fusion, set up a Fusion-backed lakehouse, create OAC datasets/workbooks over AIDP gold, set up OAC MCP for operator authoring or natural-language Fusion analytics in Claude/Cline/Copilot, run BICC extracts incrementally, productize the Oracle blog "Bring Fusion Data into AIDP Workbench Using BICC", or extract Fusion via the saas-batch REST API. Triggers — "load Fusion into AIDP", "set up Fusion bronze layer", "build CFO dashboard from Fusion", "create OAC workbook from Fusion", "run BICC extract", "Fusion AIDP medallion", "saas-batch Fusion extract".

2026-06-172

name	aidp-fusion-bootstrap
description	Guide and run the Oracle AIDP Fusion bundle bootstrap phase. Validates bundle/config readiness, checks AIDP/Fusion/IAM prerequisites, runs `aidp-fusion-bundle bootstrap --check-iam` or `bootstrap --refresh`, surfaces tenant variation choices pinned into the active profile YAML and evidence snapshots, and routes unresolved variation failures (`AIDPF-2010` / `AIDPF-2011`) to `/medallion-author`. Use when the user says 'bootstrap', 'pin tenant variation', 'create the profile', 'run pre-seed checks', 'missing profile', 'bootstrap --refresh', or needs the setup phase before seed/incremental. NOT for seed runs, incremental refresh, OAC dataset/workbook work, or net-new mart authoring.
allowed-tools	Read, Bash, Glob, Grep

aidp-fusion-bootstrap — bootstrap tenant profile and variation

This skill owns the bootstrap phase only: validate the customer project, run the CLI bootstrap safely, surface what tenant variation was pinned, and route bootstrap-specific failures. It shells out to aidp-fusion-bundle; it never edits profiles/, evidence/, or diagnostics directly.

Bootstrap is the bridge between configuration and first seed. It probes prerequisites, resolves content-pack variation points against the tenant, and writes the runtime profile used by seed and incremental runs.

When to use

"Run bootstrap", "bootstrap this tenant", "pin tenant variation".
"Create the profile", "my profile is missing", "profiles/.yaml is absent".
"Run pre-seed checks", "check IAM before seed", "verify BICC/AIDP prerequisites".
"Run bootstrap --refresh" after AIDPF-2012, PVO/source drift remediation, or a Fusion release change.
A seed or incremental precondition reports missing: ["profile"].

When NOT to use

First materialization or overwrite of bronze/silver/gold -> /aidp-fusion-seed.
Day-2 refresh -> /aidp-fusion-incremental.
Runtime drift diagnosis (AIDPF-2072, AIDPF-4070/4071, AIDPF-4040) -> /fusion-drift-doctor.
Authoring new analytical content -> /mart-author.
OAC connection, dataset, or workbook work -> OAC dataset/workbook skills.

What bootstrap does

Runs pre-onboarding probes: bundle/config shape, BICC auth, BICC catalog reachability, AIDP REST, and optional IAM checks.
Probes the tenant bronze schema for the active content pack. When a bronze table is already landed it reads the live Delta schema; when it is not yet landed (a fresh tenant) it resolves the same schema from the BICC PVO source via a metadata-only inferSchema probe — so bootstrap runs before the first seed, with no chicken-and-egg. The fingerprint is identical either way (bronze audit columns are stripped before fingerprinting).
Walks pack-declared columnAliases and semanticVariants.
Pins resolved values to profiles/<contentPack.profile>.yaml.
Writes profiles/<contentPack.profile>.schema-snapshot.yaml.
Writes evidence under evidence/<profile>/<timestamp>.yaml.
On unresolved required variation points, writes diagnostics under .aidp/diagnostics/<run_id>/.

Bootstrap is the only writer to profiles/ and evidence/. Do not hand-edit resolved profile values to make a run pass.

Workflow

1. Confirm project root and config readiness

Run from the customer project root, where bundle.yaml and aidp.config.yaml live. Validate first:

aidp-fusion-bundle validate

If available, use the shared precondition helper for a structured view. Resolve the helper relative to this skill directory, or use its absolute path when your shell is in a customer project:

python3 ../aidp-fusion-seed/preconditions.py \
  --bundle bundle.yaml \
  --config aidp.config.yaml \
  --env <env>

Interpret missing for bootstrap this way:

bundle: stop and have the user run aidp-fusion-bundle init or fix bundle.yaml.
config: route to /aidp-fusion-config; bootstrap cannot invent AIDP coordinates.
profile: this is the bootstrap target; proceed unless another blocker exists.
cluster: start or fix the AIDP cluster before default cluster-dispatched bootstrap.

Also confirm the Fusion password is in the AIDP credential store as fusion_bicc_password with key password. Do not ask the user to paste secrets into chat.

2. Choose initial bootstrap vs refresh

Use initial bootstrap when no valid profile exists:

aidp-fusion-bundle bootstrap --check-iam

Use refresh only when a prior profile exists and you are re-pinning against live bronze after drift or a Fusion release change:

aidp-fusion-bundle bootstrap --refresh --check-iam

Do not run --refresh as a blind fix for unrelated seed failures. Runtime drift codes should be diagnosed by /fusion-drift-doctor first, then routed here when the safe fix is bootstrap refresh.

3. Preserve operator control

Bootstrap can freeze tenant variation choices. Before running, tell the user:

which profile will be written,
whether this is initial pinning or refresh,
whether IAM checks are enabled,
whether the run may prompt for a multi-match variation choice.

Prefer the default interactive operator path for real tenants. Do not use --non-interactive for customer onboarding unless the user explicitly asks for CI/sandbox behavior and accepts first-candidate auto-pick semantics.

For audit identity issues (AIDPF-1020), ask for or set a concrete operator:

aidp-fusion-bundle bootstrap --check-iam --operator "<operator-id>"

4. Run bootstrap and classify the result

On success, report the concrete artifacts:

profiles/<contentPack.profile>.yaml
profiles/<contentPack.profile>.schema-snapshot.yaml
latest evidence/<profile>/<timestamp>.yaml
key resolved variation choices: column aliases and semantic variants
any IAM/BICC/AIDP warnings that remain

Then hand off to /aidp-fusion-seed for first materialization.

On failure, classify before recommending action:

Failure	Meaning	Route
`AIDPF-2010`	Required `columnAliases` variation point had no candidate on tenant bronze.	`/medallion-author`
`AIDPF-2011`	Required `semanticVariants` variation point had no matching detector.	`/medallion-author`
`AIDPF-1020`	Operator identity missing.	Re-run with `--operator` or fix `AIDP_OPERATOR` / `USER`.
BICC auth/storage	Fusion or BICC external storage prerequisite missing.	Fix Fusion/BICC setup; do not author overlays.
AIDP REST/IAM	Workspace/cluster/permission issue.	Fix config/IAM/cluster before rerun.

For AIDPF-2010 / AIDPF-2011, point the user at the diagnostics directory:

.aidp/diagnostics/<run_id>/AIDPF-2010__<variation-point>.json
.aidp/diagnostics/<run_id>/AIDPF-2011__<variation-point>.json

Then invoke or recommend /medallion-author. That skill reads the diagnostics and drafts an overlay; bootstrap remains the only step that commits the final profile/evidence by rerunning initial bootstrap or bootstrap --refresh.

5. Refresh-specific rules

Use bootstrap --refresh when:

/fusion-drift-doctor classifies drift as mechanically re-pinnable.
AIDPF-2012 reports bronze fingerprint drift and the operator confirms the bronze change is intended.
A profile predates schema-snapshot support and needs back-fill.

Refresh must not silently change pinned choices. If refresh wants to change a pinned value, surface the old value, proposed value, evidence, and ask the user before continuing. If a new candidate is needed, route to /medallion-author.

For power-user refresh after known-good onboarding, --skip-preonboarding-probes is available only with local dispatch. Do not use it as the default demo or customer path.

Output contract

Finish with a compact bootstrap ledger:

bootstrap: success
profile: profiles/finance-default.yaml
schema snapshot: profiles/finance-default.schema-snapshot.yaml
evidence: evidence/finance-default/<timestamp>.yaml
variation: 12 column aliases pinned, 2 semantic variants pinned
next: /aidp-fusion-seed

On failure:

bootstrap: failed AIDPF-2010
diagnostics: .aidp/diagnostics/<run_id>/AIDPF-2010__invoice_currency_code.json
route: /medallion-author to draft an overlay, then re-run bootstrap

Safety invariants

The CLI is the contract; never import orchestrator internals or mutate state directly.
Do not edit profiles/, profiles/*.schema-snapshot.yaml, or evidence/ by hand.
Do not treat pack YAML as proof that the tenant profile exists.
Do not run seed from this skill; hand off to /aidp-fusion-seed.
Do not hide variation choices. Surface what bootstrap pins.
Route unresolved variation (AIDPF-2010 / AIDPF-2011) to /medallion-author, not /mart-author.
Keep secrets out of chat and logs.