@aiquants/enrichment-react 0.9.0 → 0.10.0

package/README.md

@@ -227,7 +227,9 @@ The ingestion pipeline as the flow each document kind actually takes, drawn from
 - **Gates as the answer gives them.** A node's `gates` carry the flow's override already, so a flow that overrides a gate (the image flow's `ocr_document` and the media flow's `analyze_media`, their only body source, `gate_policy`) is drawn with the meaning it has there; a gate's state is read from the tenant's `featureFlags` (a flag the host did not pass is unmeasured).
   A node's gate line (`flow-node-${id}-note-1`, also in its accessible name `<title> (<line>)`) is `gateCaption(state, policy)`: a closed state names its consequence (`門: 閉 (省略)` / `門: 閉 (失敗)`), and an open or unmeasured gated node adds its policy from `GATE_POLICY_LABELS` (e.g. `門: 開・閉じたら失敗`).
   Nothing else is drawn on a node: the search path's circuit breaker is neither read nor fed by the pipeline.
-- **Detail panel** (`flow-step-detail`, `data-node-id`, `data-step-key`): a `CardSection` region named by the node's title (`h3`, `flow-step-detail-heading`), the close button `flow-step-detail-close`, and a `DescriptionList` (`flow-step-definition`) of: the step and its version (`flow-step-key`, `<step> (版 <n>)`), the phase (`flow-step-phase`), the parameters as the answer gives them, one `<key>: <JSON>` line each (`flow-step-parameters`, `flow-step-parameter-${key}`, or `引数なし`, `flow-step-no-parameters`: their meaning is the step's, so no words are added),
+- **Detail panel** (`flow-step-detail`, `data-node-id`, `data-step-key`): a `CardSection` region named by the node's title (`h3`, `flow-step-detail-heading`) with the step's description under it (`flow-step-description`), the close button `flow-step-detail-close`, and a `DescriptionList` (`flow-step-definition`) of: the step and its version (`flow-step-key`, `<step> (版 <n>)`), the phase (`flow-step-phase`),
+  the capabilities the classification governs for the step (`flow-step-capabilities`: their keys in the step's declaration order joined by `・`, or `モデルへ送らない` for a step that sends nothing to a model),
+  the parameters in the step's words, one line each (`flow-step-parameters`, `flow-step-parameter-${key}`: `<title>: <label> (<value>)` for a closed field, `<title>: <value>` for an open one, a string value as itself and any other as its JSON; or `引数なし`, `flow-step-no-parameters`),
   every edge as the executor keeps it — every node of its `depends_on` in order (`flow-step-depends-on`), the ones the figure does not draw named apart (`flow-step-indirect-dependencies`) — and every node whose `depends_on` names it (`flow-step-dependents`),
   and its gates (the foundation's bulleted `List`, `flow-step-gate-list`, of `flow-gate-${flag}` with `data-gate-state` and `data-when-closed`; a failing gate names its failure status, e.g. `閉じたときは FAILED_EXTRACT で失敗`; `flow-step-no-gates` for a node without one), plus `flow-gate-policy-override` when the flow overrides the step's declaration (`gate_policy`).
   A `read_children` node, which runs each child's own flow, also lists the catalogue's child flows (`purpose: "child_reading"`, `flow-step-child-flow-list`, `flow-child-flow-${key}` with `data-flow-key`: `<title> (<key> 版 <version>): <its nodes' titles>`) and notes that the deployment's bindings, which the catalogue does not answer, decide which child takes which flow (`flow-step-child-flow-note`; `flow-step-no-child-flows` when the catalogue has none).