Identity
Authentication, sessions and protected account flows
Supabase Auth integration
Protected dashboard routes
Server-side session handling
Technology Proof · Public status
Evidence before promises
What CTG One can demonstrate today.
This registry separates production capabilities, controlled betas, partial implementations, active development, and roadmap. It is not an SLA or uptime page; it is a public surface for technical maturity and evidence.
LIVE
3
BETA
3
PARTIAL
1
IN DEVELOPMENT
1
ROADMAP
1
LIVE
View related evidence
Data & Security
PostgreSQL transactional data with Row Level Security
Supabase/PostgreSQL
RLS policies
Server-side authorization
Input validation
Products
CTG Craft Beer Investment operating model
Closed-beta participant and admin surfaces implemented
Order, allocation, inventory, ledger and settlement schema/RPCs implemented
Production batch state machine and serialization implemented
Participant withdrawal and server-priced reinvestment request loop implemented with shared spend and target-lot capacity reservations
Finance reinvestment queue exposes bounded review evidence and canonical approve/reject actions without allowing quantity or capital overrides
Operational Golden Journey reconstructs funding, payment, production, inventory, sale/return, settlement and post-settlement liquidity evidence per lot
A clean-database transactional journey certifies sale return, settlement credit, reinvestment and confirmed payout as one conserved economic loop
Post-deploy Production readiness canary verifies exact Render identity, runtime schema compatibility and the canonical Investment surface without production mutations; real operating evidence remains required for LIVE promotion
Versioned production-readiness canary evidence is archived per deployed SHA and validated by the same fail-closed contract consumed by release governance; generated artifacts are never auto-accepted for LIVE review
Private redacted operating-evidence capture, validation, human-review and finalization tooling is implemented with PII/identifier rejection, source hashing and synthetic-evidence separation; no real production operating capture has been approved yet
SUPER_ADMIN release gate matrix consolidates technical, runtime, operating-evidence, pending-business-decision and fail-closed exposure state without enabling automatic LIVE promotion
New external funding is server-gated by authenticated identity, VERIFIED investment KYC, explicit per-lot FUNDING_OPEN state and remaining PostgreSQL capacity; no separate global funding feature flag is claimed
Clean-database migration and Golden Path contracts run in CI
Infrastructure
Versioned delivery pipeline
GitHub
Pull requests
GitHub Actions
Critical safety tests
Typecheck
Next.js production build
Render deployment
Reliability
Correlated health, structured telemetry and safe error intelligence
/api/health and runtime schema compatibility probe
Versioned structured JSON telemetry schema with recursive sensitive-field redaction
Validated request IDs plus W3C traceparent trace/span propagation on critical health and knowledge paths
Safe error classification, retryability metadata and opaque fingerprints without raw exception-message logging on adopted paths
Centralized metrics, alert routing and broad distributed tracing remain incomplete
Artificial Intelligence
Governed AI architecture, model gateway, RAG design, agent runtime and evaluation model
Public AI architecture surface
AI governance and human-in-the-loop requirements
Citation-First RAG architecture defined
Shared server-only model gateway foundation with provider allowlist and versioned runtime configuration
Bounded provider timeout/retry policy and token/latency/request-ID telemetry implemented for the current OpenAI adapter
Agent runtime contract defined
AI evaluation and security models documented
No general-purpose production agent runtime or automatic provider failover claimed
Artificial Intelligence
CTG Knowledge authenticated source-grounded RAG pilot
pgvector migration and RLS policies implemented
Admin-only curated text ingestion endpoint
Authenticated semantic retrieval endpoint
Server-side model gateway routes embeddings and grounded responses through an allowlisted provider boundary
Current OpenAI adapter enforces bounded timeout/retry behavior and provider storage disabled for generated responses
Provider/model/config version, latency, attempts, request ID and token usage are emitted as structured telemetry without logging prompt/source/answer content
Knowledge query and ingestion carry correlated W3C trace context and safe error fingerprints
Citation metadata returned independently of generated text
Deterministic post-generation citation integrity gate fails closed on missing or fabricated source references
Reproducible evaluation harness implemented; authorized semantic and operating evidence still required for LIVE promotion
Versioned first-party public evaluation corpus and dataset are Git-blob pinned with fail-closed provenance and drift validation
Controlled isolated-environment seeding, run capture, human-review, and finalization tooling implemented; first authorized human-reviewed run still pending
Ecosystem Federation
CTG One ⇄ VÉRTICE OS identity federation ("Entrar con CTG One")
Authorization-code + PKCE (S256) federation flow with timing-safe shared-secret verification (src/lib/federation/vertice.ts)
GET /api/federation/vertice/authorize issues a one-time code only for an authenticated, email-verified CTG One session
POST /api/federation/vertice/exchange is a service-secret-authenticated, rate-limited (federation.vertice.exchange scope) server-to-server code exchange
Optional minimal KYC assurance claim sourced strictly from verified profiles.kyc_status/kyc_submissions, never inferred from login, email, wallet or reputation
Authority grants lookup via identity_federation_authorities for VÉRTICE-issued roles
"Entrar con CTG One" is a live production entry point in the dashboard service hub, not a placeholder
VÉRTICE OS mobile reuses this same server-to-server exchange through its own backend BFF, which generates and custodies its own PKCE transaction; no separate CTG One-side mobile provider, scheme or migration exists or is required
No end-to-end production operating evidence (confirmed session/citizen_id parity across ctgone.com and vertice.ctgone.com) has been captured or reviewed yet; LIVE promotion is not claimed
Web3
CTGO on-chain production utility
Web3 libraries present
No verified production contract/network evidence published
Promotion criterion
A capability moves to LIVE only with code, controlled access, tests, and sufficient operating evidence. A functional beta is not equivalent to open production.
No invented metrics
We do not publish adoption, uptime, users, holders, or performance without a verifiable source.
Evolving maturity
The registry changes when the system changes, not when marketing language changes.