Factory Updates

---
name: factory-updates
description: Request and apply updates from the source factory
type: skill
agents: []
knowledge: []
---

# Factory Updates Skill

## When to Use

Use this skill when:
- The user asks to "update capabilities from the factory"
- The user wants to check for new skills, agents, or knowledge
- The user wants to renegotiate scope (add/remove domain capabilities)
- After a factory has released new components

## Prerequisites

- PABP library installed at `lib/society/pabp/`
- Stored scope agreement at `docs/transfers/scope-agreement-*.json`
- Stored capability declaration at `docs/transfers/capability-declaration.json`
- Access to the factory project path

## Process

### Step 1: Check Current State
Read the latest scope agreement from `docs/transfers/`:
- What domains are included?
- When was the last transfer?
- How many components are installed?

### Step 2: Determine Update Type

**Incremental Update** (default):
- Uses existing scope agreement
- Only transfers new/changed components
- Skips existing files

**Scope Renegotiation** (when user wants different capabilities):
- Regenerates capability declaration from current `.cursorrules`
- Negotiates new scope agreement with factory
- May add or remove domain capabilities

### Step 3: Execute Update

Run the update script:
```bash
python scripts/request_updates.py --factory-path <FACTORY_PATH>
```

Or for renegotiation:
```bash
python scripts/request_updates.py --factory-path <FACTORY_PATH> --renegotiate
```

### Step 4: Report Results

After the update completes, report:
- Components added (new)
- Components updated (changed)
- Components skipped (unchanged)
- Content transformations applied (if cross-platform)
- Foreign artifacts cleaned up (if cross-platform)
- Updated audit trail location

### Step 5: Verify

Check that:
- All new components are accessible
- No foreign IDE artifacts remain
- Audit log is saved in `docs/transfers/`
- Scope agreement is updated (if renegotiated)

## Configuration

The factory path can be configured in:
- Environment variable: `FACTORY_PATH`
- Config file: `.cursor/config/factory.json` with `{"factory_path": "..."}`
- Command line argument

## Troubleshooting

**No scope agreement found**: Run with `--renegotiate` to create a fresh agreement.

**Factory path not accessible**: Ensure the factory project is available locally.

**Import errors**: Ensure `lib/society/pabp/` is installed. Run the initial transfer first.

## Best Practices

- Always back up the current scope agreement before renegotiating
- Use incremental updates unless scope changes are needed
- Verify axiom alignment after each update with the `alignment-check` skill
- Review the audit trail in `docs/transfers/` after every update
- Keep the factory path configured in `.cursor/config/factory.json` for repeatability
- Test newly transferred components before relying on them in production workflows

## Related

- Skill: `export-agent-bundle` -- Export this project as a bundle
- Skill: `alignment-check` -- Verify axiom alignment of transferred components
- Knowledge: `agent-society-protocol` -- Protocol specification

SDG - Love - Truth - Beauty