49 lines
1.5 KiB
Markdown
49 lines
1.5 KiB
Markdown
# G7 Multi Endpoint Inventory Design
|
|
|
|
> Date: 2026-04-18
|
|
> Status: Initial implementation slice
|
|
|
|
## Goal
|
|
|
|
Define `G7 多接口盘点汇总型` as a separate family so multi-endpoint inventory scenes no longer fall back into `G1` or `G1-E`.
|
|
|
|
The first implementation slice is classification and fail-closed safety only.
|
|
|
|
## Family Definition
|
|
|
|
`G7` covers scenes that query multiple inventory/statistics endpoints by asset category and aggregate the results into one report.
|
|
|
|
Minimum signals:
|
|
|
|
1. three or more inventory/statistics endpoints
|
|
2. endpoint names or URLs carrying `assetStats`, `inventory`, `stock`, `AcqTrml`, `MeterCommonModule`, or `JlGnModule`
|
|
3. no explicit host bridge action requirement
|
|
4. no local SQL/document-generation pipeline requirement
|
|
|
|
## P0 Boundary Sample
|
|
|
|
`计量资产库存统计`
|
|
|
|
Repo-local representative:
|
|
|
|
`tests/fixtures/generated_scene/g7_multi_endpoint_inventory`
|
|
|
|
## Contract Policy
|
|
|
|
The first slice intentionally blocks runnable generation until a real G7 inventory contract exists.
|
|
|
|
The initial system must:
|
|
|
|
1. classify as `multi_endpoint_inventory`
|
|
2. preserve inventory endpoint evidence
|
|
3. avoid fallback to `single_request_table`
|
|
4. avoid fallback to `single_request_enrichment`
|
|
5. fail closed with a stable blocker
|
|
|
|
## Acceptance Criteria
|
|
|
|
1. the representative fixture classifies as `multi_endpoint_inventory`
|
|
2. at least five inventory endpoints are detected in the fixture
|
|
3. generation fails closed
|
|
4. existing `G1-E`, `G3`, `G6`, and `G2` regressions remain green
|