Smoke test entry created from the ETT00000001 bootstrap session. Will be withdrawn at the end of verification.

Second smoke-test entry, linked to MS-001 via linkedEntityType=milestone at create time.

Discovery during smoke test: please_entry_update does NOT accept linkedEntityType / linkedEntityId — linkage is a CREATE-TIME-ONLY operation. Confirmed via ToolSearch schema. The ETT_R0/CLAUDE.md template currently says "link at create time" which is correct.

Archive the now-retired Maestro workspace repo on GitHub:

1. Open https://github.com/esharpab/MJsMaestroRoot
2. Settings → Danger Zone → "Archive this repository"
3. Confirm

The repo's final commit (tombstone 67a6cd4) points readers at the new sibling layout (C:\Workspace\PLEASE\, C:\Workspace\PLEASE-projects\, C:\Workspace\MAESTRO-projects\). Archiving makes that final state read-only and signals to future visitors that the repo is intentionally frozen.

After archiving, do the follow-on TODO: delete the local C:\Workspace\Maestro\ folder.

After E-003 lands (the GitHub archive of esharpab/MJsMaestroRoot), delete the local folder:

Remove-Item -Recurse -Force C:\Workspace\Maestro

The folder currently contains only:

• .claude/ (local agent state, gitignored)
• .git/ (the MJsMaestroRoot repo — already pushed + soon archived)
• .gitignore
• the tombstone CLAUDE.md

Nothing valuable is on the disk side that isn't already on GitHub. After deletion, C:\Workspace\ will hold only the three sibling trees (PLEASE, PLEASE-projects, MAESTRO-projects).

STATUS 2026-06-12 — two new asks from Mårten + Confluence BOM page v3 updated.

Mårten replied with two follow-up asks today:

Ask A — Accordion-box (ESH10000631) datasheet with port/LED/connector detail

Per Mårten's email: "Gällande Accordion-boxen vi använder (med Fixturelink, 9-DSUB-kontakterna), finns där något separat datablad med info likt det som ni har för Accordion A2 Lite [...]. Jag har inte hittat någon dokumentation över Sparrowboxen specifikt där portar etc. beskrivs. ESH10000633 beskriver hela 'Sparrow System' och innehåller inte beskrivning av kontaktinterface, LEDar etc för Sparrboxen."

He pointed at the existing Accordion A2 Lite datasheet (on help.esharp.se) as the template format he wants matched.

Ask B — BOM appendix on the CE Declaration

Per Mårten's follow-up: "Är det möjligt att lägga in artikelnummer för de parter som ingår i Sparrow-systemet (ESH10000633) i CE-deklarationen, exempelvis som på en andra sida som attachment? Environment här har bett mig om ett dokument där det framgår vilka parter som ingår i CE-deklarationen efter att jag skickat BoM och CE-deklaration separa till dem."

Axis Environment needs a single document showing which parts are covered by the CE declaration (they have the BoM and the CE separately and want them tied together).

Martin's response — Confluence Sparrow Hardware BOM page updated to v3 (2026-06-12 08:15)

URL: https://esharp.atlassian.net/wiki/spaces/Axis/pages/474808321/Sparrow+Hardware+BOM (now v3)

Content of v3 (verified via PDF export):

1. Sparrow (ESH10000633) — BOM tree — full hierarchy showing E-Sharp vs External per row (Accordion A2 + its 4 sub-modules; FE+AL ASSY + its 3 sub-modules; USB PD PSU; coax; cable; charger; D-Sub cable). Explicit statement: "The E-Sharp parts are covered by the CE declaration."
2. E-Sharp Component Reference section with spec tables for:
   • ESH10000631 Sparrow Accordion A2 — product name, part number, platform, power input/consumption, network interface, aux USB, PoE ports (2× RJ45 + 1× Phoenix 2pol), Fixture Link DSUB 25p, HLCD, slots populated/free, dimensions, weight, compliance (CE, RoHS, REACH).
   • ESH10000636 Sparrow Fixture Electronics + Active Load — parallel table (Fixture Link, HLCD, Audio DSUB 9p, M2Active Load slot, etc.).
   • ESH10000582 USB PD 100W PSU — link to existing help.esharp.se page.
