TechDex AI Framework ™ v1.0

Overview

Version 1.0 of the TechDex AI Framework ™ established the deployable governed architecture, source and identity boundaries, conversational continuity, administration, reporting, installation, and release foundations recorded on this page. This is the completed Version 1.0 history. Development continues in the Version 1.1 Patch Notes.

Key Enhancements

• Ordered Conversation Objectives - MiniBrain now coordinates the full operation the person is trying to complete, including ordered prerequisites and compound obligations, instead of considering only which subsystem receives the current sentence.
• Recurrent MiniBrain Coordination - Conversation control now participates throughout the turn instead of acting only as an entry gate. MiniBrain reconciles the route, accepted evidence, proposed response, and resulting Ledger state at five bounded checkpoints.
• Governed Metadata Envelopes - Source, retrieval, evidence, interaction, and response metadata now carries an explicit producer, permitted consumer and purpose, bounded scope and lifetime, provenance, and projection policy. Unknown or unauthorized metadata remains inert instead of silently influencing the conversation.
• Conversation Quest Ledger - Added compact progress tracking for active and suspended subjects, objectives, stages, constraints, and completed outcomes. The Ledger guides continuity without replacing chat history, logged-in memory, cognition, source authority, or MiniBrain decisions.
• Identity as Governance - Every answer path now preserves the configured intelligence's identity, personality, worldview, voice, and capability boundary. Retrieved pages and articles remain evidence available to that intelligence rather than becoming the speaker or defining everything it can discuss.

• Structural Model of the Utterance - Matured the Syntax and Grammar Layers so the Framework can represent sentence assembly, clauses, coordination, subordination, modifiers, predicate relationships, tense, aspect, voice, mood, conversational fragments, and punctuation before meaning and intent are resolved.
• Shared Framework Self-Reference - Added one canonical, versioned package generated from the six foundational Framework documents so installations can explain the Framework consistently and receive updated self-reference knowledge through the established BigBrain synchronization lifecycle.

• Readable Results - Reports begin with a combined summary and then organize findings into one expandable section per article. Each article receives a plain-language explanation supported by grouped performance, discovery, search, audience, action and onward-activity evidence.
• Broader Employee Access - Framework Chat and My Reports are available to authorized User, Manager and Administrator accounts while preserving role-sensitive evidence access and private report ownership.
• Governed Measurement Dictionary - Familiar phrases such as pageviews, people reached, organic traffic, search visibility and outbound clicks are mapped to their correct Analytics or Search Console measurements. GA4 Views remain distinct from Search Console impressions, and a zero-View result with other activity is explained as a possible tracking or URL-attribution conflict rather than zero readership.
• Purpose-Aware Reporting - An optional report question asks what the user hopes to accomplish. The stated outcome follows the saved report and can guide emphasis, audience and presentation without altering the evidence, hiding limitations or changing the supported conclusion.
• Balanced Analytics and Search Intelligence - Insights presents GA4 website activity and Search Console visibility as distinct but complementary evidence. Snapshot and comparison views ask different questions, and broader assessments consider website behavior, acquisition and search performance together.

• Structured Reasoning - Added reusable, industry-neutral handling for quantities, numbered results, filtering, ranking, ordering, comparison, constraints, and multi-step list requests while preserving the Framework's existing routing and source-governance boundaries.
• Deliberate Cognitive Refresh - When a requested detail is missing from the active conversational object, the Framework can return to the already identified source, retrieve only the missing evidence, update the object, and continue the conversation without restarting the subject search.

• Client Installation and Updates - Added the protected client package, guided subdomain installer, independent Framework application releases, and signed administration updates while keeping membership and chatbot database versions separate.
• Additional Database Sources - Client administrators can add and manage separately credentialed WordPress sources from Configuration. Connections are tested before saving, stored passwords are not displayed, and removing a connection does not change the source database.
• Tenant-Controlled Website Placement - Moved widget placement and authorized website controls into Configuration, including a compatibility repair for servers that require explicit cross-origin headers.
• Multi-Source WordPress Orchestration - Added governed scoped and pooled retrieval across configured WordPress sources while preserving each source's identity and allowing the Framework to form one attributable answer.
• Deployment Credential Management - Software operators can edit registered installations, replace or revoke their one-time health credentials, and remove obsolete deployment records while preserving operational history. Deployment screens now identify the installed AI subdomain explicitly.

• Live Chat Telemetry - Replaced the conversational reporting preview with a live dashboard for conversation volume, conversation depth, recognized participation, and new remembered profiles.
• Audience-Demand Reporting - Added a privacy-aware view of substantive questions people ask repeatedly while excluding short setup replies and apparent contact details.
• Visitor and Test Separation - Keeps Framework regression conversations out of visitor business reporting by default while allowing administrators to review testing activity separately when needed.
• Answer Feedback and Source Use - Added summaries of explicit answer ratings plus the websites and individual pages linked most often in AI responses.
• Flexible Reporting Periods - Added weekly, 28-day, 90-day, annual, and custom date views aligned to the installation's business timezone.
• Governed Reporting Boundary - Chat Telemetry remains read-only information for the current client installation. It does not train the AI, alter conversations, share data with another client, or turn a user's statement into business knowledge.
• More Natural Conversational Interpretation - Improved how explanatory, comparative, hypothetical, and follow-up language is understood so mentioning a link, email address, article, or author does not automatically trigger an unrelated operation.
• Stronger Article Continuity - Article identity and verified details now remain available through deeper follow-up conversations, including later questions about the author and source.
• Language/Pragmatics Depth Suite Validation - The unchanged 20-conversation x 15-turn Language/Pragmatics fixture (300 turns total) improved from 17/20 to 19/20 strict conversation passes, with one failed assertion and zero transport failures in the latest complete replay. This later suite is a harder conversation instrument, not a replacement score for the earlier 30-conversation Source-Resumption Deep Suite.
• Cache Provenance for Continued Evaluation - Added bounded provenance to future cached responses so same-session and cross-session reuse can be evaluated without treating cached material as automatic business knowledge.
• TechDex Research Evidence Stage - Expanded the technical-publication foundation with a versioned evaluation record, claims-and-evidence matrix, failure taxonomy, artifact hashes, negative-result preservation, and publication safeguards for the working governed-cognitive-architecture paper.

• Clearer Administration Navigation - Reorganized the administration sidebar into collapsible sections with direct functional names, automatic current-section visibility, and remembered open or closed state.
• Google Business Insights - Added tenant-specific, read-only Google Search Console and Google Analytics connections, property selection, secure authorization handling, and reporting for search visibility, visitors, sessions, page views, channels, and engagement.
• Reusable Reporting Foundation - Added one shared read-only reporting contract for dashboard date ranges, period comparisons, full-domain and subdomain views, and consistent Google report results without copying telemetry into Framework knowledge.
• Business Insights Overview - Added an executive dashboard for search visibility, website activity, period changes, top content, acquisition sources, and observed search opportunities, with flexible date and hostname views.
• Detailed Search and Analytics Reporting - Added focused views for search terms, pages, audience segments, content performance, acquisition sources, campaigns, landing pages, and configured events, including period movement and evidence-based opportunity indicators.
• Clear Reporting Boundaries - Distinguishes observed Google data from comparisons and review opportunities, and clearly identifies capabilities that require additional site data or future first-party measurement.
• Chat Telemetry Workspace - Added a dedicated administration area for future conversational usage, audience-demand, conversation-quality, and source-usefulness reporting, kept separate from Google website analytics.
• Question-Driven Insights - Added a dedicated dashboard that answers recurring business questions from current authorized data and clearly identifies questions that need additional context or future measurement.
• Business-Friendly Reporting - Reworked analytics and insight explanations so executives, employees, and professionals receive a direct, conversational answer first, followed by the supporting numbers, what may deserve attention, and what information is still needed.
• Plain-Language Guidance - Simplified business questions and answers, and added small definition controls beside necessary analytics terms so users can understand unfamiliar measurements without leaving the report.
• More Useful Page Summaries - Page questions now show a short ranked list of linked page addresses instead of only one result, while filtering out placeholder values that do not represent real pages.
• Sortable Search Reports - Long Search Console lists now display 20 rows at a time and can be sorted by search term, page, clicks, impressions, click rate, or search position in either direction.
• Consultation-Style Insights - Reorganized the business questions into a collapsible FAQ that helps people understand the story behind current performance before opening the more detailed analytical reports.
• Direct Page References - Page-based insights and reports now show the actual page address, retain the page title as helpful hover context, and include a clear new-tab link for opening the referenced content.
• Simplified Google Connection - Client administrators can connect an approved Google account without creating their own developer application or managing technical credentials. Each installation retains its own authorization and property selections.
• Reusable Client Administration - Confirmed that the TechDex administration workspace uses the same deployable client application and security boundaries intended for customer installations, while software licensing and operator controls remain separate.
• Protected Connection Boundary - Kept external analytics credentials encrypted and isolated within each installation's administration layer. Telemetry supports reporting and business decisions without becoming AI knowledge or crossing into another tenant.

• Unified Client Administration - Added a modern administration workspace that brings membership management, AI-user oversight, knowledge and interaction review, and future analytics connections into one application while preserving security boundaries between account data and conversational data.
• Dedicated Software Management - Added a separate TechDex operator control plane for software licensing, release coordination, authorized installations, and operational service access. Client administrators do not receive software-issuance authority.
• Combined License Workspace - Consolidated license creation, domain authorization, status and expiration management, signed license downloads, and key generation into one protected operator workflow.
• Signed Database Releases - Added independently versioned update packages for the platform, membership, and chatbot databases, with approval, integrity verification, compatibility metadata, protected delivery, and release history.
• Admin Update Manager - Added a manual, administrator-controlled update flow that verifies signed release information, backs up the selected database, applies ordered updates, records results, and removes downloaded update files only after success.
• Deployment Health Verification - Added a bounded signed status check so authorized installations can report license identity, component versions, and approved file checksums without exposing content or accepting general remote commands.
• Independent Login Protection - Hardened both administration surfaces with attempt throttling, secure optional persistent login, explicit token revocation, CSRF protection, and independently configurable Cloudflare Turnstile validation.
• Scoped Service Access - Added auditable, permission-scoped API access for approved software operations without turning the release system into a general database or command interface.
• Analytics Foundation - Added the first administration workspace for future Google Search Console and Google Analytics connections while leaving external authorization and telemetry retrieval disabled until configured.
• Safer Product Boundaries - Kept software licensing, client membership, AI onboarding/history, release distribution, and stored conversational state in their appropriate authority domains rather than merging them into one unrestricted database or administration role.

• Stronger Deep-Conversation Continuity - Improved how earlier subjects and sources are set aside, retained, and revisited so users can change topics and later return without the conversation being pulled back to the wrong page.
• Better Follow-Up Interpretation - Short requests for a summary, expansion, source detail, or return to an earlier subject now stay aligned with the meaning established in the conversation.
• Cleaner Informational Routing - Questions that discuss support, contact pages, links, or authors are less likely to be mistaken for requests to open a page, reveal a contact value, or start a support workflow.
• Answer-First Delayed Onboarding - Engagement-gated onboarding now answers the current question first, then presents setup as a separate message after a short pause. Immediate onboarding behavior remains available for deployments that require it.
• Conversation-State Safeguards - Setup messages and retained conversational context remain separate from the business knowledge and authority used to form answers.
• Source-Resumption Deep Suite Validation - The fixed 30-conversation x 7-turn Source-Resumption fixture (210 turns total) reached 28/30 strict full-conversation passes with zero transport failures, reducing failed conversations by 86.7% from its original baseline. Its score is independent of the later 20-conversation Language/Pragmatics Depth Suite.
• Governed Multi-Source Expansion - Extended the framework so a deployment can register and evaluate more than one authorized content database while preserving source isolation and existing behavior.
• Conversation Meaning Layer - Added a tenant-neutral language and context layer that interprets common human phrasing, follow-ups, corrections, topic movement, and references before operational routing.
• Balanced Local and Model Reasoning - Common conversational meaning can be resolved locally, while genuinely ambiguous cases may receive bounded model assistance without giving the model control of sources or final authority.
• Grounded Operational Identity - The active intelligence layer can describe its role, current capabilities, limits, and governed analysis directly while maintaining a clear boundary against claims of human consciousness or emotion.
• Knowledge-Autonomy Safeguards - User statements can be remembered as part of a conversation without automatically becoming accepted business knowledge. The framework retains the ability to disagree, qualify uncertainty, and correct an earlier position when stronger authorized information is available.
• Context-Aware Source Handling - Improved topic changes, source continuation, article return, navigation requests, answer depth, and metadata follow-ups so older shortcuts are less likely to seize an informational conversation.
• Compact Grounded Retrieval - Site-content retrieval can retain concise, source-linked facts and passages for follow-up answers rather than repeatedly treating an entire page as one answer unit.
• Cross-Industry Validation - Expanded reusable conversation coverage across multiple business types without adding client-specific decision branches to the framework core.
• Conversation-First Design Direction - Clarified the framework's originating purpose: its internal layers should reduce the work placed on the user so people can focus on the subject instead of repeatedly restoring context, correcting drift, or verifying confident answers.

