Skip to content

Add root README with project orientation - #63

Merged
POWERFULMOVES merged 1 commit into
mainfrom
codex/create-and-populate-readme.md
Sep 23, 2025
Merged

POWERFULMOVES merged 1 commit into
mainfrom
codex/create-and-populate-readme.md

Conversation

@POWERFULMOVES

@POWERFULMOVES POWERFULMOVES commented Sep 23, 2025

Copy link
Copy Markdown
Owner

Summary

  • add a repository-level README describing the PMOVES.AI orchestration mesh and major goals
  • highlight the CATACLYSM_STUDIOS_INC, docs, and pmoves directories so newcomers can navigate quickly
  • link to critical pmoves documentation for quickstarts, runbooks, and orchestration guidance

Testing

  • not run

https://chatgpt.com/codex/tasks/task_b_68d0a8f4407483248d67116f075bcbda

Summary by CodeRabbit

  • Documentation
    • Introduced a comprehensive repository overview outlining architecture and key directories.
    • Added clear getting-started and quickstart bootstrap instructions to streamline onboarding.
    • Included links to essential docs and references to orchestration flows for easier navigation.
    • Provided guidance on regenerating a directory tour script to keep project insights current.
    • No changes to public APIs; end users benefit from improved clarity and setup guidance.

@coderabbitai

coderabbitai Bot commented Sep 23, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Adds a comprehensive README.md describing repository overview, architecture, key directories, documentation links, quickstart/bootstrap steps, orchestration flow references, and instructions to regenerate a directory tour script. No source code or public API changes.

Changes

Cohort / File(s) Summary
Documentation
README.md
New/expanded repository README with architecture overview, directory map, docs links, quickstart steps, orchestration references, and directory tour script regeneration guidance. No code or API changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled on docs with whiskers bright,
Typed out a README deep into night.
Paths and scripts in tidy rows,
A burrow of guides the project now shows.
Thump-thump! says the repo—clear and spry,
Carrots for clarity, PMOVES.AI!


📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Free

📥 Commits

Reviewing files that changed from the base of the PR and between 02a24f6 and b7b6ccb.

📒 Files selected for processing (1)
  • README.md (1 hunks)

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

Comment @coderabbitai help to get the list of available commands and usage tips.

@POWERFULMOVES
POWERFULMOVES merged commit 3bc94aa into main Sep 23, 2025
0 of 3 checks passed
POWERFULMOVES added a commit that referenced this pull request Jan 18, 2026
…eadme.md

Add root README with project orientation
POWERFULMOVES pushed a commit that referenced this pull request Feb 8, 2026
…ture

Add complete documentation and tooling for PMOVES.AI distributed
multi-architecture deployment with proper Supabase integration.

## Supabase Integration Documentation

- PMOVES_SUPABASE_SETUP_GUIDE.md - Variable mapping and configuration guide
- SUPABASE_UNIFIED_SETUP.md - Complete unified setup guide with migration steps
- PMOVES_SUPABASE_CURRENT_STATE_ANALYSIS.md - Current state and gap analysis
- PMOVES_SUPABASE_COMPREHENSIVE_EXPLORATION.md - PMOVES-supabase fork exploration
- PMOVES_SUPABASE_PRODUCTION_PATTERNS.md - Enterprise patterns and best practices
- SUPABASE_DISTRIBUTED.md - Distributed Supabase with dual-write sync

## Variable Name Standardization

Documented critical mismatch between pmoves/docker-compose.yml (custom
SUPABASE_* prefixes) and PMOVES-supabase fork (standard Supabase names).
Migration path defined to standardize variable names.

## Production Utilities

- scripts/supabase/generate-keys.sh - Generate all production secrets
- scripts/supabase/db-passwd.sh - Rotate database passwords safely

## Distributed Architecture

- ARCHITECTURE_DISTRIBUTED.md - Multi-arch distributed platform design
- scripts/deploy/detect-platform.sh - Platform, arch, GPU detection
- scripts/deploy/deploy.sh - Multi-platform deployment orchestration

## Production Validation

- PRODUCTION_READINESS_REPORT_2026-02-07.md - Security and config findings
- PRODUCTION_VALIDATION_CHECKLIST.md - Step-by-step bring-up guide
- PRODUCTION_BRING_UP_REPORT_2026-02-07.md - Phase 1 progress and issues
- ENV_TIER_AUDIT_2026-02-07.md - Tier environment file audit

## Configuration Files

- env.supabase - Standard Supabase environment variables template

## Platform Support

- Linux (x86_64, ARM64)
- WSL2 (Windows)
- NVIDIA Jetson Orin Nano (ARM64 + CUDA)
- Windows (Docker Desktop)

## Deployment Modes

- Edge: Jetson devices with standalone Supabase
- Lab: AI Lab with integrated Supabase
- VPS: Central cloud with PMOVES Supabase
- Dev: Full stack development

