analog-spec-extract

Analog Spec Extract

Reads L1_DATASHEET.json (pin types, electrical specs) and L5_ADI_SPEC.json (analog-digital interface) to enumerate every analog block that needs transistor-level design, and produces a machine-readable spec.json for each.

⛔ HARD RULE — never silently emit empty block list (Wave 47, v0.120.1)

User directive (Wave 47): "EVERY ITEM IN DESIGN DOCUMENTS SHOULD BE IMPLEMENTED!!!! EVERY!!!"

The deterministic parts of this hard rule are now programs — run them, don't re-implement them in prose:

• 8-class analog keyword scan + L5-mapping — enforced by programs/analog_content_detected_must_emit_l5_check.py (the chip-AGNOSTIC grep over input_doc/*.txt + input/docs/*.txt for oscillator / ldo / bandgap / por / pull / esd / charge_pump / trim, with per-hit negation awareness, lives there). For each detected class emit at least one minimal analog_blocks[] entry:

  {"name": "<descriptive>", "type": "<class>", "spec": "<one-line>",
   "evidence": "<file>:<line>", "implementation_status": "needs_design_work"}
  

  then run the gate against <project_dir>.
• Forbidden analog/A0_skip_decision.json top-level skip — enforced by programs/analog_a0_skip_forbidden_check.py. Replace any skip with analog/A0_implementation_status.json (per-block A1-A8 status) OR set L5.analog_blocks_detected=false when the keyword scan PASSes empty.

A1 (this skill) PASS criterion is keyword-grep cleanliness, not human judgment that "the chip looks digital".

Residual LLM judgment (not a program): the keyword scan is a recall floor, not a complete detector — recognising a NON-keyword analog block (a custom sensor-readout front-end described only functionally, with no token in the 8-class list) is exactly where your judgment is needed. Catch what the grep misses and add it to analog_blocks[] anyway.

Spurious-block flip-side (cross-ref → analog-topology-select, #466B): the recall floor also OVER-fires. A candidate emitted only because a product-name keyword in L1 matched a class — with no spec ever bound (spec == null) — is presumed spurious and must be confirmed against the L5 type enumeration (the "N analog blocks" count sentence and/or the Block A/B table headers) before A2 spends any sizing compute. Drop it if L5 doesn't enumerate that class; keep + spec-bind it if L5 does. A block's multiplicity (×N) must come from the block's OWN enumeration row, never a sibling block's evidence paragraph. The full sanity procedure + why_not_bucket_a rationale lives in analog-topology-select's "spurious-block sanity check" capture; do not re-implement it here as a deny-list — whether a name-only block is real requires reading L5, not a static rule.