Appsations SDK

SDK Config Dashboard

Every repo includes this dashboard for SDK visibility, Firebase settings, and domain hosting status. Firestore is the source of truth; the SDK sync pulls from Firestore, then refreshes Appsations-managed files.

SDK Location

The SDK lives at the repo root under appsations-sdk/.

appsations-sdk/ AGENTS.md CODEX_TASKS.md personality-agent.txt mystprint.json profiles/ dashboard/ bin/

mystprint.json

Repo fingerprint + Firebase + domain settings live in appsations-sdk/mystprint.json. Appsations Inc uses it to sync updates and costs.

Firebase Rules

Each SDK must declare its own database + storage bucket. All webapps deploy on Firebase Hosting. Cloud messaging, payment services, and SMTP/email are tracked in mystprint.json.

Warnings

Warnings are generated from the SDK config and stored in appsations-sdk/state/warnings.json.

Public lockdown controls

Each repo can trigger the shared appsationsinc-lockdown.sh helper. Use these buttons to lock, unlock, or view the status for this repo's hosting site. The commands call the admin lockdown helper so every repo stays aligned.

lock

        
unlock

        
status

        
lock all

        
unlock all

        

Payments

Canonical Square settings live in appsationsinc-config/payments.json. Use the payment manager to rotate tokens or open the developer portal.

Open payment hub

      

Auth, storage, recaptcha, messaging

Configure identity, buckets, and security signals in mystprint.json.

Auth

set-auth

        

Storage

set-storage

        

Recaptcha

set-recaptcha

        

Messaging

set-messaging

        

Google Cloud watch

Open the billing and warning dashboard for Google Cloud exports, budgets, and traffic signals.

appsations-sdk/dashboard/gcloud.html

Domain manager

Track domain ownership, usage, and DNS checks in one place.

appsations-sdk/dashboard/domains.html

Subscriptions

Review subscription renewals and status notes across divisions.

appsations-sdk/dashboard/subscriptions.html

Schedulers

See and manage launchd + cron registries in one place.

appsations-sdk/dashboard/schedulers.html

Firebase Setup Wizard

Use this panel to wire each repo into Appsations Inc Firestore. Fill in the values, then copy the commands to update mystprint.json and sync to Appsations.

set-firebase

        
set-domain

        
sync-to-firebase

        
check-warnings

        
Appsations defaults (all repos)

        
Sync all repos

        

Tip: Once set-firebase runs, sync-to-firebase writes to the Appsations database and updates appsations.last_sync.

Dataset Activation

Toggle which dataset groups are active for this repo. These flags live under datasets in mystprint.json.

set-datasets

        

Tip: Use "all" to enable everything, or leave none selected to disable all.

Secrets

Secrets live under ~/Documents/secrets. Store only references/paths in mystprint.json.

Profiles

Profiles are enabled via appsations.profiles. Every SDK includes webapp.

Work Orders

Work orders live in each repo database under work_orders and are organized by repo -> client -> created date.

work_orders/{repo_id}/clients/{client_id}/orders/{order_id} fields: created_at, inventory_usage, time_entries, status

Inventory & Time

Track parts under inventory and log usage in inventory_usage. Time entries go in time_entries keyed by the logged-in user (default: paulhopkins).

Billing & Financials

Billing config lives in billing. Division financials are stored in each repo database under financials, while Appsations Inc aggregates across databases.

Subscriptions

Track every subscription in subscriptions for cost control, renewals, and elimination planning. Billing is centralized under Appsations Inc.

subscriptions/{subscription_id} fields: vendor, status, billing_cycle, renew_date, amount, currency

Expenses & Receipts

Expenses are tracked in expenses with receipts in expense_receipts. Expense accounts are centralized under Appsations Inc for billing and reconciliation.

expenses/{expense_id} expense_receipts/{receipt_id} expense_accounts/{account_id}

Customer Accounts & CRM

Customer accounts live in customers with details in customer_accounts. CRM ownership belongs to ConsciousVisionaries for customer info, pipelines, and touchpoints.

customers/{customer_id}/accounts/{account_id} crm/{record_id} crm_pipeline/{stage_id}

Repo DB monitoring

All repo dashboards read/write to their own database. Appsations Inc registers each repo to monitor change logs for billing, compliance, and health reporting.

Tools & Management

Enable toolsets by profile and manage the SDK with Appsations helpers. Core tools live in appsations-sdk/bin/ (Codex, sync, warnings).

appsationsinc-sdk-manager.sh install|sync|set-profiles|set-google-projects|set-datasets appsations-sdk/bin/appsations-sync.sh appsations-sdk/bin/appsations_codex_tasks