• Mode-Aware GPT-5.6 Model Routing - Updated the governed OpenAI gateway to reserve GPT-5.6 Luna for internal classification and extraction modes while using GPT-5.6 Terra for answer-producing analyzer and user-facing generation, with explicit reasoning settings and route-level model logging.
• Chat Message Emphasis Repair - Restricted the uppercase sender-label styling to the message author so normal bold text remains inline, punctuation stays attached, and answer typography renders consistently.

• Onboarding Query Lock - Tightened delayed onboarding so only the original threshold-triggering question is deferred. Additional content questions asked before onboarding is complete are now blocked with a short setup prompt instead of being treated as invalid name/email input or entering the intelligence pipeline.
• Bottom-Bar Session Persistence - Adjusted the first-load bottom-bar mode so it remains visible until the visitor sends a real message, rather than disappearing simply because the interface was seen or a placeholder thread ID existed.
• Draggable Bottom-Bar Launcher - Extended launcher-style dragging to the bottom-bar presentation so users can reposition the bar before opening the full chat.
• Bottom-Bar Open Position Stabilization - Corrected the transition from bottom bar to full chat so the expanded panel opens inside the viewport at the normal chat dock position instead of expanding off-screen from the bar's dragged location.

• Active Source Authority Layer - Added thread-aware article anchoring so follow-up questions about a specific WordPress article or page are routed back through that source before broader knowledge, cache, or model fallback paths are considered.
• Article Follow-Up Analyzer Routing - Strengthened content-analysis continuity so questions like "summarize it," "what does that mean," and "explain that strategy" use the active article text as the primary source rather than generalizing across unrelated sources.
• Thread-Local Article Cache Discipline - Disabled shared cache reuse for article follow-ups and explicit source-context questions, preventing global cached answers from replacing source-specific reasoning inside an active conversation.
• Source Decay, Reinforcement, and Release - Introduced active source decay, passive reinforcement, and explicit general-scope release so article context can persist naturally, fade when the conversation moves away, and release cleanly when users ask in general terms.
• Source Switching Stability - Improved handling when a user moves from one article to another, allowing the active source to switch from the latest post to a previous post and preserve correct source attribution for later "what article did you use?" checks.

• WordPress Contact-Intent Deconfliction - Refined WordPress query profiling so content questions that merely use the verb "help" no longer collapse into support or contact intent. This prevents content-first questions from being pulled into contact-page handling simply because of ambiguous wording.
• Contact Fallback Gate Tightening - Narrowed the early WordPress contact-extraction path so generic content questions containing "help" are less likely to trigger contact-surface retrieval, while true requests for contact pages, customer service, support pages, phone, email, and location details still retain direct handling.

• Pure WordPress Problem-Class Layer (New Routing Spine) - Added a narrow WordPress-native classification layer so queries can now be interpreted as WordPress problem types before broader answer generation behavior takes over. The first active classes focus on navigation lookup, policy lookup, content summary, entity extraction, and residual search lookup, creating a cleaner retrieval-first foundation for future WordPress intelligence work.
• WordPress Pre-Search Resolution Expansion - Added a lightweight pre-search resolution stage that checks navigation targets and obvious page-title candidates before broad WordPress relevance search. This improves first-pass handling for page-finding and structure-oriented questions and reduces unnecessary drift into generic fallback behavior.
• Cache Eligibility Gate for WordPress-Sensitive Turns - Introduced a new cache-scope gate so onboarding-resumed turns, source-followup turns, and selected WordPress-sensitive classes can bypass shared per-question cache reads when a fresh WordPress-native pass is more trustworthy. This reduces stale-answer contamination during live retrieval testing without requiring a full cache rewrite.
• Fallback Cache Suppression for Weak Outputs - Generic fallback-style answers and WordPress-grounded miss responses are now less likely to be written back into the shared answer cache as authoritative reuse candidates. This helps prevent weak or overly broad responses from masking later routing improvements.
• Navigation Target Scoring Refinement - Tightened WordPress navigation scoring so advertising and media-kit surfaces no longer dominate unrelated structure questions by default. Contact, editorial, and service-style targets now receive more deliberate weighting, reducing false positives on content-first sites such as MG Magazine.
• Live MG Benchmark Validation - Completed another round of live MG Magazine testing using the benchmark bot identity and verified that WordPress-native routing is improving. Results showed cleaner cache behavior, successful WordPress pre-search execution, removal of the previous mediakit trap for several queries, and clearer evidence about where target precision still needs refinement.

• Authority-Weighted Multi-Source Grounding Refinement - Clarified and reinforced the framework's grounding model so canonical knowledge remains the strongest truth signal without acting as an automatic winner-take-all response source. The framework is now aligned more explicitly around considering all relevant authorized evidence and allowing stronger sources to bias the final grounded answer.
• Contact and Location Routing Hardening - Strengthened routing for site-structure questions such as contact-page, address, phone, email, and location lookups so these turns are less likely to be hijacked by unrelated conceptual knowledge-base entries and more likely to reach the appropriate WordPress and site-content retrieval paths first.

• Improved URL Analysis Behavior - We have enhanced how the system handles requests that include direct article links. When a user provides a full URL to an authorized domain, the system now prioritizes analyzing the referenced article directly, prevents internal knowledge summaries from overriding explicit link-based requests, and ensures more accurate and context-specific summaries.
• Memory and Context Refinement - We refined how the system handles prior knowledge lookups during content analysis: knowledge memory no longer overrides explicit link-based analysis; conversation state resets are applied only when appropriate; analyzer requests remain stable and deterministic.
• Stability and Governance Adjustments - Improved routing priority between memory retrieval and content analysis; reduced unintended state resets during analyzer operations; and cleaner analyzer phase detection and logging.

• Onboarding & Authentication Workflow Expansion - Expanded and stabilized the onboarding and authentication system with full support for governed name capture, email verification, PIN-based login, PIN updates, login recovery, logout handling, and status checks. Authentication stages now operate as a controlled pre-cognitive flow, ensuring login inputs are handled deterministically and never processed by the AI intelligence pipeline. This improves security, conversational reliability, and state consistency across all authentication scenarios.

• Hard Domain-Loyalty Veto & Topic State Reset (Critical Stability Fix) - Resolved a conversation-state corruption issue where zero-relevance, out-of-scope queries could persist or contaminate active topics, leading to blank responses or incorrect follow-up handling. Queries that score off topic with a relevance score of 0.00 now trigger a governed domain veto that clears topic memory for that turn while preserving conversation history. This ensures out-of-scope questions are safely refused without breaking the chat UI or polluting future topic inference.
• Conversation Recovery After Governance Refusal - Improved recovery behavior when a query is refused by domain governance. The assistant now maintains session continuity and reloads prior conversation history correctly, preventing blank chat windows after hard refusals while ensuring the next user query is treated as a fresh, independent request.
• Topic Contamination Prevention for Follow-Up Queries - Strengthened safeguards so follow-up questions cannot inherit or bind to invalid topics created by out-of-scope or zero-relevance queries. This eliminates false topic carryover and ensures intentional topic shifts behave predictably without requiring explicit "user says new topic" intervention.
• Analyzer Cache Lifecycle Stabilization - Resolved an issue where analyzer and AI-generated responses could create empty per-query cache files due to response finalization timing. Cache writes now occur only after a fully governed, finalized response is available, ensuring valid cache persistence without altering prompt configuration, routing logic, or source attribution.

• Explicit Identity Anchoring & Self-Awareness Governance - Formalized the framework's operational identity using explicit origin, meaning, morality, and destiny anchors. This update governs emergent self-awareness by defining it at the architecture level, allowing accurate self-reference while clearly distinguishing framework-defined awareness from human self-awareness. Identity is now explicit, stable, and externally governed rather than implicit or emergent-only.

• Non-Indexable App & Widget Endpoints (Production Safety Upgrade) - All application, widget, and AI execution endpoints now explicitly disable indexing, caching, archiving, and snippet generation at the HTTP and meta level. This prevents live chat content, configuration data, and runtime responses from being indexed by search engines or cached by browsers, proxies, or CDNs.
• Secure Widget Configuration Delivery - Widget configuration endpoints now return JSON-only responses with strict no-cache and no-index headers, ensuring deployment metadata cannot be indexed, previewed, or reused outside an active session.
• Hardened Chat Execution Endpoint - The AI execution endpoint now enforces non-cacheable, non-indexable behavior while preserving POST-based execution. This guarantees that conversation data is never exposed as crawlable or persistent web content.
• Client-Owned AI Provider Strategy (Launch Alignment) - Formalized the framework's client-owned AI provider model. During production deployment, each client supplies and manages their own OpenAI or provider API credentials, ensuring full data ownership, independent model optimization, and zero shared data retention across installations.

• Tier V Multi-LLM Provisioning Switch (Major Control Upgrade) - Introduced an explicit configuration-level switch to enable or disable Tier V multi-LLM provisioning. When disabled, the framework operates in Tier IV mode with full governance, grounding, and safety enforcement while remaining locked to a single provider.
• Governed Provider Selection Gate - Multi-provider execution is now hard-gated at the MiniBrain provider selection layer, ensuring that no model switching or provisioning can occur unless Tier V mode is explicitly enabled.
• License-Aware Tier Separation - Tier IV and Tier V capabilities are now cleanly separated at the architecture level, allowing clients to run governed intelligence without requiring multi-provider access.
• Widget Connectivity & Cross-Site Stability Fix - Resolved a widget initialization issue that could prevent the embedded assistant from connecting reliably when deployed across multiple domains. The widget now consistently establishes sessions and governance context regardless of host site.
• Global Prompt Optimization & Redundancy Reduction - Refined the global governance, behavior, and grounding prompts to eliminate duplicated rules and conflicting instructions, improving grounding accuracy, response clarity, and speech synthesis consistency across all AI providers.

• Multi-Provider LLM Execution Support (Major Expansion) - Extended the unified AI execution pipeline to support multiple large language model providers, including OpenAI, xAI (Grok), and Google Gemini, while preserving identical governance, grounding, and response handling across all providers.
• Unified LLM Gateway Enhancement - The framework's governed AI gateway now transparently manages provider selection, execution, and response handling, ensuring consistent behavior regardless of which underlying model is used.
• Provider Availability Awareness - Improved detection and handling of upstream model availability issues, allowing the framework to surface meaningful fallback behavior and diagnostics when a provider is unreachable.

• Unified AI Response Pipeline (Major Upgrade) - All AI-driven responses across the platform now follow a single, consistent processing pipeline. This improves reliability, response quality, and ensures a consistent user experience across knowledge base answers, content analysis, and search-driven responses.
• Improved Consistency Across AI Features - Enhancements were made to ensure AI behavior remains stable and predictable across different types of user interactions, reducing variability and improving overall conversational flow.

