B2BEA.org Rebuild qa-release-readiness-spec
qa-release-readiness-spec artifact · for B2BEA.org Rebuild · status approved
qa-release-readiness-spec artifact · for B2BEA.org Rebuild · status approved
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
- status: draft
- purpose: Define release readiness gates for the B2BEA.org rebuild before implementation planning or V1 launch approval.
- version: 1
- artifact: qa-release-readiness-spec
- client id: b2bea
- created at: 2026-05-07T15:35:22.233Z
- created by: atlas-codex
- hard stops: 4 items
- project id: a820dd0c-6cef-4133-bfbd-d802fd806e44
- repositories: website: object, design_system: object
- project title: B2BEA.org Rebuild
- release scope: shell_basis: object, design_basis: string, v1_route_basis: object
Machine-readable source fields
draft
Define release readiness gates for the B2BEA.org rebuild before implementation planning or V1 launch approval.
1
qa-release-readiness-spec
b2bea
2026-05-07T15:35:22.233Z
atlas-codex
- Do not start build execution until plan and exec plan review approve a bounded slice.
- Do not launch with separate /admin and /studio shells unless owner reverses the single-admin decision.
- Do not normalize signature custom surfaces into generic components when they are explicitly approved custom exceptions.
- Do not let the standard survey system replace the special V1 maturity assessment flow without an approved migration decision.
a820dd0c-6cef-4133-bfbd-d802fd806e44
https://github.com/b2bea-org/b2bea-website.git
Windows checkout repaired by removing invalid tracked macOS Icon file.
C:/Users/jstnk/Downloads/cc/projects/b2bea/b2bea-website
fabc8f2
https://github.com/b2bea-org/b2bea-org-design-system.git
C:/Users/jstnk/Downloads/cc/projects/b2bea/b2bea-org-design-system
d83614a
B2BEA.org Rebuild
Single /admin shell; studio/publishing becomes admin module; current /studio routes redirect or mount under /admin.
Vendor portal private prefix is /vendor.
Company workspace private prefix is /company.
Public discovery/content and auth/account surfaces remain V1 where classified v1_keep.
Hardened B2BEA design system is target. Lovable is only seed/reference; reusable/index/operational/authenticated surfaces use the B2BEA design system unless a custom-page exception is approved.
97 routes classified; 94 v1_keep and 3 redirects; maturity assessment remains V1 as bounded special flow; no deferred routes after owner decision.
2cec821e-07ba-4aca-81fb-078f163adf44
| id | name | owner | checks | required before | evidence required |
|---|---|---|---|---|---|
| QA-01 | Route Inventory Conformance | atlas-codex or assigned reviewer | - Every implemented route maps to route-family-inventory as v1_keep or redirect. - No top-level /studio shell remains as a separate private shell after migration, except redirects or admin-mounted modules. - /vendor-portal redirects to /vendor if retained for compatibility. - Maturity assessment routes use the special-flow contract, not the standard survey system contract. | implementation_dispatch | - route table diff - redirect map - manual route smoke results |
| QA-02 | Design System Conformance | design/reviewer | - Pages use B2BEA tokens/components from the design-system repo or approved local equivalents. - Custom pages are limited to home, campaign/resource landing, approved HTML imports, or signature editorial features. - Operational/private pages avoid one-off decorative layouts and follow reusable page-template contracts. - No surface treats Lovable output as final authority without B2BEA hardening. | release_candidate | - component/token usage review - desktop/mobile screenshots for representative page families - custom exception list |
| QA-03 | Access And Permission Boundary | engineering/reviewer | - Unauthenticated users cannot access /admin, /vendor, /company, member-only account/dashboard routes, or private APIs. - Vendor users cannot access company workspace or admin-only data. - Company users cannot access vendor portal data unless explicitly entitled by contract. - Admin modules enforce admin permission, including publishing/studio functions. - Survey exports and maturity assessment outputs follow permission and lifecycle contracts. | release_candidate | - auth matrix test results - API/RLS checks where applicable - negative-path screenshots or logs |
| QA-04 | Publishing And Content Safety | content/admin reviewer | - Draft/review/publish lifecycle works for public content types kept in V1. - Resource/blog pages have canonical metadata, slug policy, redirect policy, and preview behavior. - Custom HTML imports are sanitized/reviewed and recorded as approved custom exceptions. - No unpublished, archived, or removed content appears in public navigation/search. | release_candidate | - publishing workflow smoke - metadata crawl - custom import review notes |
| QA-05 | Responsive And Browser Smoke | qa/reviewer | - Representative pages pass desktop and mobile viewport smoke. - Navigation, drawers, forms, modals, dashboards, and assessment flows have no overlapping text or broken responsive states. - No blocking console errors on core paths. - Images/assets render and are not dark, cropped, or placeholder-like where users need real inspection. | release_candidate | - Playwright or browser screenshots - console/error log summary - asset-render checklist |
| QA-06 | Data And Migration Safety | engineering/reviewer | - Implementation plan identifies which existing data models are reused vs migrated. - Schema changes include rollback/forward migration notes and do not break existing artifacts/content. - Seed/import scripts are idempotent where practical and scoped to B2BEA project/client data. - Private workspace, entitlement, survey, and publishing records have clear ownership and lifecycle state. | implementation_dispatch_and_release_candidate | - migration review - dry-run import results when applicable - data ownership checklist |
| QA-07 | Release Decision Gate | Justin / release owner | - All blocking readiness gates are pass or explicitly waived with owner/date/reason. - Known issues are classified as block, defer, or accepted risk. - Rollback path and post-launch monitoring owner are documented. - Final V1 route list and redirects are approved. | production_launch | - release acceptance artifact or approval note - known issues register - rollback note |
77853042-e7a4-48bd-91a4-6e48d0484b1b
draft
10
2f473004-9063-4fe9-8290-5cbd1b19dfb4
draft
1
4c3651ac-9a69-4117-a355-750b61f540c9
draft
4
427c04a9-40b7-4e55-a642-65b2aee20b2b
draft
1
823d14d7-5992-42f3-a2f4-f4738a045f7c
draft
1
a9636e2f-a4be-4586-82dd-c1a7bf3199fa
draft
1
355b3249-3af9-45a4-9c45-67777bd2d72d
draft
1
2cec821e-07ba-4aca-81fb-078f163adf44
draft
3
05e0ed7c-416a-4d8f-853a-bc3dfa3d64f6
draft
1
dcfc8620-9f28-4019-aeeb-de3e279fd7a7
draft
3
80328220-3deb-4cf9-a68f-d440b41a38da
draft
3
- anonymous
- member
- company user
- vendor user
- admin
- empty
- typical populated
- long text/content
- missing optional media
- unauthorized/forbidden
- home
- resource/blog landing
- representative resource detail
- directory/listing page
- auth/account route
- member dashboard/profile
- maturity assessment flow
- /admin
- /admin/studio or /admin/publishing
- /vendor
- /company
- redirect routes
- mobile narrow
- tablet or mid-width
- desktop
plan
- plan
- exec_plan_review
- build_execution
- verification_report
- release_acceptance