What changed across School-GIT

This page is the high-level release map for the current platform so older docs do not keep presenting removed or compatibility-only systems as the main architecture.

Browser authentication moved to TypeScript APIs backed by private AETHER + URL records. Opaque sessions, remembered-account switching, strong-password enrollment, 12-digit verification inbox delivery and internal account mail replace Google/Passport as the primary sign-in model.

Points are now represented as a private AETHER-backed virtual bank account with checking, savings, an auditable ledger, live game sessions, educational loans, virtual earning taxes, BRIA fees and one-time overdue learning fees. Client-side balances are not authoritative.

Platform chat now passes through /api/bria-metered/chat. The existing two-hour daily active-use allowance is preserved; after it is exhausted, paid chats reserve the 12-point BRIA base fee plus the configured virtual service tax. The default 100-point extension adds another two hours, and failed paid upstream execution refunds the reservation.

ABR continues as the personalized structural cognition engine. PABR adds an opt-in personal-twin layer for language habits, preferences, structured behavioral signals, consented voice/avatar identity profiles and persona modes.

BRIA includes the optional PB theme: a lazily-mounted Three.js/post-processing chat environment with depth, particles, reactor geometry and heavy interactive controls. Other themes do not mount that render stack.

The Clicker now registers a real server-side game heartbeat, preserves the 0.5-point-per-accepted-click plus 5-every-20-clicks gross reward model, applies the virtual earning tax during settlement, and renders a Three.js production district where purchased buildings and decorative workers appear in the world. There is no controllable player avatar.

The old user-facing Bottles dashboard is superseded by Projects + RC projects and RS-backed services. Legacy container routes can remain an internal runtime compatibility boundary while the product UI speaks in projects and apps.

RC is the single project runtime surface: source, services, stable subdomains, live execution, versions and public routing all resolve through the same project model.

RC Storage / AETHER / URL-DB

The active storage surface is now /rc/storage. RC databases bind only to existing RC projects: URL-DB carries authenticated logical records while AETHER owns private references, revisions, content hashes and audit state. Older storage compatibility endpoints are internal-only and are not part of current creator guidance.

Public dynamic RC responses now use a per-project, content-addressed AETHER-backed cache with aggressive presets, TTL/stale controls, byte and entry budgets, LRU/LFU/hybrid eviction, query/Vary policy, warming, scoped purges and integrity verification.

Dynamic project requests receive a four-minute upstream deadline before the managed 504 surface. RC 404s use the managed error surface, live revision events refresh connected pages, and projects without custom branding receive one of twelve deterministic gateway-injected PNG favicons.

The V2 client/server contract is repaired so JSON create/update/favorite/accepted-reply/detail/feed operations agree. Discussion discovery continues through the AETHER typed index while payloads stay URL-backed.

GXHAD advances from its first 100 literal dot-source components to 300. IDs 101–300 add thread structure, authoring, interaction, moderation, discovery, identity, media, accessibility, resilience and collaboration/automation controls.

Account creation is limited to ages 13–17. Signup now requires a short-lived signed age-assurance claim. Camera frames are processed ephemerally and are not intentionally persisted; uncertain age-band estimates do not get guessed into access.

Thirty teen-development guidelines are backed by a TypeScript monitoring layer with behavioral velocity checks, local risk detectors, optional external-classifier correlation, privacy-minimized AETHER audit records and block/escalate/appeal metadata. Discussions and replies run through this layer before persistence.

The authenticated /repo surface provides a read-only Monaco source viewer, server-side SHA-256 hashes, path filtering and secret exclusion. Browser copy restrictions and watermarks are deterrence; external OS/camera capture cannot be guaranteed by a normal webpage.

mt-3 text-4xl font-black tracking-[-.04em] sm:text-6xl