3. External Component Manufacturer Reference — Toocki TCT140-22 (charger) with EU/UK REPs, Toocki USB-C cable (EAN), Phoenix Contact 1656291 (D-Sub), plus E-Sharp internal items with cross-references.
4. Sub-tables for ESH10000637 (Alpha Wire 6716 + Phoenix 1754568 + Degson 15EDGK) and ESH10000614 (Samtec HLCD).
5. Authorized Representatives — Toocki products — EU (E-CrossStu) + UK (YH Consulting) addresses.

Remaining gaps vs Mårten's asks

Ask A — Accordion-box datasheet:

• ✅ Most spec content covered in the table
• ❌ LEDs not on the page — Mårten explicitly wrote "kontaktinterface, LEDar etc" verbatim. Highest-likelihood follow-up.
• ⚠️ Per-port labels missing (e.g. "ETH1 — Mgmt", "PoE-1 — Front") — only port types/counts shown
• ⚠️ Pinouts for DSUB 25p Fixturelink + DSUB 9p Audio not present — can reference Sparrow Hardware Datasheet rather than duplicate
• ⚠️ Product photo / panel layout not in the rendered PDF — may be embedded in Confluence view
• ⚠️ Operating conditions (temp/humidity) one-row addition

Ask B — CE Declaration coverage:

• ⚠️ Confluence page shows the coverage clearly but Mårten asked for a single document (PDF Axis Environment can archive)
• ❌ No PDF coverage document produced yet — two options:
  • (A) Extend the existing CE Declaration PDF (currently 2 pages, signed Daniel Rhodin 2026-01-20) with the BOM tree as page 3 — Daniel re-signs. One document, one signature.
  • (B) Issue a separate "CE Declaration Coverage Statement" PDF that references the original CE doc + lists the parts in scope. Lighter weight, no re-sign if framed as clarification.

Next actions

