Configuration Protocol

Overview

This document defines how to configure the Singular Dream environment, manage secrets, and control external integrations.

1. Secrets Management (Doppler)

We use Doppler for centralized secret management. Do not store sensitive keys in .env files committed to the repository.

Prerequisite

Ensure the Doppler CLI is installed and you are logged in:

doppler login

Injection

To run the application with full secrets injected:

doppler run -- pnpm dev

Checking Secrets

To verify if a specific secret is available in your current scope:

doppler secrets --only-names | grep <KEY_NAME>

2. Environment Variables (`.env.local`)

Local overrides should be placed in .env.local. This file is git-ignored.

Required Keys

Key	Description
`NEXT_PUBLIC_FIREBASE_PROJECT_ID`	Must be set to `singular-dream-dev` for Emulator usage.
`NEXT_PUBLIC_FIREBASE_API_KEY`	Public API key.
`TWILIO_ACCOUNT_SID`	(Injected via Doppler)
`TWILIO_AUTH_TOKEN`	(Injected via Doppler)

3. External Integrations

3.1 Twilio (SMS)

Purpose: Vendor Authentication.
Credential Source: Doppler (sd-condo project).

Verification: You can verify the Twilio connection using the verify-twilio.js script (if available) or via curl:

doppler run -- bash -c 'curl -s -X GET "https://api.twilio.com/2010-04-01/Accounts/$TWILIO_ACCOUNT_SID.json" -u "$TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN"'

3.2 Firebase (Identity & Data)

Local Emulator: Default for development.
Production: Live Firebase instance.
Switching: Controlled by NEXT_PUBLIC_FIREBASE_PROJECT_ID.

Version History

Version	Date	Author	Change
0.1.0	2026-01-29	Antigravity	Initial Audit & Metadata Injection