Skip to content

README.md

Latest commit

 

History

History
51 lines (41 loc) · 2.33 KB

README.md

File metadata and controls

51 lines (41 loc) · 2.33 KB

uapi/components/base/bitcode

This directory holds the shared Bitcode operator component systems used by /terminal, auxillaries, conversations, and the retained route chrome.

In V26 second-gate work, this directory is not a grab-bag. It is the reusable carrier layer for:

  • route chrome,
  • shared activity vocabulary,
  • notifications and menus,
  • execution and Exchange master-detail components,
  • and the supporting primitives needed to keep /terminal cleanly componentized.

Main system areas

  • layout/ Navbar, user menu, route-surface classification, and related chrome carriers.
  • activity/ Shared activity vocabulary bridging transactions-first execution streams and later notification/public/personal activity classes.
  • notifications/ Operator notification surfaces tied to the transactions and auxillary shell.
  • execution/ Shared transaction tables, payload readers, detail panels, explainers, activity streams, and field/metric carriers.
  • orbitals/ Shared auxillary visual and ring-adjacent primitives reused by the retained auxillary source owners.

V26 second-gate rule

New product behavior should prefer this shared layer when the result is:

  • reusable across /terminal, /auxillaries, and /conversations,
  • typed and provable,
  • cleaner than page-local duplication,
  • and aligned to Bitcode operator UX rather than marketing or demo posture.

Do not use this directory to hide page-local uncertainty. If a concern is only meaningful for one route and has not stabilized, keep it route-local until the abstraction is real.

This shared layer is also part of the second-gate markdown/refurbishment requirement. If shared operator chrome or execution carriers change materially, their README carriers are expected to stay current in the same checkpoint.

Key docs