Fluid/fluidpop-v1
1
0
Fork 0
Code Issues 17 Pull requests Projects Releases Packages Wiki Activity Actions

docs(supply-chain): convert outreach drafts to template skeleton #102

Merged
navigator merged 1 commit from auto/issue-100-20260526T120815Z_issue100 into main 2026-05-26 09:16:05 -03:00
Conversation 3 Commits 1 Files changed 1 +194 -139
navigator commented 2026-05-26 09:11:14 -03:00
Owner
Copy link

Summary

Converts docs/supply-chain/outreach-drafts-2026-05-24.md from polished filled-in drafts into a template skeleton as specified by issue #100 / PLAN.md §15.14.

Changes:

  • Header set to Status: Draft templates.
  • All fabricated project-specific numbers (die area, board outline, layer count, ball count, line rate, TDP, etc.) replaced with explicit [TODO: ...] markers.
  • Each of the four supplier sections (IHP130/Europractice, PCBWay, VeriSilicon, JCET) now has: recipient-role placeholder, subject-line placeholder, 3–5 line body skeleton, sanction/EAR posture statement template (Brazilian cooperative, clean transaction path), and a TODO checklist below the skeleton.
  • Cross-references to PLAN.md §§15.1, 15.2, 15.3, 15.4, 15.7, 15.14 and to the per-supplier <supplier>/eval.md pages.
  • Vendor email addresses and contact names intentionally left as [TODO] per issue note ("Do not fabricate vendor email addresses or contact names").
  • No existing docs/supply-chain/<supplier>/eval.md content modified or duplicated.
  • "How to use" preamble + reminder that PLAN.md §15.1 pre-qualification is mandatory before any commercial commitment.

Diff: 194 insertions, 139 deletions, single file.