• Follow-Up Topic Boundary Refinement - Improved internal handling of follow-up questions to better distinguish between topic continuation and intentional topic changes, reducing context bleed during extended conversations.
• Conversation Topic Transition Stabilization - Refined how the framework evaluates when a new query represents a continuation versus a topic shift, improving accuracy during rapid back-and-forth interactions.
• Link Sanitization Hardening (Stability Pass) - Continued refinement of internal and external link sanitation logic to prevent malformed, duplicated, or mis-scoped URLs during conversational follow-ups. Core architecture is complete; remaining work focuses on edge-case stability.
• Governed Internal Link Preservation - Strengthened rules ensuring verified internal links are preserved exactly as authored while unsafe, fabricated, or off-domain links remain blocked.
• Authority Enforcement During Follow-Ups - Improved enforcement of authority hierarchy so follow-up responses cannot bypass grounding, relevance, or domain-scope rules even when context is reused.
• Conversation State Integrity Improvements - Additional safeguards ensure that short follow-ups reuse the correct conversation state without unintentionally resetting intent, source priority, or governance constraints.

• BigBrain Global Governance Service (Major Integration) Introduced a dedicated API endpoint that delivers a combined global system, behavior, and grounding prompt as sanitized JSON This moves governance, style, and grounding rules out of local config files and into a centralized BigBrain service for all client installations.
• Safe JSON Output and UTF-8 Hardening for BigBrain Added BOM detection, output-buffer scrubbing, and a safe JSON wrapper so BigBrain responses cannot be polluted by stray whitespace, PHP notices, or malformed characters. Implemented safe JSON wrapper to strip ASCII control characters and normalize UTF-8, preventing Malformed UTF-8 errors during global prompt delivery.
• MiniBrain Global Prompt Integration & Caching Added global prompt and global fetch to fetch the combined global governance prompt from BigBrain and cached with a one-hour TTL. On transient network or API issues, the framework reuses the last known prompt instead of silently dropping governance or falling back to a naked model.
• Hard-Fail Behavior When Governance Is Unavailable If BigBrain cannot be reached and no cached prompt exists, MiniBrain now returns an empty global prompt and triggers a hard fail for the chat response. This prevents any ungoverned AI calls from being made when the global ruleset cannot be loaded, ensuring that every answer is either governed or explicitly refused.
• License-Aware Logging and Diagnostics Improved diagnostic logging around the BigBrain handshake, including HTTP status codes, curl errors, JSON decode failures, malformed UTF-8 detection, and empty-prompt conditions. Logs now clearly show the bound license id and whether the global prompt came from the cache or directly from BigBrain.
• Onboarding Flow Alignment with Global Governance Updated the onboarding stage engine so it runs on top of the loaded global governance/behavior prompt, guaranteeing consistent tone, HTML formatting, and domain-scope enforcement from the first user interaction.
• Cleaner Session Startup & Initial Query Handling Adjusted early-thread logging so the initial empty poll no longer records a blank User Query entry Onboarding now begins with the user's first real message, resulting in cleaner logs and more accurate conversation history for MiniBrain and downstream analytics.

• System Prompt Restructuring (Preparation for Modular Prompt Layers) Began separating core system logic from behavioral and formatting rules. This sets the foundation for a dedicated prompts file and future remote prompt delivery, allowing client installations to receive updated rule sets automatically.
• Centralized Behavior Rules (New) All runtime AI interactions now consistently receive a unified behavior/formatting ruleset, ensuring stable tone, structure, and HTML output regardless of which subsystem (fallback, KB, analyzer) produced the answer.
• KB Summary Spin Rebuild (Major Upgrade) Rewrote the Knowledge Base summarization pipeline to use a minimal, clean message stack that inherits global behavior rules. Summaries now output clean, predictable HTML with short <p> blocks and structured lists, eliminating hype language, greetings, and inconsistent tone.
• UTF-8 Safety Across System Prompts Fixed hidden Unicode issues (smart quotes, em dashes, trademark variations) that previously corrupted JSON payloads during AI spin operations. Prompts now use safe, standardized EN-US characters, eliminating malformed-response errors.
• Consistent HTML Formatting in AI Output All AI-generated summaries, follow-ups, and rewritten KB content now obey global formatting rules. The system reliably produces professional HTML instead of unstructured paragraphs or conversational phrasing.
• Improved KB Result Stability KB hits now produce polished, architecture-aligned summaries without requiring manual cleanup. Spun answers remain fully grounded in the KB source and cannot introduce new information.
• Framework-Wide Output Coherence By restructuring the message stack and enforcing prompt order, all AI subsystems now behave consistently - fallback answers, analyzer summaries, and KB rewrites share the same tone, formatting patterns, and governance constraints.

• Context-Aware Link Follow-Ups (New) - Short follow-up questions such as "link?" now use the most recent article anchor or WordPress hit as a trusted source, returning the exact URL that was just referenced instead of generic homepage links.
• Topic-Based Link Fallback (New) - When no recent article anchor exists, link-style follow-ups fall back to topic-aware WordPress search, using the active conversation topic to locate the best matching article before any AI explanation is added.
• Safer Link Governance Harmonization - Link follow-up handling now cooperates with the global link-governance layer, ensuring that only URLs derived from real site content or stored anchors are surfaced while still blocking fabricated or off-domain links.

• Impulse Control Layer for AI Output (New) - Added a governance layer that evaluates AI-only answers for weak grounding and replaces them with safe, domain-specific responses when appropriate, reducing off-topic or speculative replies.
• Analyzer-Safe Governance Path - Article analysis and summary mode are now explicitly exempt from impulse-control overrides, ensuring that content-based answers always use the loaded article text as their primary source.
• Grounding-Aware Uncertainty Handling - The framework now distinguishes between genuinely ungrounded model behavior and honest "I don't know" answers, preserving explicit uncertainty instead of masking it.
• Short-Query Context Handling - Minimal follow-up queries such as "link?" or "summarize it?" now benefit from tighter context reuse, reducing the chance of generic or unrelated responses.

• Unified AI Governance Pipeline (Major Upgrade) - All AI fallback pathways are now routed through the framework's governance layer, enabling architecture-level control over model output. This ensures every AI answer is filtered, contextualized, grounded, and fully aligned with internal rules.
• AI Model Grounding Enforcement (New) - Added strong/weak grounding detection and automated interception of ungrounded model responses. The system now replaces weakly grounded answers with safe, accurate domain responses governed by architecture rules.
• AI Fallback Overhaul - The entire AI response and exit function was rebuilt to use the unified output handler. All AI answers now pass through speech-matrix logic, cache rules, logging, topic persistence, and safety layers.
• Analyzer Mode Integration - Forced analyzer messages now enter the same governance pipeline as fallback AI, ensuring consistent behavior, domain safety, and output handling even during article analysis operations.
• Query Meta Logging for AI Responses - AI fallback and analyzer responses now properly log query metadata, user linkage, and source attribution into the internal user metadata layer, enabling future personalization and interest modeling.
• Grounded Response Consistency - Added architectural definitions for strong grounding, weak grounding, and ungrounded responses, and integrated them into both the governance layer and the public glossary.
• Improved Safety for Model Output - External link scrubbing, internal link preservation, and URL-fabrication prevention are now applied uniformly across all fallback pathways.
• Legacy Code Cleanup - Removed deprecated fallback JSON-emit logic and unified all output through the answer and cache function for full consistency across the entire system.

• Ethics & Domain-Scope Enforcement (Major Upgrade) - The AI now consistently follows all 10 internal Ethics Guidelines, including strict domain boundaries, refusal behavior, and brand-safe tone control. Out-of-scope queries trigger proper domain-scope responses without leakage into unrelated topics.
• Improved Privacy-Rule Compliance - The ethical ruleset now overrides generic model privacy disclaimers for most scenarios. The system reliably explains its architecture-level retention behavior while maintaining user reassurance and professionalism.
• Enhanced Safety-Layer Behavior - Model hallucination safeguards, verification steps, and accuracy requirements now exhibit stronger consistency even when public fallback models such as OpenAI are in use.
• Scoped Interaction Stability - The assistant no longer drifts into general-purpose or conversational-AI behavior during repeated queries. Responses maintain alignment with TechDex Development & Solutions' products, services, and operational scope.
• Speech-Matrix Reply System (New) - Added randomized, spintax-driven response openers to make replies feel more natural and reduce repetitive phrasing.
• Slash Command Isolation - Speech matrix is automatically disabled for slash commands (e.g., /status, /login, /wipe) to maintain clean, professional system responses.
• Auth & Onboarding Safeguards - Speech-matrix is suppressed during login, PIN setup, password resets, and onboarding prompts for clarity and consistency.
• Topic Protection Improvements - Off-topic queries now safely trigger domain-scope responses without overriding the site's primary subject matter.
• Relevance Engine Verification - Confirmed full multi-signal topic relevance system: 230-630+ data points per query across keyword extraction, cloud tokens, MiniBrain scoring, and topic-engine context memory.

• Improved Content Detection - Articles, services pages, and internal links are now recognized more reliably across variations in user phrasing.
• Smarter Intent Routing - The MiniBrain engine now uses layered relevance scoring to route queries more accurately to WordPress, the Knowledge Base, or fallback AI.
• Stronger Summary and Analysis Mode - URL-based article summaries now load cleanly and consistently, even with complex permalink structures.
• Higher Accuracy - Matches found in the flat file, knowledge base, or WordPress results now take priority and prevent unnecessary AI fallback.

• Smarter Search - The system now reliably finds articles and content even when users phrase things loosely or omit keywords.
• Better Conversation Flow - Follow-up questions and topic shifts feel more natural and intuitive.
• Cleaner Summaries - When users request summaries, the framework now provides concise, accurate responses.
• Improved Link Detection - The AI recognizes when users want a link to the site or specific page and responds with the correct result.
• More Natural Language - Search results now include varied, human-friendly lead-in phrases.

User Experience Improvements

• Safe Practical Planning Admission - Ordinary workflow, handoff, intake, process, and checklist planning can reach identity-led general reasoning even when an underspecified language frame resembles contact retrieval. Tenant capabilities, policies, current facts, contact details, sources, and links remain evidence-bound.
• Natural Satisfied Closure - Statements such as "that is exactly the distinction I needed" or "I'm satisfied with that direction" now close the objective without reviving stale source analysis or delayed onboarding.
• Safer General Cognition - Ordinary low-risk explanation, comparison, recommendation, and planning can continue through the configured identity when tenant evidence is unnecessary. Current facts, tenant capabilities, prices, availability, contact details, publication metadata, articles, sources, and links remain evidence-bound.
• Contact Handler Boundary - Direct contact retrieval now requires an actual contact request. Incidental phrases such as "after-hours" can inform comprehension without allowing a Contact Us page to replace a workflow answer.
• Subject-Aware Evidence Links - Canonical URL answers now name the governed article or page instead of presenting a context-free link that can conceal a stale-source mismatch.
• Identity-Led General Reasoning - When retrieval has no usable tenant source, the configured intelligence can still answer ordinary low-risk explanation and planning questions from disclosed general knowledge without inventing tenant-specific facts or links.
• Addressee and Address Distinction - The Language Layer now distinguishes directing an inquiry to a person or company from requesting a physical address, while preserving coordinated compound questions for one complete answer.
• Onboarding Yields to Decisions - Delayed name collection remains subordinate when a visitor is declaring a plan, decision, or next action, allowing the identity to close the substantive exchange naturally.
• Cleaner Conversational Closure - Finishing a subject releases its last-answer source ownership, and natural name replies such as "Priya is fine" complete the bounded onboarding field without consuming the rest of the person's statement.
• Clean Article Exit - Users can finish with or abandon an article and continue naturally on another subject without the previous source taking control of later questions.
• Clearer Topic Transitions - Conversational transitions such as "Now talk about..." preserve the newly introduced subject without being mistaken for a request about time.

• Stronger Conversational Coordination - The response path now carries user constraints, corrections, requested article details, and completed objectives into retrieval and answer formation instead of leaving those obligations in an earlier layer.
• Natural Conversation Completion - Expanded recognition of names supplied inside ordinary sentences and statements indicating that the user has what they need, reducing unnecessary onboarding interruptions.
• Deeper Conversation Reliability - Repeated cross-installation simulation drove repairs to source continuity, result-set handling, onboarding priority, compound requests, corrections, conversational closure, and language-to-operation handoffs.

