About & Contact Management
Relevant source files
The following files were used as context for generating this wiki page:
About and Contact Management defines the systems used to establish professional credibility and facilitate user inquiries within the Portfolio project. The "About" component manages the narrative of the operator's 22-year history in operations and AI development, while "Contact" provides the entry point for fractional advisory, bespoke builds, and design services.
These modules work together to convert visitors into clients by grounding professional claims in evidence and providing clear, structured pathways for communication.
Professional Identity Management
The About module organizes information into a chronological timeline and a set of operational commitments. It categorizes the operator's experience into distinct eras, starting from technical IMAX projection systems to current AI systems building.
Chronological Structure
The history is managed as a sequential list of "receipts" that verify professional claims.
Sources: about.html:64-94, index.html:105-110
Operational Commitments
Professional behavior is governed by four core commitments that dictate how systems and engagements are managed.
| Commitment | Description |
|---|---|
| Evidence before narrative | Labels every claim as verified, staged, or planned. |
| Process before tool | Prioritizes finding the business constraint before selecting technology. |
| Handoff, not dependency | Ensures clients receive documentation, guidance, and walkthroughs. |
| Correction is a feature | Allows users to redirect or reject system outputs to maintain trust. |
Sources: about.html:98-112
Communication Channel Management
The Contact module directs users through specific channels based on the nature of their inquiry. The system utilizes a split-email architecture to separate administrative and operational concerns.
Channel Directory
| Channel Type | Endpoint/Identifier | Purpose |
|---|---|---|
| Contract/Advisory | keithsoyka@gestaltview.onmicrosoft.com | High-level builds and system implementation. |
| Operations/General | keithsoyka@gmail.com | Frontline operations and general inquiries. |
| Voice | (646) 741-6849 | Direct phone communication. |
| Scheduling | cal.com/keith-soyka-gestaltview/15min | Free discovery calls. |
| Professional | linkedin.com/in/keithsoyka413 | Professional networking and verification. |
Sources: contact.html:49-70, README.md:14-19
Inquiry Processing Flow
The system processes inquiries by requiring specific metadata (problem, timeline, budget) to determine fit before committing to a call.
Sources: contact.html:84-88, services.html:170-175
Engagement Lifecycle Management
Contact management extends into the lifecycle of a service engagement. The project defines a four-step process to move from initial contact to a documented handoff.
- Discovery Call: Confirmation of the business problem, owner, data, and constraints.
- Fixed-Scope Proposal: Formalization of outcomes, deliverables, price, and acceptance criteria.
- Build or Advise: Execution through visible milestones with early surfacing of uncertainty.
- Handoff: Delivery of documentation, operating guidance, and a walkthrough for the next owner.
Sources: services.html:178-185
Data Flow and Validation
Within specific product modules like the Agent Trainer, contact data (buyer email and company name) is subject to persistence requirements. Technical documentation identifies critical path flows where contact information must be captured during onboarding and passed forward to generation steps.
- State Persistence: The system writes email data during onboarding.
- Validation: Components check for uninitialized states to prevent redundant prompts.
- Handoff Reliability: Data must remain stable across route transitions (e.g., from Onboarding to Package Generation) to avoid blocking the revenue gate.
Sources: showcase/agent-trainer-sprint.html:115-135, showcase/agent-trainer-sprint.html:195-205
Summary
About & Contact Management serves as the trust-building infrastructure for the portfolio. It converts the operator's history into actionable credibility and provides a structured funnel for processing inquiries. By enforcing an "evidence-first" standard and separating communication channels, the system ensures that engagements are bounded, documented, and based on verifiable operational constraints.