Maestro
Live demo — data resets daily at 03:00 UTC. Nothing you enter is saved.

Sparrow complete product

ESH10000633 · Rev R1

in_progresselectronics

System-level Sparrow product. Test implementation lives in Maestro TAT package ESH10000633_SparrowUnitTest_v01 (https://github.com/esharpab/testdevelopment-esharp-tat-registry-ESH10000633_SparrowUnitTest_v01).

Reports Milestones (7)Audit Log

Everything here lives inside a Project (a code + revision, e.g. ESH10000540 R3). The backbone is the V-model, read top-to-bottom: define what the product must do, plan how to prove it, execute the proof on real units, then learn from the field — and the Loop closes back up to the top.
This map is live: a block is green with a count when this project actually has that entity, and dashed/dim when it’s empty. Click any block to open its tab; hover for details. Arrows are the meaningful links; the implicit “belongs to this Project” edge is left out for legibility.

What each thing means

Requirement
One thing the product must do or satisfy — the “what”.
Test Case
A defined check that proves one or more requirements — the “how we prove it”. A verified_by trace link ties a test case to the requirement(s) it covers; that link is exactly what Coverage % counts. (So: a test case refers to the requirements it verifies.)
Verification Plan
A named grouping of test cases, approved before a test campaign and optionally gated by a milestone.
Verification Record
The result of running one test case against one unit: pass / fail / error / na. This is the evidence a requirement is actually met.
DUT
Device Under Test — an individual physical unit (by serial number) that records and test data attach to.
Deviation
A documented waiver against a verification record (e.g. accept a known non-conformance, with justification).
Entry
A knowledge note: a decision (settled choice), notice (assumption / risk / open question), issue (tracked problem), or concept (idea under exploration). It can attach to any other entity.
Design Rule
A reusable, checkable engineering constraint. Running the checks turns each violation into a Conflict.
Conflict
An open flag raised by a failed design-rule check (or an end-of-life / component-library issue) that needs resolving.
Milestone
A dated gate; verification plans can be tied to it.
Field Issue (RMA)
A failure reported from the field on a returned unit; Root-Cause Analysis explains why it happened.
The Loop (S-16)
loop_trace reconciles a field issue against that unit’s own verification record (did it pass at the edge of the band?). closes_loop records the corrective decision or design rule so the lesson is captured — and clears the project’s open-loop count.
Interface / Port
A contract between projects; each port can be driven by a requirement (and cascade one into the connected project).
BOM Component
A part on this project’s bill of materials, optionally linked to the shared Component Library.
GRR Study
A Gauge R&R study measuring how repeatable a test case’s measurement is.
Test Data
Production / Maestro run results recorded against DUTs — the population behind a single verification record.
0% Coverage
0% Done
0 Requirements
68 Test Cases
13 Open Entries

Timeline

Color = derived gate state · hover a tile for its note.
cancelled
Gate 1 — Design Release (all sub-assemblies at Manufacturing in MES; ESH10000634 R3 approved)
May 15, 2026
cancelled
Gate 2 — Inventory Procurement (all shortfalls resolved; ESH10000182 build order confirmed)
Jun 5, 2026
cancelled
Gate 3 — Test & Production Infrastructure (ESH10000654 verified; test procedure complete; DUT serials defined)
Jun 5, 2026
cancelled
Gate 4 — First Article (S/N 001 assembled and passed production test)
Jun 12, 2026
marker
Schema test
Jun 15, 2026
cancelled
Gate 5 — Production Run (20 systems assembled + standalone deliverables 10×636, 20×614, 20×637, 20×EPN1000786)
Jul 6, 2026
cancelled
Gate 6 — Delivery (final QC, packaging, delivery documentation complete)
Jul 13, 2026
not started
🏁 Release
· 3/6

Status & gates

Chronological — Release is the final gate. Derived & read-only; edit via trace_milestone_* tools.
MS-G1Gate 1 — Design Release (all sub-assemblies at Manufacturing in MES; ESH10000634 R3 approved) cancelleddue 2026-05-15
MS-G2Gate 2 — Inventory Procurement (all shortfalls resolved; ESH10000182 build order confirmed) cancelleddue 2026-06-05
MS-G3Gate 3 — Test & Production Infrastructure (ESH10000654 verified; test procedure complete; DUT serials defined) cancelleddue 2026-06-05
MS-G4Gate 4 — First Article (S/N 001 assembled and passed production test) cancelleddue 2026-06-12
TEST_MILESTONE_TO_CHECK_SCHEMASchema test markerdue 2026-06-15
MS-G5Gate 5 — Production Run (20 systems assembled + standalone deliverables 10×636, 20×614, 20×637, 20×EPN1000786) cancelleddue 2026-07-06
MS-G6Gate 6 — Delivery (final QC, packaging, delivery documentation complete) cancelleddue 2026-07-13
Release / Readiness not started 3/6 met
pending Requirements approved
  • PWR-26: draft
  • PWR-31: draft
  • PWR-12: draft
  • PWR-13: draft
  • PWR-15: draft
  • SIG-14: draft
  • SIG-04: draft
  • SIG-06: draft
  • SIG-05: draft
  • SIG-07: draft
pending Coverage ≥ 100%
  • No requirements in scope
pending All test cases pass
  • 28/68 passed
  • 40 not yet run
met No blocking issues open
met Deviations resolved
met Interfaces frozen
Attention 9 open entries
Composition 11 dependencies need attention: ESH10000534 R4 (amber), ESH10000535 R3 (amber), ESH10000536 R2 (amber), ESH10000540 R3 (amber), ESH10000543 R2 (amber), ESH10000634 R3 (amber), ESH10000631 R1 (amber), ESH10000636 R1 (amber), ESH10000582 R1.0 (amber), ESH10000614 R0 (amber), ESH10000637 R0 (amber)

Test Cases

28 Pass 0 Fail / Deviated 0 N/A 40 Open10 / 68 Maestro impl.

Coverage — 0.0% · Done — 0.0%

0 Done 0 Partial 0 Not Started 0 Missing74 Draft0 Obsolete
Entries
29 of 29
CodeKindTitleSeverityScopeStatusMilestoneCreated
E-001 notice G-01: ESH10000182 (Accordion A2 Bare) build order not placed — critical path blocking record withdrawn — 2026-05-22
E-002 notice G-05: ESH10000637 (PSU Power Cable) procurement — need 40, 0 on hand warning record withdrawn — 2026-05-22
E-003 notice G-06: EPN1000677 (5-port USB wall charger) — 2 short of 20-unit need info record withdrawn — 2026-05-22
E-004 notice G-13: ESH10000158 R5 procurement decision DUE 2026-05-27 blocking record withdrawn — 2026-05-22
E-005 notice ISSUE-001: ESH10000538 M2base loopback — intermittent Sparrow N-Top startup faults warning record open — 2026-05-22
E-006 notice 5 user-pin functional groups missing from fixture-electronics-test warning record open — 2026-05-22
E-007 notice PT-SIG.04 marginal fail — J6 audio bias-load voltage 0.5% over upper limit warning record closed — 2026-05-25
E-008 notice ASM-01 info record open — 2026-05-26
E-009 notice ASM-02 info record open — 2026-05-26
E-010 notice ASM-03 info record open — 2026-05-26
E-011 notice Q-AUDIO-001 info record closed — 2026-05-26
E-012 decision Production test scope: system-level only, not sub-assembly re-test info record closed — 2026-05-26
E-013 decision ESH10000539 R1→R2 BOM change disposition info record closed — 2026-05-26
E-014 decision Audio test (fe_J6_audio.yaml) limit derivation from full tolerance stack info record closed — 2026-05-26
E-015 decision fe_Jx_pwr.yaml limit derivation — 5V_DIV / 12V_DIV / GND from divider tolerance stack info record closed — 2026-05-26
E-016 decision fe_J9_pwr.yaml limit derivation — VMON / HOST_V windows from rail spec, ADC chain (ADS7828/AD5593R) and MPIO chain info record closed — 2026-05-26
E-017 decision fe_J9_rs485.yaml limit derivation — VMEAS windows from MAX491 V_OD + COM-08 chain accuracy info record closed — 2026-05-26
E-018 decision fe_J7_mpio_relay.yaml limit derivation — FE_MPIO loopback + RELAY-fabric (via TA patches) info record closed — 2026-05-26
E-019 decision fe_J5_fixed_load.yaml limit derivation — TA pullup + FE GND_SW + 200 K VMEAS-divider loading info record closed — 2026-05-26
E-020 decision fe_J5_mpio.yaml limit derivation — AD5592R loopback chain (Sparrow N-Top → FE pass-through → IDC N-Top → TA) info record closed — 2026-05-26
E-021 decision fe_J5_pwm.yaml limit derivation — ATMEGA4809 PWM through HiZ MPIO read at 4 V_SET levels info record closed — 2026-05-26
E-022 decision Test rig spec: FE↔TA GND-bridge relay (ESH10000589 `_RELAY0`) ON by default in production tests info record open — 2026-06-04
E-023 decision Split `fe_Jx_gnd` from `fe_Jx_pwr` — new sub-test is the only one with GND-bridge relay OFF info action open — 2026-06-04
E-024 notice fe_J8_active_load AL.01 root cause — TA decoder addresses were inferred off-by-one (FIXED in v1.0.255) warning action open — 2026-06-04
E-025 notice Maestro silently passes numeric measurements when `{{var}}` substitution fails — use sentinel dict warning action open — 2026-06-04
E-026 decision AL bench-test operating points: IDC 15 V / 0.4 A, Phoenix 15 V / 1 A info record open — 2026-06-09
E-027 notice RETRO: AL.05 over-drove IDC J8 at 2 A in v1.0.247–v1.0.262 — inspect cabling that ran those versions warning action open — 2026-06-09
E-028 notice Package-wide YAML schema drift: type: String/Numeric/Boolean should be lowercase info action open — 2026-06-10
E-029 decision PT-SIG.11 auto-scale clause covered by post-cal repeat-of-per-gain sweep (v1.0.316+) info record open — 2026-06-18