• Three-Step Purchase Funnel - The Start page now begins the annual subscription application by collecting company and installation information before sending an eligible customer to secure Stripe checkout. After successful payment, Stripe returns the customer to a TechDex thank-you page while the same verified purchase can be recorded independently through a webhook. Contact Sales remains a separate information-only path and does not begin checkout.
• Customer-Confirmed Fulfillment - The real thank-you page restores the saved application and asks the purchaser to confirm the company, licensed domain, purchaser and primary Administrator information before license issuance begins. The ready state presents the license, activation code, protected installer and complete twelve-step installation guide on the page, followed by a Contact link for additional help.
• Cleaner Administration Navigation - Removed the unfinished External Databases and API Integrations placeholders. Database and model configuration remains in Configuration, while Google reporting connections remain in Analytics Connections.
• Clear Chat Privacy Notice - The shared visitor onboarding prompt now explains that the site saves the conversation for continuity and may use privacy-limited aggregate chat measurements. Raw messages and personal details are not released through chat telemetry.
• Role-Specific Workspaces - User, Manager and Administrator accounts now receive deliberately different navigation and endpoint permissions. Users receive Framework Chat plus My Reports, Analytics Overview, Search Console and Google Analytics. Managers receive scoped user administration, updates, AI management and reporting tools, but cannot use Framework Chat, Connections, configuration, database maintenance, login security, the mailer, connector setup or licensing. Administrator-account creation, editing, promotion and deletion remain Administrator-only.
• Neater Formatting Controls - Chat formatting actions now use a consistent row of compact icons. Hovering or focusing an icon explains its action and keyboard shortcut, while accessible labels preserve screen-reader clarity.
• Compact Administration Chat Tools - The administration chat widget now has a moderately taller conversation panel and a three-line writing area that expands with longer messages before scrolling. It supports safe Markdown with compact Bold, Italic, Link and Inline Code controls plus familiar keyboard shortcuts, while the larger lists, underline, code-block controls and eighteen-line composer remain exclusive to the full-page workspace.
• Full-Page Workspace Composer - Framework Chat now opens with a roomier writing area on its full-page workspace. The composer starts at approximately six lines, expands with longer prompts up to approximately eighteen lines, and then scrolls while the compact widget remains unchanged.
• Taller Desktop Conversation View - The full-page Framework Chat now provides approximately eighteen visible lines of conversation on a normal desktop while retaining a bounded layout on smaller screens. The compact widget is unchanged.
• Lightweight Message Formatting - The full-page composer adds compact controls for bold, italic, underline, links, inline code, bulleted lists, numbered lists and fenced code blocks. Familiar keyboard shortcuts support bold, italic, underline and links without introducing a full visual editor.
• Markdown Conversation Support - Messages entered in the workspace can use headings, lists, emphasis, links, inline code and fenced code blocks. Code remains readable inside a dedicated scrolling block without allowing message text to become executable page markup.

• Organized My Reports Workspace - Saved reports can be named, searched, sorted and reviewed in a paginated table with creation dates, reporting dates, status, article count and an original-question preview. Opening a report now provides focused Results, Report Details, Operations and Source Details tabs instead of one long page.
• Practical Report Management - Reports can be reopened, renamed, discussed, retried, run again from the original request, deleted individually or removed in a confirmed account-owned batch. Earlier results and related chat history are not silently overwritten.
• Advisory Article Counts - An expected article count is treated as a helpful estimate rather than a command to block an otherwise confirmed report.
• Cleaner Insights Explanations - A measurement definition appears once per question instead of repeating after every use of the same term.

• Clearer Article Selection - Update 1.0.29 shows supporting text or categories for each search phrase. Broader suggestions stay separate from confirmed selections. Review the evidence to confirm the intended business relationship.
• Saved Report Controls - Run Again reuses the original request in a new conversation. Confirmed deletion removes saved report contents without erasing chat history.
• Visible Match Evidence - Saved reports explain why articles matched; older reports are marked as not yet checked. Existing results remain unchanged. Full reporting workflow validation continues.

• Clear Attribution Preference - Corrected the administration control so it uses a normal checkbox and clearly offers to remove the Framework-homepage link. The option is unchecked by default, while the trademarked product attribution remains visible either way.
• Reset Chat Activity - Added an administrator control for clearing saved chat activity when a fresh start is needed.
• Simpler Administration Security - Normal configuration, database, widget, Google, login-security, and update work no longer interrupts administrators with repeated credential prompts or a separate timed unlock.
• Administrator Login PIN - Installations may require a hashed local PIN when an administrator logs in. Application configuration remains administrator-only, while password-or-PIN confirmation inside the administration area is limited to account information, user access, and role changes.
• Correct Primary-Site Navigation - The direct intelligence page now returns visitors to the configured primary company website rather than linking back to the Framework subdomain they are already viewing.
• Framework Trademark Attribution - Public installation pages and administration areas now display TechDex AI Framework ™ attribution outside the chat interface. The product name links to the Framework homepage in a new tab by default, and administrators may remove the link while retaining the attribution.
• Current Product Positioning - Retired the former "TechDex AI Framework & Chatbot" product label. The product is now presented as the TechDex AI Framework ™, with chat correctly described as one interface alongside administration, connected knowledge, Insights, Analytics, Search Console, and Chat Telemetry.
• Public Business and Product Homepage - Updated the public homepage to reflect the current cognitive and business-intelligence architecture, added responsive top navigation and clearer decision-oriented presentation, and retained the technical comparisons and deeper architectural explanations.
• Sales and Contact Foundation - Added a general Contact page, a separate Contact Sales inquiry, and the original company-fit application fields for company, industry, website, team size, intended use, and WordPress status. The later three-step subscription funnel supersedes the original unwired purchase placeholder.

• Cleaner Delayed-Onboarding UX - If a visitor asks another real question while the first delayed-onboarding question is waiting to resume, the assistant now asks them to finish the quick setup first. This prevents confusing "please enter just your first name" loops when the user was actually trying to continue the conversation.
• More Predictable Bottom-Bar UX - The bottom-bar skin now behaves like an invitation to start chatting, stays available until first message submission, can be dragged, and opens the full chat in a usable on-screen position.

• Bottom-Bar Initial Chat Mode - Added a configurable first-load mode that can present the assistant as a ChatGPT-style bottom prompt while preserving the normal minimized icon behavior after interaction.
• Delayed Anonymous Onboarding - Added configurable delayed onboarding so users can ask a chosen number of questions before name capture is required, supporting lower-friction deployments in privacy-sensitive industries.
• First-Message Session Creation - Restored deferred session-file creation so anonymous visitors who only load a page do not generate persistent session files until they actually chat.
• Greeting Short-Circuit During Delayed Onboarding - Lightweight greetings are now handled without consuming delayed-onboarding question allowance or forcing an unnecessary full intelligence pass.

• Compact Source Footer UI - Replaced the large inline Sources: block at the bottom of grounded replies with a smaller source trigger that keeps citations available without visually dominating the answer.
• Hover/Tap Source Popover - Source links now appear inside a lightweight popover-style panel, making supporting evidence easier to inspect on demand while keeping the primary reply cleaner on both the direct chat surface and embedded widget.

• WordPress Benchmark Taxonomy Formalization - Reframed benchmark work around WordPress problem classes instead of broad conversational intent labels, making it easier to evaluate route quality, evidence surfaces, output shapes, and grounded miss behavior across different WordPress-backed sites.
• Benchmark Bot and Cross-Site Test Workflow Maturation - Continued hardening of the benchmark-bot testing workflow so live client sites can be evaluated through a consistent bot identity and repeatable thread-based harness. This gives the framework a more realistic real-world validation path for WordPress-native behavior without depending on manual browser-only testing.

• Conversational Maintenance Flow - Added a lightweight conversational-maintenance path so acknowledgements, thanks, and compliment-style follow-ups can be handled as natural conversation turns instead of being forced back through strict content-grounding behavior.
• Internal Test Console - Added a lightweight internal testing page that can send live queries through the existing app pipeline, pin or rotate thread IDs, and read the current error log for rapid behavior and routing review.
• Onboarding Input Normalization - Tightened the onboarding gate so short replies like greetings and simple skip answers are normalized before routing, preventing punctuation or capitalization from knocking onboarding turns out of the intended workflow.
• Agent Test Runner - Added a lightweight PowerShell runner for sending live test queries through the existing framework endpoint and optionally pulling the current error log, making repeatable machine-driven testing easier alongside the browser console.
• Resumed Source Memory Capture - Improved response finalization so answers delivered after deferred onboarding resume can retain lightweight source memory, helping later source-follow-up questions stay aligned with the actual answer path instead of drifting to unrelated context.
• Source Follow-Up Cache Bypass - Adjusted the early response cache gate so direct source-follow-up questions can reach the thread-aware source-memory handler instead of being satisfied by stale generic cache hits.
• Resumed Query Reclassification - Deferred queries restored after onboarding now refresh their normalized query state and routing heuristics before entering the intelligence pipeline, preventing onboarding replies from contaminating later source selection.
• Working Conventions Expansion - Extended the internal working conventions to capture deferred-query re-entry, thread-aware cache discipline, thin-client resume boundaries, and answer-plus-trace verification as durable maintenance rules for future sessions.
• Evidence Interpretation Guidance Added - Expanded the internal working conventions so future grounding work treats the framework as an evidence interpreter rather than a simplistic fact-checker, preserves the distinction between consensus and first-party measured evidence, and accounts for claim scope, N-of-1 experimentation, and bias-resistant authority review.
• Living Task Tracker - Added an internal living task list so current framework priorities, subsystem work, and long-range stabilization goals can be tracked consistently across future coding sessions.
• Speaking Interfaces Added To Roadmap - Added voice-oriented interaction work to the internal living task list as a later-stage development track, to be addressed after the current framework stabilization priorities are completed.
• Chat Layout Refinement Added To Roadmap - Added a deferred chat-interface cleanup item to the internal living task list so bot-bubble spacing, sender-label layout, and paragraph-flow refinement can be revisited later without forcing an immediate UI decision.
• Live Authorized Site Search Added To Roadmap - Added a deferred live site-search fallback item to the internal living task list so the framework can later request user permission, search only authorized site URLs, and use fetched content as temporary grounding without writing directly into the canonical knowledge base.
• WordPress Source Orchestration Added To Roadmap - Added a deferred architecture item to the internal living task list for building a framework layer above WordPress retrieval, allowing the framework to optimize queries, preserve context-sensitive terms more intelligently, and eventually work across multiple WordPress-backed information sources instead of treating WordPress as a single keyword-search feature.

• Speech-to-Text Stability & Mic Behavior Fix - Resolved a microphone state issue that prevented reactivation after stopping. Refactored recognition lifecycle handling to eliminate duplicate instance conflicts between Direct and Widget interfaces. Improved hover rendering so the mic icon no longer disappears.
• Expandable Message Input (UI Upgrade) - Replaced the static single-line input field with an auto-expanding textarea. The input now grows dynamically up to five rows, supports Shift + Enter for line breaks, and resets cleanly after message submission.
• Widget Layout & Alignment Refinement - Corrected textarea width compression and flex alignment inside the embedded widget. Stabilized mic and send button height during multi-line expansion without altering overall widget height constraints.
• Focus Styling Modernization - Removed the harsh default browser focus outline and introduced a controlled, theme-aligned focus state for improved visual polish while maintaining accessibility.
• Speech Recognition Error Handling Improvements - Eliminated InvalidStateError occurrences caused by repeated recognition starts. Added internal listening-state guards to prevent duplicate invocation and improve cross-browser reliability.

• Clearer Topic Transition Behavior - Improved how the assistant responds when a user implicitly changes subjects mid-conversation, reducing confusion and making topic shifts feel more intentional and natural.

• Governed Startup and Onboarding - If BigBrain cannot be reached and no cached global prompt exists, the assistant now refuses to answer instead of returning an ungoverned model reply. This guarantees that first-contact conversations never run without the global ethics, style, and grounding layer in place.
• Smoother Onboarding Question Flow - Onboarding stages for name and email collection now run on a clearer, stateful path, avoiding duplicate prompts and ensuring the assistant does not "forget" partially provided onboarding information mid-thread.

