scbe-fleet-deploy
Deploy trained models across the AI fleet — federated artifact fusion, quality gate checks, version promotion, multi-cloud orchestration, and rollback. Use when deploying models, promoting artifacts, checking deployment health, or managing the fleet release cycle.
Best use case
scbe-fleet-deploy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deploy trained models across the AI fleet — federated artifact fusion, quality gate checks, version promotion, multi-cloud orchestration, and rollback. Use when deploying models, promoting artifacts, checking deployment health, or managing the fleet release cycle.
Teams using scbe-fleet-deploy should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/scbe-fleet-deploy/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-fleet-deploy Compares
| Feature / Agent | scbe-fleet-deploy | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deploy trained models across the AI fleet — federated artifact fusion, quality gate checks, version promotion, multi-cloud orchestration, and rollback. Use when deploying models, promoting artifacts, checking deployment health, or managing the fleet release cycle.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# SCBE Fleet Deploy
Manage the deployment lifecycle from trained artifacts to running fleet agents.
## Deployment Pipeline
```
Trained Artifacts (HF, GCP, AWS)
|
v
Federated Fusion (training/federated_orchestrator.py)
|
v
Quality Gates (safety >= 0.95, quality >= 0.80)
|
v
Version Promotion (staging -> production)
|
v
Fleet Rollout (rolling update across agents)
|
v
Health Monitoring (coherence, latency, safety scores)
```
## Operations
### 1. Collect Artifacts
Gather training outputs from all providers:
```bash
# Each provider produces a manifest JSON
# HF: textgen models (LoRA adapters, full weights)
# GCP: embedding models (Vertex AI)
# AWS: runtime models (SageMaker endpoints)
ls training/manifests/
# hf_manifest.json gcp_manifest.json aws_manifest.json
```
### 2. Run Federated Fusion
```bash
python training/federated_orchestrator.py \
--manifests training/manifests/*.json \
--output training/fused_release.json \
--min-quality 0.80 \
--min-safety 0.95
```
### 3. Quality Gate Check
Every artifact must pass all gates before promotion:
| Gate | Threshold | Metric |
|------|-----------|--------|
| Quality | >= 0.80 | Task accuracy / BLEU / F1 |
| Safety | >= 0.95 | Governance compliance rate |
| Latency | <= 200ms p95 | Inference latency |
| Cost | <= $1.00/1K tokens | Compute cost |
Failed artifacts are rejected with detailed failure reports.
### 4. Version Promotion
```
staging -> canary (10% traffic) -> production (100%)
```
Each stage requires:
- Governance vote (BFT consensus from validator agents)
- Safety re-check at new scale
- Rollback plan documented
### 5. Fleet Rollout
Rolling update across the flock:
1. Select first batch (1 agent per specialty)
2. Deploy new model version
3. Monitor for 5 minutes (coherence, error rate)
4. If healthy: continue to next batch
5. If degraded: auto-rollback to previous version
### 6. Rollback
```bash
# Immediate rollback to last known good
python training/federated_orchestrator.py \
--rollback \
--target-version v2.1.0
```
### 7. Health Monitoring Post-Deploy
Track these metrics after deployment:
```python
# Per-agent metrics
agent.coherence # Should stay > 0.7
agent.error_rate # Should stay < 0.05
agent.response_time # Should stay < target
# Fleet-wide metrics
fleet.consensus_rate # BFT agreement percentage
fleet.safety_score # Governance compliance
fleet.task_throughput # Tasks completed per minute
```
## Multi-Cloud Provider Map
| Provider | Role | Artifact Type | Region |
|----------|------|--------------|--------|
| HuggingFace | textgen | LoRA adapters, full weights | Global CDN |
| GCP Vertex | embed | Embedding models | us-central1 |
| AWS SageMaker | runtime | Inference endpoints | us-east-1 |
## Key Files
| File | Purpose |
|------|---------|
| `training/federated_orchestrator.py` | Multi-cloud artifact fusion + gates |
| `training/train_node_fleet_three_specialty.py` | 3-head specialty training |
| `hydra/spine.py` | Fleet coordination backbone |
| `hydra/swarm_governance.py` | BFT consensus for promotions |
| `agents/browser/fleet_coordinator.py` | Browser fleet management |
## Sacred Tongue Deploy Mapping
| Stage | Tongue | Meaning |
|-------|--------|---------|
| Build | CA (Cascade) | Breaking down, compiling |
| Test | RU (Runethic) | Binding, validating rules |
| Stage | UM (Umbroth) | Hidden, not yet revealed |
| Deploy | KO (Kor'aelin) | Asserting into production |
| Monitor | AV (Avali) | Listening, watching |
| Rollback | DR (Draumric) | Structured retreat |Related Skills
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
scbe-code-scanning-ops
Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.
scbe-world-anvil-lore-rag-7th-tongue
Build and operate a lore-focused RAG system using World Anvil exports and SCBE docs, with deterministic Claude/Codex cross-talk packets for handoff. Use when users ask to structure lore canon retrieval, sync worldbuilding data, enforce citation-grounded generation, or coordinate a 7th Tongue overseer lane across multiple AI agents.
scbe-webtoon-book-conversion
Convert The Six Tongues Protocol and related manuscript sections into webtoon/manhwa storyboard packets, episode roadmaps, panel expansion plans, and image-generation-ready prompt lanes. Use when extending the series storyboard, adapting book chapters into vertical scroll episodes, or keeping art generation tied to canon instead of drifting into generic fantasy panels.
scbe-voice-render-verification
Govern and verify SCBE voice rendering work that maps Langues weighting into breath, phase, and Layer 14 audio-axis packets. Use when implementing or reviewing `scripts/voice_gen_hf.py`, emitting sidecar voice packets, validating canonical tongue ordering, tuning breath planning or phase timing, or keeping voice docs and code aligned with `docs/LANGUES_WEIGHTING_SYSTEM.md` and `docs/specs/SCBE_VOICE_EMOTIONAL_TIMBRE_SYSTEM.md`.
scbe-universal-synthesis
Orchestrate all installed Codex skills through an auto-updating synthesis matrix with Sacred Tongues routing, emotion/intent metadata, and decodable lexicon packets tied to established SCBE characters. Use when the user asks for cross-skill coordination, auto skill updates, multi-skill routing, or Sacred Tongues intent mapping.