ITU compliance for the AEC: the Rev 5 plan and the Stage 0 requirements matrix - #5
Merged
Merged
Conversation
…-filter, proof) Planning revision, no code. Records the next effort — prove the AEC chain passes G.167 / P.340 / a G.168-adapted battery / P.1100-P.1120 with asserted margin — as six stages: requirements matrix, calibrated ITU signal layer, residual-echo post-filter + comfort noise, compliance test suite, proof notebook, external/docs integration. Scope decisions settled (anchors incl. automotive, post-filter approved, margin policy proposed); Stage 0 is blocked on allowlisting itu.int in the dev environment's network policy. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TLE2rvptWxV8catE8vTvgx
Distilled from the recommendation texts themselves (P.1110/P.1120 automotive series, P.340, P.501, G.168, G.167, G.131): three tiers of matrix rows — the automotive battery as the operative modern AEC spec (Tier A, incl. the P.340 Category-1 full-duplex targets), a G.168-adapted battery (Tier B, labeled adapted, line-only tests excluded explicitly), and G.167 historical rows (Tier C; the rec is withdrawn and its values provisional). Every row: clause, requirement, required value, margin target (>= 6 dB level / <= half time), scope tag (ALGO/MIXED/TERMINAL), owning test name. Plus the Stage 1 asset list (CSS generators, AM-FM orthogonal pair, level toolchain, cabin/TV paths, driving noise) and the Stage 2 design constraints the rows pin (residual <= -64 dBm0(A) at <= 1.5 dB double-talk transparency). HANDOFF: Stage 0 marked done with the findings that shaped the matrix. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TLE2rvptWxV8catE8vTvgx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs-only PR (no code): the plan and the foundation document for the ITU compliance effort.
HANDOFF Rev 5 — the plan
Six stages to prove the AEC chain passes the applicable ITU specifications with asserted margin: requirements matrix → calibrated ITU signal layer → residual-echo post-filter + comfort noise → compliance test suite → proof notebook → external/docs integration. Scope decisions recorded: anchors are the automotive series (P.1100/P.1110/P.1120) + P.340 + a G.168-adapted battery + G.167 as historical tier; the post-filter is approved; margin policy is ≥ 6 dB on level clauses / ≤ ½ time on time clauses, asserted in CI so margin erosion fails, not just violation.
Stage 0 —
docs/itu-compliance.mdThe requirements matrix, distilled from the recommendation texts themselves (all read end-to-end this session: P.1110/P.1100 03/2017, P.1120 10/2025, P.340 05/2000, P.501 04/2025, G.168 04/2015, G.167 03/1993, G.131 11/2003):
Each row: clause, requirement, required value, margin target, ALGO/MIXED/TERMINAL scope tag, owning test name (row IDs become gtest names). Plus the Stage 1 signal/asset build list (CSS generators from the P.501 sample tables, AM-FM orthogonal double-talk pair, dBm0/dBPa/dBov calibration, cabin and time-varying echo paths) and the Stage 2 design constraints the rows pin.
Grounding for the simulation approach, from the texts: P.340 (10.3.1) and G.167 (5.2.3.1) explicitly permit simulated echo paths; P.1110 clause 8 defines digital insertion interfaces so "no HATS is necessary"; and P.1120 (10/2025) normatively cites P.340 (2000) — the edition in hand — resolving the P.340-2019 procurement gap for every operative table.
Known gaps recorded in the matrix: three tests use ITU real-speech attachment WAVs (Stage 1 will fetch for git-ignored local use or run documented synthetic stand-ins marked method-equivalent); P.502 is not on the free portal (methods reconstructed from the citing test descriptions).
🤖 Generated with Claude Code
https://claude.ai/code/session_01TLE2rvptWxV8catE8vTvgx
Generated by Claude Code