• Confluence v4 pass: add LED inventory + per-port labels in the Notes column. ~20 min.
• Generate CE coverage PDF deliverable (option A preferred per Mårten's literal wording). Draft to land under attachments/E-005/ as markdown → PDF → Daniel signs.
• Wait on Mårten's MD format reply — still in his court (no change from 2026-06-08 status).

STATUS 2026-06-08 — RoHS accepted by Axis; MD now in Axis's court.

Mårten replied 2026-06-08 confirming receipt:

Tack så mycket. Jag såg CE-deklarationen och den bör räcka för RoHS. Återkommer angående materialdeklaration, ska höra med komponentingenjören här.

What this means:

• ✅ RoHS deliverable is closed. Master CE Declaration for ESH10000633 accepted as covering RoHS for the whole stack (the "placed on market" doctrine argument worked).
• ⏳ MD deliverable is in Axis-side investigation. Mårten will check with Axis's component engineer about what MD format their PLM actually needs. Ball is in his court now — we wait.

Implication for our open work:

• Toocki path for X3/X4 — Mårten handles directly (still).
• Our remaining own-side work shrinks to: X7 docs pack (ESH10000636 — see E-012 for the Active Load MD), X8 datasheet (Accordion A2 — now in progress via Confluence v3 per 2026-06-12 update above), X9-13 material spec (3D-printed standoffs), and the MES BOM data-quality TODOs (separate, can do anytime).

Next action: none on Axis until Mårten replies on MD format. Could opportunistically start E-012 (Active Load Confluence MD) which doubles as X7 datasheet, but no Axis-side blocker now.

STATUS 2026-06-03 — Mårten reply + CE Declaration delivered.

Mårten skickade två uppföljnings-mejl 2026-06-03 med tre asks:

1. ESH10000582 (X2, USB PD 100W PSU) — MD/RoHS
2. "Agent Q2 (Sparrow-boxen)" — interpreted as ESH10000633 (Sparrow Complete); MD/RoHS/datasheet
3. "Accordion-boxen" — interpreted as ESH10000631 (Sparrow Accordion A2, X8); MD/RoHS/datasheet

Mårten bekräftade också att han kontaktar Toocki direkt för X3 (TCT140-22) och X4 docs → off our plate.

Customer-side nomenclature note: "Agent Q2" är Axis interna produktnamn för systemet som integrerar ESH10000633. "Agent" finns även som en connector-designator på Sparrow FE-kortet (J10-15/13/16/14 i ESH10000540 R3) — coincidence vs. design-intent oklart, men compliance-frågan är på ESH10000633-nivå.

BOM-bekräftelse via MES (2026-06-03): ESH10000633 R1 top-level BOM innehåller direkt både ESH10000582 R1.0 (X2) och ESH10000631 R1 (X8). ESH10000631 R1 BOM innehåller ESH10000182 R0 (Accordion A2 Bare, X1). Tre items i scope ligger alltså på tre olika BOM-nivåer av samma produkt.

Juridisk grund: Per EU "placed on market"-doktrin täcker master CE Declaration för ESH10000633 RoHS för alla sub-assemblies som inte säljs separat — inklusive ESH10000582 och ESH10000631. Sub-assembly-nivå behöver ingen egen CE för att vara compliant. ✅ Customer-accepted 2026-06-08.

Martin replied 2026-06-03:

• Bifogade CE Declaration ESH10000633 (signerad Daniel Rhodin / CEO 2026-01-20, täcker EMC 2014/30/EU + RoHS 2011/65/EU)
• Pekade på NY Axis-specifik Help Center URL-mönster (JSM portal, ej offentlig):
  • Landing: https://esharp.atlassian.net/helpcenter/axis/
  • Artikel: https://esharp.atlassian.net/helpcenter/axis/portal/34/article/183566337
• Frågade Mårten vilken MD-nivå Axis PLM behöver (system-level vs per item; IPC-1752A format eller egen mall) — viktigt att veta innan vi gör MD-arbetet, formatet är inte trivialt att göra om

Help Center URL-pattern uppdaterad — två mönster finns nu:

• Public: help.esharp.se/e-sharp-helpcenter/<esh-code>-<slug> (t.ex. ESH10000582)
• Axis JSM portal: esharp.atlassian.net/helpcenter/axis/portal/34/article/<id> (Axis-customer-only)

Välj pattern utifrån publik: offentlig för marknadsföring, JSM-portal för kund-specifika docs.

STATUS 2026-05-28 — Partial delivery sent to Axis. Confluence page updated with the per-item table + sub-tables (X1 ESH10000637 and X5 ESH10000614). Customer-facing link sent to Axis.

Delivered URL: https://esharp.atlassian.net/wiki/spaces/Axis/pages/474808321/Sparrow+Hardware+BOM (Confluence space Axis, page id 474808321).

Original request from Axis (Swedish, verbatim):

"Jag skulle behöva datablad, RoHS och materialdeklaration för samtliga artiklar. Dessa behövs för att kunna läggas upp i vårt PLM-system. Om det är något ni köper in går det bra med leverantörens MPN så den dokumentation går att få den vägen. För artiklar hos er undrade jag även om det går att slå upp dessa någonstans på er hemsida eller liknande."

"Går det att slå upp dessa parter på er hemsida eller liknande? Har inte funnit mycket info när jag sökt efter dem på er hemsida men ni kanske inte gjort sådant synligt. Uppskattar all hjälp jag kan få och kommer som jag nämnde behöva artikelnummer med RoHS, datablad och MD för dem. I de fall ni köper in parterna från andra leverantörer (kablarna exempelvis) får du om möjligt gärna dela med dig av de MPNsen"

Deliverable per item (3 documents): datasheet, RoHS declaration, material declaration.

Item-handling rules (per Axis):

• Purchased items — send MPN only; Axis fetches docs from the supplier.
• E-Sharp in-house items — provide the 3-document pack directly, OR point Axis at a self-serve lookup. Help-center pattern confirmed: https://help.esharp.se/e-sharp-helpcenter/<eshcode>-<slug>. So far only X2 confirmed to have a page (datasheet + manual; no compliance docs yet).

Scope = top-level Sparrow BOM (ESH10000633 R1, 9 items):

MPN findings (2026-05-28 — physical box / spool inspection + sub-BOM expansion):

EPN1000786 — Phoenix Contact 1656291 (VS-25-DSUB-20-LI-1.0) ✅ (from MES record)

EPN1000677 — Toocki TCT140-22 (5-port GaN charger):

• Brand: Toocki · Name: "GaN Quick Charger" · Model No.: TCT140-22
• Brand owner: Shenzhen Toocki Network Technology Co., Ltd. (Bantian Street, Longgang District, Shenzhen)
• Actual factory: Shenzhen Ezreal Technology Co., Ltd. (PingHu street, Longgang District, Shenzhen, 518111, China)
• Carton/lot code: TC0372Z-2 / Made in China
• Specs: 100-240V 50/60Hz 2.5A in; 3× USB-C @ 100W max ea; 2× USB-A @ 60W max ea; 140W total; 1.5 m EU AC cable; ~400 g
• Compliance markings on box: CE, FCC, WEEE, RoHS ✅
• UK REP: YH Consulting Limited, Office 147 Centurion House, London Road, Staines-upon-Thames, Surrey, TW18 4AX
• EU REP: E-CrossStu GmbH, Mainzer Landstr. 69, 60329 Frankfurt am Main
• Contact: www.toocki.com · +86 0755-89399212
• Path for Axis: request RoHS / CE / FCC / REACH pack from EU REP (E-CrossStu) or UK REP (YH Consulting), citing MPN TCT140-22. Mårten handles directly (2026-06-03).

EPN1000678 — Toocki 100W USB-C cable 1m:

• Brand: Toocki · CN product name: 心悦 C-C100W 数显数据线 1m 黑色
• Carton/lot code: TC0450Z / Made in China · EAN-13: 6975600780260
• Manufacturer: Shenzhen Toocki Network Technology Co., Ltd.
• Compliance markings visible on back: RoHS ✅ — no CE/FCC visible (recommend second photo to confirm).
• Path for Axis: request docs from Toocki citing EAN + carton code + CN product name. Mårten handles directly (2026-06-03).

ESH10000582 — USB PD 100W PSU (in-house, X2):

• Help-center URL: https://help.esharp.se/e-sharp-helpcenter/esh10000582-usb-pd-100w-psu
• Contains: Product Brief, Datasheet, Manual, Connector pinout — missing: standalone RoHS / REACH / MD section.
• Publicly accessible (no login).
• RoHS coverage 2026-06-03: included under parent CE Declaration for ESH10000633. Axis-accepted 2026-06-08.

ESH10000637 — Sparrow PSU Power Cable 1m (in-house, X1) — sub-BOM: | Component | Part # | Notes | |---|---|---| | Wire — black | Alpha Wire 6716 BK001 | 16 AWG (1.30 mm²) mPPE, 1-conductor unshielded, EcoWire family, UL 11028 105 °C 600 V, cULus E50552 · CE · UKCA · EU/China RoHS ✅, Made in USA. Confirmed via spool photo 2026-05-28. | | Wire — red | Alpha Wire 6716 RD001 | Same series + specs as 6716 BK001, red jacket. Inferred from Alpha Wire's standard color-suffix convention; confirmed by distributor catalog listings (Newark 58R1675, Anixter, Lapp Tannehill, RS Components). Verify spool label says RD001 (not RD005 etc. — same part, different spool length). | | Connector 1 | EPN1000249 | Phoenix Contact 1754568 (MSTB series, 2POS 5.08 mm terminal block plug). MES record currently has LCSC catalog code C5477418 in description — needs MES update. | | Connector 2 | EPN1000703 | Degson Electronics 15EDGK-3.81-02P-14-00A(H) — 2POS 3.81 mm female pluggable |

⚠️ Neither Alpha Wire 6716 BK001 nor 6716 RD001 is listed in the MES BOM for ESH10000637 — MES BOM only lists the 2 connectors. Two real consequences: (a) docs pack must add the wire manually; (b) BOM data-quality TODO — wire stock should be added as BOM line items.

Path for Axis: the X1 cable docs pack consists of (1) Alpha Wire 6716 datasheet + RoHS from alphawire.com (single datasheet covers both colors — identical specs), (2) Phoenix Contact 1754568 datasheet/RoHS from phoenixcontact.com, (3) Degson 15EDGK datasheet/RoHS. E-Sharp assembles + signs as the "cable assembly" pack.

ESH10000614 — Sleeved Coax Cable HLCD-20-40 (in-house, X5) — sub-BOM: | Component | Part # | Notes | |---|---|---| | Coax cable assembly | EPN1000718 | Samtec HLCD-20-40.00-TRS-TLS-4 — Samtec HLCD high-density low-crosstalk differential coax assembly. RoHS / REACH / IMDS available from samtec.com. | | Connector head | ESH10000615 | "Kontakthuvud HLCD-20-40.00-TRS-TLS-4". Reclassified as externally built (per E-008 2026-05-11). Manufacturer/MPN not in MES — needs supplier-records lookup. | | Threaded insert | EPN1000319 | 3DJake RUT-GE-M2x04-001 (M2 × 4 mm) | | Screw | EPN1000141 | M2 × 4 mm — generic; MPN not in MES | | Washer | EPN1000195 | M2.5 — generic; MPN not in MES |

Path for Axis: the X5 cable docs pack consists of (1) Samtec HLCD-20-40.00-TRS-TLS-4 datasheet/RoHS/IMDS from samtec.com, (2) 3DJake threaded insert spec, (3) generic hardware declaration for the M2 screw + M2.5 washer (or upgrade MES to record actual supplier), (4) E-Sharp connector head ESH10000615 — supplier docs pending.

Open questions:

1. Recover Toocki MPNs — done.
2. Confirm CE/FCC marking on EPN1000678 (cable) — Mårten handles directly.
3. Help-center pages for the other in-house items? Test URL pattern for X1, X5, X7, X8. (X7 + X8 partially addressed via Confluence v3 2026-06-12 — Axis-specific Confluence space rather than public help-center.)
4. Compliance docs on help-center pages — add Compliance section to each (long-term answer to "kan slå upp på hemsidan").
5. Confirm red wire variant on X1 — high-confidence match to 6716 RD001; spool-label glance to verify the suffix is 001 (not 005 / 002).
6. Confirm supplier/MPN for ESH10000615 connector head (X5 sub-BOM) — externally built but no MPN recorded in MES.
7. MD format Axis PLM accepts — IPC-1752A nivå A/B/C? IEC 62474? Egen Excel-mall? På system-nivå eller per item? Status 2026-06-08: Mårten investigating internally with Axis component engineer; await reply.
8. 2026-06-12 NEW: LED inventory + per-port labels for ESH10000631 — for Confluence v4 + X8 datasheet completion per Mårten's verbatim "kontaktinterface, LEDar etc" ask.
9. 2026-06-12 NEW: CE Declaration coverage PDF — Axis Environment needs single-document deliverable. Two options: (A) extend existing CE Declaration to 3 pages with BOM appendix, Daniel re-signs; (B) issue separate Coverage Statement PDF referencing the existing CE.

Follow-on TODOs (separate):

• MES BOM gap (X1): add Alpha Wire 6716 BK001 + 6716 RD001 as BOM line items on ESH10000637. Requires MES UI.
• MES part-record updates:
  • EPN1000249: set manufacturerName=Phoenix Contact, manufacturerPartNumber=1754568 (currently MES has only C5477418 LCSC reference in description).
  • EPN1000141 / EPN1000195: record actual screw/washer manufacturer + MPN.
  • EPN1000677 / EPN1000678: update with MPN / EAN / actual-manufacturer info (per box inspection).
  • All require MES UI (no write tool from here).

Partial response sent to Axis (2026-05-28):

• Confluence page: https://esharp.atlassian.net/wiki/spaces/Axis/pages/474808321/Sparrow+Hardware+BOM
• X1 — Alpha Wire 6716 (16 AWG mPPE, RoHS) in black + red + Phoenix Contact 1754568 + Degson 15EDGK — E-Sharp will assemble docs pack
• X2 — Datasheet self-serve at https://help.esharp.se/e-sharp-helpcenter/esh10000582-usb-pd-100w-psu (RoHS / MD on request)
• X3 — Toocki TCT140-22 — request docs from EU REP E-CrossStu GmbH or UK REP YH Consulting Limited
• X4 — Toocki cable, EAN 6975600780260 (carton TC0450Z) — request docs from Toocki; flag CE/FCC unclear
• X5 — Samtec HLCD-20-40.00-TRS-TLS-4 + 3DJake inserts + connector head (supplier TBC) + generic hardware — E-Sharp will assemble docs pack
• X6 — Phoenix Contact 1656291 (D-Sub cable)
• X7, X8, X9-13 — E-Sharp in-house items, "preparing docs pack, will revert with timeline"

Delivery vehicle: Confluence page in the Axis customer space (esharp.atlassian.net/wiki/spaces/Axis).

Requested by: Axis (external) Purpose: load into Axis's PLM system (RoHS / REACH / material compliance)

There is a .git/ repo at C:\Workspace\ (workspace root) that:

• Has origin = https://github.com/esharpab/hardware-ESH10000540-R3.git (wrong — that URL is for the ESH10000540 R3 project).
• Tracks files across PLEASE\, PLEASE-projects\, MAESTRO-projects\, and the deprecated Electro-Engineering\.
• Confuses sub-repos: from inside any project repo that doesn't have its own .git/, git commands resolve to this parent and report misleading status (this is what tripped us up during the ESH10000158 R6 bootstrap on 2026-05-28 — see ETT00000002 / E-025).

Likely cause: stray git init or git clone was run at the wrong level at some point. Probably a hangover from the pre-migration Electro-Engineering layout.

Action: verify nothing essential lives only in this parent repo (its commit history references "End-of-session updates" — confirm these are duplicated in proper per-project repos), then delete C:\Workspace\.git\. The per-project repos under PLEASE-projects\ and MAESTRO-projects\ are the authoritative repos and are unaffected.

Verification commands:

cd C:\Workspace
git log --oneline -20
git remote -v
git ls-files | head -20

Low priority but should be done before another bootstrap, otherwise the same nested-git confusion will recur.

Internal e-mail from team asking sharpisar to fill in what a new hire needs as introduction across our systems/ways of working.

Confluence page: https://esharp.atlassian.net/wiki/spaces/ESIN/pages/476708872/Genomg+ng+av+system+arbetss+tt

My planned contributions:

• Help to build Sparrow units and test them (assembly + test walkthrough for new hires).
• Help with Sparrow test station (intro to the station, how to run tests, common issues).

Source: team-wide e-mail received 2026-05-29.

Linked to MS-002.

Deadlines:

• Internal review: 2026-06-05 (Fri)
• Submission to KTH: 2026-06-08 (Mon)

Input requested from colleague (paste, 2026-06-01)

Hej Martin, Vi närmar oss inlämning av KTH-anbudet (deadline 8 juni, intern review 5 juni). För att vi ska kunna maxa mervärdes-poängen och få ihop CV + bilagor behöver jag följande från dig:

1. On-site i Stockholm Hur mycket tid kan du tänka dig att jobba hos KTH? Räcker det med 1 dag/vecka, eller är 2 möjligt? (Påverkar 500 SEK i mervärde — krävs att vi kryssar "ja" på 4.1.3.3 b.)

2. Konkreta leveranser per Synopsys-roll 1–2 punkter per roll med produktnamn/projekt + vad du konkret levererade. T.ex. "HAPS-100 multi-FPGA-baksida, ledde SI på X SERDES-länkar, släppt 20XX." Behövs för att mervärdes-bedömarna ska kunna sätta full pott på "komplexa högintegrerade system" (annars riskerar vi 200 i stället för 500 SEK avdrag).

3. Felsökningsanekdot En konkret incident vi kan lägga in i CV: symptom → vad du hittade → vad du fixade → hur du verifierade. 2–3 meningar räcker. Mervärdes-poängen "felsökning/optimering i komplexa system" bedöms direkt från CV.

4. Verktyg — bekräfta/komplettera

• SI/PI-simulering: använder du HyperLynx eller Sigrity vid sidan av Ansys SIWave/HFSS?
• PCB-verktyg: Cadence eller Altium någon gång, eller bara Xpedition/PADS?
• Versionshantering: Git, Perforce, annat?

6. Designuppgift PCB-stack (Bilaga, max 1 A4) KTH vill ha förslag på hur PCB-stackar (limmade kretsar mellan två vertikala PCB) ansluts till huvudkort. Behöver en skiss + några rader text från dig — 1–2 timmar bör räcka, jag polerar texten sen. Hela uppgiften nedan.

7. Två referensuppdrag (2021 eller senare) KTH kan komma att begära två referenser med liknande profil. Förslag på personer från Synopsys-tiden (eller annan)? Vi tar kontakt med dem för samtycke först.

Punkterna 2, 3 och 6 är de viktigaste — om något ska prioriteras är det dessa. Säg till om du behöver hjälp att formulera, jag kan ta första utkast och du finputsar.

My checklist

• (1) Decide on-site days/week (1 vs 2) — answer 4.1.3.3 b
• (2) Synopsys-roller: 1–2 konkreta leveranser per roll (produkt + vad jag levererade + år) ← prio
• (3) Felsökningsanekdot för CV: symptom → fynd → fix → verifiering ← prio
• (4) Bekräfta verktygslista: HyperLynx/Sigrity? Cadence/Altium? Git/Perforce?
• (6) PCB-stack-bilaga: skiss + några rader text (1 A4, 1–2 h) ← prio
• (7) Föreslå 2 referenter (Synopsys-tiden eller annat), 2021+

Existing BOA_CB_CLK_B2B stencil appears to have square holes for the connectors — needs verification and likely replacement.

Actions:

1. Pull the existing stencil and visually verify the connector apertures are square (vs the round/shaped apertures that should be there).
2. Cross-check against the connector footprint(s) in the design files to determine what aperture shape the connectors actually need.
3. If the stencil is wrong: order a new one — latest Friday 2026-06-12 (MS-003).

Why blocking by 06-12: stencil lead time + need it in hand before the next build pass that uses BOA_CB_CLK_B2B.

Ask from colleague (Swedish, verbatim):

Hej Martin!

Här kommer länk till de som vi tidigare använt till E-Box assembly: https://www.digikey.se/sv/products/detail/sparkfun-electronics/10363/9657941

Kablarna ovan klipper vi i två delar.

Om det är möjligt att hitta en kompatibel som inte har lika hög kontakt hade det varit toppen, då den just nu är så pass hög att kabeln kläms mot sig själv när locket går på.

När vi hittat en som funkar ska vi återkoppla till Johan så han kan beställa.

Bara hör av dig om du har några frågor.

Tack för hjälpen!

Summary (EN):

• Current part: SparkFun 10363 (Digikey 9657941), used in E-Box assembly. The cable is cut into two pieces.
• Problem: the connector is too tall — when the lid closes the cable gets pinched against itself.
• Goal: find a compatible cable with a lower-profile connector.
• When a candidate is identified, loop in Johan so he can place the order.

Action:

1. Identify exact electrical/mechanical spec of the existing 10363 connector (pitch, pin count, gender, current rating) from the Digikey page.
2. Search Digikey / Mouser / Farnell for compatible alternatives with a lower mating height.
3. Confirm with colleague + Johan before ordering.

No hard deadline mentioned.

Write a markdown document describing the Active Load and upload it to Confluence.

Likely target product: ESH10000636 (Sparrow ASSY Fixture Electronics with Active Load) — X7 in the ESH10000633 Sparrow BOM. Confirm scope when picked up: is the document about the whole FE+Active-Load assembly, or specifically the Active Load circuitry/principles?

Cross-link to E-005 (Axis BOM): ESH10000636 (X7) is currently flagged as "pending — help-center page TBC" in the Axis docs pack. A clean MD description of the Active Load on Confluence could be reused as the X7 datasheet / product brief deliverable when Axis next pushes for the missing in-house docs packs.

Open before starting:

• Confluence space — public marketing space or Axis customer space (esharp.atlassian.net/wiki/spaces/Axis/)?
• Audience — internal engineering, customer (Axis), or both?
• Scope — pure circuit description, or full product brief (including mechanical, interfaces, use case)?

Source material to pull from:

• ESH10000636 / ESH10000540 (FE PCBA, R3) project repos
• Sparrow Hardware Datasheet v3 (ESH10000633_..._R1/01_ProductSpec/) — likely has an Active Load section to lift / adapt

KTH called for the 45-min interview per FFU 4.1.3.2 c, and the interview was completed 2026-06-10.

Outcome (engineer's read):

• Technical evaluation: strong. Direct quote from KTH: "impressive CV."
• Live wedge: on-site time in Stockholm. Engineer's assessment is that the on-premises frequency is the remaining concern KTH may weigh.

Recap of what was committed in the submission:

• "Ja" on 4.1.3.3 b → 500 SEK mervärde discount booked into the comparison price.
• Quantitative commitment per the colleague handoff (E-008): 2 dagar varannan vecka, flexibla (~1 dag/vecka average).
• Travel cost analysis from the executive summary: ~130 SEK/h impact at full on-site frequency → ~1 470 SEK/h net after Skåne↔Stockholm.
• LOU + FFU 6.9 prevent re-pricing after submission, so the timpris is locked once awarded.

Three framings prepped for follow-up correspondence:

1. Elastic model — baseline 2 dagar varannan vecka, peak (2-4 day extended stays) during design reviews, board bring-up, integration weeks. Average normalises to ~1 dag/vecka with the peaks aligned to physical milestones.
2. Probe what their actual concern is rather than negotiating volume:
   • Coordination / unblocking → offer high-bandwidth async (daily standup, dedicated channel, 24 h response window)
   • Lab access / co-location → schedule travel around hardware milestones
   • Cultural / team-fit → longer onboarding period at higher presence
3. Reframe the value — most design and simulation work runs from anywhere (Xpedition + Vivado + Ansys via Git); on-site is for the things that genuinely need physical presence (reviews, debug, hand-over). Counters the "more is better" instinct without conceding rate.

Anchor argument: the committed 2 dagar varannan vecka is what's on TendSign — that's the baseline. Any extra presence is offered as a bonus / elastic peak, not a renegotiation downward.

Structural disadvantage to be aware of: Stockholm-based consultants can offer 3+ days/week at the same timpris with no travel penalty. If KTH evaluates on volume alone, that's the corner case where Martin loses. The defence is the technical-strength + elastic-model combination.

Next actions:

• If KTH sends a follow-up question on on-site frequency → respond with framing (1) or (2) depending on what their email signals about the underlying concern.
• Decision timeline: unknown until KTH discloses. Track here.
• Award notification → MS-002 closes (success) or this entry closes (loss + learnings captured).

Cross-references:

• E-008 (this project, closed 2026-06-08) — the original submission + input-package delivery to colleague.
• MS-002 (this project) — KTH-papers milestone, currently overdue / open.