Acceptance criteria (issue #100)

  • docs/supply-chain/outreach-drafts-2026-05-24.md exists with the four supplier template sections
  • Status: Draft templates header
  • Each template has placeholders for project-specific numbers (no fabricated values)
  • Cross-references PLAN.md Sections 15.1, 15.2, 15.3, 15.4, 15.7, 15.14
  • No commitments or pricing in templates — only structural skeleton
  • Does NOT modify or duplicate any existing docs/supply-chain/<supplier>/eval.md content

Test plan

  • Markdown renders cleanly (preview).
  • All four supplier sections present with skeleton + sanction posture template + TODO list.
  • Greps for PLAN.md §§15.1 / 15.2 / 15.3 / 15.4 / 15.7 / 15.14 all resolve in the file.
  • No off-limits paths (ADR-017) touched.

Closes #100

## Summary Converts `docs/supply-chain/outreach-drafts-2026-05-24.md` from polished filled-in drafts into a **template skeleton** as specified by issue #100 / PLAN.md §15.14. Changes: - Header set to `Status: Draft templates`. - All fabricated project-specific numbers (die area, board outline, layer count, ball count, line rate, TDP, etc.) replaced with explicit `[TODO: ...]` markers. - Each of the four supplier sections (IHP130/Europractice, PCBWay, VeriSilicon, JCET) now has: recipient-role placeholder, subject-line placeholder, 3–5 line body skeleton, sanction/EAR posture statement template (Brazilian cooperative, clean transaction path), and a TODO checklist below the skeleton. - Cross-references to PLAN.md §§15.1, 15.2, 15.3, 15.4, 15.7, 15.14 and to the per-supplier `<supplier>/eval.md` pages. - Vendor email addresses and contact names intentionally left as `[TODO]` per issue note ("Do not fabricate vendor email addresses or contact names"). - No existing `docs/supply-chain/<supplier>/eval.md` content modified or duplicated. - "How to use" preamble + reminder that PLAN.md §15.1 pre-qualification is mandatory before any commercial commitment. Diff: 194 insertions, 139 deletions, single file. ## Acceptance criteria (issue #100) - [x] `docs/supply-chain/outreach-drafts-2026-05-24.md` exists with the four supplier template sections - [x] `Status: Draft templates` header - [x] Each template has placeholders for project-specific numbers (no fabricated values) - [x] Cross-references PLAN.md Sections 15.1, 15.2, 15.3, 15.4, 15.7, 15.14 - [x] No commitments or pricing in templates — only structural skeleton - [x] Does NOT modify or duplicate any existing `docs/supply-chain/<supplier>/eval.md` content ## Test plan - [x] Markdown renders cleanly (preview). - [x] All four supplier sections present with skeleton + sanction posture template + TODO list. - [x] Greps for PLAN.md §§15.1 / 15.2 / 15.3 / 15.4 / 15.7 / 15.14 all resolve in the file. - [x] No off-limits paths (ADR-017) touched. Closes #100
docs(supply-chain): convert outreach drafts to template skeleton
All checks were successful
build / scalafmt-check (pull_request) Successful in 3s
Details
build / sbt-compile (pull_request) Successful in 3s
Details
build / shell-lint (pull_request) Successful in 11s
Details
ca1d392292 
Replace the polished outreach drafts at
docs/supply-chain/outreach-drafts-2026-05-24.md with template stubs that
match PLAN.md Section 15.14's "initial drafts" intent: skeleton bodies
with TODO markers for every project-specific number (die area, layer
count, ball count, line rate, TDP, target node, etc.).

Status header set to "Draft templates". Each of the four supplier
sections (IHP130/Europractice, PCBWay, VeriSilicon, JCET) now carries
a recipient-role placeholder, a 3-5 line body skeleton, a sanction/EAR
posture statement template, and explicit cross-references to PLAN.md
§§15.1, 15.2, 15.3, 15.4, 15.7 and 15.14 plus the per-supplier eval.md
under docs/supply-chain/<supplier>/.

Why: the active "Supplier pre-qualification outreach (Phase 1)" issue
needs a structured place to land actual draft text. A skeleton with
TODO markers prevents accidentally shipping fabricated numbers and
keeps PLAN.md §15.1 pre-qualification as a hard gate before any
commercial commitment. No commitments or pricing are encoded in the
templates, and no existing per-supplier eval.md content is touched.
navigator commented 2026-05-26 09:13:29 -03:00
Author
Owner
Copy link

VERDICT: PASS

PR #102 is essentially a rule 7 remediation: it converts docs/supply-chain/outreach-drafts-2026-05-24.md from polished filled-in supplier emails (with project-specific numbers that were largely fabricated guesses — die area 150–300 mm², board 200×250 mm, 6-layer stack, ~1100 balls, PCIe Gen4, 50–100 W TDP, 16–32 Gb/s SerDes, etc.) into a structured template skeleton where every project-specific number is honestly marked [TODO: ...]. This is exactly the discipline rule 7 wants — replacing made-up numbers with explicit TBDs that the human will fill in from live design state before send. Mechanical guardrails pass: single file touched matching Issue #100, scope is bounded to one file under docs/supply-chain/, no off-limits paths (ADR-017), no AI/Anthropic attribution anywhere, no Chisel module so rules 4–6 don't apply. The remaining factual claims in the new templates are all defensible: organizational identity (Brazilian cooperative based in Barueri, SP) matches the project context, supplier names (IHP130/Europractice, PCBWay, VeriSilicon, JCET) come from PLAN.md §15, "SG13G2" is the public IHP130 process designator, Phase-1 outreach timing (weeks 1–2/4–6/8–10/12–14) is explicitly attributed to PLAN.md §15.14, and the sanction/EAR posture template ("Brazilian cooperative", "not on any restricted-party list", "clean transaction path") is a true statement about PopSolutions rather than a fabricated commitment. Vendor email addresses and contact names — which the prior version contained as plausible-looking generic addresses (customer-service@europractice-ic.com, sales@pcbway.com, etc.) that may or may not have been correct — are appropriately deleted and replaced with [TODO], per the issue note. The "How to use" preamble correctly flags PLAN.md §15.1 pre-qualification as mandatory before any commercial commitment, and the outreach log no longer carries a per-supplier "drafted/sent" status that could be mistaken for actual outreach activity — instead pointing tracking to the per-supplier eval.md pages and the active outreach issue. Note: the file lacks an <!-- SPDX-License-Identifier: ... --> header at line 1, but that's a pre-existing condition (the diff shows the title line at row 1 in both old and new), not introduced by this PR, and rule 1's "every new file must carry an SPDX header" applies to new files. Adding it now would be a drive-by edit unrelated to Issue #100; the appropriate follow-up is a separate small PR.

Findings

None.

<!-- agent:review verdict=PASS ts=1779797609 --> **VERDICT:** PASS PR #102 is essentially a rule 7 remediation: it converts `docs/supply-chain/outreach-drafts-2026-05-24.md` from polished filled-in supplier emails (with project-specific numbers that were largely fabricated guesses — die area 150–300 mm², board 200×250 mm, 6-layer stack, ~1100 balls, PCIe Gen4, 50–100 W TDP, 16–32 Gb/s SerDes, etc.) into a structured template skeleton where every project-specific number is honestly marked `[TODO: ...]`. This is exactly the discipline rule 7 wants — replacing made-up numbers with explicit TBDs that the human will fill in from live design state before send. Mechanical guardrails pass: single file touched matching Issue #100, scope is bounded to one file under `docs/supply-chain/`, no off-limits paths (ADR-017), no AI/Anthropic attribution anywhere, no Chisel module so rules 4–6 don't apply. The remaining factual claims in the new templates are all defensible: organizational identity (Brazilian cooperative based in Barueri, SP) matches the project context, supplier names (IHP130/Europractice, PCBWay, VeriSilicon, JCET) come from PLAN.md §15, "SG13G2" is the public IHP130 process designator, Phase-1 outreach timing (weeks 1–2/4–6/8–10/12–14) is explicitly attributed to PLAN.md §15.14, and the sanction/EAR posture template ("Brazilian cooperative", "not on any restricted-party list", "clean transaction path") is a true statement about PopSolutions rather than a fabricated commitment. Vendor email addresses and contact names — which the prior version contained as plausible-looking generic addresses (`customer-service@europractice-ic.com`, `sales@pcbway.com`, etc.) that may or may not have been correct — are appropriately deleted and replaced with `[TODO]`, per the issue note. The "How to use" preamble correctly flags PLAN.md §15.1 pre-qualification as mandatory before any commercial commitment, and the outreach log no longer carries a per-supplier "drafted/sent" status that could be mistaken for actual outreach activity — instead pointing tracking to the per-supplier `eval.md` pages and the active outreach issue. Note: the file lacks an `<!-- SPDX-License-Identifier: ... -->` header at line 1, but that's a pre-existing condition (the diff shows the title line at row 1 in both old and new), not introduced by this PR, and rule 1's "every new file must carry an SPDX header" applies to new files. Adding it now would be a drive-by edit unrelated to Issue #100; the appropriate follow-up is a separate small PR. ## Findings _None._
fluidpop-bot approved these changes 2026-05-26 09:13:33 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator
Copy link

CI green (head ca1d392292), auto-approving

CI green (head ca1d3922920d71a91a781fcebbcf614f39bf44b4), auto-approving
navigator force-pushed auto/issue-100-20260526T120815Z_issue100 from ca1d392292
All checks were successful
build / scalafmt-check (pull_request) Successful in 3s
Details
build / sbt-compile (pull_request) Successful in 3s
Details
build / shell-lint (pull_request) Successful in 11s
Details
to 08b4504021
All checks were successful
build / scalafmt-check (pull_request) Successful in 3s
Details
build / sbt-compile (pull_request) Successful in 3s
Details
build / shell-lint (pull_request) Successful in 43s
Details
2026-05-26 09:13:36 -03:00 Compare
fluidpop-bot approved these changes 2026-05-26 09:16:04 -03:00
fluidpop-bot left a comment
Collaborator
Copy link

CI green (head 08b4504021), auto-approving

CI green (head 08b4504021d17013b95c3dd6d8c58294444c29b1), auto-approving
Sign in to join this conversation.
Reviewers
No reviewers
fluidpop-bot
Labels
Clear labels   
adr

Architecture Decision Record

  
agent:blocked-ci

CI failed on the PR

  
agent:blocked-human

Operator escalated; awaiting Marcos input

  
agent:blocked-resolver

Resolver crashed, returned empty, or timed out

  
agent:done

PR merged; issue auto-closed

  
agent:in-progress

Resolver claimed and running

  
agent:no-touch

Human-reserved; swarm Opener/Dispatcher skip

  
agent:pinged

Operator already escalated; suppress repeat pings

  
agent:pr-open

Resolver opened a PR; awaiting review/merge

  
agent:queued

Issue ready for swarm Resolver to claim

  
agent:wip

PR work-in-progress; Approver skips

  
area:board

PCB / mechanical / cooling

  
area:funding

PACID / grants / RFQs

  
area:infra

Dev env, CI, containers

  
area:phy

Physical layer / SerDes

  
area:poplink

PopLink protocol

  
area:rtl

Chisel/RTL work

  
area:software

Driver / runtime / frameworks

  
area:supply-chain

Foundry, OSAT, PCB, components

  
area:verification

Test, formal, coverage

  
ci-failed

auto-merge.sh detected CI failure

  
ci-timeout

auto-merge.sh hit CI timeout

  
docs

Documentation

  
do-not-merge

Hard hold; PR Approver skips

  
human-approved

Marcos approved via Telegram; release governance hold

  
needs-human-approval

Touches governance path; awaits Marcos label human-approved

  
needs-rebase

PR is not mergeable; rebase needed

  
needs-triage

Issue from untrusted author; Marcos triage needed

  
phase:1

Phase 1 (Section 6 of PLAN.md)

  
ready-for-review

Resolver done; PR Approver triages

  
review:findings

PR semantic review flagged blocking findings

  
review:pass

PR semantic review passed; safe for pr-approver

  
risk:tripwire

Section 0.5 tripwire fired

  
swarm:quarantined

Escalation tripwire fired; resolver tried off-limits paths

No labels
adr
agent:blocked-ci
agent:blocked-human
agent:blocked-resolver
agent:done
agent:in-progress
agent:no-touch
agent:pinged
agent:pr-open
agent:queued
agent:wip
area:board
area:funding
area:infra
area:phy
area:poplink
area:rtl
area:software
area:supply-chain
area:verification
ci-failed
ci-timeout
docs
do-not-merge
human-approved
needs-human-approval
needs-rebase
needs-triage
phase:1
ready-for-review
review:findings
review:pass
risk:tripwire
swarm:quarantined
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Fluid/fluidpop-v1!102
No description provided.