Skip to content

README.md

Latest commit

 

History

History
49 lines (41 loc) · 1.82 KB

README.md

File metadata and controls

49 lines (41 loc) · 1.82 KB

Shared Execution Carriers

This directory holds the reusable execution-level components that power the Bitcode activity ledger, selected-activity detail, explainers, and payload reading.

The V26 second-gate rule for this layer is simple:

  • if an activity/detail/payload pattern appears repeatedly across /terminal, conversations, or related retained workspaces, it should converge here as a typed, testable carrier.

Main component groups

  • activity-ledger master
    • BitcodeTransactionsTable.tsx
    • BitcodeTransactionsFilterBar.tsx
    • BitcodeTransactionsActiveFilters.tsx
    • BitcodeTransactionsDataTable.tsx
    • BitcodeTransactionsPagination.tsx
  • selected-detail structure
    • BitcodeDetailRowList.tsx
    • BitcodeMetricGrid.tsx
    • BitcodeDetailCollection.tsx
    • BitcodeDetailPanel.tsx
    • BitcodeChipCloud.tsx
    • BitcodeActionPillRow.tsx
  • payload reading
    • BitcodePayloadInspector.tsx
    • BitcodePayloadShape.tsx
    • BitcodePayloadTree.tsx
    • BitcodePayloadRowsCard.tsx
    • BitcodePayloadCollectionCard.tsx
    • BitcodePayloadDetailCard.tsx
  • help and explainers
    • BitcodeInlineExplainer.tsx
    • bitcode-transaction-explainers.ts
  • activity/log streams
    • BitcodeExecutionStreamPanel.tsx

Design goals

  • route-owned orchestration, shared presentation carriers
  • typed props and predictable field-group shapes
  • consistent explainers and payload posture
  • stable accessibility and test selectors
  • no fallback to raw page-local <pre> blocks for important JSON-bearing detail
  • markdown/documentation parity with the active activity-detail and payload carriers during second-gate closure

Used by

  • ../../../app/terminal/README.md
  • activity detail cards under uapi/app/terminal/*
  • retained execution/log readers that continue to converge inward during V26