# VibePackr

> VibePackr (built on BT-OS) is an enterprise governed AI execution control plane developed by VibePackr Co., Ltd. (Seoul, Republic of Korea). For supported Work routed through VibePackr, the protected Packr Engine (Rust) evaluates applicable authority, policy, and scope before execution, constrains supported actions, validates results, and binds evidence for review and separate human acceptance.

## Core Thesis & Epistemic Boundaries

- **Core Thesis**: AI can propose. You govern execution.
- **Fundamental Separation**:
  - `Capability != Authority` (An AI model or agent's ability to reason, plan, or call a tool does not grant permission to execute an enterprise operation.)
  - `Identity != Work-Specific Authority` (IAM/PAM authentication and resource reachability do not independently authorize every proposed Work request.)
  - `Gateway / Orchestration != Work Governance` (API gateways control endpoint traffic; orchestrators coordinate multi-step workflows; VibePackr governs whether a specific supported Work request is authorized to execute, under what boundary, and records integrity-bound evidence.)
  - `Preparation != Activation` (`GAPE` read-only source/snapshot reconciliation and `Integration Helper` architecture-bound planning prepare context and plans; neither registers, binds, or authorizes execution.)
  - `Execution != Proven Outcome != Human Acceptance` (A technical execution receipt records an observed outcome to support review; it does not certify model truth, regulatory compliance, or final business acceptance.)
- **Target Operating Model**: Customer-controlled, single-tenant headless VM appliance (`Headless` is the default posture; `PackrGUI` is an on-demand human request, inspection, and review surface; `VMAdmin` and `PacktoryAdmin` have separate operational scopes and no independent Work authority).
- **Non-SI Integration Model**: Productized Assistance reduces reliance on vendor-delivered Systems Integration (SI) projects through declarative contracts, bounded source discovery (`GAPE`), `Integration Helper` planning, and governed Packs. Non-SI does not mean zero customer integration effort, zero custom adapters, or universal configuration-only integration.
- **Explicit Scope & Claim Boundaries**:
  - Applies only to supported Work routed through VibePackr integrations; does not claim interception of every agent, tool, or operating-system action.
  - Use SDK Engine to generate local adapter candidates in Part.5 with documented Online or Offline toolchains. Implementation review, registration, Work binding and execution authority are separate. Full Enterprise integration and desktop embedding require separately supported implementation; SDK authoring is optional for existing supported Work.
  - Bounded local `Packtory` (local asset discovery, revision, and storage lifecycle) is distinct from future hosted/sharing concepts; remote Rescue transport remains disabled.
  - Published materials and reference diagrams do not establish commercial general availability (GA), cloud marketplace approval, regulatory compliance certification (e.g., ISO, NIST, HIPAA), or an executed Service Level Agreement (the published SLA is a draft requiring legal review).

## Primary Pages

- [Overview (Homepage)](https://www.vibepackr.com/): Single-tenant enterprise AI appliance overview, Non-SI integration architecture, governed workflow stages, execution authority boundaries, and whitepaper access.
- [Architecture & Execution Boundaries](https://www.vibepackr.com/architecture/): Primary operating model, current capability scope (`Contract`, `GAPE`, `Integration Helper`, `Packr Engine`, `Headless`, `PackrGUI`, `Packtory`), gateway vs. work governance, and identity vs. execution authority.
- [How It Works (8 Step-by-Step Workflow Stories)](https://www.vibepackr.com/howto/): Illustrative walkthroughs covering core governed lifecycle, policy denial, proposal vs. authority separation, concurrency/shared resources, auditability, extension boundaries, recovery, and end-to-end review.
- [Reference Library](https://www.vibepackr.com/resources/): Curated engineering diagrams, whitepaper plates, and reading guides across Architecture, Governance, Adoption, and Future Concepts.
- [Legal & Draft Support SLA](https://www.vibepackr.com/legal/): Customer-facing legal notice and [Draft Enterprise Product Support & SLA](https://www.vibepackr.com/legal/sla/) (12 clauses covering supported scope, single-tenant responsibility, Non-SI boundary, Official vs. Customer Packs, and incident severity).

## Detailed Architecture & Governance References

- [3D XYZ Architecture Space](https://www.vibepackr.com/resources/xyz-architecture-space/): Orthographic 3D coordinate projection mapping 15 functional roles across Authority & Control (`X`), Work Lifecycle (`Y`), and System Plane (`Z`), plus OS Channel Fabric and OSI network context (Whitepaper Figure 27).
- [AI / Agent Compromise and Execution Authority](https://www.vibepackr.com/resources/agent-compromise/): Five-stage control-boundary explainer showing why prompt injection or agent compromise alone does not grant execution authority for supported routed Work.
- [Governed Execution in the Enterprise Architecture](https://www.vibepackr.com/resources/governed-execution-architecture/): Supplementary responsibility view connecting optional preparation, policy declarations, Packr Engine admission/denial, validation, and surrounding enterprise controls (Whitepaper Figure 26).
- [Enterprise Ecosystem: Capability vs. Authority Map](https://www.vibepackr.com/resources/enterprise-ecosystem/): Ten-layer ecosystem role map separating AI capability bands from the protected VibePackr authority boundary and real-world enterprise effects (Whitepaper Figure 25).
- [Deployment and Trust Boundaries](https://www.vibepackr.com/resources/trust-boundary/): Customer-controlled single-tenant appliance boundary vs. external AI service processing boundaries (Whitepaper Figure 24).
- [The Iceberg: Four Layers of Execution Architecture](https://www.vibepackr.com/resources/iceberg-architecture/): Visible surface, capability layer, governance & trust, and protected execution core (Whitepaper Figure 15).
- [Enterprise Architecture: The Complete Picture](https://www.vibepackr.com/resources/system-overview/): Separation of context/preparation (`GAPE`, `Integration Helper`) from governed Work (`Packr Engine`) (Whitepaper Figure 23).
- [GAPE: Source Discovery, Reconciliation and Review](https://www.vibepackr.com/resources/gape-context/): Scoped Git/Rust/Tauri static source discovery, snapshot reconciliation, and offline HTML review views (Whitepaper Figure 4).
- [SDK Engine: Extension Without Extra Authority](https://www.vibepackr.com/resources/integration-extension/): Local SDK adapter authoring in Part.5, optional Online/Offline toolchains, separate implementation review and registration, and Work-specific authority (Whitepaper Figure 20).
- [Governed Execution: From Request to Review](https://www.vibepackr.com/resources/execution-boundaries/): Eight-stage Work lifecycle from Work request and policy/approval evaluation to governed execution, receipt, and recovery (Whitepaper Figure 7).
- [Shared Responsibility Model](https://www.vibepackr.com/resources/shared-responsibility/): Customer, VibePackr, and third-party responsibilities across objectives, data rights, models, integration, and operations (Whitepaper Figure 10).
- [Enterprise Evaluation Path](https://www.vibepackr.com/resources/evaluation-path/): Dependencies before expansion across existing AI platforms, enterprise stack gaps, and assurance requirements (Whitepaper Figure 13).
- [Deployment and Recovery Boundaries](https://www.vibepackr.com/resources/recovery-boundaries/): Compute, persistent state, backups, access, and readiness validation for single-tenant VM appliances (Whitepaper Figure 11).
- [Packtory: Future Knowledge Architecture Concept](https://www.vibepackr.com/resources/knowledge-concept/): Exploratory future hosted/sharing concept, explicitly distinguished from current bounded local Packtory functions (Whitepaper Figure 12).

## Product Documentation & Practical Evaluation Guides

- [Documentation Overview](https://www.vibepackr.com/docs/): Index of product surface commands, recorded Headless and PackrGUI examples, and operating prerequisites.
- [Headless Operations Guide](https://www.vibepackr.com/docs/headless-operations-guide-en.html): Six-step CLI workflow (`packrctl`) for baseline checks, Work submission, reconciliation, and report verification.
- [Recorded Headless Worked Run](https://www.vibepackr.com/docs/headless-worked-run-en.html): Step-by-step trace of one retained local `R234` Headless Work from rejected input to corrected submission and validated report.
- [PackrGUI Operations & Workspaces](https://www.vibepackr.com/docs/packrgui-guide-en.html): Unified workspace documentation covering [Business Workspace](https://www.vibepackr.com/docs/packrgui-business-en.html), [Engineering Workspace](https://www.vibepackr.com/docs/packrgui-engineering-en.html), [Operations Workspace](https://www.vibepackr.com/docs/packrgui-operations-en.html), and [Final Work Report Verification](https://www.vibepackr.com/docs/packrgui-final-report-en.html).
- [Packtory Library & Built-in Audit Packs](https://www.vibepackr.com/docs/packtory-library-guide-en.html): Inspection of bundled Audit Review and Audit Evidence Format Packs ([Built-in Packs Walkthrough](https://www.vibepackr.com/docs/packrgui-builtin-packs-en.html)) and [Packtory Administration](https://www.vibepackr.com/docs/packtory-admin-guide-en.html).
- [Integration Helper, SDK & AI Connections](https://www.vibepackr.com/docs/integration-sdk-guide-en.html): Architecture-bound integration declarations, [Worked Examples & Helper JSON](https://www.vibepackr.com/docs/worked-examples-en.html), and [Agent Recipes, GAPE & AI Connections](https://www.vibepackr.com/docs/agent-ai-guide-en.html).
- [Appliance Administration & Troubleshooting](https://www.vibepackr.com/docs/vibepackr-admin-guide-en.html): Administrative Console guide, [Cross-Surface Usage Workflows](https://www.vibepackr.com/docs/use-workflows-en.html), and [Troubleshooting Reference](https://www.vibepackr.com/docs/troubleshooting-guide-en.html).
- [Evaluation & PoC Guide Packs](https://www.vibepackr.com/guides/): Practical evaluation paths including [PoC Guide: Plan, Run, Evaluate and Close](https://www.vibepackr.com/guides/poc/), [PoC Deployment Reference](https://www.vibepackr.com/guides/poc/deployment.html), [Custom Execution Guide](https://www.vibepackr.com/guides/custom-execution/), and [What Is a Guide Pack?](https://www.vibepackr.com/guides/about-packs/).

## Current Technical Whitepapers & Edition Details

- [Full Context for LLMs (llms-full.txt)](https://www.vibepackr.com/llms-full.txt): Complete plain-text architectural reference, component definitions, 15 XYZ role specifications, and FAQ for generative AI grounding.
- [Machine-Readable AI Context Graph (ai-context.json)](https://www.vibepackr.com/ai-context.json): Structured JSON knowledge graph of VibePackr's epistemic boundaries, component roles, 3D XYZ coordinates, and canonical artifact SHA-256 digests.
- [3D XYZ Architecture Space Engineering Plate (A4 PDF)](https://www.vibepackr.com/resources/xyz-architecture-space/xyz-architecture-space-a4.pdf): Printable vector reference for the 15 roles across X, Y, and Z axes.

## Contact & Entity

- **Company**: VibePackr Co., Ltd. (Seoul, Republic of Korea)
- **Inquiries & Evaluation**: support@vibepackr.com (Clicking `mailto:` opens the user's local mail client; sending an email does not automatically register a support case or provision an environment.)

## Enterprise knowledge assets and accountable AI use

PINM is the internal intelligence core in VibePackr's knowledge asset model. Distill validated Work, structure methods and evidence, and label reviewed knowledge as user Custom Packs for governed local Packtory reuse. The enterprise can retain this asset base after personnel changes without transferring it to an AI provider. External AI calls remain separate data flows governed by configuration, policy and provider terms.

The Governed Work Execution Control Plane applies Work Authority, policy and scope to supported Work. Execution decisions, denials, validation, evidence and technical receipts support enterprise AI review; the responsible organization retains final compliance and acceptance decisions.

Installation and tool workflow: Part.1 installation -> Part.2 GAPE -> Part.3 Helper planning -> Part.4 Contract/Document -> Part.3 Helper validation -> optional Part.5 SDK and separate registration -> optional Part.6 Builder -> Part.7 use -> Part.8 operations. Online and Offline remain available choices; Offline is not the universal default.
- [Current technical whitepaper - EN - 18 October 2026 R3](https://www.vibepackr.com/whitepaper/VibePackr-Governed-AI-Execution-20261018-EN-R3.pdf): 66 pages, 29 chapters, 26 SVG diagrams; SHA-256 `82d85e1bd051ce580ff20f8381a6df1c976ae0be22bd28bdf8c58cc9c12e1c57`.
- [Current technical whitepaper - KO - 18 October 2026 R3](https://www.vibepackr.com/whitepaper/VibePackr-Governed-AI-Execution-20261018-KO-R3.pdf): 66 pages, 29 chapters, 26 SVG diagrams; SHA-256 `315844c762f457cdfdbc73c0a49aa22172238af5ee80fa515a0763dac276bfa4`.
- [Current whitepaper edition details](https://www.vibepackr.com/whitepaper/Whitepaper-Edition-Index-20261018.json)

## Current Parts 1-8 user manuals

- [Part.1 - Installation and first connection](https://www.vibepackr.com/docs/manuals/Part_01_Installation.html): Choose OS, package and connection prerequisites.
- [Part.2 - GAPE observation, comparison and sharing](https://www.vibepackr.com/docs/manuals/Part_02_GAPE.html): Capture the scoped revision and inspect the returned architecture.
- [Part.3 - Integration Helper operation](https://www.vibepackr.com/docs/manuals/Part_03_Integration_Helper.html): Prepare before declaration; validate and hand off after declaration.
- [Part.4 - Contract and Document authoring](https://www.vibepackr.com/docs/manuals/Part_04_Document.html): Declare intent, constraints, inputs and review context.
- [Part.5 - SDK Engine practice and candidates](https://www.vibepackr.com/docs/manuals/Part_05_SDK_Engine.html): Generate local adapters only when custom authoring is required.
- [Part.6 - Builder and Additional Packs](https://www.vibepackr.com/docs/manuals/Part_06_Builder.html): Prepare a candidate when an existing approved Pack does not cover the need.
- [Part.7 - PackrGUI and headless operation](https://www.vibepackr.com/docs/manuals/Part_07_PackrGUI.html): Follow Work identity, execution, validation and report review.
- [Part.8 - Operations, troubleshooting and support](https://www.vibepackr.com/docs/manuals/Part_08_Operations.html): Preserve the failed attempt, classify the issue and prepare a minimal support record.