Cleaned up the Variouss folder

Corpus/ISMS/AI Threat Modeling.md

@@ -1,6 +1,6 @@
 # Using AI for Threat Modeling
 
-[Create a threat analysis chatbot](../Various/Create%20a%20threat%20analysis%20chatbot.md)
+[Create a threat analysis chatbot](../Various/LLMs%20and%20Vibe%20Coding/Create%20a%20threat%20analysis%20chatbot.md)
 
 
 [PLOT4AI](https://plot4.ai) (Privacy Library Of Threats 4 Artificial Intelligence): A threat modeling library to help you build responsible AI

Corpus/ISMS/Metrics for Information Security.md

@@ -22,7 +22,7 @@ W. Krag Brotby and Gary Hinson (PRAGMATIC Security Metrics, 2013) state metrics
 - Independent: Measured dispassionately and objectively, based on verifiable evidence; and
 - Cost-effective: Generate more value than they cost to gather, analyze, present and use.
 
-![](../Various/PRAGMATIC_security_metrics_examples.xlsx)
+![](../Various/Privacy/PRAGMATIC_security_metrics_examples.xlsx)
 
 Standards and Frameworks:
 - [ISO 27004](../Standards/ISO27x/ISO%2027004.md)

Corpus/Information Security/Risks/Security Threat Modeling.md

@@ -5,7 +5,7 @@
 https://insights.sei.cmu.edu/blog/threat-modeling-12-available-methods/
 
 Related:
-	- [Create a threat analysis chatbot](../../Various/Create%20a%20threat%20analysis%20chatbot.md)
+	- [Create a threat analysis chatbot](../../Various/LLMs%20and%20Vibe%20Coding/Create%20a%20threat%20analysis%20chatbot.md)
 
 
 ![700](Threat%20scenario%20elements.jpeg)

Corpus/Information Security/Risks/Threats MoC.md

@@ -7,6 +7,6 @@
 [Threat Modeling](Security%20Threat%20Modeling.md)
 [Threat Catalogues](Threat%20Catalogues.md)
 	[SCF Threat Categories for Establishing a Threat Catalog](../../Standards/other/SCF%20Threat%20Categories%20for%20Establishing%20a%20Threat%20Catalog.md)
-[Privacy Threat Modeling](../../Various/Privacy%20Threat%20Modeling.md)
+[Privacy Threat Modeling](../../Various/Privacy/Privacy%20Threat%20Modeling.md)
 [Security Threat Modeling](Security%20Threat%20Modeling.md)
 

Corpus/Various/Application architecture.md

@@ -1,117 +0,0 @@
-
-# Application architecture – Deciding which functionality goes where
-
-Here’s a decision framework to help you choose the right approach for each piece of functionality:
-
-## WeWeb (Frontend Logic)
-
-**Use when:**
-
-- UI/UX logic and interactions
-- Client-side data formatting and presentation
-- Form validation (basic, user-facing)
-- Navigation and routing logic
-- Real-time UI updates from Supabase subscriptions
-- Simple calculations that don’t need to be secured
-
-**Examples:** Date formatting, sorting/filtering displays, form field validation, conditional UI rendering
-
-## SQL Functions + RPC
-
-**Use when:**
-
-- Complex data operations involving multiple tables
-- Business logic that must be consistent and secure
-- Performance-critical operations (closer to data)
-- Data validation that can’t be bypassed
-- Calculations that need to be atomic
-- Logic that might be reused across different clients
-
-**Examples:** User permission checks, complex reporting calculations, multi-step data updates, financial calculations
-
-## Edge Functions
-
-**Use when:**
-
-- External API integrations (payments, email, webhooks)
-- Heavy computational tasks
-- File processing and transformations
-- Custom authentication flows
-- Business logic that needs full programming language capabilities
-- Third-party service communications
-
-**Examples:** Stripe payment processing, PDF generation, image resizing, sending emails, complex AI/ML operations
-
-## Database Triggers
-
-**Use when:**
-
-- Automatic responses to data changes
-- Audit logging and history tracking
-- Data consistency enforcement
-- Background maintenance tasks
-- Cross-table updates that must happen atomically
-
-**Examples:** Updating timestamps, creating audit logs, maintaining calculated fields, sending notifications on data changes
-
-## Decision Matrix
-
-**Performance Priority:**
-
-- SQL Functions > Database Triggers > Edge Functions > WeWeb
-
-**Security Requirements:**
-
-- Database Triggers ≥ SQL Functions > Edge Functions > WeWeb
-
-**External Integration Needs:**
-
-- Edge Functions > WeWeb > SQL Functions > Database Triggers
-
-**Complexity of Logic:**
-
-- Edge Functions > SQL Functions > WeWeb > Database Triggers
-
-**Real-time Requirements:**
-
-- Database Triggers > SQL Functions > WeWeb > Edge Functions
-
-## Practical Examples
-
-**User Registration Flow:**
-
-- WeWeb: Form UI and basic validation
-- Edge Function: Email verification, external service calls
-- SQL Function: Create user profile with complex business rules
-- Database Trigger: Create related records, audit log
-
-**E-commerce Order Processing:**
-
-- WeWeb: Shopping cart UI, order summary
-- SQL Function: Inventory checks, price calculations
-- Database Trigger: Update inventory, create audit trail
-- Edge Function: Payment processing, order confirmation emails
-
-**Reporting Dashboard:**
-
-- WeWeb: Charts, filters, display logic
-- SQL Function: Complex data aggregations
-- Database Trigger: Update materialized views
-- Edge Function: Export to PDF, email reports
-
-## General Guidelines
-
-**Start with the data layer and work outward:**
-
-1. Database Triggers for automatic data consistency
-2. SQL Functions for secure business logic
-3. Edge Functions for external integrations
-4. WeWeb for user interface and experience
-
-**Security rule:** Never trust the client - critical business logic should be in SQL Functions or Edge Functions, not WeWeb.
-
-**Performance rule:** Keep data-heavy operations close to the database (SQL Functions/Triggers).
-
-**Maintainability rule:** Keep similar logic in the same layer when possible.
-
-The key is often using multiple approaches together rather than choosing just one - they complement each other in a well-architected application.​​​​​​​​​​​​​​​​

Corpus/Various/Building functionality in Supabase.md

@@ -1,67 +0,0 @@
----
-tags:
-  - iso27DIY
-  - dev
-  - SupaBase
----
-# Building functionality in Supabase
-Supabase offers several ways to build functionality beyond just SQL and Edge Functions. Here are the main approaches:
-
-## Core Functionality Building Methods
-
-**1. SQL Functions (Database Functions)**
-
-- Postgres has built-in support for SQL functions that live inside your database and can be used with the API 
-- Created directly in the database using SQL
-- Accessible via the Dashboard’s SQL editor
-
-**2. Edge Functions**
-
-- Deno-based serverless functions
-- Run on the edge for low latency
-- Good for custom business logic and integrations
-
-**3. Database Functions & RPC (Remote Procedure Calls)**
-
-- RPC in Supabase allows developers to invoke custom PostgreSQL functions directly from the client side, particularly useful for encapsulating complex operations 
-- RPC enables executing database functions directly, allowing batching of multiple operations into a single RPC call 
-- Called using the `.rpc()` method in client libraries
-
-## Additional Functionality Methods
-
-**4. Database Triggers**
-
-- PostgreSQL triggers that automatically execute functions when certain database events occur
-- Can be combined with SQL functions for automated workflows
-
-**5. Row Level Security (RLS) Policies**
-
-- Policy-based access control that acts as business logic
-- Enforces rules at the database level
-
-**6. Auto-generated REST APIs**
-
-- Automatic CRUD operations based on your database schema
-- No additional code needed for basic operations
-
-**7. Real-time Subscriptions**
-
-- Listen to database changes in real-time
-- Automatically generated based on your tables and RLS policies
-
-**8. GraphQL API**
-
-- Auto-generated GraphQL APIs  available alongside REST
-- Provides flexible querying capabilities
-
-**9. Webhooks**
-
-- Database webhooks that can trigger external services
-- Can be set up to respond to database events
-
-**10. PostgREST Extensions**
-
-- Custom PostgreSQL extensions that extend functionality
-- Can be installed to add specialized features
-
-The most common approaches for custom business logic are SQL functions (accessed via RPC), Edge Functions, and database triggers, with each serving different use cases depending on where you want the logic to run and how complex your requirements are.

Corpus/Various/Design Document for ISO 27001 Certification Support Online Service.md

@@ -1,203 +0,0 @@
----
-tags:
-  - project/iso27DIY
----
-As suggested by Perplexity AI on  June 23, 2025 on the following prompt:
-
-```markdown
-Below is a list of challenges for a small company to acquire ISO 27001 certification. Write a design document for an online service that will support this company on it's journey towards certification: 
-
-**Prioritize and Simplify Documentation** 
-- Focus on essential documents such as the Information Security Policy, Risk Treatment Plan, and Statement of Applicability. Use templates and streamline processes to reduce the documentation burden. 
-
-**Leverage External Expertise** 
-- Consider hiring an ISO 27001 consultant or using online tools and platforms designed for small businesses to guide you through the process and provide templates and checklists. 
-
-**Automate Where Possible** 
-- Use software solutions that automate risk assessments, documentation management, and compliance tracking. This can save time and reduce errors. 
-
-**Conduct Regular Self-Assessments** 
-- Schedule periodic reviews of your ISMS to ensure it remains effective and up to date. Treat these as mini-audits, checking against the standard’s requirements. 
-
-**Stay Informed and Trained**
-- Invest in self-training through online courses, webinars, and resources specific to ISO 27001. This will help you understand the standard and stay current with best practices.
-
-**Collaborate with Peers or Networks** 
-- Join professional networks or forums where you can share experiences, ask questions, and learn from others facing similar challenges. 
-
-**Use Open Source and Cost-Effective Tools**
-- Implement open-source or affordable security tools to manage risks and controls within your budget constraints
-```
-
-# Design Document: ISO 27001 Certification Support Online Service
-
-
-## 1. Overview
-
-This design document outlines an online service tailored for small companies aiming to achieve ISO 27001 certification. The service addresses common challenges such as documentation overload, lack of expertise, limited resources, and the need for ongoing compliance, as identified in the provided list. The solution emphasizes simplicity, automation, collaboration, and cost-effectiveness.
-
----
-
-## 2. Objectives
-
-- **Simplify and prioritize ISO 27001 documentation**
-- **Provide expert guidance and resources**
-- **Automate compliance and documentation workflows**
-- **Enable regular self-assessment and progress tracking**
-- **Offer training and knowledge resources**
-- **Foster peer collaboration**
-- **Integrate open-source and affordable security tools**
-
----
-
-## 3. Key Features
-
-### 3.1. Documentation Hub
-
-- **Template Library:**  
-  Pre-built, customizable templates for essential documents (e.g., Information Security Policy, Risk Treatment Plan, Statement of Applicability).
-- **Guided Documentation Wizard:**  
-  Step-by-step forms that guide users through filling out each document, with tooltips and examples.
-- **Version Control:**  
-  Track changes, revisions, and approvals for each document.
-
-### 3.2. Expert Guidance
-
-- **Consultant Marketplace:**  
-  Access to vetted ISO 27001 consultants for one-off advice or ongoing support.
-- **Automated Checklists:**  
-  Interactive checklists for each stage of the certification process.
-- **Knowledge Base:**  
-  Frequently asked questions, best practices, and troubleshooting guides.
-
-### 3.3. Automation Tools
-
-- **Risk Assessment Engine:**  
-  Automate risk identification, evaluation, and treatment planning, with pre-populated risk scenarios for small businesses.
-- **Compliance Tracker:**  
-  Dashboard for tracking progress against ISO 27001 controls and requirements.
-- **Automated Reminders:**  
-  Notifications for upcoming reviews, policy renewals, and self-assessments.
-
-### 3.4. Self-Assessment Module
-
-- **Mini-Audit Toolkit:**  
-  Self-assessment forms based on ISO 27001 requirements, with scoring and action item generation.
-- **Progress Reports:**  
-  Visual dashboards and downloadable reports to monitor readiness for certification.
-
-### 3.5. Training & Resources
-
-- **E-Learning Platform:**  
-  ISO 27001-specific courses, webinars, and microlearning modules for staff.
-- **Resource Library:**  
-  Curated articles, videos, and external links for ongoing learning.
-
-### 3.6. Collaboration & Community
-
-- **Peer Forum:**  
-  Secure discussion boards for sharing experiences, challenges, and solutions.
-- **Group Projects:**  
-  Enable teams to collaborate on documentation and risk assessments in real time.
-- **Mentorship Matching:**  
-  Pair users with experienced peers or mentors for guidance.
-
-### 3.7. Integration with Open Source and Cost-Effective Tools
-
-- **Tool Directory:**  
-  Curated list of recommended open-source and affordable security tools (e.g., password managers, vulnerability scanners).
-- **API Integrations:**  
-  Connect external tools for asset management, incident tracking, and more.
-
----
-
-## 4. User Roles
-
-- **Admin:**  
-  Full access to all features, user management, and settings.
-- **Team Member:**  
-  Access to assigned tasks, documentation, and training.
-- **Consultant/Advisor:**  
-  Limited access for reviewing documents and providing feedback.
-
----
-
-## 5. User Journey Example
-
-1. **Onboarding:**  
-   User answers a few questions about company size, industry, and current security maturity.
-2. **Documentation Setup:**  
-   User selects required documents from the template library and customizes them using the wizard.
-3. **Risk Assessment:**  
-   User completes an automated risk assessment, generating a risk treatment plan.
-4. **Self-Assessment:**  
-   User runs a mini-audit using the self-assessment toolkit and receives a readiness score.
-5. **Training:**  
-   Staff complete relevant e-learning modules.
-6. **Collaboration:**  
-   User joins the forum to ask questions and shares progress in a group project.
-7. **Expert Review:**  
-   User books a session with a consultant to review documentation.
-8. **Certification Prep:**  
-   User tracks progress with the compliance dashboard and prepares for the external audit.
-
----
-
-## 6. Technical Architecture
-
-- **Frontend:**  
-  Responsive web application (React or Angular)
-- **Backend:**  
-  RESTful API (Node.js/Python), secure document storage, user management
-- **Database:**  
-  PostgreSQL or MongoDB for user data, documents, and audit logs
-- **Integrations:**  
-  APIs for external tools and consultant scheduling
-- **Security:**  
-  End-to-end encryption, role-based access control, regular penetration testing
-
----
-
-## 7. Security & Compliance
-
-- **GDPR-compliant data handling**
-- **Encrypted storage for sensitive documents**
-- **Audit logs for all user actions**
-- **Regular vulnerability assessments**
-
----
-
-## 8. Cost & Licensing
-
-- **Freemium Model:**  
-  Basic features free for small teams; premium features (consultant marketplace, advanced automation) via subscription.
-- **Open-Source Integrations:**  
-  No additional cost for integrating community tools.
-
----
-
-## 9. Success Metrics
-
-- **Time to complete documentation**
-- **User satisfaction (NPS)**
-- **Number of companies achieving certification**
-- **Engagement in training and community features**
-
----
-
-## 10. Roadmap (First 12 Months)
-
-1. **MVP Launch:**  
-   Documentation hub, risk assessment engine, self-assessment module
-2. **Phase 2:**  
-   Training platform, community forum, consultant marketplace
-3. **Phase 3:**  
-   Advanced automation, open-source tool integrations, mentorship matching
-
----
-
-## 11. Conclusion
-
-This online service is designed to make ISO 27001 certification accessible, efficient, and affordable for small companies. By combining expert guidance, automation, collaboration, and cost-effective tools, it empowers organizations to achieve and maintain compliance with confidence.
-
-Sources

Corpus/Various/Elevator Pitch.md

@@ -1,14 +0,0 @@
-## Elevator pitch
-
-ISO27DIY is a method to implement information security management, and become ISO 27001 compliant, without the need for external consultants or expensive software. 
-The ISO27DIY workshop series is freely available on YouTube, dramatically lowering the barrier for certification for small and medium enterprises to become ISO 27001 certified. 
-Additional resources and support are available on the iso27diy.com website. 
-
-### Key value proposition
-
-* A method for implementing ISO 27001 in your own organization 
-* Workshop videos freely available on YouTube
-* No need for external consultants or expensive software
-
-
-See also [ISO27DIY benefits](../../AuditGlue/ISO27DIY%20benefits.md)

Corpus/Various/Example JSON file.md

@@ -1,18 +0,0 @@
-```
-{
-  "firstName": "Jane",
-  "lastName": "Doe",
-  "age": 30,
-  "isStudent": false,
-  "hobbies": ["reading", "hiking", "cooking"],
-  "address": {
-    "street": "123 Main St",
-    "city": "Anytown",
-    "zipCode": "90210"
-  },
-  "contactNumbers": [
-    {"type": "home", "number": "555-1234"},
-    {"type": "work", "number": "555-5678"}
-  ]
-}
-```

Corpus/Various/How Paperless.io attracted users.md

@@ -1,23 +0,0 @@
-Source: [Indie Hackers](https://www.indiehackers.com/post/on-building-growing-a-document-automation-saas-to-2k-mrr-8abc4b43d8?utm_campaign=post-8abc4b43d8&utm_medium=email&utm_source=ih-series-growth-acquisition)
-Interviewee: [Jacob Engels](https://www.linkedin.com/in/jacob-engels-1166b5146/)
-
-## How have you attracted users and grown Paperless?
-
-Our first channel was cold email outreach. We created a pretty incredible process of finding leads on LinkedIn, enriching data via a personal assistant and then personalizing outreach at scale. We had opening rates of up to 80%, reply rates of ~40-45% and this was just crazy. We also tested various industries and verticals to see where we could find the biggest traction.
-
-In more detail:
-
-We were using the LinkedIn Sales Navigator to build solid lists of interesting contacts. Trying different batches of leads (company size and industry) helped us come up with around 30 different target groups we were contacting.
-
-Through Phantombuster we were exporting those contacts into an Excel File. Our personal assistant later searched for the email addresses with different tools such as [Hunter.io](https://click.pstmrk.it/2m/Hunter.io/pxBB3ScN/g09c/b1wYDVrXAZ/LU1yOEJIQ0N4MjlMa2ZJUzBJYW0 "https://click.pstmrk.it/2m/Hunter.io/pxBB3ScN/g09c/b1wYDVrXAZ/LU1yOEJIQ0N4MjlMa2ZJUzBJYW0") Rocketreach, Leadleaper, Name2email, SalesQl, Signal Hire, Snovio and Clearbit.
-
-The final Leads + email addresses were exported to a sales automation tool named [Klenty.com](https://click.pstmrk.it/2m/Klenty.com/qBBB3ScN/g09c/oeoAOd4Ntu/LU1yOEJIQ0N4MjlMa2ZJUzBJYW0). WIth simple A/B/C Tests we were steadily finding out which headlines and what content prompts leads to answer our emails. Four simple rules helped us achieve those crazy high numbers:
-
-KISS - Keep it simple and stupid.  
-Nail the tone - Don’t smell like a salesman or marketeer  
-Simple yes/no CTA  
-Follow-Up x3
-
-Depending on the answer and considering the Self-SignUp was not yet ready we were pushing hard for a 30 min call to generate insights and create a need/urgency. In the call, it was all about asking the right questions, but that’s worth another story :)
-
-Initially, we let our early access users into our platform in exchange for feedback. Some of them converted to paid customers and we’re still heavily focused on interviewing and speaking with these early adopters to really nail our positioning, find product-market-fit and determine our best customers worth focusing on.

Corpus/Various/JSON validation for Postgres.md

@@ -1,237 +0,0 @@
----
-tags:
-  - json
-  - supabase
----
-# JSON Schema validation for Postgres
-
-When using the JSON (or JSONB) datatype, the data needs to be validated to assure database integrity.
-
-pg_jsonschema is a PostgreSQL extension for SupaBase that can validate `json` and `jsonb` data types against a JSON Schema. The extension offers two functions:
-
-
-```java
--- Validates a json *instance* against a JSON Schema *schema*
-json_matches_schema(schema json, instance json) returns bool
-
--- Validates a jsonb *instance* against a JSON Schema *schema*
-jsonb_matches_schema(schema json, instance jsonb) returns bool
-```
-
-JSON Schema is a way to define what valid JSON should look like for a particular use case:
-
-- What properties an object should have
-- What data types are expected
-- Which fields are required vs optional
-- Validation constraints (like minimum/maximum values, string patterns, etc.)
-- Default values and descriptions
-
-A JSON Schema is itself a JSON document. Here's a simple example of a JSON schema:
-
-```json
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "type": "object",
-  "properties": {
-    "name": {
-      "type": "string",
-      "description": "Person's full name"
-    },
-    "age": {
-      "type": "integer",
-      "minimum": 0,
-      "maximum": 150
-    },
-    "email": {
-      "type": "string",
-      "format": "email"
-    }
-  },
-  "required": ["name", "email"]
-}
-```
-
-You can check input against a schema in SQL like this: 
-
-```sql
-create table some_table(
-id serial primary key, -- db-column `id` column is an auto-incrementing primary key
-metadata json not null, -- db-column `metadata` must contain a JSON value and cannot be null
-check ( -- table-level check constraint to match the JSON in `metadata` to the schema
-	json_matches_schema(
-		schema :='{
-			"type": "object", -- we require an object ...
-			"properties": {
-				"foo": { -- with a single string property `"foo"` ...
-				"type": "string"
-			}
-		},
-		"required": ["foo"], -- property `"foo"` is required ...
-		"additionalProperties": false -- and no additional properties are allowed
-	}',
-	instance := metadata -- the value of the `metadata` column is passed ...
-											-- as the `instance` argument to the `json_matches_schema` function, for each row 
-)
-)
-);
-
-
--- Now we can attempt to insert a row into `some_table`,
--- with the `metadata` value provided as `<SQL input>`
-
-insert into some_table(metadata)
-values
-	(<SQL input>);
-
--- <SQL input> needs to be replaced with an actual JSON value, e.g. '{"foo": "bar"}'.
--- The insert will only succeed if the contents of `metadata` matches the schema in the check constraint.
-```
-
-## Validating for a set of allowed values
-
-Use the `enum` keyword to validate that a value must be one of a specific set of allowed values.
-
-**String values:**
-
-```json
-{
-  "type": "string",
-  "enum": ["red", "green", "blue"]
-}
-```
-
-**Mixed data types:**
-
-```json
-{
-  "enum": ["active", "inactive", null, 42]
-}
-```
-
-**In an object property:**
-
-```json
-{
-  "type": "object",
-  "properties": {
-    "status": {
-      "type": "string",
-      "enum": ["pending", "approved", "rejected"]
-    },
-    "priority": {
-      "type": "integer",
-      "enum": [1, 2, 3, 4, 5]
-    }
-  }
-}
-```
-
-
-## Validating for a data range
-
-**Inclusive bounds (default):**
-
-```json
-{
-  "type": "integer",
-  "minimum": 1,
-  "maximum": 10
-}
-```
-
-This allows values from 1 to 10, including 1 and 10.
-
-**Exclusive bounds:**
-
-```json
-{
-  "type": "number",
-  "exclusiveMinimum": 0,
-  "exclusiveMaximum": 100
-}
-```
-
-This allows values greater than 0 and less than 100, but not 0 or 100 themselves.
-
-**Mixed Bounds:**
-
-```json
-{
-  "type": "number",
-  "minimum": 0,
-  "exclusiveMaximum": 1
-}
-```
-
-This allows values from 0 (inclusive) to 1 (exclusive), so 0 ≤ value < 1.
-
-**One-Sided Ranges:**
-
-```json
-{
-  "type": "integer",
-  "minimum": 18
-}
-```
-
-```json
-{
-  "type": "number",
-  "maximum": 3.14159
-}
-```
-
- 
-**In Object Properties:**
-
-```json
-{
-  "type": "object",
-  "properties": {
-    "age": {
-      "type": "integer",
-      "minimum": 0,
-      "maximum": 150
-    },
-    "temperature": {
-      "type": "number",
-      "minimum": -273.15,
-      "maximum": 1000.0
-    }
-  }
-}
-```
-
- 
- **Regex Validation:**
-
-```json
-{
-  "type": "string",
-  "pattern": "^[a-zA-Z0-9]+$"
-}
-```
-
-**Date Validation:**
-
-JSON Schema supports the ISO 8601 date format:
-
-```json
-{
-  "type": "string",
-  "format": "date"
-}
-```
-
-`"date"` validates dates like: `2023-12-25`
-`"date-time"` validates like: `2023-12-25T10:30:00Z` or `2023-12-25T10:30:00.123Z`
-`"time"` validates like: `10:30:00` or `10:30:00.123`
-
-Using the ISO 8601 date format is recommended for interoperability.
-Custom date patterns can be validated with Regex.
-
-Ranges can be validated using the `"minimum"` and `"maximum"` keywords like before.
-
-## Documentation**
-- [pg_jsonschema](https://github.com/supabase/pg_jsonschema)
-- [JSON Schema](https://json-schema.org/)

Corpus/Various/LLMs and Vibe Coding/Create a proactive conversational agent.md

@@ -74,8 +74,8 @@ Prompt: `elaborate on designing the slot configuration schema`
 Here's a detailed approach to designing a flexible slot configuration schema that can handle various conversation types and business requirements:
 
 ## Slot Configuration Database Schema
-![](../../AuditGlue/System%20alternative/slot_config_schema.sql)
-![](../../AuditGlue/System%20alternative/slot_config_erd.mermaid)
+![](../../../AuditGlue/System%20alternative/slot_config_schema.sql)
+![](../../../AuditGlue/System%20alternative/slot_config_erd.mermaid)
 
 This ERD shows the complete database schema for the conversational agent's slot configuration system. Here's a breakdown of the key relationships and design decisions:
 
@@ -98,7 +98,7 @@ This ERD shows the complete database schema for the conversational agent's slot
 **slot_collection_attempts** provides detailed audit trail of user interactions for analytics and debugging
 
 Let me show you a Python implementation that demonstrates how to work with this schema:
-![](../../AuditGlue/System%20alternative/slot_manager_implementation.py)
+![](../../../AuditGlue/System%20alternative/slot_manager_implementation.py)
 
 ### Key Design Features
 

Corpus/Various/Privacy/Privacy Threat Modeling.md

@@ -1,6 +1,6 @@
 MITRE PANOPTIC Privacy Threat Model
 - https://ptmworkshop.gitlab.io/#/panoptic
 - https://ptmworkshop.gitlab.io/static/media/PANOPTIC-MTR.517c2bf5fd91f93354aa.pdf
-![PANOPTIC.xlsx](PANOPTIC_version_1.b6b9783933c97d02395e.xlsx)
+![PANOPTIC.xlsx](PANOPTIC%20Privacy%20Threat%20Model%20sheet.xlsx)
 
-![](PANOPTIC-MTR.517c2bf5fd91f93354aa.pdf)
+![](PANOPTIC%20Privacy%20Threat%20Model.pdf)

Corpus/Various/The Psychology Behind SaaS Pricing.md

@@ -1,37 +0,0 @@
----
-title: "The Psychology Behind SaaS Pricing That Most Founders Completely Miss"
-source: "https://www.reddit.com/r/SaaS/comments/1lh0e56/the_psychology_behind_saas_pricing_that_most/?share_id=CYg0pG3jXWObUQLzVP5od&utm_content=2&utm_medium=ios_app&utm_name=iossmf&utm_source=share&utm_term=22"
-author:
-  - "[[Sea_Reputation_906]]"
-published: 2025-06-21
-created: 2025-06-23
-description:
-tags:
-  - "clippings"
----
-
-**The anchoring effect: show your expensive plan first**
-
-When you show your expensive plan first, it makes everything else seem like a bargain. Had a client who was struggling with conversions until we reordered their pricing page to show the premium plan first. Suddenly their middle tier started selling like crazy. People saw the $199/mo plan and thought "well $79 is a steal compared to that!"
-
-**Freemium gets you freeloaders**
-
-One client had 10,000+ free users but only like 12 paying customers. Their free plan was way too generous. Another client ditched freemium entirely, switched to a 14-day trial and hit $25K MRR in under 6 months. The difference? People actually had to make a decision instead of sitting in free-user purgatory forever.
-
-**The $9.99 thing actually works**
-
-Harvard Business School found that a 1% improvement in pricing can lead to an 11% increase in profit. We've tested this with multiple clients and charm pricing consistently outperforms round numbers.
-
-**Simpler is always better**
-
-If your pricing page needs an FAQ section to explain it, you've already lost. Most users won't email to ask questions about your pricing, they'll just bounce. Keep it stupid simple: 2-3 plans max, clear names, bullet points.
-
-**Higher prices can increase demand (seriously)**
-
-When you hide your top-tier pricing behind a "contact us" button, it creates weird FOMO for big customers. They imagine they're missing out on some special features. Enterprise leads literally tripled for one client after making this change.
-
-I see so many founders pricing based on competitors or their costs instead of psychology. The data is clear tho - understanding how people perceive pricing matters way more than your actual costs.
-
-What pricing experiments have you guys tried? Anything that surprised you?
-
-(P.S. If you need help building your MVP, DM me. Been getting a ton of requests lately, happy to chat.)