Version History & Changelog
Relevant source files
The following files were used as context for generating this wiki page:
Version History and Changelog documents the evolution of the Keith Soyka Portfolio project, tracking site iterations, product releases, and showcase registry updates. The system categorizes changes based on evidence standards—verified, staged, or planned—to maintain technical transparency.
The documentation spans multiple versioning layers, including the main portfolio site (v10.x), the Dynamic Inner World Showcase (v1.9), and specialized product packages like the GestaltView Agent Trainer (v0.1.0).
Sources: CHANGELOG.md:1-25, README.md:1-5, README.md:40-45
Portfolio Site Iterations
The Portfolio site follows a semantic versioning pattern to track content updates, SEO optimizations, and infrastructure changes. Recent iterations focus on the transition from a general operator profile to a specialized AI systems builder portfolio.
Release History
| Version | Date | Primary Focus | Key Changes |
|---|---|---|---|
| v10.2 | 2026-10-02 | Conversion Pass | Lane A package refactoring, conversion units, and "Find the real constraint" CTA updates. |
| v10.1 | 2026-09-29 | SEO Gap Patch | Addition of missing meta descriptions, canonical URLs, and OpenGraph tags to standalone sheets. |
| v10.0 | 2026-09-28 | Major Release | Addition of the Dynamic Inner World Showcase, retirement of old contact numbers, and Vercel/HuggingFace deployment setup. |
Sources: CHANGELOG.md:3-25, README.md:7-14
Evolution of Strategic CTAs
Version 10.2 introduced a significant shift in user engagement strategies. The project replaced general calls to action like "Book a free 15-minute call" with direct technical prompts such as "Find the real constraint." This version also reframed services into specific "conversion units" that explicitly define what the client receives upon engagement.
Sources: CHANGELOG.md:4-10
Showcase & Artifact Versioning
The showcase/ directory maintains its own internal registry versioning separate from the main site. This allows the Dynamic Inner World artifacts to iterate independently of the site's layout and navigational structure.
The diagram shows how the registry.json file serves as the canonical index for all showcase artifacts, currently at version 1.9.0.
Sources: showcase/registry.json:200-205, showcase.html:30-40
Generative Render Engine (v1.9)
The Generative Render Engine demo represents the current v1.9 standard for runtime-wired artifacts. It operates using the production Gen-Engine's contract, including 15 artifact types and 8 synthesis styles. The provenance envelope in this version is demo-computed to verify source integrity without exposing production secrets.
Sources: showcase/render-engine.html:20-50, showcase/registry.json:90-105
Product & System Snapshots
Specific modules within the portfolio track their own build progress and scale metrics. These snapshots provide a technical record of system complexity and deployment readiness.
GestaltView Agent Trainer (v0.1.0)
The Agent Trainer package is currently in a pre-release or early-access state (v0.1.0). The version history for this module tracks the development of the "Productized Floor," which includes a perpetual license for white-label AI assistant scaffolds.
Sources: showcase/agent-trainer-pricing.html:120-130
System Scale (Aug 2026 Snapshot)
Technical documentation from August 2026 recorded the following scale for the GestaltView v3 flagship system:
- Database: 217 Postgres tables, 299 RLS policies, and 75 DB functions.
- Codebase: 722 TypeScript files across runtime repositories.
- Architecture: Separation of Corpus and Runtime into distinct repositories.
Sources: work.html:36-42
Evidence Standards in Documentation
Every claim and version update in the project follows a strict evidence standard to ensure technical accuracy. This categorization is applied to version entries and roadmap items.
- Verified: Backed by a shipped artifact, successful test run, or direct observation.
- Staged: Feature is in the build process and documented, but not yet live in production.
- Planned: Intent exists, but development has not yet commenced.
Sources: README.md:40-45, work.html:18-22
The Version History & Changelog serves as the technical source of truth for the Portfolio's growth, ensuring that all system changes are inspectable and evidenced. By separating site-level changes (v10.x) from artifact-level updates (v1.9), the project maintains a clear record of both presentation and functional evolution.
Sources: CHANGELOG.md:2, README.md:47