Merge all open pull requests into main

.github/DISCUSSION_TEMPLATE/general.yml

@@ -0,0 +1,15 @@
+title: "[General] "
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this space for general discussions about simulation theory, the repository, or anything else you'd like to share with the community.
+  - type: textarea
+    id: discussion
+    attributes:
+      label: What would you like to discuss?
+      description: Share your thoughts, questions, or ideas with the community.
+      placeholder: Start your discussion here...
+    validations:
+      required: true

.github/DISCUSSION_TEMPLATE/ideas.yml

@@ -0,0 +1,23 @@
+title: "[Idea] "
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Share an idea for improving the repository, adding new content, or exploring new aspects of simulation theory.
+  - type: textarea
+    id: idea
+    attributes:
+      label: Idea Description
+      description: Describe your idea in detail.
+      placeholder: My idea is...
+    validations:
+      required: true
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Why do you think this would be valuable? What problem does it solve or what opportunity does it open?
+      placeholder: This would be valuable because...
+    validations:
+      required: false

.github/DISCUSSION_TEMPLATE/q-and-a.yml

@@ -0,0 +1,23 @@
+title: "[Q&A] "
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Ask a question about simulation theory, the content in this repository, or anything related you'd like help understanding.
+  - type: textarea
+    id: question
+    attributes:
+      label: Question
+      description: What would you like to know?
+      placeholder: Ask your question here...
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Provide any additional context or background information that may help answer your question.
+      placeholder: Any relevant context, references, or prior research...
+    validations:
+      required: false

.github/DISCUSSION_TEMPLATE/show-and-tell.yml

@@ -0,0 +1,23 @@
+title: "[Show and Tell] "
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Share something you've built, discovered, or created related to simulation theory. Show the community your work!
+  - type: textarea
+    id: showcase
+    attributes:
+      label: What are you sharing?
+      description: Describe what you'd like to show the community.
+      placeholder: I'd like to share...
+    validations:
+      required: true
+  - type: textarea
+    id: links
+    attributes:
+      label: Links & Resources
+      description: Add any relevant links, demos, papers, or resources.
+      placeholder: https://...
+    validations:
+      required: false

.github/copilot-instructions.md

@@ -0,0 +1,48 @@
+# Copilot Instructions for simulation-theory
+
+## Repository Purpose
+
+This repository contains the mathematical and philosophical framework known as "The Trivial Zero" — a computational proof that reality is self-referential, authored by Alexa Louise Amundson (BlackRoad OS Inc.).
+
+## Repository Structure
+
+- `README.md` — The primary paper (~750 KB): "The Trivial Zero: A Computational Proof That Reality Is Self-Referential"
+- `EXPANSION.md` — Extended sections of the paper
+- `INDEX.md` — 81-item index of observations and connections
+- `equations/` — Mathematical equations organized by category
+- `proofs/` — Formal mathematical arguments for key claims
+- `figures/` — Visual representations and reference tables
+- `notebooks/` — Computational notebooks and scripts
+- `qwerty/` — QWERTY encoding constants and equalities
+- `SHA256.md` — File integrity and commit history verification
+- `REAL.md` — Core axiom
+
+## Key Concepts
+
+- **Ternary computing** — Base-3 logic (balanced ternary: {−1, 0, +1}) is central to the theoretical framework
+- **QWERTY encoding** — Each word is encoded as the sum of key positions on a QWERTY keyboard; these sums reveal self-referential patterns
+- **Simulation theory** — The repository documents a framework in which reality is described as a self-referential computational system
+- **Self-reference** — Gödel, fixed points, Y-combinators, and the Born rule are treated as evidence of computational self-reference
+
+## Contribution Guidelines
+
+When adding or modifying content:
+
+1. **Mathematical equations** belong in `equations/` and should follow the format in existing files (equation block, plain-English description, QWERTY encoding if relevant)
+2. **Formal proofs** belong in `proofs/` and should reference the relevant paper section (§ number)
+3. **Python or computational code** belongs in `notebooks/`
+4. **New observations or connections** should be integrated into the main `README.md` or `EXPANSION.md` at the appropriate section (§ number)
+5. **Figures and tables** belong in `figures/`
+
+## Formatting Conventions
+
+- Equations use plain-text math notation with Unicode symbols (ℏ, Σ, ∫, ∂, etc.)
+- Section references use §NNN format
+- QWERTY values are noted as `WORD = value [optional: = SYNONYM]`
+- Code blocks use triple backticks
+
+## Important Notes
+
+- Issue #5 ("DO NOT EDIT") — some content is marked read-only; respect this designation
+- The paper is the primary artifact; all other files are supporting documentation
+- Issues in this repository often contain new content (equations, observations, code) to be incorporated into the framework

.github/workflows/deploy.yml

