company-bootstrap

Files (2)

• SKILL.md
• skill.json

SKILL.md (first lines)

# Company Bootstrap

Bootstrap or adopt a Company without assuming a fixed business shape.

## Entry modes

### NEW COMPANY

`purpose + founder constraints → market/business thesis → minimum functions → skills/capabilities/assets → provision → verify → pilot → outcomes`

Start from what the Company needs to accomplish. Select the smallest reusable skill set that covers required capabilities and departments. Create company-local skill candidates only for gaps. Do not install harness-only skills into Company work.

### EXISTING COMPANY

`discover systems/assets/processes → reconstruct model/KPIs → map functions + sources of truth → map skills → preserve what works → establish baselines → improve progressively`

Observe before reorganizing. Existing processes that map to a reusable skill are adopted/reused. Existing working processes with no reusable match become company-local SkillGene candidates with evidence references; they are not discarded merely because the global catalog lacks a definition.

## Skill plane

1. Search the global Company Skill Registry by purpose, department, scope and required capabilities.
2. Reuse active installations where possible.
3. Install reusable catalog skills Company-scoped through `skill-installation` assets.
4. Preserve company-specific procedures as `company-skill-definition` assets plus `CorporateGene(type=skill)`.
5. Use verified BusinessOutcome learning to evolve candidate → challenger → champion; use silent/quarantine/retired for losing/risky variants.
6. Only if a company-local skill proves genuinely reusable across contexts should it be proposed for the shared global catalog; that system-level promotion is governed through KAST.

## Boundaries

Company skills do not grant authority, budget, credentials or legal capacity. KYC, MFA, contracts, new debt/capital and other reserved actions remain human/Founder boundaries.

From riquelmechile/XanxitoSpA, MIT.

More from riquelmechile/XanxitoSpA