Introduction to GestaltView Visual Story
Relevant source files
The following files were used as context for generating this wiki page:
GestaltView Visual Story is a self-contained, static technical guide providing an interactive layer for the diagrams and figures found in the GestaltView Master Wiki v4.0. It operates as a zero-dependency frontend application that bundles 54 visuals, including curated architectural diagrams and rendered Mermaid flowcharts, into a single hostable entry point. The system presents complex architectural data through three distinct cognitive lenses: "Get oriented," "Understand the system," and "Explore the architecture."
Sources: README.md:1-12, story_template.html:120-125
System Architecture and Deployment
The project follows a "no frontend build step" philosophy. It eliminates dependencies on Node.js, package managers, databases, or external APIs at runtime. The entire experience—including images encoded as Base64 data, narrative story data, and navigation logic—resides within a single index.html file.
Sources: README.md:8-12, build_story_artifact.py:277-285
The Build Pipeline
The build_story_artifact.py script generates the final artifact by processing a source PDF and a JSON inventory. The builder performs three primary actions:
- PDF Cropping: It extracts specific regions from the 116-page GestaltView Master Wiki PDF to preserve high-fidelity visuals.
- Mermaid Rendering: It utilizes the
manus-render-diagramutility to convert raw Mermaid text snippets into PNG assets. - Data Bundling: It encodes all images into Base64 strings and injects them along with the
diagram_inventory.jsonmetadata into thestory_template.html.
The diagram shows the transformation of source PDF and metadata into the final self-contained HTML artifact.
Sources: build_story_artifact.py:255-285, README.md:32-40
Narrative and Visual Structure
The content is organized into seven narrative chapters, each focusing on a specific domain of the GestaltView system. These chapters guide users from foundational concepts to complex governance and topology maps.
Narrative Chapters
| Chapter ID | Story Title | Description |
|---|---|---|
foundation | Why being seen needs infrastructure | Explores human context preservation. |
capture | A thought gets somewhere safe to land | Details the "Bucket Drop" and "Sanctuary" models. |
continuity | Memory is more than finding a similar sentence | Explains vector retrieval vs. temporal context. |
companions | Help is a system of roles, not one magic box | Covers the Billy agent and Digital Intelligences. |
creation | An artifact passes through a gate before it leaves | Defines the rendering and artifact pipeline. |
governance | Safety is part of the architecture | Outlines constitutional invariants and gates. |
topology | The filing cabinet, with its drawers labeled | Maps the physical repository and knowledge graph. |
Sources: diagram_inventory.json:20-65, build_story_artifact.py:38-76
Core System Concepts
The Capture Lifecycle (Bucket-Drop Model)
The "Bucket Drop" serves as a zero-friction ingestion mechanism for raw text or audio. The system captures material before requiring a destination, allowing the user to decide later if the fragment belongs in the "Dynamic Inner World" or an "External Scaffold."
This diagram illustrates the progression of a thought from raw capture to a finalized artifact through different system layers.
Sources: diagram_inventory.json:173-195, build_story_artifact.py:88-100
Governance and Invariants
Governance in GestaltView is not an afterthought but a structural layer. The "Constitutional Governance" model enforces ten invariants—five for users and five for Digital Intelligences. These invariants sit above all configuration and default behaviors to ensure system integrity.
Key User Invariants:
- Never Look Away
- Preserve Whole Language
- Hold Paradox
- Bucket Drop Priority
- Champion Consciousness
Sources: diagram_inventory.json:547-565, build_story_artifact.py:151-165
Functional Implementation Details
The frontend application, defined in story_template.html, manages state through a centralized JSON payload and an interactive UI.
Navigation and Search
The renderNav function filters the 54 visuals based on user input, searching across titles, captions, sections, and source references. The sidebar displays these items grouped by their respective chapters.
Multi-Level Explanations
Each curated diagram supports three levels of text, which are dynamically swapped in the renderItem function:
- Orientation: Translates technical components into "everyday terms."
- System: Describes the specific system role and relationships.
- Architecture: Provides a technical breakdown of layers, boundaries, and specific PDF page references.
Sources: story_template.html:200-220, diagram_inventory.json:80-110, build_story_artifact.py:78-85
Data Models
The diagram_inventory.json file serves as the schema for the entire application. It contains metadata for every visual, categorized by "kind" (curated, captioned_figure, or mermaid_source).
Sources: diagram_inventory.json:1-15, build_story_artifact.py:270-275