# VibePackr enterprise agent integration kit

Ordinary workers do not edit these files. An administrator or supported setup
flow connects the kit to the organization's runtime and supplied installation.

Use this kit to help your organization's AI runtime agent install, connect,
prepare integrations and operate VibePackr through the interfaces supplied in
your release. Instructions are in English. Existing Parts 1–8 remain the full
user manuals.

## 1. Load the instructions

This kit does not install itself into your agent or change your agent settings.
First extract it into a private workspace and read this file.

- If your runtime supports `SKILL.md` folders, use its documented skill import
  mechanism to import the relevant folders under `skills/`. Each folder is
  self-contained. Do not copy VibePackr's internal development skills.
- Otherwise attach or explicitly ask the agent to read the required `SKILL.md`
  files as Markdown. Use the same instructions without claiming native skill
  discovery or automatic loading.
- Confirm which skill name and file the agent actually read. File installation
  alone does not prove the runtime loaded it. Start with a read-only task, such
  as identifying the supplied package and listing missing prerequisites.
- [runtime-plan.example.toml](runtime-plan.example.toml) is a human/agent planning worksheet. It is **not**
  a product connection profile, import format, permission grant or executable
  agent configuration. An administrator or the setup agent fills permitted values
  in a private planning copy. Ordinary workers do not edit this file. Never put keys, passwords or tokens in it.

No particular AI provider, hosted model, local model, MCP host or coding agent
is required by these instructions. Native skill discovery and tool execution
depend on your runtime's actual features and your organization's policy.

For the supplied local MCP adapter, the administrator/setup agent follows
[MCP setup and recovery](MCP_SETUP.md). It generates a private connection
descriptor; ordinary workers do not edit Skills, TOML or MCP JSON. The runtime's
documented import step and a live connection check are still required. Read the
supported tool table before assuming that a CLI action also has an MCP tool.

## 2. Choose a path

Start with [the workflow coordinator](skills/vibepackr-agent-workflow/SKILL.md)
for a multi-tool task or an interrupted run. Its case reference covers
installation, binding, integration, partial effects and resumption.

For an installation already in use, start with
[post-installation expansion](skills/vibepackr-postinstall-expansion/SKILL.md).
Adding a legacy system, connector, AI runtime or model requires a new GAPE
observation of the approved changed architecture and a comparison with the
retained baseline. Runtime discovery/binding is a separate product check; GAPE
does not establish runtime readiness or access permission.

| Stage | Skill folder | Inputs | Observable result |
|---|---|---|---|
| Appliance installation | [vibepackr-install](skills/vibepackr-install/SKILL.md) | Complete approved appliance package, Linux administrator authority | Installer exit and actual health/readiness observations |
| Architecture observation | [vibepackr-gape](skills/vibepackr-gape/SKILL.md) | Approved manifest and permitted revision-bound source scope | Snapshot and snapshot-validation result |
| Preparation before declarations | [vibepackr-integration-helper](skills/vibepackr-integration-helper/SKILL.md) | Complete supported synthetic/request envelope | Discovery/normalization findings |
| Contract and Document declarations | [vibepackr-declarations](skills/vibepackr-declarations/SKILL.md) | Complete source Document, full request and published target references | Parsed draft and reviewed mapping |
| Validation after declarations | [vibepackr-integration-helper](skills/vibepackr-integration-helper/SKILL.md) | Revised full envelope | Actual validation/preparation/status responses |
| Adapter candidate, when needed | [vibepackr-sdk-engine](skills/vibepackr-sdk-engine/SKILL.md) | Supported full request, selected toolchain/dependency set | New adapter candidate and its manifest |
| Pack candidate, when needed | [vibepackr-builder](skills/vibepackr-builder/SKILL.md) | Supplied Builder, supported template/Pack, permitted role | Candidate revision and actual validation state |
| Governed operation | [vibepackr-headless](skills/vibepackr-headless/SKILL.md) or [vibepackr-packrgui](skills/vibepackr-packrgui/SKILL.md) | Provisioned appliance connection, identity, current role and authorized operation | Same Work's result, validation and receipt |

The usual route is installation → optional GAPE observation → Helper discovery
→ declarations → Helper validation/preparation → SDK and/or Builder when the
integration requires them → authorized operation. Helper is used on **both**
sides of declaration work. Skip SDK when a supplied supported integration
already meets the requirement. Skip Builder when an existing approved Pack
already meets it. Do not build a new adapter or Pack merely to complete a list.

The expansion route is: preserve the working baseline → rerun GAPE for the
approved changed scope → compare observations → Helper impact assessment →
declarations and conditional SDK/Builder work → product validation of the new
connection/binding → isolated example and affected existing-use checks →
supported activation within the organization's authority. Keep the old
connection and in-flight Work intact until the change has a validated disposition.

## 3. Keep four facts separate

1. The AI agent can draft requests and invoke permitted tools.
2. The product returns the actual validation, binding and authority decisions.
3. A candidate or a successful local synthetic example is not an approved Pack
   or an operational Work.
4. Completion requires the actual result and, for executed Work, its matching
   product validation and receipt. The agent's notes are not that receipt.

Use only release-supplied public commands and supported interfaces. Do not
replace a refusal with invented success, guessed IDs, modified manifests,
direct store edits or arbitrary shell workers. Do not weaken authentication,
certificate checks, isolation or approval requirements to make a step pass.

## 4. Run a safe first exercise

Ask your agent:

> Read START_HERE.md and the SDK Engine skill. Identify the actual OS/CPU,
> executable, package identity and synthetic request. Show the planned inputs
> and fresh output folder. Analyze the supplied synthetic request within my
> authorized local workspace. Preserve existing results. Do not submit Work,
> enroll a customer, contact a provider or change an appliance.

For appliance operation, start by reading the headless or GUI skill and
confirming the administrator-supplied connection and expected installation.
Do not substitute the local SDK exercise for an appliance connection check.

Online and offline environments are supported choices. The optional SDK Rust
dependency set is intended for closed on-premises builds; offline mode is not
the default. That set does not supply model weights, provider access, every
third-party tool or all native OS prerequisites.

## 5. Record and resume

Use [RUN_RECEIPT.template.md](RUN_RECEIPT.template.md) for a minimized operator note. Preserve originals,
record actual process exits separately from product JSON, and use a fresh
output directory when changing inputs. If a request times out after submission,
reconcile its original ID/state before submitting again.

Host identities, credentials, customer data, prompts and raw logs remain inside
the organization's approved boundary. Do not send them to a hosted AI runtime,
support service or another operator unless that exact disclosure is authorized.
Refer to credentials through your approved credential mechanism, not chat text.

If the release does not supply an interface, template, required enrollment
material or suitable native environment, record the missing prerequisite and
the responsible owner. Continue independent preparation; do not invent a route.

## Manual mapping

Part.1 installation; Part.2 GAPE; Part.3 Integration Helper; Part.4 Contract and
Document; Part.5 SDK Engine; Part.6 Builder; Part.7 PackrGUI/headless; Part.8
operations and troubleshooting. Use the supplied manual index to open the
current headings, including when an older filename redirects to the same Part.