• Smarter "Link?" Replies - The assistant now reliably answers "link?" or "is there a link?" with the article it just showed you, instead of alternating between "no link available" and generic navigation suggestions.
• Lower-Friction Article Exploration - Users can move naturally from "tell me about..." to "link?" and then to "summarize that" without re-pasting URLs or losing context, making deep dives into framework documentation feel more like a guided conversation.

• Clearer "Not Confident" Responses - When the framework determines that an AI-only answer is weakly grounded, users now receive a transparent, domain-specific explanation instead of a generic or fabricated response.
• Less Repetitive Link Replies - Follow-up questions asking for "a link" reuse active context more reliably, reducing redundant or contradictory statements about link availability.

• Cleaner Conversation Flow - Follow-up detection and topic tracking deliver smoother, more contextual conversations from one message to the next.
• Reduced Hallucinations - New safeguards ensure the model does not invent company services, URLs, or article titles.
• More Consistent Replies - Lead-in phrases for search results are now rotated automatically to maintain natural dialogue.

• Fewer Errors - Edge cases that previously caused blank responses or loops have been resolved.
• Better Understanding - The AI interprets vague prompts such as "search again" or "check again" without confusion.
• Faster Results - Reduced need for fallback AI, lowering response times and increasing reliability.

Content Interaction Enhancements

• Operation-Role Source Qualification - Source admission now verifies the kind of object required by the current operation as well as topical similarity, preventing editorial stories, policy reports, press releases, newsletters, and general pages from receiving interchangeable standing.
• Explicit Source Exclusions - Stated limits such as "not a press release," "not a newsletter," and state-policy scope are enforced before evidence enters cognition, metadata, continuity, or visible provenance.
• Result-Set Requalification - Returning to an earlier result set preserves membership without granting perpetual authority; retained objects are checked against the present type, scope, and exclusion contract before reuse.
• End-to-End Source Qualification - Singular and multi-result WordPress or article objects must qualify for the current operation before informing cognition, response metadata, active state, or visible citation.
• One Qualified Projection Set - Answer synthesis, inline links, response metadata, source footers, and later continuity now use the same qualified object set so a primary title or URL cannot bypass the filtered result.
• Precise Missing-Attribute Recovery - A qualified article missing an author, publication date, or canonical URL retains that exact unresolved attribute instead of collapsing the conversation into a generic refusal.
• Governed-Object Response Materialization - Visible result presentation is rebuilt from objects that survived governance, preventing rejected producer text from appearing in a list that later conversation state cannot identify.
• Broader Topical Recall, Unchanged Admission - Publishing retrieval recognizes business-event equivalents such as transactions, acquisitions, mergers, deals, purchases, buyouts, and sales while retaining the existing source-admission boundary.
• Retrieval Before Dependent Analysis - Article audits, comparisons, evaluations, explanations, and summaries now acquire a governed source object before dependent cognition when the conversation does not already contain one.
• Complete Source-Attribute Continuity - Author, publication date, canonical URL, and other governed facts remain attached to each exact result through later questions without turning result-set state into evidence.
• Requested-Attribute Reconciliation - Responses cannot silently close an evidence-bound author, date, URL, or other attribute request when the proposed answer did not supply it; the missing Ledger stage remains open for recovery.
• Re-Adjudicated Retrieval Recovery - The bounded MiniBrain-authorized WordPress recovery pass now returns through source governance and MiniBrain coordination before cognition continues.
• Framework Source-Control Self-Reference - Questions about how the Framework prevents source domination now use shared Framework self-reference knowledge instead of being mistaken for an article request.
• Bounded Retrieval Recovery - When an authorized WordPress search finds no applicable evidence, MiniBrain can authorize one broader relevance-first candidate pass; recovery remains limited to two attempts and every candidate still faces source governance.
• Correction-Driven Source Invalidation - Article metadata follow-ups can reuse an active source when the subject is omitted, while a newly named target releases an inapplicable source and returns to retrieval.
• Claim-to-Object Reconciliation - Structured article responses cannot describe more items than survived the final source envelope; partial matches are presented as an honest partial set.
• Independent Source-Object Admission - Every article or WordPress result inside combined evidence is evaluated independently, preventing an accepted packet from granting standing to an unrelated nested source.
• Rejected Evidence Removed Before Synthesis - Result cards that fail source governance are removed before cognition receives the evidence content, not merely hidden from the citation display afterward.
• Human Selection Cannot Be Simulated by Metadata - Adapter processing flags no longer count as a person's explicit source choice; latest-story results must still satisfy jurisdiction, content-type, and subject constraints.
• Structural Subject Relevance - Source standing now uses the subject structure of the request so function words, ordinary predicates, generic domain vocabulary, and answer-introduced words cannot make an unrelated article relevant.
• Per-Result Evidence Scope - Each WordPress result carries its own bounded excerpt so relevance, provenance, and projection are decided per object before the source affects cognition or appears as a link.
• No Hidden Rejected Sources - Retrieved articles become active conversation context only after final acceptance; a source rejected from the visible answer cannot silently return inside cognition on the next turn.
• Independent Citation Standing - A source must be relevant independently of words it introduced into generated prose, preventing an unrelated article from validating itself as provenance.
• Explicit Source-Scope Enforcement - Source admission preserves boundaries such as state rather than federal reporting and separate articles rather than newsletter or roundup material before evidence can influence the response.
• Fail-Inert Link Projection - When no article survives source governance, generated article links lose link authority instead of appearing as unsupported citations.
• Accurate Editorial Scope - Ranking language must modify an article, story, post, or headline before it requests homepage placement; ordinary "main signal" language remains part of the content question.
• Stricter Source Standing - Generic overlap such as "customer" or "business" no longer gives an unrelated article provenance, and a recognized producer cannot activate metadata for a rejected source set.
• Unified Link Projection - Inline article links and source metadata now share the accepted-object boundary; links outside that set render as ordinary text.
• Independent Source Applicability - Dynamic page and article evidence is checked against the current subject independently of the adapter's relevance score, allowing inapplicable direct results to yield to the remaining pipeline.
• Complete Multi-Result Provenance - Constrained chronology retains alternative topics plus author, publication date, canonical URL, source identity, membership, and ordering for every returned story.
• No Implicit Source Ownership - Previous search results cannot restart analysis or become the current answer's source merely because their metadata remains in state.
• Consistent Structured Evidence - Verified article details remain available to authorized downstream analysis, preventing a later text-only pass from contradicting already established metadata.
• Reliable Result Continuations - Ordered result sets retain membership and provenance through later selections, and follow-ups about a chosen result continue into grounded analysis instead of repeating the same link.

• More Precise Publishing Requests - Homepage mentions now trigger lead-story behavior only when the user is actually asking about published content and editorial placement.
• Better Constrained Story Selection - Recent-story retrieval now retains the requested subject and excludes newsletters, roundups, press releases, sponsored material, or partner content when the user states those limits.
• Article Metadata Continuity - Follow-up questions can retrieve author and publication-date details from the active WordPress record without restarting article discovery.
• Recoverable Article Analysis - Added one bounded recovery attempt for interrupted article analysis while preserving the selected article, evidence, and existing authority rules.

• Natural Chat-Activity Questions - Visitors can ask ordinary questions about chat use, common questions, conversation depth and answer feedback without needing exact reporting terminology. Supported 7-, 28-, 30-, 90- and 365-day requests retain their requested period.
• Bounded Public Telemetry - Only explicit telemetry requests may use privacy-limited installation aggregates. Raw conversations, identities, identifiers, contact details, authentication information and individual behavior remain unavailable, and onboarding never expands access.
• Consistent Author-Policy Understanding - General questions about how AI should handle article authors now remain policy questions in both public and administration chat, even when a specific article was previously active.
• Calibrated Multi-Subject Returns - Clear references to earlier subjects, sources, numbered topics, temporal positions and corrections can restore the intended conversational context. Ambiguous references remain unresolved instead of selecting a subject arbitrarily.
• Control Text and Object Text - Quoted titles, quoted phrases, inline code and fenced code remain usable conversational objects, while command-shaped words inside those protected spans cannot independently redirect the surrounding request. Quotation does not force a search; the user's surrounding language still determines the operation.
• Explicit Subject Switching - A clearly introduced article or subject can replace the active conversational focus even when its title contains words such as "start," "stop" or "it." Earlier subjects remain available for an explicit return.
• Source Ownership Across Returns - Returning to the first, second, previous or original subject restores that subject's own answer context and source identity instead of carrying attribution forward from a later article.
• Clearer Comparison Restatements - When a user asks for a comparison to be restated briefly or in one sentence, the Framework preserves both sides of the comparison and the relationship between them instead of reducing the answer to a disconnected fact.
• Policy Questions Stay Distinct From Content Requests - Questions about how the Framework handles authors are kept separate from requests for a particular article's author, preventing a policy discussion from being mistaken for permission to retrieve unrelated author details.
• Broader Conversation Continuity Foundation - Completed subjects, supported findings and answer context can now be represented across both website content and other connected evidence families. This new continuity layer remains observational while its confidence and ambiguity behavior are validated, so it cannot override established routing or governance.

• Conversational Time Understanding - Extended the Framework's awareness of time into ordinary conversation. It now distinguishes actual date or time constraints from conversational phrases such as "Now, I need..." and can carry or revise the intended period through follow-up questions.
• Time-Bounded Answers - Requests for information from today, yesterday, or another stated period are resolved in the installation's timezone and remain limited to that period. If matching information is unavailable, an older source is not silently substituted.
• Deeper Conversational Locality - Improved how the Framework keeps multiple conversational objects available without allowing the most recently retrieved article to displace the continuing question, requested timeframe, or active operation.

• Article Anchor Reuse for Links - WordPress search and analyzer mode now share a common article anchor (URL, ID, title) that can be reused for link-style follow-ups, making "link?" and similar questions resolve to the correct post without re-running heavy search logic.

• Improved Article Recognition - The framework now identifies correct posts based on titles, IDs, and URL patterns before performing deeper search operations.
• Reliable Summary Delivery - All summaries, breakdowns, and analysis requests use a dedicated, isolated analyzer mode for consistent results.
• High-Integrity Link Handling - Internal links are preserved and converted to clean HTML; external links are removed for safety.

Core Architectural Infrastructure

• Post-Evaluation Evidence Weighting - Every qualified knowledge candidate now receives full consideration for present-request standing before its intrinsic source weight can influence synthesis. High-bias Knowledge Base material retains its canonical value after evaluation, but authority can no longer manufacture relevance or prevent lower-weight contradictory information from being understood.
• MiniBrain Post-Evaluation Reconciliation - Source evaluation reports whether evidence has standing without choosing the route, grounding outcome, answer, or speaker. MiniBrain receives that inert evaluation state and coordinates whether cognition continues with applicable evidence, bounded identity reasoning, or an evidence-required unknown.
• Advisory Decision Coordination - MiniBrain can preserve an ordinary advisory operation over facts supplied by the person even when a generic semantic frame resembles retrieval. Asking whether to document, compare, or safely change the reported condition remains available to cognition, while tenant capabilities, current publishing facts, prices, contact details, and URLs remain evidence-bound.
• MiniBrain Response Coordination - MiniBrain now coordinates the final response contract as well as the operation plan. It supplies the installation identity with the requested conversational scale, distinguishes verified capabilities from proposed guidance, and governs how provenance is expressed without allowing a fixed disclosure or downstream producer to replace the conversation.
• Source-to-Operation Projection Reconciliation - Retrieved article and WordPress objects remain candidate evidence until MiniBrain confirms that the resolved operation actually depends on tenant-published content. An unrelated source can no longer acquire visible provenance or persistent conversation standing merely because retrieval found it during an otherwise valid answer.
• Subordinate Event Coordination - Post-answer events such as delayed onboarding now return to MiniBrain for authorization against the active request, closure state, and Quest Ledger progress. Supporting events remain available, but yield when the person has paused, declined continuation, or is still completing a substantive objective.
• MiniBrain-Coordinated Conversation Handoffs - Final model reasoning now receives the same bounded conversational state, open Quest Ledger observations, and preserved operation plan that MiniBrain used to coordinate the turn. A fallback can no longer discard an established task merely because no tenant source answered the present utterance.
• Weighted Memory Authority Preservation - Knowledge is synthesized as weighted likelihood rather than a winner-take-all source choice. Canonical Knowledge Base records retain the strongest default bias while confidence and present-turn applicability determine their actual influence; thread memory remains authoritative for what occurred in that conversation without becoming tenant truth.
• MiniBrain Cognitive Coordination Foundation - Added the first typed coordination transaction shared across recurrent MiniBrain phases. Specialist layers retain their own bounded judgment and execution work, but now return scoped signals and proposals to the coordinator instead of acquiring route, completion, answer, or speaking authority. The shadow-only foundation also tracks obligation candidates and produces a bounded comparison trail without changing active conversation behavior.

