UTC :: --:--:-- RUST :: stable :: 1.97.1 CLIENT :: browser :: detecting PYPI :: litlaunch :: 1.1.3 GITHUB :: LitLaunch :: live CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.1.3 CLOUDFLARE :: pages :: operational GITHUB :: RoleThread :: live NODE :: lts :: 24.18.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 301k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x UTC :: --:--:-- RUST :: stable :: 1.97.1 CLIENT :: browser :: detecting PYPI :: litlaunch :: 1.1.3 GITHUB :: LitLaunch :: live CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.1.3 CLOUDFLARE :: pages :: operational GITHUB :: RoleThread :: live NODE :: lts :: 24.18.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 301k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x
report::path :: planned

Bug reports route to the right system

Product reports are routed through the appropriate project issue tracker so bugs stay close to the code that owns them.

PRELAUNCH

Product Reports

  • LitLaunch issues belong with the LitLaunch repository.
  • RoleThread Lite issues belong with the RoleThread Lite repository.
  • Future product issue paths will be disclosed when those products are public.

Site Reports

  • Website defects may route to the SCG web platform issue tracker after public launch.
  • A custom intake system comes later only if it becomes more useful than GitHub-native routing.
  • Public visitor access stays GitHub-based while product support paths mature.

GitHub Access

  • Top-level public project access uses the Lattice-Foundry GitHub organization.
  • Internal SCG infrastructure and web-platform work remains separate.
  • External issue links will be added once public repository visibility and templates are ready.