The iceberg: four layers of execution architecture
Read the visible interface together with the less visible capability, governance and execution layers. This detailed reference preserves the original iceberg structure; it is not a Marketplace listing or an approval record.
Technical Whitepaper · EN and KR Editions · 18 October 2026 · Figure 15
Open the full-resolution image to zoom; use your browser’s Back button to return. The complete plate is preserved; the explanation below remains readable without zooming.
Read the guide
A reading guide to the figure and its scope, not a claim of current implementation for every depicted concept.
Visible surface
The iceberg is a layered metaphor, not the primary current operating model. VibePackr runs headless by default; PackrGUI is an on-demand human request and review client. Administration and status have separate scopes and no independent Work authority.
Capability layer
Use Headless for terminal workflows, GAPE for scoped read-only review, Integration Helper for preparation and local Packtory for supported assets. Add local SDK authoring when needed. Register and validate integrations separately. Hosted sharing is planned and is separate from local asset management.
Governance and trust
Identity, permission, execution context, process identity, communication boundaries and evidence storage support bounded operations. Their presence in a drawing is not validation evidence.
Execution core
The deepest layer represents protected execution decisions, state handling, trust boundaries and evidence binding. Public labels describe roles without exposing internal implementation identifiers. Deterministic control decisions do not imply deterministic AI-generated content.
Evaluation questions
The right-hand panels ask reviewers to establish artifact identity, deployment readiness, supported interfaces, security boundaries, recovery procedures and traceability. They are questions, not completed review statuses.
Reference materials and limits
Use architecture, evaluation criteria, installation guidance, responsibility explanations and draft support terms together. The picture is not proof of Marketplace availability, commercial release, certification or production outcomes.
About this reference
Figure 15 is provided as a current English SVG and included in both the English and Korean technical whitepapers dated 18 October 2026. Open the SVG to zoom, or use the PDF figure index to find the full plate.
Use this reference to understand architecture, responsibilities and planned capabilities. Use the applicable release documentation for deployment, and assign certification, legal and business acceptance decisions to your authorized reviewers.
Quick overview: the homepage uses a separate decorative iceberg. This page contains the detailed four-layer architecture reference.
Apply this boundary to one governed workflow.
Select one enterprise AI workflow, identify the required authority and policy conditions, and review the evidence needed before acceptance. Use the 11-step PoC guide or contact our architecture team to agree on the scope of your evaluation.
Contact boundary notice: Clicking “Request an Evaluation” opens your local email client addressed to support@vibepackr.com; it does not automatically create a support ticket or provision an environment. Please exclude credentials, personal data, and confidential logs.