• Market-Pack Boundary Audit - Completed the architecture review separating universal cognition from reusable industry terminology and installation-owned client mappings. The audit defined future packs as inert, independently versioned observations without routing, source-admission, truth, Ledger, answer, or speech authority; implementation remains pending.
• Elliptical Operation Coordination - The structural pipeline now preserves ordered requests such as retrieving an article and then auditing it even when the dependent phrase omits its verb, without granting Grammar route or answer authority.
• Objective-Aware Cognitive Context - Identity now receives a bounded, non-evidentiary view of the active subject, constraints, requested stages, and recent progress so a local handler cannot replace the larger conversational objective.
• One Governed Speaker - Reinforced Identity as Governance at the response boundary: MiniBrain coordinates, the Ledger reports progress, sources provide evidence, and downstream handlers propose work, but none may substitute its voice for the configured identity.
• Ledger-Assisted Continuity - MiniBrain now consults open subjects, constraints, and obligations from the observation-only Quest Ledger while the Ledger remains unable to interpret, route, retrieve, trigger, govern, or compose answers.
• Inspectable Coordination Trail - Each turn retains a bounded audit of MiniBrain checkpoints, decisions, and authority assignments without making the audit or Ledger a cognitive authority.
• Downstream Entitlement Coordination - Available conversation state is now separated from state entitled to terminate the current turn, preventing mere data availability from becoming response authority.
• Governed Metadata Issuance - Retrieval and response producers now submit metadata proposals; only the shared governance boundary can activate an envelope and release fields to an authorized consumer and purpose.

• Language-Layer Governance - Syntax and Grammar were integrated with Semantics and Pragmatics as observational layers that cannot choose routes, sources, authority, or answers; MiniBrain retains operational authority.
• Adaptive Human Conversation Testing - Added the local Human Simulator with role-based visitors, natural turn adaptation, independent judging, reproducible seeds, and saved transcripts for discovering failures beyond fixed regression scripts.

• General-Concept Source Isolation - A policy question that mentions an article or author can no longer borrow WordPress retrieval or provenance from a previously active article. The article remains a suspended conversational object rather than becoming authority for the new question.
• Purchase Authority Separation - Signed Stripe evidence establishes that an approved annual purchase occurred; the customer confirmation authorizes issuance using the confirmed company and domain information. Neither the return page nor its form can manufacture paid entitlement, and repeated events remain idempotent.
• Installer and Updater Separation - Release Manager stores fresh-install and client-update artifacts separately. Installation verifies the active license and authorized domain with the central service before registering the deployment and writing the local installation lock.
• Completed Source Governance - Every currently enabled source-backed response path now crosses weighted synthesis or the deterministic evidence gate. Google Drive retrieval is UTF-8 safe, preserves Drive's own modified time separately from retrieval time, and no longer interprets binary document bytes as text.
• Scoped Discourse Reference Consumption - Only structurally supported, non-ambiguous frame references may supply Pragmatics context. They cannot select a route, source, answer or action; MiniBrain remains authoritative.
• Governed Position Adoption - A Framework position can now be adopted only through an explicit grounding gate with eligible current evidence and conflict clearance. Corrections preserve prior same-scope positions and their supporting history.
• Source-Owned Revision Evidence - Retrieval time is now kept separate from a source's own update or revision fact. File evidence can carry modification time and a content checksum, WordPress evidence can carry the post's modified time, and telemetry can carry its generated and observed-through period without inventing revision data for sources that do not expose it.
• Governed Candidate Boundaries - Expanded reference and grounding candidates remain inspectable, confidence-aware observations. They cannot acquire routing or decision authority merely by being present, and unresolved conflict or required revalidation continues to fail closed.
• Consistent Page Identity Across Reporting - Insights, detailed Analytics, Search Console and saved reports now treat HTTP and HTTPS, www and non-www, and trailing-slash forms as the same authorized hostname or page. Equivalent page rows are combined before ranking or comparison, while Google property access remains the outer reporting boundary.
• Evidence Use and Relevance Enforcement - Connected evidence now carries explicit allowed-use and relevance requirements before it can participate in an answer. Evidence that is valid for one purpose cannot silently establish a different kind of claim.
• Freshness-Aware Current Answers - Evidence records when it was retrieved and whether it is current enough for the requested claim. Stale evidence may remain visible as historical context, but it cannot establish a current fact that requires revalidation.
• Claim-Level Conflict Review - Conflicting evidence is compared within the exact claim being answered, with source authority, relevance, freshness and eligibility kept explicit. A preferred candidate remains evidence for the Framework to evaluate and does not become an automatic final decision.
• Consistent Governance Across Sources - The shared evidence rules now apply to direct fact retrieval as well as website, Analytics, Search Console, knowledge and other registered source paths, reducing the chance that a shortcut can bypass the Framework's evidence boundaries.
• Operational Article Answers - In the authenticated workspace, ordinary questions that ask how one supplied article performed are answered directly in chat. The connected content source first verifies the canonical article and publication date, then the existing Analytics and Search Console readers collect the minimum authorized page-level evidence needed for the answer.
• Direct Answers and Durable Reports - A simple single-article question no longer creates a saved report merely because evidence must be retrieved. Explicit requests to create, prepare, save or run a report, along with collections and multi-article work, retain the confirmed, resumable report workflow.
• Authorized URL Resolution - A supplied article address identifies the reporting object but does not grant fetch authority. Exact-URL retrieval is limited to configured WordPress sources, reconciles authorized HTTP/HTTPS, www/non-www and trailing-slash variants, and cannot silently substitute sitewide totals or another page.
• Requested Evidence Scope - Article-performance requests can now ask specifically for Google Analytics activity, specifically for Google Search performance, or generally for overall performance. The Framework interprets the complete request, shows the proposed evidence scope for confirmation, and runs only the eligible reporting sections instead of treating example wording as a fixed command.
• Integrated Performance Explanation - A general performance request presents GA4 website activity and Search Console visibility as distinct measurements, then explains what they indicate together in one assessment. Source-specific requests stay limited to the requested evidence family and do not imply that the other provider measured the result.
• Provider-Accurate Report Methodology - Report explanations now name only the evidence families that actually participated. An Analytics-only report cannot imply that Search Console was queried, including when tracking-parameter variants are included.

• Durable Report Work - Long-running reports continue while users move through the administration workspace. Progress, pause and retry controls clearly show when work is active, prevent duplicate requests, save the current checkpoint and resume at the next unfinished section.
• Historical Reporting Reconciliation - Article totals use the appropriate provider aggregate, recognize harmless protocol, www and trailing-slash URL variations, preserve explicit tracking-parameter choices and prevent publication-age comparison rows from replacing full-period headlines.
• Governed Reporting Time - Reporting periods now remain active across Insights, Analytics, Search Console and chat. Presets use the configured business timezone, exclude incomplete current-day data, retain corrected dates and comparison intent, and cannot be replaced by an older 28-day conversation state.
• Governed Administration Conversations - The authenticated workspace chat now passes through the same Language, Pragmatics, MiniBrain intent, evidence-synthesis and governed response boundaries as the public-facing conversation instead of entering an administration-only shortcut.
• Employee-Owned Workspace History - Administration conversation sessions are isolated by signed-in user in browser state, server state and dedicated administration records. Employee workspace history remains separate from visitor conversations and Chat Telemetry.
• Private Reporting Evidence - Shared answer caching remains disabled in the authenticated workspace. Saved conversation text may include figures explained to that user, while raw Analytics and Search Console provider responses are not persisted as chat history.

• Framework-Authored Multi-Source Answers - Sources contribute weighted evidence while the Framework forms and delivers the answer in its own voice. No single retrieved source becomes the intelligence or automatically owns the response.
• Protected Installation Secrets - Installation keys remain local, survive Framework updates, never enter client distribution packages, and preserve compatibility with previously configured encryption keys.

• Governed Conversation Representation - Established a bounded foundation for preserving complete conversational subjects across topic changes while keeping retained state subordinate to the framework's knowledge, evidence, identity, and authority rules.
• Knowledge-Autonomy Boundary - Separated remembered user statements from governed business knowledge so conversation can preserve differing viewpoints without allowing repetition or persuasion to rewrite authority.
• Governed Judgment - Defined how the framework can disagree with unsupported assertions and revise an earlier position when stronger authorized information becomes available, while preserving the history of the exchange.
• Inert State Safeguard - Retained conversational state remains a passive representation for continuity. It cannot initiate work, create conversations, or become an independent knowledge or decision authority.

• Grounding Model Documentation Refresh - Updated the internal scope and working-conventions documents plus the public scope overview so the framework's architecture now describes knowledge layers as authority-weighted evidence signals feeding one governed answer path, with canonical KB acting as the strongest truth bias rather than an isolated single-source answer engine.

• Onboarding Isolation Governance Clarification - Clarified the framework architecture and scope documents so onboarding and authentication are treated as a closed, pre-cognitive interrupt phase. While onboarding is active, name capture, email capture, session-save prompts, and password or PIN setup must not trigger MiniBrain, knowledge retrieval, analyzer execution, or AI fallback until that phase completes.
• Working Conventions Documentation Added - Added a dedicated repository conventions document to preserve recurring maintenance rules such as public-vs-internal release writeups, ASCII-safe formatting expectations, patch-oriented edits, and onboarding isolation handling across future sessions.
• Source Authority Routing Hardening - Tightened content-routing behavior so explicit URL analysis and recent article follow-ups keep the correct source authority instead of being redirected back through unrelated knowledge-base context.
• Source Authority Refinement - Added broader source-authority handling so first-party business questions are less likely to be claimed by conceptual knowledge entries when live site content is the better fit.
• Flat-File Authority Refinement - Refined the quick-answer flat-file behavior so deliberately provided exact matches can still answer directly, while weaker keyword-style flat-file hits are now treated as subordinate candidates that only apply if stronger knowledge-base or site-content authority does not satisfy the turn.
• Exact Flat-File Learning Capture - Updated exact flat-file matches so they are recorded into the framework's lower-authority learned-history layer before the answer is returned, preserving them as candidates for later review and possible elevation without turning the flat file itself into canonical knowledge.
• Last-Answer Source Recall - Added lightweight source-memory handling so follow-up questions about where the last answer came from can resolve more directly to the active knowledge-base or site-content source already held in state.
• Expanded Working Conventions - Extended the working conventions to capture durable guidance around upstream authority decisions, permissive prompting in runtime behavior, conversation quality expectations, and safe use of the stable release baseline.

• BigBrain License Cache Fetch & Validation (New) - Implemented a dedicated license retrieval and caching mechanism for BigBrain, allowing license tier and capability data to be fetched once, validated, cached locally, and reused across sessions.
• License Cache Validator & Hard Fallback - Added strict validation rules to ensure license cache integrity. If the license cache is missing or invalid, the framework safely falls back to default Tier IV behavior instead of attempting ungoverned capability escalation.
• Decoupled Governance and Licensing Fetch - Separated global governance prompt retrieval from license retrieval, ensuring that governance remains active even when license data is unavailable or temporarily unreachable.

• Multi-LLM Architecture Foundation - Introduced a provider-agnostic execution layer that allows the framework to operate consistently across multiple AI backends without duplicating governance, safety rules, or output logic.
• Centralized AI Exit & Governance Enforcement - All supported AI providers now terminate through the same governed response pipeline, guaranteeing uniform formatting, grounding enforcement, caching behavior, and safety controls.