@@ -3,6 +3,8 @@ name: Deploy to GitHub Pages
 on:
   push:
     branches: [main]
+  pull_request:
+    branches: [main]
   workflow_dispatch:
 
 permissions:
@@ -25,13 +27,16 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Setup Pages
+        if: github.event_name != 'pull_request'
         uses: actions/configure-pages@v4
 
       - name: Upload artifact
+        if: github.event_name != 'pull_request'
         uses: actions/upload-pages-artifact@v3
         with:
           path: .
 
       - name: Deploy to GitHub Pages
+        if: github.event_name != 'pull_request'
         id: deployment
         uses: actions/deploy-pages@v4

.github/workflows/issue-agent.yml

@@ -0,0 +1,112 @@
+name: Issue Agent
+
+on:
+  issues:
+    types: [opened, edited, reopened, labeled]
+
+permissions:
+  issues: write
+
+jobs:
+  analyze-issue:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Analyze issue and post comment
+        uses: actions/github-script@v7
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const issueNumber = context.issue.number;
+            const issueTitle = context.payload.issue.title;
+            const issueBody  = context.payload.issue.body || '(no description provided)';
+            const issueUser  = context.payload.issue.user.login;
+            const labels     = (context.payload.issue.labels || []).map(l => l.name).join(', ') || 'none';
+
+            // Call GitHub Models API for AI-powered analysis
+            const response = await fetch('https://models.inference.ai.azure.com/chat/completions', {
+              method: 'POST',
+              headers: {
+                'Content-Type': 'application/json',
+                'Authorization': `Bearer ${process.env.GITHUB_TOKEN}`
+              },
+              body: JSON.stringify({
+                model: 'gpt-4o-mini',
+                messages: [
+                  {
+                    role: 'system',
+                    content: `You are a rigorous technical agent reviewing GitHub issues for the "simulation-theory" repository — a research project on simulation theory, mathematics, quantum mechanics, and philosophy. Your job is to carefully read each issue and provide a thorough, structured analysis.
+
+For each issue produce:
+1. **Summary** — a concise one-paragraph summary of what the issue is about.
+2. **Key Points** — bullet list of the most important observations or questions raised.
+3. **Relevance to Simulation Theory** — how this issue connects to the project's themes.
+4. **Suggested Actions** — concrete next steps or questions for the author.
+
+Be rigorous, thoughtful, and constructive. Keep the tone academic and helpful.`
+                  },
+                  {
+                    role: 'user',
+                    content: `Please analyze this GitHub issue:\n\n**Title:** ${issueTitle}\n**Author:** ${issueUser}\n**Labels:** ${labels}\n\n**Description:**\n${issueBody}`
+                  }
+                ],
+                max_tokens: 1500,
+                temperature: 0.4
+              })
+            });
+
+            let analysisText;
+            if (response.ok) {
+              let data;
+              try {
+                data = await response.json();
+              } catch (error) {
+                console.log('Failed to parse JSON from GitHub Models API response:', error);
+              }
+
+              if (data && data.choices && data.choices.length > 0 && data.choices[0].message) {
+                analysisText = data.choices[0].message.content;
+              } else if (data) {
+                console.log('Unexpected response structure from GitHub Models API:', JSON.stringify(data));
+              }
+            } else {
+              console.log(`GitHub Models API returned ${response.status}: ${await response.text()}`);
+            }
+
+            // Fallback: structured analysis without AI
+            if (!analysisText) {
+              analysisText = `**Summary**\nIssue #${issueNumber} titled *"${issueTitle}"* was submitted by @${issueUser}. ${issueBody.length > 0 ? 'It contains a description that may include images or text.' : 'No description was provided.'}\n\n**Labels:** ${labels}\n\n**Suggested Actions**\n- Review the content of this issue and add appropriate labels if missing.\n- Respond to the author with any clarifying questions.\n- Link related issues or pull requests if applicable.`;
+            }
+
+            const marker = '*This comment was generated automatically by the Issue Agent workflow.*';
+            const commentBody = `## 🤖 Agent Analysis\n\n${analysisText}\n\n---\n${marker}`;
+
+            // Look for an existing Issue Agent comment and update it if found to avoid spamming
+            const { data: existingComments } = await github.rest.issues.listComments({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: issueNumber,
+              per_page: 100
+            });
+
+            const existingAgentComment = existingComments.find(c =>
+              c.user &&
+              c.user.type === 'Bot' &&
+              typeof c.body === 'string' &&
+              c.body.includes(marker)
+            );
+
+            if (existingAgentComment) {
+              await github.rest.issues.updateComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                comment_id: existingAgentComment.id,
+                body: commentBody
+              });
+            } else {
+              await github.rest.issues.createComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: issueNumber,
+                body: commentBody
+              });
+            }