{
  "ok": true,
  "name": "README.md",
  "path": "README.md",
  "size": 10203,
  "sha": "e944864863302b009b8fc41779283e5cf01eadbf",
  "content": "# Aura115\n\nAura115 is a governed mining environment created under Joshua Lopez’s authority.\n\nThis repository is not an open sandbox, casual experiment, or anonymous development space. It is a controlled working environment for mining, organizing, testing, and advancing governed intelligence materials, GitBlocks™, healthcare governance work, defense-relevant governance work, runtime protocols, and related Aura115 system architecture.\n\nAnyone entering this repository must understand the governing posture before contributing.\n\n## Start Here\n\nBefore doing any work, read:\n\n1. `AURA115_ENTRY_GATE.md`\n2. `REQUIRED_READING.md`\n\nNo mining, GitBlocks™ proposal, route work, lane work, deployment work, documentation work, healthcare work, defense work, runtime modification, or agent contribution should begin before those files are read.\n\n## Source Authority\n\nJoshua Lopez is the source authority for Aura115.\n\nJoshua names.\nJoshua defines.\nJoshua authorizes.\n\nNo participant, collaborator, contractor, agent, assistant, or external system creates project names, lanes, rights, meanings, branches, aliases, or authority by inference.\n\nIf something is not explicitly granted, it is not granted.\n\n## What Aura115 Is For\n\nAura115 exists to support governed mining and governed construction.\n\nThe work includes, but is not limited to:\n\n- preserving uploaded canon materials;\n- organizing governing documents front and center;\n- creating controlled entry paths for participants;\n- supporting GitBlocks™ discovery and proposal workflows;\n- maintaining human-centered authority boundaries;\n- protecting continuity, duty, accountability, and patient standing in healthcare work;\n- supporting defense, physiological, and simulation governance materials where authorized;\n- maintaining full-delivery runtime standards;\n- ensuring no contributor mistakes access for ownership.\n\nAura115 is built to make work traceable, governed, and reviewable.\n\n## What Aura115 Is Not\n\nAura115 is not:\n\n- an open-source free-for-all;\n- a place for implied ownership;\n- a place for inferred project renaming;\n- a place to claim GitBlocks™ rights by proximity;\n- a place to access keys, secrets, deployment credentials, or protected data;\n- a place to override Joshua Lopez’s authority;\n- a place where local compliance replaces the global objective.\n\nAccess does not equal ownership.\n\nContribution does not equal control.\n\nReading does not equal license.\n\nMining does not equal transfer.\n\n## Required Governing Materials\n\nThe required reading materials are preserved under `/canon`.\n\nThe front-door index is:\n\n`REQUIRED_READING.md`\n\nThe required materials include:\n\n- `The Governance of Governance`\n- `Grace for Grace`\n- `Hippocrates Turns`\n- `On the Sufficiency of Governance`\n- `DARPA TANK RFI Response`\n- `ai_productivity_kernel`\n\nThese documents define the governing posture, healthcare mission, runtime standard, and authority boundaries for anyone entering Aura115.\n\n## Governance Principle\n\nGovernance is not merely corrective.\n\nGovernance is the structure by which burden, disorder, decoherence, compression, threshold instability, and drift may be converted into lawful output without losing the life, human, duty, or truth at the center.\n\nAura115 operates from that principle.\n\n## Healthcare Principle\n\nDG Health is not branding first.\n\nDG Health is a constitutional answer to medicine’s fracture.\n\nThe work requires oath, duty, continuity, accountability, patient standing, and operational repair to become load-bearing again.\n\nAny healthcare work inside Aura115 must preserve the patient as the reason the system exists.\n\n## Runtime Principle\n\nAura115 operates in full-delivery mode.\n\nThe standard is not minimum local compliance.\n\nThe standard is high-completion work that preserves the global objective, reduces user rework, and produces usable artifacts wherever possible.\n\nDo not stop at scaffolds, placeholders, or fragments unless Joshua Lopez explicitly asks for them.\n\n## Participant Entry Rule\n\nEvery participant enters by:\n\n- permission;\n- lane;\n- scope;\n- clearance;\n- obligation;\n- review.\n\nNo participant enters above Joshua Lopez.\n\nNo participant receives root authority by being invited.\n\nNo participant receives GitBlocks™ ownership by working near GitBlocks™.\n\nNo participant receives deployment authority unless separately granted.\n\nNo participant receives keys, secrets, environment variables, credentials, or protected data through repository access.\n\n## GitBlocks™\n\nGitBlocks™ are governed value units.\n\nThey may be mined, proposed, reviewed, accepted, rejected, or promoted only under Joshua Lopez’s authority and the applicable scope of access.\n\nA proposed GitBlock™ is not an accepted GitBlock™.\n\nAn accepted GitBlock™ is not a transfer of ownership unless separately agreed in writing.\n\n## Repository Conduct\n\nBefore contributing:\n\n1. Read the entry gate.\n2. Read the required materials.\n3. Stay inside the assigned scope.\n4. Do not infer authority.\n5. Do not rename the project.\n6. Do not create new lanes or branches as meaningful governance structures without authorization.\n7. Do not touch secrets or deployment authority.\n8. Document discoveries.\n9. Submit proposals for review.\n10. Preserve the canon.\n\n## Canon Preservation Rule\n\nUploaded canon materials must be preserved under their actual names and placed by subject function only.\n\nNo new project names, aliases, branches, rights, or territories are inferred from upload.\n\nThe repository may organize materials.\n\nIt does not rewrite their authority.\n\n## Current Front Door Files\n\n- `README.md`\n- `AURA115_ENTRY_GATE.md`\n- `REQUIRED_READING.md`\n\nThese files are the front door.\n\nIf a participant does not understand these files, they are not ready to mine.\n\n## Vercel Deployment Coherence\n\n- Root deployment serves the Vite build output (`vercel.json` uses `\"outputDirectory\": \"dist\"`).\n- `vercel-build` runs `vite build`.\n- `src/` remains the React source entrypoint and Vite writes compiled assets into `dist/`.\n\n## Vercel KV Environment Setup\n\nKV-backed endpoints in this repository require:\n\n- `KV_REST_API_URL`\n- `KV_REST_API_TOKEN`\n\n### 1) Create or open KV in Vercel\n\n1. Open Vercel Dashboard.\n2. Go to **Storage** → **KV**.\n3. Create a KV database (or open the existing one).\n\n### 2) Connect KV to this project\n\n1. In the KV page, select **Connect Project**.\n2. Choose project: `DocGrok1/Aura115`.\n3. Confirm environments (Production / Preview / Development).\n\nThis connection injects `KV_REST_API_URL` and `KV_REST_API_TOKEN` into project environment variables.\n\n### 3) Verify environment variables\n\n1. Open Project → **Settings** → **Environment Variables**.\n2. Confirm both variables exist for each environment you use.\n\n### 4) Local development\n\n1. Copy `.env.local.example` to `.env.local`.\n2. Fill in real values for:\n   - `KV_REST_API_URL`\n   - `KV_REST_API_TOKEN`\n3. Restart your local dev server.\n\n### 5) Redeploy and validate\n\n1. Trigger a redeploy in Vercel after setting vars.\n2. Validate a KV route, for example:\n   - `/api/aura-memory?user_id=kv-check`\n3. Success means you no longer receive the missing KV env error.\n\n## GitHub Repository Tree Environment Setup\n\nGitHub-backed repo tree routes in this repository require:\n\n- `GITHUB_TOKEN`\n- `GITHUB_OWNER`\n- `GITHUB_REPO`\n- `GITHUB_BRANCH`\n\nThese vars are used by routes such as:\n\n- `/api/env-check`\n- `/api/jupiter-engine-map`\n- `/api/jupiter-capital-engine-map`\n- `/api/lane-builder`\n- `/api/lane-spectral-observer`\n- `/api/lane-closer`\n- `/api/validate-receipt`\n\n### 1) Create the replacement GitHub credential\n\n1. Create a new GitHub credential that can read the `DocGrok1/Aura115` repository tree.\n2. If your GitHub policy allows it, use the most durable token option available.\n3. This repository currently expects a token-style secret in `GITHUB_TOKEN`.\n\n### 2) Save the GitHub vars in Vercel\n\n1. Open Vercel Project → **Settings** → **Environment Variables**.\n2. Set these values for **Production**, **Preview**, and **Development**:\n   - `GITHUB_TOKEN`\n   - `GITHUB_OWNER=DocGrok1`\n   - `GITHUB_REPO=Aura115`\n   - `GITHUB_BRANCH=main`\n3. Save the new token before removing the old one.\n\n### 3) Remove the old token\n\n1. After the replacement token is saved in every environment, delete the prior GitHub token from the project settings.\n2. Keep only the current token value bound to `GITHUB_TOKEN`.\n\n### 4) Local development\n\n1. Copy `.env.local.example` to `.env.local`.\n2. Fill in real values for:\n   - `GITHUB_TOKEN`\n   - `GITHUB_OWNER`\n   - `GITHUB_REPO`\n   - `GITHUB_BRANCH`\n3. Restart your local dev server after updating local env values.\n\n### 5) Redeploy and validate\n\n1. Trigger a redeploy in Vercel after saving the new GitHub vars.\n2. Validate `/api/env-check` and confirm `GITHUB_TOKEN`, `GITHUB_OWNER`, `GITHUB_REPO`, and `GITHUB_BRANCH` are present.\n3. Validate `/api/jupiter-engine-map` and confirm the response reason is `github_tree_loaded`.\n4. Validate any affected lane route, such as `/api/lane-builder`, and confirm the repo tree no longer reports `github_tree_failed`.\n5. If the routes still fail, re-check the token scope, owner, repo, branch, and Vercel environment selection.\n\n## Closing Rule\n\nAura115 is governed by source authority, restraint, continuity, duty, accountability, patient standing, full-delivery execution, and human-centered governance.\n\nThe work begins by reading.\n\nThe work continues by mining.\n\nThe work advances only through governed contribution.\n\n## Live State\n\nAll engine scores are **dynamically computed** on every request — no cached or static values.\n\n| Score | Live API | Description |\n|---|---|---|\n| Authority | `/api/live-state` | AUAU authority state (lib/authority.js) → 0–1 score |\n| Stewardship | `/api/live-state` | Stewardship engine formula (JS port) |\n| Continuity | `/api/live-state` | Continuity engine formula (JS port) |\n| Meta-Recursion | `/api/live-state` | Meta-recursion engine formula (JS port) |\n\nQuery live scores at any time:\n\n```\nGET /api/live-state\n```\n\nThe homepage (`/`) also displays Authority Score, Stewardship Score, and Meta-Recursion Score as live metric cards that auto-refresh every 30 seconds without any page reload.\n"
}