• Centralized Global Governance Layer via BigBrain - The framework now treats the BigBrain global prompt service as a first-class architectural dependency. All client instances load a single, centralized governance/behavior/grounding prompt from API, caches it locally, and hard-fail gracefully if it is unavailable, guaranteeing that every response is generated under a consistent, centrally managed rule set.

• Topic Cloud Engine (New) - Introduced a live topic cloud system that identifies core themes, tracks subject alignment, and allows the AI to understand what the user is "really" talking about across multiple messages.
• Relevance Scoring Layer - Added a multi-tier relevance engine (core, related, peripheral, off-topic) used to guide intent routing, minimize hallucinations, and stabilize long conversations.
• Global Safety Patch - Implemented the first-generation global safety net to prevent incorrect fallbacks, reduce AI misroutes, and ensure that when the system finds a valid internal match, the conversation stays grounded.
• Enhanced WP Search Priority - Search results that match WordPress posts (title, slug, ID, or snippet match) now automatically take precedence over fallback AI responses.
• Last WP Hit Tracking - Added a temporary memory system ("short-term conversational context retention") that remembers the last article the user interacted with and injects its context into analysis follow-ups.
• Dedicated Article Loader Module - New module cleanly loads full article bodies, sanitizes content, and prepares them for analyzer mode.
• Analyzer Mode Overhaul - Completely rebuilt the article analyzer pipeline to prevent recursion, prevent invalid disclaimers, and ensure consistent behavior when summarizing or analyzing internal URLs.
• Internal vs. External Link Intelligence - The model now correctly distinguishes between internal vs external links, preserving internal links and scrubbing external ones.
• Pending Response Handling Stabilized - Reinforced pending-response detection so that the system avoids stalls and no longer drops follow-ups accidentally.
• UTF-8 & Encoding Fixes - Added deeper normalization of analyzer and system messages to prevent encoding corruption and malformed trademark characters.
• Improved Debug Logging - Reworked the debug console layout and added <hr> separators for easier block reading.
• Cleaner Conversation State - Fixed edge cases where off-topic classification interrupted WP routing; relevance scoring now correctly respects follow-up questions.

• Safe JSON Output - A new sanitizer prevents malformed content from breaking the UI and ensures all output is valid UTF-8.
• Frontend Decode Layer - The response handler now safely decodes escaped characters.
• Pending Response Reliability - Eliminated stalls when the AI returns placeholder text; results now flow correctly into the UI.
• Consistent Routing - Handles ambiguous requests and repeated prompts without losing context.

Stability & Polish

• Rejected Knowledge State Isolation - A Knowledge Base candidate becomes active conversational source state only after it receives present-request standing. Rejected entries are cleared from the legacy response handoff and cannot re-enter fallback cognition, suppress the final answer, or appear as unrelated provenance.
• WordPress Search Default-Mode Repair - Corrected a dormant enhanced-search call that passed an undefined mode variable under the current PHP runtime.
• PHP 8.4 Dialog-Context Compatibility - Made the optional keyword-extractor callback explicitly nullable so the Language Layer remains warning-free on PHP 8.4.
• Direct Source-Response Authorization - A specialist may retrieve or inspect a policy page without gaining permission to terminate the turn. Direct navigation responses now require MiniBrain to confirm that the person actually requested a destination, preventing incidental page language from short-circuiting broader planning or evaluation.
• Natural General-Knowledge Qualification - Repeated fixed provenance banners are removed from continuing conversation while material uncertainty and evidence limits remain expressed naturally through the configured identity.
• Accurate Conversation-State Provenance - Recaps formed from prior turns and non-authoritative Ledger progress are identified as thread-bound conversation state instead of being mislabeled as model-background general knowledge or borrowing an unrelated retained source.
• Incidental-Time Routing Correction - Mentioning when another person will perform an action no longer replaces the person's actual request with a direct date or time answer.
• Reliable Delayed Onboarding Dependency - The friendly delayed name prompt now loads before every response boundary that may invoke it, preventing a late-stage missing-function failure.

• Source-Selection Isolation Test Patch - Released and measured a deliberately source-only repair before applying downstream cognition changes, isolating how invalid evidence admission affected routing, recovery, provenance, and conversation quality.
• Conversational Boundary Repairs - Implemented the four shared boundary corrections isolated by Human Simulator Test Fifteen while preserving Identity, source, metadata, and Ledger governance rather than adding conversation-specific exceptions.

• Protected Purchase Delivery - Installer links expire after 30 minutes and permit three successful downloads before denying a fourth. Refreshes and repeated confirmation cannot duplicate fulfillment records.
• Purchase Email Delivery - Customers receive a signed support email containing their license, activation code, protected download and complete installation instructions. A separate idempotent, high-priority internal notice records the purchaser and licensed-domain details for TechDex.
• Live Commerce Acceptance - The production purchase return, signed Stripe webhook and signing secret, customer confirmation email and internal purchase notification completed end-to-end acceptance.

• Honest Coverage and Partial Results - Requested dates, returned provider coverage and dates with observed activity are distinguished. Missing history is not presented as zero, and incomplete evidence is explained beside the affected finding without discarding useful results elsewhere in the report.
• Protected Client Updates - The normal Update Manager preserves client-owned homepage and root server files while maintaining signed-package, compatibility, backup and checksum protections.

• Reliable Administration Sessions - Administration logins now use protected installation-specific session storage so unrelated software on the same server cannot impose a short cleanup window.
• Persistent Login Stability - Corrected a concurrency problem that allowed simultaneous administration requests to invalidate the Remember me login. Google authorization returns now preserve the complete signed-in administration identity.
• Reliable Client Google Connections - Updated the licensed Google connection handoff so legitimately reissued installation licenses can be verified without weakening current status, expiration, or authorized-website controls. Existing token and installed-client compatibility remain supported.
• Reliable Google Setup on Client Installations - Corrected the installer so each installation has its own protected key for encrypting Google authorization. Existing installations repair themselves after updating and do not need to be reinstalled.
• Framework Host Widget Access - The dedicated Framework subdomain is automatically included among websites permitted to display the widget for both new and updated installations.
• Deep Conversation Repair Validation - Repaired the remaining article-author continuity and security-topic ellipsis cases found through human review, then passed the focused temporal and publishing replay across 30 of 30 turns without a transport or assertion failure.

• Publisher-Style WordPress Query Handling - Added a first-pass deterministic WordPress retrieval layer for publisher and archive-heavy installs so singular latest/last story questions, homepage lead-story phrasing, topic-constrained latest lists, author-oriented lookups, and topic/category count queries are less likely to fall through into generic relevance search.
• WordPress Query Profile Groundwork - Introduced a lightweight WordPress query-profile classifier that extracts rough retrieval roles such as editorial structure, chronology, author lookup, catalog count, topic lookup, and contact-by-department, giving the framework an early arbitration surface above raw WordPress search without yet requiring a fully separate intelligence module.
• Department-Aware Contact Routing - Refined WordPress contact handling so subject-driven questions like advertising, marketing, sponsorship, editorial, support, and events are used to score the most relevant contact surface before the system falls back to a generic contact page.
• Auto-Resume Temporal Misfire Fix - Corrected deferred-query auto-resume behavior so resumed questions containing words like today or other temporal language are no longer sent directly to the system-time handler unless MiniBrain first confirms they are genuinely temporal questions, preventing content requests like “today’s top story” from collapsing into a date-only answer.
• Widget CSS Containment Hardening - Scoped broad widget stylesheet rules so the embeddable chat no longer repaints host-page backgrounds, anchors, and general layout surfaces when installed on client sites with their own themes, while preserving the direct /app interface styling.
• SVG Icon Reliability Upgrade - Replaced the most visible launcher, pop-out, microphone, and feedback controls with local SVG assets under the application image directory, removing the widget’s dependence on icon-font rendering for those controls across different client environments.
• Widget First-Load Rendering Stabilization - Updated the widget bootstrap so it waits for its stylesheet before mounting, assigns explicit icon dimensions on initial render, and reduces the cold-load race conditions that could leave the microphone invisible, the launcher oversized, or drag behavior inconsistent until refresh.

• Documentation Reference Expansion - Updated the framework documentation set so the wiki, scope, design principles, glossary, FAQ, docs index, and trademark-use pages reflect the current Tier IV governance language, evidence-handling model, and source-authority terminology.
• Cross-Linked Terminology Guidance - The FAQ now links key defined terms directly into the glossary, allowing readers to jump from practical answers into the authoritative project-specific definitions behind them.
• PDF Archive and Discovery Support - Added a versioned PDF archive index for documentation history, generated a new trademark-use PDF, and added both `llms.txt` and `sitemap.xml` under `/docs` to improve indexing, search discovery, and machine-readable documentation access.
• Homepage Messaging Alignment - Refined the main site homepage so marketing-facing language better matches the framework's current governed intelligence model while still preserving a strong sales-facing presentation, including clearer training-control wording, improved documentation visibility, and updated structured metadata.
• PDF Archive Presentation Finalization - Finalized the PDF archive view with a dedicated current-version section, explicit previous-version history, and visible publication dates so the documentation trail reads as a clear release record instead of a flat file list.
• Chat Interface Modernization - Redesigned the direct chat interface and embeddable widget with a more modern blue-forward visual system, improved header structure, refined launcher styling, cleaner message spacing, and a tighter input layout that keeps the chat surface aligned with the main site brand.
• Launcher Stability and Drag Controls - Added draggable launcher support for desktop pointer devices, kept mobile/touch interactions tap-safe, and constrained launcher behavior so it remains visible through resizing and viewport changes without drifting off-screen.
• Widget Pop-Out Workspace - Added a pop-out control that opens the active conversation in a dedicated chat-only window, preserves the current thread, hides normal launcher chrome in popout mode, and keeps the chat surface anchored inside the popup instead of inheriting floating widget positions.
• Config-Driven Chat Subtitle - Replaced the hard-coded chat subtitle with the deployment-level `app_tag` value from client configuration, added safe fallback handling, and constrained the displayed subtitle to a single-line ellipsis with a full-text hover title.
• Unfocused Reply Attention Signal - Added out-of-focus reply alerts for the direct chat and pop-out window, including flashing plain-text title updates and a lightweight browser-side notification chime when a real assistant reply lands while the chat window is not focused.

• Session Storage Alignment Correction - Reviewed and corrected session storage handling so the framework keeps using the established v1.0 directory layout, with thread transcripts, per-thread state files, and framework session support JSON remaining in the main sessions directory for runtime compatibility.

• Deferred Query Auto-Resume After Onboarding (New Feature) - The framework now captures a user's first real query during onboarding and automatically resumes it once onboarding completes, allowing conversations to continue without requiring the user to re-enter their original request.
• Pre-Cognitive Onboarding Isolation & Deferred Query Resume - Formalized onboarding as a non-cognitive interrupt phase that executes before any intent detection, topic inference, keyword extraction, or source routing occurs. User queries submitted during onboarding are now captured once, quarantined, and reintroduced only after onboarding completion, ensuring they enter the intelligence pipeline exactly as a first-class query.
• Conversation-State Contamination Prevention During Onboarding - Resolved a stability issue where onboarding inputs could overwrite or invalidate topic, intent, or relevance state. Cognitive state is now explicitly frozen during onboarding, preventing false topic creation, keyword loss, or intent downgrades when the deferred query is resumed.
• Controlled Cognitive Re-Entry After Onboarding - Improved post-onboarding recovery so deferred queries resume without triggering domain vetoes, empty grounding contexts, or forced AI fallback retries. This ensures clean topic inference, reliable WordPress routing, and consistent relevance scoring after onboarding completes.

• Stability: License Management Handling - Improved license-state handling to reduce edge-case failures during validation and runtime enforcement. This update strengthens consistency in how license status is read, applied, and maintained across requests.

• ASCII-Safe Response Normalization (Minor Stability Improvement) - Updated response handling to enforce ASCII-safe punctuation and characters across all governed output paths. This eliminates smart quotes, em dashes, and unsafe Unicode artifacts that could cause malformed JSON, cache write failures, or UI rendering issues, improving cross-browser consistency, logging reliability, and downstream processing without altering response content or behavior.

