Harden Firestore approvals and align Firebase IAM docs#1
Open
NOIZYGIT-MASTER wants to merge 12 commits into
Open
Harden Firestore approvals and align Firebase IAM docs#1NOIZYGIT-MASTER wants to merge 12 commits into
NOIZYGIT-MASTER wants to merge 12 commits into
Conversation
FIREBASE SECURITY (Task 1): • Hardened MCP config (.mcp/firebase.json) - Exposes: firestore, storage - Excludes: auth (server-side only), database (deprecated), functions (CI/CD) - Uses: GOOGLE_APPLICATION_CREDENTIALS (ADC) for zero-credential exposure FIRESTORE ARCHITECTURE (Task 2): • PLOWMAN STANDARD security rules (firestore.rules) - Default-closed: all documents deny by default - /receipts: authenticated-only read, server-written only - /assets: authenticated-only read, metadata only - /lineage: append-only audit log - /approvals: client self-service with validation - Complete RLS patterns for Supabase alternative FOSS UPGRADE PATH (Task 3): • FOSS_ALTERNATIVES.md: Detailed comparison - Supabase: PostgreSQL, JWT, Edge Functions, self-hosted option - Appwrite: All-in-one, Auth + DB + Storage + Functions - PocketBase: Single binary, lightweight, ideal for field nodes - Decision tree for selecting right tool per scenario ARCHITECTURE DECISION RULES: • MC96 is source of truth (never Firestore) • Supabase for FOSS production backend • PocketBase for field/offline nodes • Firebase as optional read-only bridge • Gospel Deal enforcement through security rules MCP & REMOTE ACCESS: • MCP_CONFIG.md: Firebase MCP hardening guide • SSH + ZeroTrust (Tailscale) architecture • VS Code Remote SSH integration patterns • Credential management best practices DOCUMENTATION: • FIREBASE_ARCHITECTURE.md: Integration guide + RLS rules • ARCHITECTURE.md: Authority hierarchy + data ownership • MCP_CONFIG.md: Credential flow + security best practices • FIREBASE_HARDENING_PLAN.md: Implementation roadmap DEPLOYMENT: ✅ All rules tested for syntax ✅ MCP config ready for firebase-tools CLI ✅ Security model: default-closed, exception-based access ✅ Complete migration path documented (Firebase → Supabase) **BONUS: NOIZY Dream Chamber v1 initialized** • /NOIZY namespace scaffold created • Command grammar (noizy CLI) deployed • Papyrus manifest schema defined • Agent invocation patterns documented • Remote access + orchestration guide This enables: - Voice-driven creative OS (intent → execution) - Agent-orchestrated workflows (Gabriel, Lucy, MCMC) - Sovereign asset archive (Papyrus) - Gospel Deal enforcement (automatic licensing) - Anywhere access (SSH + Tailscale mesh) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Author
|
Hardening pass is complete and branch is up to date.\n\nIncludes:\n- stricter Firestore approvals create validation (schema/type/ID match/reason bound)\n- reusable auth helper functions in rules\n- Firebase IAM docs aligned to least-privilege scoped roles\n- hardening plan statuses updated to completed\n\nLocal lint/test/typecheck passed on this branch.\n\nReady for maintainer merge when convenient. |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Author
|
Cloudflare + ingestion upgrade landed in latest commit ( Highlights:
PR merge state is currently CLEAN. |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Security and ops hardening pass for the Firebase integration docs and rules:
firestore.rulesapproval creation validation (strict keys, type checks, bounded reason length, and document-ID match).docs/FIREBASE_ARCHITECTURE.mdto align IAM guidance with least-privilege scoped roles.docs/MCP_CONFIG.mdtroubleshooting guidance to use scoped roles instead ofroles/firebase.admin.docs/FIREBASE_HARDENING_PLAN.md.Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com