Start with these three diagrams: what sits beneath the interface, how the components connect, and who is responsible for what.
49 pages · 26 figures · English · PDF · 50 MB · 28 September 2026
Technical reference; release-specific alignment remains under review.
Explore the capability, governance and execution layers through the iceberg.
Explore the iceberg →
Separate preparation from Work. Start with the whitepaper’s bounded operating model.
See the architecture →
Compare customer, VibePackr and external-provider responsibilities.
Review the responsibilities →Conceptual reference plates and bounded roles follow the September 2026 English whitepaper. Confirm availability and supported scope for your evaluation.
Compare the customer-controlled appliance target model with an illustrative provider-managed service. External AI processing, operating responsibilities and release-evaluation questions remain explicit.
Read the role map first, then inspect the detailed responsibility view. Full images and readable explanations are available in both guides.
AI can propose. Execution requires governed authority. Explore the boundary between AI capability and real-world effects, and why a successful technical result is not sufficient evidence of authorization.
Explore the detailed reference →
A supported request reaches the protected Packr Engine with declared context, scope and applicable authority. Existing identity, security and observability remain surrounding controls. Preparation, execution, outcome review and human acceptance are related but separate responsibilities.
Explore the detailed reference →Vendor names and logos identify illustrative examples, not confirmed integrations, partnerships, endorsements or certifications. Categories overlap. Availability and supported interfaces require confirmation. Then compare the deployment and trust boundaries →
Go deeper into components, execution, adoption and future concepts.
For architecture and integration review
The original four-layer iceberg structure, with evaluation questions and reference materials.
Whitepaper Figure 15 · 6 reading sectionsExplore the detailed reference →Separate context and preparation from Work; one protected core, with no mandatory SDK stage.
Whitepaper Figure 23 · 7 reading sectionsExplore the detailed reference →
Scoped Git/Rust/Tauri source discovery, snapshot reconciliation and offline viewers; discovery does not grant authority.
Whitepaper Figure 4 · 6 reading sectionsExplore the detailed reference →
Extension roles and developer considerations; current integration status not established.
Whitepaper Figure 20 · 6 reading sectionsExplore the detailed reference →For security, governance and ownership discussions
Work scope, authority, supported execution and evidence for separate validation, acceptance and closure.
Whitepaper Figure 7 · 8 reading sectionsExplore the detailed reference →The full role map: eight customer concerns, product boundaries, external providers and shared takeaways.
Whitepaper Figure 10 · 7 reading sectionsExplore the detailed reference →For evaluation planning and operational readiness
Authorized context, preparation, governed Work and review; extension is conditional, not a fixed stage.
Whitepaper Figure 13 · 6 reading sectionsExplore the detailed reference →
Customer-controlled headless VM target posture; compute, persistent state, backups, access and validation are separate dependencies.
Whitepaper Figure 11 · 7 reading sectionsExplore the detailed reference →Exploratory architecture — not current availability
Not current availability. Future hosted/sharing concepts are separate from bounded local Packtory; remote Rescue transport remains disabled. These materials do not announce a release date.
Bring the diagrams and one concrete workflow to discuss supported interfaces, responsibilities, operating requirements and the evidence needed for a decision.
Discuss an evaluation