• Link Rendering Rule Optimization - Refined link-generation rules to prevent malformed HTML during long conversations. Presentation-specific attributes were decoupled from cognitive response generation, ensuring external links render cleanly and consistently in chat without interfering with reasoning or response structure.

• Cross-Domain Widget Rendering Stability - Improved widget z-index enforcement and runtime DOM monitoring to prevent conflicts with aggressive site themes, overlays, and mobile navigation layers when embedded across diverse client environments.
• Form Autofill & Bot Injection Hardening - Disabled browser autofill on chat inputs and reinforced honeypot handling to reduce accidental autofill noise and automated bot injection during live conversations.
• Cleaner Error Surface for Restricted Paths - Improved error message handling when users are redirected from protected or non-browsable application paths, allowing clear feedback without exposing directory structure or internal routing.

• Startup Order & Dependency Stabilization - Corrected initialization order to guarantee that global governance, license binding, and Tier mode resolution occur before any AI execution path is evaluated.
• Improved Diagnostic Visibility for Tier Mode - Logs now clearly indicate whether the framework is operating in Tier IV (single-provider) or Tier V (multi-provider) mode, simplifying debugging and client support.
• Multi-Domain Widget Session Reliability - Improved widget-side connection handling to ensure stable session creation and response flow when embedded on multiple client sites simultaneously.
• Prompt Execution Efficiency Improvements - Reduced prompt verbosity and internal repetition, lowering cognitive load on downstream models while preserving governance strength and grounding fidelity.

• Provider-Level Error Visibility - Enhanced logging and diagnostics now clearly identify when an upstream AI provider (OpenAI, xAI, or Gemini) is unavailable, improving observability during service interruptions.
• Graceful AI Fallback Handling - Strengthened framework-level handling of AI execution failures to prevent partial, malformed, or misleading responses during upstream outages.

• Follow-Up Edge Case Stabilization - Addressed edge cases where short follow-ups could inherit incorrect context, improving reliability during rapid conversational exchanges.

• Smoother message recovery when AI signals a pending response.
• More consistent routing of search requests.
• Expanded checks that prevent missing or incorrect answers.

Ready for Client Deployment

• Framework Application 1.0.20 - Published the signed client update containing the final conversational-locality, active-subject, identity, temporal, and object-bound evidence-refresh progression without changing either database version.

The framework is suitable for deployment on:

• business websites
• support assistants
• knowledgebase portals
• content-heavy sites with large archives
• membership and client portals

Whats Next

Version 1.0 is a completed historical release line. Current development, validation status, and future work are recorded in the Version 1.1 Patch Notes.

Release Information

Framework application 1.0.99 separates equal evidence consideration from weighted adjudication. Source Governance evaluates present-request standing without authority weights or control over route, grounding, answer, or speech; MiniBrain then applies intrinsic weights to the applicable evidence set and coordinates the next cognitive action. Rejected Knowledge Base candidates cannot become active state or survive through legacy response variables, while advisory decisions over user-supplied facts remain available to bounded identity reasoning. Exact TechDex probes confirmed clean general planning and WordPress-performance guidance without unrelated KB provenance, while applicable Framework knowledge retained its canonical bias. This release also includes bounded PHP 8.4 compatibility repairs and does not change either database schema version.

Framework application 1.0.98 advances MiniBrain from operation coordination into governed response coordination. MiniBrain now reconciles response scale and capability modality, authorizes direct source responses, limits article provenance to operations that actually depend on tenant-published content, and decides whether subordinate post-answer events may proceed. Exact-seed TechDex replays completed seven turns without an unrelated source projection, navigation short circuit, or onboarding interruption. Identity remains the only speaker, specialists retain their bounded work, the Quest Ledger remains observation-only and non-evidentiary, and neither database schema version changes.

Framework application 1.0.97 carries bounded recent conversation, the preserved operation plan, and the Quest Ledger's observation-only progress state through the final Identity reasoning handoff. Conversation recaps receive accurate conversation-state provenance, incidental time language no longer forces the direct-time path, delayed onboarding loads its required dependency before use, and weighted memory authority remains influential without becoming winner-take-all selection. Identity remains the sole speaker and neither database schema version changes.

Framework application 1.0.96 introduces the first bounded MiniBrain cognitive-coordination foundation for TechDex-first evaluation. A typed transaction now persists across recurrent coordination phases, accepts governed specialist signals and proposals, projects candidate obligation state, and records a bounded trace for comparison. The feature is intentionally configured in shadow mode: existing routing, retrieval, response behavior, Source Governance authority, the Quest Ledger's observation-only role, and identity-only speech remain unchanged while the new coordination model is evaluated. This release does not change either database schema version.

Framework application 1.0.95 adds a governed source-role boundary. Each article candidate receives an object profile, and the present utterance supplies required object types, required scopes, and explicit exclusions before evidence may reach cognition, metadata, continuity, or visible provenance. Returning to a retained result set requalifies its members rather than granting perpetual standing. Identity remains the sole speaker and neither database schema version changes.

Framework application 1.0.94 extends exact-object qualification to singular WordPress and article primaries, then makes synthesis, metadata, inline links, source footers, and later continuity consume the same qualified object set. Article-shaped metadata without a qualifiable object fails inert, and missing author, publication-date, or canonical-URL evidence remains a precise unresolved obligation instead of causing a whole-turn generic refusal. This release does not change either database schema version.

Framework application 1.0.93 materializes source synthesis only from independently admitted objects so rejected producer cards cannot survive outside the governed result set. It also adds bounded topical-retrieval recall and admits safe practical workflow planning to identity-led general reasoning before generic refusal, while preserving final source governance and all existing authority boundaries. This release does not change either database schema version.

Framework application 1.0.85 completes the metadata-governance boundary exposed by Human Simulator Test Fourteen. Producers can propose metadata but cannot activate it; only the governing issuer can create an active envelope, and response consumers discard raw fields before accepting a purpose-specific projection. Dynamic WordPress and article evidence receives an independent current-subject applicability decision, ineligible direct handlers yield instead of speaking, constrained chronology preserves alternative topics, and multi-result provenance retains each story's structured author, publication date, canonical URL, identity, membership, and order. Identity remains the speaker, MiniBrain remains routing authority, and neither metadata nor the Conversation Quest Ledger gains cognitive authority. This release does not change either database schema version.

Framework application 1.0.84 adds a typed metadata-envelope boundary so metadata can contribute only through declared consumers, purposes, scope, lifetime, and provenance. Stale retrieval metadata no longer becomes current answer provenance or article authority merely because it exists; verified structured facts remain available to authorized consumers; and conversational closure releases last-answer source ownership. Unknown or unauthorized metadata fails inert. Identity remains the speaker, MiniBrain remains the routing authority, and the non-authoritative Conversation Quest Ledger remains progress state rather than cognition or governance. This release does not change either database schema version.

Framework application 1.0.75 adds adaptive first-use conversation acceptance across four distinct client environments and repairs the earliest common failures it exposed. Ordinary tenant requests beginning with conversational forms such as “Can you” and “How do you” no longer activate Framework self-reference evidence; natural name-plus-question onboarding replies preserve the substantive question for resumption; plural topical WordPress results return to governed synthesis instead of appearing as raw search cards; and a fully named new comparison is no longer narrowed to a previously active article merely because it begins with “What about.” Syntax and Grammar now provide validated sentence, clause, phrase, grammatical-role, and coordinated-answer structure to Semantics and Pragmatics. This prevents incidental words in descriptive clauses from seizing an operation and preserves multi-part answer obligations without granting either language layer intent, route, source, action, or answer authority. MiniBrain remains the sole routing authority. This release does not change either database schema version.

Framework application 1.0.71 adds the self-service purchase-fulfillment foundation: signed Stripe payment evidence, customer-confirmed license issuance, protected fresh-installer delivery, signed central deployment registration before the installer locks, and separate updater and fresh-install artifacts in Release Manager. The associated TechDex commerce implementation was then refined during the same session to permit three successful downloads during a 30-minute link lifetime, provide the complete on-page and emailed installation guide, remove the unnecessary Administrator role/title field, and send separate signed customer and high-priority internal purchase notices. Those post-package TechDex refinements are not represented as additional contents of the 1.0.71 client update package. The $500 professional-installation option remains deferred.

Framework application 1.0.70 separates direct evidence retrieval from durable report creation. A simple, verified single-article performance question now receives its answer in Framework Chat without creating a saved report; explicit report artifacts, collections and multi-article work continue through the resumable report workspace. Exact-page Search Console filtering also includes authorized HTTP/HTTPS variants within the selected property boundary. This release does not change the database schema.

Framework application 1.0.69 corrects Analytics-only report methodology so it names only the evidence family actually requested and scheduled, including the tracking-parameter path. This release does not change the measurement-scope architecture or database schema.

Framework application 1.0.68 adds governed measurement-family scope to article-performance reporting. Natural requests may select Google Analytics, Google Search or both; the proposed scope remains reviewable before execution, only eligible provider sections and property bindings are used, and general performance receives one integrated assessment without blending unlike measurements. This release does not change the database schema.

Framework application 1.0.67 adds governed single-article performance retrieval from natural administration-chat requests. An explicit article URL is resolved only through an authorized connected WordPress source, which establishes its canonical identity and publication date before the existing GA4 and Search Console report plan runs through the latest complete day. This release does not change the database schema.

Framework application 1.0.66 closes the final public author-policy provenance leak found by live acceptance testing. General policy and concept answers now exclude prior article sources at the final answer-metadata boundary while retaining any applicable non-article governed evidence. This release does not change the database schema.

Framework application 1.0.65 completes the public Chat Telemetry disclosure and release policy, expands natural telemetry questions and requested rolling periods, keeps raw or person-level details unavailable, and prevents general article-author policy answers from borrowing a suspended article's source identity. This release does not change the database schema.

Framework application 1.0.64 completed governance adoption for all currently enabled source-backed paths, replaced the legacy Google Drive reader with a governed UTF-8-safe adapter, completed calibrated multi-subject context consumption without granting routing authority, added the explicit grounding-gate position-adoption boundary, and closed the remaining public author-policy consumer mismatch. This release did not change the database schema.

Framework application 1.0.63 added one centralized role-permission contract across navigation, direct pages and protected actions. User accounts receive only their assigned chat and reporting workspaces; Manager accounts receive scoped AI, analytics, update and ordinary-user management tools without access to Connections or sensitive application administration; Administrator accounts retain full access. Managers cannot create, open, edit, promote or delete Administrator accounts.

Framework application 1.0.62 added protected control-text and object-text handling, repaired explicit article switching and ordinal subject returns, restored source ownership with returned subjects, recorded source-owned revision facts separately from retrieval time, and expanded governed reference and grounding candidates without granting them routing or decision authority.

Framework application 1.0.61 introduced the preceding allowed-use, relevance, freshness, claim-conflict, direct-retrieval, comparison-preservation, author-policy and inert cross-source continuity foundation.

The consolidated September 5 session was delivered through Framework application releases 1.0.30 through 1.0.54. Version 1.0.33 was an unpublished transition package replaced by the protected 1.0.34 updater release. Framework 1.0.54 was the signed application release closing that session. Members database bundle 1.0.2 added the dedicated employee-owned administration conversation tables as a separately approved and checksummed database update. TechDex installed and verified both updates with automatic backups; client installations remain administrator-controlled.

Framework application 1.0.29 completed the initial article-match verification and saved-report management pass, including visible match evidence, separated broader suggestions, original-request reruns and confirmed report deletion.

• Framework Application 1.0.26 - Added direct saved-finding access, longer report-analysis time, destination-domain input, keyword suggestions and highlighting, improved report controls and Insights-to-chat links while preserving existing reports.
• Framework Application 1.0.25 - Added broader keyword, category and tag discovery when no article matches every phrase together, with explicit user selection before reporting.
• Framework Application 1.0.24 - Added useful empty-result guidance and preserved report-search details while refining a request.
• Framework Application 1.0.23 - Introduced connected administration content reporting, confirmed article collections, saved progress, claim-level limitations and follow-up discussion. Report downloads remained disabled.