Related: Task #71 (Implement unified Supabase configuration)
Related: Task #63 (Execute phased production bring-up)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
POWERFULMOVES pushed a commit that referenced this pull request Feb 8, 2026
Fix Supabase service startup failures by aligning environment variable
names with PMOVES-supabase fork standard naming conventions.

## Variable Name Standardization

Updated docker-compose.yml to use standard Supabase variable names
with fallbacks to old names for backward compatibility:

- JWT_SECRET (was SUPABASE_JWT_SECRET)
- JWT_EXPIRY (was SUPABASE_JWT_EXP)
- ANON_KEY (was SUPABASE_PUBLISHABLE_KEY)
- SERVICE_ROLE_KEY (was SUPABASE_SECRET_KEY)
- SITE_URL (was SUPABASE_SITE_URL)
- API_EXTERNAL_URL (was SUPABASE_PUBLIC_URL)

## Changes to docker-compose.yml

supabase-gotrue:
  - GOTRUE_JWT_SECRET=${JWT_SECRET:-${SUPABASE_JWT_SECRET:-...}}
  - GOTRUE_JWT_EXP=${JWT_EXPIRY:-${SUPABASE_JWT_EXP:-...}}
  - GOTRUE_JWT_ADMIN_SECRET=${SERVICE_ROLE_KEY:-${SUPABASE_SECRET_KEY}}

supabase-postgrest:
  - PGRST_JWT_SECRET=${JWT_SECRET:-${SUPABASE_JWT_SECRET}}

supabase-realtime:
  - JWT_SECRET=${JWT_SECRET:-${SUPABASE_JWT_SECRET}}

supabase-storage:
  - ANON_KEY=${ANON_KEY:-${SUPABASE_PUBLISHABLE_KEY}}
  - SERVICE_KEY=${SERVICE_ROLE_KEY:-${SUPABASE_SECRET_KEY}}
  - PGRST_JWT_SECRET=${JWT_SECRET:-${SUPABASE_JWT_SECRET}}

supabase-studio:
  - SUPABASE_ANON_KEY=${ANON_KEY:-${SUPABASE_PUBLISHABLE_KEY}}

## Changes to env.shared

Added standard Supabase variables aligned with PMOVES-supabase fork:
- JWT_SECRET
- JWT_EXPIRY
- ANON_KEY
- SERVICE_ROLE_KEY
- SITE_URL
- API_EXTERNAL_URL

## Related Documentation

- pmoves/docs/SUPABASE_UNIFIED_SETUP.md
- pmoves/docs/PMOVES_SUPABASE_SETUP_GUIDE.md
- pmoves/docs/PMOVES_SUPABASE_CURRENT_STATE_ANALYSIS.md

Fixes services failing to start due to empty/undefined JWT variables.

Related: Task #71 (Implement unified Supabase configuration)
Related: Task #63 (Execute phased production bring-up)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
POWERFULMOVES pushed a commit that referenced this pull request Feb 8, 2026
…ture

Add complete documentation and tooling for PMOVES.AI distributed
multi-architecture deployment with proper Supabase integration.

## Supabase Integration Documentation

- PMOVES_SUPABASE_SETUP_GUIDE.md - Variable mapping and configuration guide
- SUPABASE_UNIFIED_SETUP.md - Complete unified setup guide with migration steps
- PMOVES_SUPABASE_CURRENT_STATE_ANALYSIS.md - Current state and gap analysis
- PMOVES_SUPABASE_COMPREHENSIVE_EXPLORATION.md - PMOVES-supabase fork exploration
- PMOVES_SUPABASE_PRODUCTION_PATTERNS.md - Enterprise patterns and best practices
- SUPABASE_DISTRIBUTED.md - Distributed Supabase with dual-write sync

## Variable Name Standardization

Documented critical mismatch between pmoves/docker-compose.yml (custom
SUPABASE_* prefixes) and PMOVES-supabase fork (standard Supabase names).
Migration path defined to standardize variable names.

## Production Utilities

- scripts/supabase/generate-keys.sh - Generate all production secrets
- scripts/supabase/db-passwd.sh - Rotate database passwords safely

## Distributed Architecture

- ARCHITECTURE_DISTRIBUTED.md - Multi-arch distributed platform design
- scripts/deploy/detect-platform.sh - Platform, arch, GPU detection
- scripts/deploy/deploy.sh - Multi-platform deployment orchestration

## Production Validation

- PRODUCTION_READINESS_REPORT_2026-02-07.md - Security and config findings
- PRODUCTION_VALIDATION_CHECKLIST.md - Step-by-step bring-up guide
- PRODUCTION_BRING_UP_REPORT_2026-02-07.md - Phase 1 progress and issues
- ENV_TIER_AUDIT_2026-02-07.md - Tier environment file audit

