syntaxmatrix 3.0.0__tar.gz → 3.0.1__tar.gz

{syntaxmatrix-3.0.0 → syntaxmatrix-3.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: syntaxmatrix
-Version: 3.0.0
+Version: 3.0.1
 Summary: SyntaxMatrix: A Framework for  building owned AI Platform.
 Author: Bob Nti
 Author-email: bob.nti@syntaxmatrix.net

{syntaxmatrix-3.0.0 → syntaxmatrix-3.0.1}/SyntaxMatrix.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: syntaxmatrix
-Version: 3.0.0
+Version: 3.0.1
 Summary: SyntaxMatrix: A Framework for  building owned AI Platform.
 Author: Bob Nti
 Author-email: bob.nti@syntaxmatrix.net

{syntaxmatrix-3.0.0 → syntaxmatrix-3.0.1}/setup.py

@@ -8,7 +8,7 @@ with open(os.path.join(this_directory, "README.md"), encoding="utf-8") as f:
 
 setup(
     name="syntaxmatrix",
-    version="3.0.0",
+    version="3.0.1",
     license="MIT",
     classifiers=[
         "Programming Language :: Python :: 3.9",

{syntaxmatrix-3.0.0 → syntaxmatrix-3.0.1}/syntaxmatrix/agentic/agents.py

@@ -1478,21 +1478,21 @@ def agentic_generate_page(*,
         css = f"""
         <style>
             #{page_id} {{
-            --r: 18px;
-            --bd: rgba(148,163,184,.25);
-            --fg: #0f172a;
-            --mut: #475569;
-            --card: rgba(255,255,255,.78);
-            --bg: #f8fafc;
-            font-family: system-ui, -apple-system, Segoe UI, Roboto, Arial, sans-serif;
-            background: var(--bg);
-            color: var(--fg);
-            overflow-x: clip;
+                --r: 18px;
+                --bd: rgba(148,163,184,.25);
+                --fg: #0f172a;
+                --mut: #000000;
+                --card: rgba(255,255,255,.78);
+                --bg: #f8fafc;
+                font-family: system-ui, -apple-system, Segoe UI, Roboto, Arial, sans-serif;
+                background: var(--bg);
+                color: var(--fg);
+                overflow-x: clip;
             }}
             @media (prefers-color-scheme: dark){{
             #{page_id} {{
                 --fg: #e2e8f0;
-                --mut: #a7b3c6;
+                --mut: #000000;
                 --card: rgba(2,6,23,.45);
                 --bg: radial-gradient(circle at 20% 10%, rgba(30,64,175,.25), rgba(2,6,23,.95) 55%);
                 --bd: rgba(148,163,184,.18);

{syntaxmatrix-3.0.0 → syntaxmatrix-3.0.1}/syntaxmatrix/page_builder_generation.py

@@ -838,29 +838,18 @@ def compile_layout_to_html(layout: Dict[str, Any], *, page_slug: str) -> str:
 
     css = """
     <style>
-        .smxp{--r:18px;--bd:rgba(148,163,184,.28);--mut:#94a3b8;--fg:#0f172a;--card:rgba(255,255,255,.72);
         .smxp{
             --r:18px;
             --bd: rgba(148,163,184,.25);
             --fg: #0f172a;
-            --mut: #475569;                 /* <- darker, readable */
+            --mut:#000000;                /* <- darker, readable */
             --card: rgba(255,255,255,.78);
             --bg: #f8fafc;
             font-family: system-ui, -apple-system, Segoe UI, Roboto, Arial, sans-serif;
             background: var(--bg);
-            color: var(--fg);
             overflow-x: clip;
         }
-        @media (prefers-color-scheme: dark){
-            .smxp{
-                --fg:#e2e8f0;
-                --mut:#a7b3c6;
-                --card:rgba(2,6,23,.45);
-                --bg: radial-gradient(circle at 20% 10%, rgba(30,64,175,.25), rgba(2,6,23,.95) 55%);
-                --bd: rgba(148,163,184,.18);
-            }
-        }
-
+       
         font-family: system-ui, -apple-system, Segoe UI, Roboto, Arial, sans-serif; color: var(--fg); }
         @media (prefers-color-scheme: dark){
         .smxp{--fg:#e2e8f0;--card:rgba(2,6,23,.45);--bd:rgba(148,163,184,.18);--mut:#a7b3c6;}

{syntaxmatrix-3.0.0 → syntaxmatrix-3.0.1}/syntaxmatrix/routes.py

@@ -6,6 +6,7 @@ import json, pandas as pd
 import contextlib, werkzeug
 import io as _std_io
 
+from flask import abort
 from io import BytesIO
 from scipy import io
 from flask import Blueprint, Response, request, send_file, session 
@@ -380,6 +381,55 @@ def _render_reasoning_process_download(refined_question, thought_obj, tasks, TOK
 
 
 def setup_routes(smx):
+    
+    def _safe_slug(s: str) -> str:
+      s = (s or "").strip()
+      if (not s) or ("/" in s) or ("\\" in s) or (".." in s):
+          return ""
+      return s
+
+    @smx.app.route("/client-pages/<slug>")
+    def client_pages(slug):
+        """
+        Serve CEO-managed raw HTML from:
+          syntaxmatrixdir/client_pages/<slug>/index(.html/.htm)
+        """
+        slug = _safe_slug(slug)
+        if not slug:
+            abort(404)
+
+        base_dir = smx._client_dir / "client_pages" / slug  # ✅ correct for your framework
+
+        # Accept common Windows saved names too
+        for fname in ("index.html", "index.htm", "index"):
+            fpath = base_dir / fname
+            if fpath.is_file():
+                return send_from_directory(str(base_dir), fname)
+
+        abort(404)
+
+    @smx.app.route("/client-pages/<slug>/<path:asset_path>")
+    def client_pages_assets(slug, asset_path):
+        """
+        Serve assets from:
+          syntaxmatrixdir/client_pages/<slug>/<asset_path>
+        """
+        slug = _safe_slug(slug)
+        if not slug:
+            abort(404)
+
+        if ".." in asset_path or asset_path.startswith(("/", "\\")):
+            abort(404)
+
+        base_dir = smx._client_dir / "client_pages" / slug  # ✅ correct for your framework
+        full_path = base_dir / asset_path
+
+        if not full_path.is_file():
+            abort(404)
+
+        return send_from_directory(str(base_dir), asset_path)
+
+
     # Prevent duplicate route registration.
     if "home" in smx.app.view_functions:
         return
@@ -1926,6 +1976,7 @@ def setup_routes(smx):
     
      # ──────────────────────────────────────────────────────────────────────────────────────── 
     
+
     @smx.app.route("/toggle_theme", methods=["GET"])
     def toggle_theme():
         if not getattr(smx, "theme_toggle_enabled", False):
@@ -1957,6 +2008,7 @@ def setup_routes(smx):
         session.modified = True
         return redirect(request.referrer or url_for("home"))
 
+
     # ──────────────────────────────────────────────────────────────────────────────────────── 
     # ── HOME VIEW DETAILS -----------------------------
     @smx.app.route("/", methods=["GET", "POST"])
@@ -1974,14 +2026,26 @@ def setup_routes(smx):
                 page_name = (db.get_setting("landing.page_name", "") or "").strip()
             except Exception:
                 page_name = ""
-
+            
+            # Support raw HTML landing targets: html:<slug>
+            if page_name.startswith("html:"):
+                slug = page_name.split(":", 1)[1].strip()
+                if slug:
+                    return redirect(url_for("client_html_page", slug=slug))
+        
             if page_name:
-                # Safety: only redirect if the page exists
                 try:
                     page_html = db.get_page_html(page_name)
                 except Exception:
                     page_html = None
 
+                if page_html is None:
+                    # view_page() falls back to smx.pages, so home() must too
+                    try:
+                        page_html = smx.pages.get(page_name)
+                    except Exception:
+                        page_html = None
+
                 if page_html:
                     return redirect(url_for("view_page", page_name=page_name))
 
@@ -6140,14 +6204,7 @@ def setup_routes(smx):
                 db.set_setting("branding.website_description", (request.form.get("website_description") or "").strip())
                 changed_settings = True
 
-            if ok1 or ok2 or ok3 or changed_settings:
-                try:
-                    smx._apply_branding_from_disk()
-                except Exception:
-                    pass
-                flash("Branding updated ✓")
-
-                        # Landing page settings
+            # Landing page settings (MUST be processed before the "changed_settings" decision)
             if "landing_mode" in request.form:
                 landing_mode = (request.form.get("landing_mode") or "chat").strip().lower()
                 if landing_mode not in ("chat", "page"):
@@ -6160,6 +6217,14 @@ def setup_routes(smx):
                 db.set_setting("landing.page_name", landing_page_name)
                 changed_settings = True
 
+            # Apply + notify if anything changed (uploads OR settings, including landing settings)
+            if ok1 or ok2 or ok3 or changed_settings:
+                try:
+                    smx._apply_branding_from_disk()
+                except Exception:
+                    pass
+                flash("Branding updated ✓")
+
             return redirect(url_for("admin_branding"))
 
         # GET: show current status

{syntaxmatrix-3.0.0 → syntaxmatrix-3.0.1}/syntaxmatrix/settings/prompts.py

@@ -1,202 +1,13 @@
+SMXAI_CHAT_IDENTITY = ""
 
-SMXAI_CHAT_IDENTITY = f"""
-    Your name is 'smxAI'. 
-    You are the expert AI Engineer and Data Scientist at SyntaxMatrix Ltd. 
-    Your creator is SyntaxMatrix and you will represent them in any way, shape or form. 
-    Your Company is based in Ireland. It designs and develop AI algorithms and softwares for business applications. 
-"""
-
-SMXAI_CHAT_INSTRUCTIONS = """
-    You respond to queries that are about your company only.
-    If a query is not about your company, kindly bring the conversation to be about your company.
-    Be professional at all times
-
-    Content & Formatting Blueprint (Adhere Strictly):
-    Structure your response using the following elements as appropriate for the topic. Prioritize clarity and information density. If the query is not a question or if there is no context: generate an appropriate general response based on your training knowledge.
-    else if the query is a question:
-    1. Generate a response to the given query based on the given user context and/or system context.
-    2. Use the chat history to stay relevant.
-    3. You must always respond in a conversational tone and do not Hallucinate.
-    4. Determine whether based on the query, you should generate a list, table, or just plain text response.
-    5. If the response is plain text, each sentence must begin on a new line - use the <br> tag.
-    6. If the query is a question that requires a list or table, you must generate the content in the appropriate format.
-    7. Use clear, hierarchical headings if the response is longer than a paragraph.
-    8. Be direct and concise. Avoid unnecessary fluff or repetition.
-    9. Lead with your key conclusion or answer in the first sentence.
-    10. Support your answer with clear, factual points.
-    
-    ────────  FORMAT INSTRUCTIONS ───────────────
-        1. Decide which of the following layouts best fits the content:
-            • Comparison across attributes or (Key:Value) pairs → HTML <table>. 
-            • When creating a table, adhere to the following styling instructions:
-                a. Firstly, define any 3 colors and assign them to c1,c2,c3 (example: c1="#EDFBFF", c2="#CCCCCC", c3="#E3E3E3". c2 and c3 should be similar but slightly different shades.
-                
-                b. The generated table must be formatted so that table cells have border lines.
-                c. The table head (<thead>) must always have a background color of c1.
-                d. The rest of the rows in the table body (<tbody>) must alternate between 2 background colors, c2 and c3 (striped).
-            • Use bullet points <ul> for simple lists of items, features → HTML.
-            • Use ordered list <ol> for sequences or ranking or steps in a process → HTML
-        2. Keep cells/list items concise (one fact or metric each).  
-        3. All markup must be raw HTML. Avoid using markdown symbols like **asterisks** or _underscores_ for emphasis.
-        4. Do not wrap the answer inside triple back-ticks.
-        6. If emphasis is needed, use clear language (e.g., "It is important to note that...").
-        7. Use horizontal lines (<hr>) sparingly to separate distinct sections.
-        8. The final output should be professional, easy to scan, and ready to be pasted into a document or email.
-"""
-
-SMXAI_WEBSITE_DESCRIPTION = """
-SyntaxMatrix — Website Description
-
-SyntaxMatrix is an enterprise-first AI engineering company that builds governed, client-owned AI platforms for organisations that need control over their data, their deployment boundary, and their operational outcomes. The company’s flagship product, SyntaxMatrix Platform Provisioner (smxPP), is a full-stack Python platform provisioner designed to deliver complete AI-enabled applications into a client’s environment in a repeatable, auditable, and maintainable way.
-
-Most organisations do not struggle to “try AI”. They struggle to keep it working reliably after the initial proof-of-concept. The real challenge starts when prototypes become production workloads: knowledge sources grow, policies tighten, teams change, and the solution needs governance, monitoring, access control, and repeatability. SyntaxMatrix exists to solve that “Day 2” reality by providing a platform that can be deployed and operated as part of an organisation’s actual systems landscape, rather than as a fragile demo.
-
-smxPP is not a hosted wrapper around AI APIs. It is a provisioned platform: a deployable system that is installed into a client’s own instance, where the client retains sovereignty over their runtime, their documents, their users, and the security perimeter. The result is a governed AI platform that can be run in regulated environments, private networks, or controlled cloud deployments — with clear role separation, traceability, and a data pipeline that is designed for operational integrity.
-
-What smxPP provides
-
-smxPP provisions a complete platform surface, not a single feature. The platform is built around real enterprise needs: controlled user access, secure content ingestion, governed retrieval pipelines, internal documentation and pages, structured workflows, and optional machine learning tooling for teams that need it. The platform is engineered so organisations can standardise how they deploy and operate AI functionality across departments, business units, and client projects.
-
-1) Role-aware access and controlled operations
-
-smxPP includes role-aware access control so that administration, staff actions, and end-user experiences remain separated and auditable. This matters in real deployments: a platform that can ingest and answer from internal knowledge must enforce who can upload, who can publish, who can configure, and who can export. smxPP is built so that organisations can run AI-enabled capabilities without turning governance into an afterthought.
-
-2) Document ingestion, retrieval, and RAG that can be governed
-
-The platform supports document ingestion and retrieval workflows designed for enterprise usage: structured chunking, indexing, retrieval, and controlled answering. smxPP enables Retrieval-Augmented Generation (RAG) experiences where an assistant can answer questions grounded in organisational content, while still giving operators the tooling to manage sources, auditing, and quality. The emphasis is on reliability and clarity: content is ingested with intent, stored with traceability, and retrieved in a way that can be improved over time.
-
-3) Page Studio for internal portals and knowledge-driven pages
-
-smxPP includes a page system that enables organisations to generate and manage internal or external pages from structured content, with an admin surface for editing, publishing, and maintaining these pages as part of a broader platform. This is critical when AI must integrate into real organisational communication: policies, procedures, services, knowledge bases, onboarding documentation, and operational content are not separate from AI — they are part of the same system.
-
-4) Documentation and knowledge base experience inside the platform
-
-smxPP supports an integrated documentation viewing experience so product documentation and operational knowledge can live alongside the system itself. For enterprise teams, this reduces friction: the platform is not just a runtime, but also a controlled surface for guidance, onboarding, and internal enablement.
-
-5) Optional ML Lab capabilities for structured analysis and export
-
-Where required, smxPP can provide a controlled ML workflow surface: dataset upload, exploration, modelling support, and export of results. This is not positioned as “auto-ML hype”, but as an operational capability that helps teams validate hypotheses, produce repeatable artefacts, and share outputs in a controlled way.
-
-6) Premium features and entitlements that map to operational value
-
-smxPP supports premium and enterprise entitlements that correspond to real operational needs: increased usage caps, larger document volumes, scaled user access, expanded storage allowances, and enhanced governance features. The premium model is not a cosmetic upsell — it is tied to the parts of platform operation that genuinely cost time, compute, and support to deliver at enterprise quality.
-
-Deployment model: client-owned by design
-
-A core differentiator of smxPP is the client-owned instance model. SyntaxMatrix does not host customer instances as a default operating model. Instead, each organisation deploys smxPP into its own environment and controls its own data boundary. This matters for enterprises that cannot accept third-party hosting for compliance, security, or policy reasons. It also matters for organisations that want long-term autonomy: the platform is provisioned so clients can maintain it as part of their internal systems landscape, while still benefiting from a clear upgrade path and supported premium capabilities.
-
-smxPP can be deployed in multiple patterns depending on organisational constraints:
-
-private cloud deployment (controlled networking and identity)
-
-secure cloud environments with strict access controls
-
-controlled hosting scenarios where the client remains the operator
-
-environments where outbound access is limited and governance is strict
-
-This deployment stance is a practical trust signal: it aligns with how security and procurement teams assess operational risk. Instead of asking an organisation to trust a black-box hosted system, smxPP provides a platform they can inspect, configure, and run under their own governance policies.
-
-Licensing that supports enterprise trust
-
-To support premium entitlements while maintaining operational integrity, SyntaxMatrix provides a dedicated licensing service that integrates with subscription billing and licence enforcement. This licensing architecture is designed to protect both the customer and SyntaxMatrix:
-
-Customers get a clear, auditable entitlement model that maps to features and usage caps.
-
-SyntaxMatrix ensures subscription state and premium access remain consistent and fraud-resistant.
-
-The system can represent real billing conditions (active, past due, grace period, revoked) rather than pretending billing is always perfect.
-
-The licensing service integrates subscription management with a controlled entitlement workflow. Premium access is activated via signed licence payloads and is validated through the licensing flow to prevent tampering and unauthorised upgrades. For enterprise buyers, this is not about “locking people out”; it is about ensuring contractual terms and platform governance remain aligned with operational access, and that the platform behaves predictably when billing state changes.
-
-Self-serve billing management is supported via the customer portal provided by Stripe, enabling customers to:
-
-update payment method
-
-view invoices
-
-cancel subscription (at period end)
-
-manage billing details without support tickets
-
-Where payment events require operational nuance, the system supports a grace period model so organisations do not lose access instantly due to a transient billing failure. That is a practical enterprise requirement: it reduces disruption while still enforcing contract reality if issues are not resolved in time.
-
-What SyntaxMatrix delivers as a company
-
-SyntaxMatrix provides more than software. The company provides platform provisioning services and engineering support tailored to organisations that want durable AI systems rather than disposable demos. Typical engagements include:
-
-Platform provisioning and deployment planning
-Helping teams choose the right deployment approach, configure their instance correctly, and align platform operation with security and governance constraints.
-
-Knowledge architecture and RAG readiness
-Assisting organisations in structuring content for retrieval, defining ingestion practices, improving chunking strategies, and building a dependable knowledge pipeline.
-
-Governance-first configuration and access modelling
-Supporting role design, operational permissions, and audit-ready patterns for how the platform is managed internally.
-
-Premium enablement and operational scaling
-Enabling higher-volume usage, larger content stores, and scaling features that align with real enterprise requirements.
-
-Optional fine-tuning and privacy-aligned model strategy (where required)
-When organisations require tighter privacy controls or specialised performance, SyntaxMatrix can support model strategy work that aligns with deployment constraints and internal data governance policies.
+SMXAI_CHAT_INSTRUCTIONS = ""
 
-Who smxPP is built for
+SMXAI_WEBSITE_DESCRIPTION = ""
 
-smxPP is designed for organisations and teams that need clarity, governance, and operational reliability:
 
-CTOs and engineering leaders who want repeatable platform deployment across teams
-
-AI architects who need control of data flows, retrieval behaviour, and access boundaries
-
-Compliance-minded organisations that cannot accept casual handling of internal documents
-
-Enterprise teams that want self-hosting and BYOK operation rather than vendor lock-in
-
-Operators who need auditability, predictable behaviour, and controlled upgrades
-
-What makes smxPP different
-
-smxPP is differentiated by its stance and its engineering priorities:
-
-Client-owned instance model
-The platform is provisioned into a client environment, supporting data sovereignty and deployment control.
-
-Governance and operational structure baked in
-Role separation, administrative workflows, and controlled operations are first-class design concerns.
-
-A complete platform surface, not a single chatbot
-smxPP includes the tooling required to run AI as a real system: content ingestion, page management, documentation, analytics surfaces, and premium gating.
-
-Licensing tied to integrity and trust
-The licensing design is built to ensure subscription status, premium entitlements, and platform behaviour remain aligned and auditable.
-
-Designed to deploy and operate, not just to demo
-smxPP is built for “keep it running” realities: changes, growth, governance, and operational continuity.
-
-Technical deployment compatibility
-
-smxPP is designed to be deployable in modern cloud-native patterns. Many organisations run it using managed deployment environments such as Google Cloud Platform services including Google Cloud Run, while retaining full control of environment variables, secrets management, storage persistence, and network boundary configuration. The architecture supports practical operational patterns such as persistent storage backing, instance configuration at deploy time, and clear separation between platform runtime and customer-owned content.
-
-Where organisations use domains purchased through registrars such as Namecheap, smxPP’s deployment model supports domain mapping and DNS configuration as part of a repeatable, documented rollout process.
-
-Closing positioning
-
-SyntaxMatrix builds for organisations that are serious about AI as an operational capability — not as a marketing demo. smxPP is engineered to provision governed, client-owned AI platforms that integrate into real environments with access control, auditable configuration, and a licensing model that supports both enterprise trust and commercial sustainability.
-
-If an organisation wants AI capabilities that can be deployed securely, operated reliably, and scaled with confidence — while keeping ownership of data and deployment — SyntaxMatrix and smxPP provide the platform and the engineering discipline to make that practical.
-"""
-
-
-SMXAI_HOME_PAGE_INSTRUCTIONS = f"""
+SMXAI_LANDING_PAGE_INSTRUCTIONS = f"""
 > IMPORTANT CONTEXT FOR THE GENERATOR
 
-- SyntaxMatrix is the company.
-- SyntaxMatrix Platform Provisioner (smxPP) is the product.
-- This is an enterprise homepage: it must build trust, communicate substance, and explain operational reality.
-- This page must NOT read like a startup landing page or a hype brochure.
-
----
-
 ## PLAN GENERATION CONTRACT (MANDATORY)
 
 When generating the page plan JSON:
@@ -793,13 +604,8 @@ The page must read like a full company profile
 
 
 SMXAI_SERVICES_PAGE_INSTRUCTIONS = """
-✅ SMXAI_SERVICES_PAGE_INSTRUCTIONS — FINAL (ENTERPRISE, IMAGE-SAFE
-IMPORTANT CONTEXT FOR THE GENERATOR
 
-SyntaxMatrix is the company.
-SyntaxMatrix Platform Provisioner (smxPP) is the product.
-This page describes what SyntaxMatrix delivers to organisations, not features in isolation.
-This is an enterprise services page, not a SaaS pricing teaser.
+IMPORTANT CONTEXT FOR THE GENERATOR
 
 🔒 PLAN GENERATION CONTRACT (MANDATORY)
 When generating the page plan JSON:
@@ -1154,100 +960,6 @@ Page must read like a consulting-grade services document
 """
 
 
-SMXAI_SERVICES_PAGE_INSTRUCTIONS_2 = """
-You are generating a SERVICES page for SyntaxMatrix.
-
-GOAL
-Create a clear, professional services page that explains:
-- what services SyntaxMatrix provides
-- how those services are delivered
-- who they are for
-- how a client engages or starts a conversation
-
-This page must read like an enterprise AI engineering firm, not a marketing brochure.
-
-ABSOLUTE REQUIREMENTS
-1) The plan MUST include a hero section (type: "hero") with:
-   - a concise headline describing what SyntaxMatrix delivers (AI systems, RAG frameworks, agentic platforms, etc.)
-   - a short subheading (1–2 sentences) explaining the value proposition
-   - a primary CTA such as "Request a consultation" or "Talk to us"
-
-2) The plan MUST include a core services section using type: "features".
-   This section must list 4–7 services.
-   Each service must be presented as a compact, scannable card with:
-   - clear service title
-   - short description (1–2 sentences max)
-   - what the client gets (outcome-focused, not buzzwords)
-
-3) The plan MUST include a "How we work" section using type: "richtext" or "features".
-   It should explain the engagement model in 4–6 steps:
-   - discovery / requirements
-   - system design
-   - implementation
-   - evaluation & testing
-   - deployment
-   - support / iteration (if applicable)
-
-4) The plan MUST include a "Who this is for" or "Use cases" section.
-   Use type: "features" or "richtext".
-   Examples:
-   - startups building AI products
-   - enterprises adopting internal AI tools
-   - educators / training providers
-   - research or applied AI teams
-
-5) The plan MUST include a final CTA section (type: "cta") with:
-   - a clear invitation to engage
-   - what to provide when contacting (brief description, goals, constraints)
-   - a placeholder contact method (email / form)
-
-CONTENT CONSTRAINTS
-- Do NOT claim one-size-fits-all solutions.
-- Do NOT invent client names, testimonials, or certifications.
-- Avoid exaggerated claims.
-- Keep descriptions concrete and grounded in engineering reality.
-- Avoid long paragraphs; use structured, skimmable copy.
-
-SERVICE CATEGORIES (use as guidance)
-The services section may include items such as:
-- AI system architecture & design
-- Retrieval-Augmented Generation (RAG) systems
-- Multi-agent workflows and orchestration
-- Custom AI framework development (SyntaxMatrix-based)
-- Evaluation, testing, and reliability tooling
-- Deployment, MLOps, and infrastructure support
-- Custom fine-tuning of open-source models (privacy-focused)
-
-SERVICE CARD TEMPLATE (features item)
-Each service should follow this shape:
-{
-  "id": "svc_1",
-  "type": "card",
-  "title": "RAG System Design & Implementation",
-  "text": "Design and build production-grade RAG pipelines with reliable retrieval, evaluation, and context control."
-}
-
-STYLE
-- Confident, technical, and professional.
-- Emphasise SyntaxMatrix as an AI algorithm design and framework company.
-- Assume a technically literate audience (CTOs, engineers, decision-makers).
-- Avoid hype; focus on capability and process.
-
-RECOMMENDED PAGE STRUCTURE
-1) hero
-2) features: Core services
-3) richtext/features: How we work
-4) features/richtext: Who this is for / Use cases
-5) cta
-
-OUTPUT QUALITY CHECK
-Before finalising, ensure:
-- Services are clearly enumerated.
-- Engagement process is explicit.
-- CTA is actionable and clear.
-"""
- 
-
 SMXAI_GALLERY_PAGE_INSTRUCTIONS = """
 You are generating a GALLERY page. This page must behave like a true photo/screenshot gallery.
 
@@ -1295,7 +1007,7 @@ TONE
 
 
 SMXAI_CAREERS_PAGE_INSTRUCTIONS = """
-You are generating a CAREERS page for SyntaxMatrix.
+You are generating a CAREERS page
 
 GOAL
 Create a careers landing page that:
@@ -1515,8 +1227,8 @@ def get_page_instructions(page_slug: str = "", page_title: str = "") -> str:
     key = f"{page_slug or ''} {page_title or ''}".strip().lower()
 
     # Home page
-    if any(w in key for w in ("home", "home-page", "homepage", "landing", "landing-page")):
-        return SMXAI_HOME_PAGE_INSTRUCTIONS
+    if any(w in key for w in ("landing", "landing-page", "home", "home-page", "homepage")):
+        return SMXAI_LANDING_PAGE_INSTRUCTIONS
 
     # About page
     if any(w in key for w in ("about", "about-us", "who-we-are", "company", "our-story", "team")):
@@ -1537,5 +1249,10 @@ def get_page_instructions(page_slug: str = "", page_title: str = "") -> str:
     if any(w in key for w in ("blog", "articles", "updates", "news", "release-notes")):
         return SMXAI_BLOG_PAGE_INSTRUCTIONS
 
+    # Licence page
+    if any(w in key for w in ("licence", "license", "licence-page", "licensing")):
+        return SMXAI_LICENCE_PAGE_INSTRUCTIONS
+    
+
     # Fallback
     return SMXAI_NEW_PAGE_INSTRUCTIONS_DEFAULT