GoJet V10 is a greenfield short-link and resource platform implemented from specification first.
GoJet V10 is an independent greenfield product. The V10 designation is a standalone product identity; no earlier GoJet release, repository, branch, commit, migration, generated artifact, runtime configuration, or implementation is a dependency, migration source, compatibility baseline, or normative evidence.
This repository is the only implementation repository for GoJet V10. Prior GoJet repositories, branches, commits, migrations, generated artifacts, Git history, or runtime configuration are not implementation dependencies and are not normative evidence.
The specification pack defines product behavior before code:
specifications/GoJet_V10_MASTER_PLAN_OPTIMIZED.md— architecture, capabilities, security invariants, implementation nodes, Gates and release definition.specifications/GoJet_V10_BRAND_DESIGN_SYSTEM_OPTIMIZED.md— brand, design tokens, components, motion, responsive behavior, accessibility and cross-surface UX patterns.specifications/GoJet_V10_PAGE_LEVEL_IA_OPTIMIZED.md— routes, page composition, states, workflows, responsive behavior and SEO contracts.
GoJet V10 is under active implementation. GitHub Issues are the persistent project ledger:
- Master Development Tracker — Issue #1
- P00 — Issue #2 — completed
- Current node P01 — Issue #8
- Current P01 implementation — PR #9
The active implementation branch is develop/p01-engineering-foundation. P00/G0 is complete; P01 is building the reproducible frontend engineering foundation. A node or Gate is not considered complete until its specification-defined tests, exact-commit evidence and accountable review have passed.
- Website
- Auth
- Docs
- Workspace
- Admin
- Installer
- Public resource, error and safety surfaces
Links and smart routing, QR, file sharing with mandatory ClamAV, text sharing, Link in Bio, analytics, campaigns/tags, custom domains and entitlement, workspace/RBAC, notifications, billing/payments, support/mail, authentication/OAuth/Turnstile, API keys, outbound webhooks, destination/domain risk, abuse handling, operations/audit, technical SEO and native-only deployment.
Implementation follows P00–P22 and must satisfy G0–G13. A capability is not considered complete because it existed elsewhere or because a UI mock exists; it is complete only when the current repository implementation and required evidence pass its Gates.