## Configuration Files

- env.supabase - Standard Supabase environment variables template

## Platform Support

- Linux (x86_64, ARM64)
- WSL2 (Windows)
- NVIDIA Jetson Orin Nano (ARM64 + CUDA)
- Windows (Docker Desktop)

## Deployment Modes

- Edge: Jetson devices with standalone Supabase
- Lab: AI Lab with integrated Supabase
- VPS: Central cloud with PMOVES Supabase
- Dev: Full stack development

Related: Task #71 (Implement unified Supabase configuration)
Related: Task #63 (Execute phased production bring-up)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
POWERFULMOVES pushed a commit that referenced this pull request Feb 8, 2026
Fix Supabase service startup failures by aligning environment variable
names with PMOVES-supabase fork standard naming conventions.

## Variable Name Standardization

Updated docker-compose.yml to use standard Supabase variable names
with fallbacks to old names for backward compatibility:

- JWT_SECRET (was SUPABASE_JWT_SECRET)
- JWT_EXPIRY (was SUPABASE_JWT_EXP)
- ANON_KEY (was SUPABASE_PUBLISHABLE_KEY)
- SERVICE_ROLE_KEY (was SUPABASE_SECRET_KEY)
- SITE_URL (was SUPABASE_SITE_URL)
- API_EXTERNAL_URL (was SUPABASE_PUBLIC_URL)

## Changes to docker-compose.yml

supabase-gotrue:
  - GOTRUE_JWT_SECRET=${JWT_SECRET:-${SUPABASE_JWT_SECRET:-...}}
  - GOTRUE_JWT_EXP=${JWT_EXPIRY:-${SUPABASE_JWT_EXP:-...}}
  - GOTRUE_JWT_ADMIN_SECRET=${SERVICE_ROLE_KEY:-${SUPABASE_SECRET_KEY}}

supabase-postgrest:
  - PGRST_JWT_SECRET=${JWT_SECRET:-${SUPABASE_JWT_SECRET}}

supabase-realtime:
  - JWT_SECRET=${JWT_SECRET:-${SUPABASE_JWT_SECRET}}

supabase-storage:
  - ANON_KEY=${ANON_KEY:-${SUPABASE_PUBLISHABLE_KEY}}
  - SERVICE_KEY=${SERVICE_ROLE_KEY:-${SUPABASE_SECRET_KEY}}
  - PGRST_JWT_SECRET=${JWT_SECRET:-${SUPABASE_JWT_SECRET}}

supabase-studio:
  - SUPABASE_ANON_KEY=${ANON_KEY:-${SUPABASE_PUBLISHABLE_KEY}}

## Changes to env.shared

Added standard Supabase variables aligned with PMOVES-supabase fork:
- JWT_SECRET
- JWT_EXPIRY
- ANON_KEY
- SERVICE_ROLE_KEY
- SITE_URL
- API_EXTERNAL_URL

## Related Documentation

- pmoves/docs/SUPABASE_UNIFIED_SETUP.md
- pmoves/docs/PMOVES_SUPABASE_SETUP_GUIDE.md
- pmoves/docs/PMOVES_SUPABASE_CURRENT_STATE_ANALYSIS.md

Fixes services failing to start due to empty/undefined JWT variables.

Related: Task #71 (Implement unified Supabase configuration)
Related: Task #63 (Execute phased production bring-up)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@POWERFULMOVES
POWERFULMOVES deleted the codex/create-and-populate-readme.md branch March 7, 2026 21:41
POWERFULMOVES added a commit that referenced this pull request Jul 18, 2026
…c/plan (#2162)

* docs(gov): stage-4a Mode-A tally-ingestion design spec

Governance-side seam that ingests aggregate secret-ballot counts -> signable
TallyResult without the per-voter voter->support map. Lock-on-first-use mode
guard makes 08's never-mix-modes invariant structural; eligibility from the
registry roll (not the ballot); abstentionPolicy knob (quorum|excluded)
defaulting to quorum with a contrast sweep; hard integrity guards
(safe-integer, voterCount<=eligibleCount); backward-compatible ballotRef
binding into the tallyPreimage. Defers the count<->receipt correspondence
proof to 4b.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* docs(gov): stage-4a Mode-A tally-ingestion implementation plan

3 TDD tasks: (1) pure outcome math + abstentionPolicy knob + contrast sweep
in a self-contained mode-a-tally.ts; (2) backward-compatible ballotRef binding
in tallyPreimage; (3) ingestSecretTally + lock-on-first-use mode guard +
tally() secret-path. Zero new deps; guards as hard invariants in the shared
pure function; import direction one-way (no cycle).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* chore(submodule): bump PMOVES-ToKenism-Multi -> 0b978a1 (stage 4a Mode-A tally ingestion, PR #63)

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant