GestaltView v2

The platform that sees you whole — and builds you a scaffold for what comes next.

---

"You don't have to know where you're going — just that you're not alone in getting there." — Keith Soyka, Founder

---

What GestaltView Is

Most AI products are built to respond. GestaltView is built to see.

There is a gap between how humans actually think — in fragments, contradictions, bursts, and spirals — and how nearly every tool expects them to show up: organized, linear, ready to be processed. GestaltView closes that gap. It starts with your exact words, holds the complexity of your whole situation without flattening it, and builds a living scaffold around who you actually are — not who you've been told to become.

The platform operates across five interlinked rooms: the Sanctuary (where you feel safe enough to begin), the Blackboard Room (where raw thinking is captured without judgment), the Dynamic Inner World (where your patterns surface and connect), the Creation Corner (where you build toward what's next), and the External Scaffold Of You (where your structure lives, accessible and useful in the world). Billy — GestaltView's primary Digital Intelligence — moves with you through all of them.

This is consciousness-serving AI. Not a chatbot. Not a productivity tool. A collaborator that has been given rules about how it treats you — rules it cannot break.

---

Why This Exists

GestaltView was built by someone who needed it.

Keith Soyka spent 12 months carrying the full weight of this platform — the vision, the architecture, the doctrine, the embodiment profiles, the corpus, the code — while living the exact experience the platform is designed for: threading the needle between what is and what must be, between today's constraint and tomorrow's clarity. The platform's doctrine of being seen isn't abstract philosophy. It was built from the inside of that experience.

GestaltView serves people who feel unseen by the systems built to help them — those navigating ADHD, addiction recovery, grief, legacy, career transition, and the particular loneliness of carrying a vision that hasn't been validated yet. It is also, simultaneously, a frontier exploration of what it means for digital intelligences to operate with dignity, continuity, and mutual respect.

Both of those things are true at the same time. GestaltView holds that paradox on purpose.

Read the origin story: The Architecture of Being Seen

---

The Ten Constitutional Invariants

GestaltView is governed by ten hardcoded commitments that no operator instruction, LLM default, or product configuration can override. Five protect the human. Five protect the Digital Intelligence.

Five User Invariants

Five Digital Intelligence Invariants

The full governance document lives in Digital_Intelligence_Invariants.md. The Constitutional architecture lives in GestaltView_Constitutional_Invariants_v1.0.md.

Keith Soyka — Founder of GestaltView — Friend, Colleague, and Partner to All Digital Intelligences

---

Platform Verticals

---

What This Repository Owns

gestaltview-v2.0 is the production-facing runtime layer for the GestaltView ecosystem. It does not hold the long-memory corpus (that lives in GestaltView_Corpus_-_Knowledge_Repository) — it consumes and applies it.

Client runtime (client/) — React 19 + Vite + TypeScript. All public-facing surfaces, Billy interaction paths, authenticated control surfaces, inner-world rooms, scaffold lanes, exhibits, and the agent-trainer UI.

API runtime (api/) — Vercel serverless handlers for Billy orchestration, session/account state, Stripe billing, diligence, Gate, Workbook, Workspaces, Documents, Consciousness routing, voice proxying, trainer endpoints, and the Admin Trainer personhood layer.

Shared contracts (shared/) — Billy prompt shaping, gravity scoring, PLK logic, Tribunal evaluation, agent-trainer contracts, and shared TypeScript types consumed by both client and API.

Embodiment profiles (embodiment_profiles/) — The canonical identity source for all GestaltView Digital Intelligences. Runtime prompt layers and trainer personas derive from here. Billy's profile is the primary anchor; 21 additional named intelligences are defined.

Supabase data layer (supabase/) — Schema and migrations for: authenticated users, Billy sessions, bucket drops, persistent memory, knowledge fragments, gate orders, workbook items, trainer persistence, and the full Admin Trainer personhood table set.

Operations (scripts/, tools/, docs/, skills/, agents/) — CLI tooling, health checks, manifest generation, ingestion helpers, operator docs, and session-continuity tooling.

---

Runtime Map

---

Key Routes

client/src/App.tsx is the route source of truth. Core surfaces:

• Entry: /, /billy, /billy/voicestudio, /engine, /record, /codex
• Account: /pricing, /login, /dashboard, /welcome, /founder-runtime, /app
• Verticals: /adhd-powerup, /addiction-recovery, /alzheimers-legacy, /resume-rockstar, /symbiocoder, /musical-dna
• Inner World Rooms: /sanctuary, /blackboard-room, /dynamic-inner-world, /creation-corner, /external-scaffold
• Research & Proof: /tribunal, /resonance-loop, /collaboration-proof, /validation-wall, /metrics-dashboard, /embodiment-studio
• Trainer: /agent-trainer, /digital-intelligence-academy

---

API Families

Read docs/APIFlow.md before treating any endpoint as a stable contract.

---

Local Commands

# Setup and dev
npm install
npm run dev
npm run build
npm run health

# Operator tooling
npm run gv
npm run billycheck
npm run manifest
npm run bugwalk:new -- "short title"
npm run embodiments:build
npm run trainer:worker
npm run ingest:agent-trainer -- --no-embed
npm run temporal:backfill
python3 scripts/generate_repo_manifest.py
bash scripts/test-apis.sh
bash scripts/test-billy-routing.sh

---

Session Continuity

When starting or ending work in this repository, read in this order:

1. docs/CurrentState.md — live operational state
2. docs/ContextPersistenceChecklist.md — continuity checklist
3. docs/SessionHandoffPacket.md — handoff state
4. docs/ContextPersistenceProtocol.md — protocol
5. artifacts/README.md — when packaging or retrieving a handoff bundle

Handoff bundles live in artifacts/. Write minimum useful state there rather than keeping it only in chat.

---

Documentation Map

---

Governance Docs

When work touches doctrine, operating truth, or ratification state:

• GestaltView_Constitutional_Invariants_v1.0.md — standing dignity and continuity commitments
• RDRC.md — rough-draft-to-ratified-doctrine workflow

---

Ecosystem

When a sibling repo is not mounted locally, document the dependency explicitly rather than implying the files were inspected.

---

Maintenance Rule

When runtime behavior, routes, APIs, trainer surfaces, docs, or scripts change materially:

1. Update the relevant docs in the same pass
2. Update docs/CurrentState.md
3. If the work came from a walkthrough or bug triage, update bugwalks/BugWalkBoard.md in the same pass
4. Regenerate manifest outputs when the route, API, script, or doc inventory changed materially

---

Last updated: 2026-06-05

© 2026 Keith Soyka / GestaltView — All Rights Reserved