docs(phy): partnership scoping doc + commercial RFQ template + outreach log #55

Merged

navigator merged 1 commit from auto/issue-6-20260525T173842Z_issue6 into main

2026-05-25 14:45:31 -03:00

navigator commented

2026-05-25 14:44:06 -03:00

Owner

Summary

Issue #6 asks for three concrete outreach artifacts on top of the
phy-options.md skeleton already in main:

docs/phy/partnership-scoping.md — formal scoping document for
USP-LSI, UFRGS GME, Unicamp CCS and IIT Madras. Covers project
context, target spec (with explicit <FILL> placeholders, no
pre-fabricated numbers), channel context for the water-cooled 8-chip
carrier, IP and licensing framing compatible with CHARRUA + AGPL
while protecting student publication rights, NDA / contracting flow,
and the funding caveat (subject to PACID).
docs/phy/rfq-commercial.md — RFQ template for Innosilicon /
VeriSilicon / Alphawave on SMIC N+2. Mandates an export-control /
FDPR chain-of-title attestation in Section 6; responses omitting
that section will not be evaluated. Covers deliverables, target
spec, RTL interface (PopLinkPHYIO), commercial terms requested,
and evaluation criteria.
docs/phy/outreach-log.md — append-only tracker keyed by
partner / vendor, state, reference doc, and owner. Hosts the F-T4
tripwire (all four PHY paths confirmed unavailable → escalate).

docs/phy/README.md index updated to list the three new files.

What this PR is NOT

It does not pre-populate vendor figures, partner positions, or cost
ranges. The phy-options.md skeleton mandates that those only appear
after a signed RFQ response or a signed scoping memo. All concrete
numbers in the new docs are <FILL> placeholders or cross-references
to PLAN.md and existing ADRs.
It does not send anything. The scoping doc and RFQ are templates;
they ship after legal review of the IP framing (Section 5) and the
export-control attestation language (Section 6).

Acceptance criteria mapping (issue #6)

Issue step	This PR
1. Channel-loss budget for 8-chip water-cooled carrier	`outreach-log.md` "Other workstreams" row pins it as pending board CFD outputs; `partnership-scoping.md` §4 lists the inputs we can share under NDA. Closes-out remains for board work to land.
2. Engage USP-LSI + UFRGS GME with formal scoping doc; NDAs + IP letters	`partnership-scoping.md` is that document; NDA + IP-assignment flow in §6.
3. BAG primitive port to IHP SG13G2	Tracked as a workstream row in `outreach-log.md`, blocked on academic partner selection (correct dependency).
4. RFQs to Innosilicon + VeriSilicon for SMIC N+2 SerDes	`rfq-commercial.md` is the template; vendor rows seeded in `outreach-log.md`.
5. Brazilian export-control counsel re: FDPR exposure	Tracked as a workstream row in `outreach-log.md`.

Test plan

PR builds clean (docs-only, no code touched).
Markdown renders correctly on Forgejo.
PHY README index lists all four files.
No off-limits paths touched (ADR-017 boundaries respected).
No vendor figures or partner positions fabricated (skeleton's "no estimates without citation" rule).

Closes #6.

## Summary Issue #6 asks for three concrete outreach artifacts on top of the `phy-options.md` skeleton already in main: 1. **`docs/phy/partnership-scoping.md`** — formal scoping document for USP-LSI, UFRGS GME, Unicamp CCS and IIT Madras. Covers project context, target spec (with explicit `<FILL>` placeholders, no pre-fabricated numbers), channel context for the water-cooled 8-chip carrier, IP and licensing framing compatible with CHARRUA + AGPL while protecting student publication rights, NDA / contracting flow, and the funding caveat (subject to PACID). 2. **`docs/phy/rfq-commercial.md`** — RFQ template for Innosilicon / VeriSilicon / Alphawave on SMIC N+2. Mandates an export-control / FDPR chain-of-title attestation in Section 6; responses omitting that section will not be evaluated. Covers deliverables, target spec, RTL interface (`PopLinkPHYIO`), commercial terms requested, and evaluation criteria. 3. **`docs/phy/outreach-log.md`** — append-only tracker keyed by partner / vendor, state, reference doc, and owner. Hosts the F-T4 tripwire (all four PHY paths confirmed unavailable → escalate). `docs/phy/README.md` index updated to list the three new files. ## What this PR is NOT - It does not pre-populate vendor figures, partner positions, or cost ranges. The `phy-options.md` skeleton mandates that those only appear after a signed RFQ response or a signed scoping memo. All concrete numbers in the new docs are `<FILL>` placeholders or cross-references to PLAN.md and existing ADRs. - It does not send anything. The scoping doc and RFQ are templates; they ship after legal review of the IP framing (Section 5) and the export-control attestation language (Section 6). ## Acceptance criteria mapping (issue #6) | Issue step | This PR | |---|---| | 1. Channel-loss budget for 8-chip water-cooled carrier | `outreach-log.md` "Other workstreams" row pins it as pending board CFD outputs; `partnership-scoping.md` §4 lists the inputs we can share under NDA. Closes-out remains for board work to land. | | 2. Engage USP-LSI + UFRGS GME with formal scoping doc; NDAs + IP letters | `partnership-scoping.md` is that document; NDA + IP-assignment flow in §6. | | 3. BAG primitive port to IHP SG13G2 | Tracked as a workstream row in `outreach-log.md`, blocked on academic partner selection (correct dependency). | | 4. RFQs to Innosilicon + VeriSilicon for SMIC N+2 SerDes | `rfq-commercial.md` is the template; vendor rows seeded in `outreach-log.md`. | | 5. Brazilian export-control counsel re: FDPR exposure | Tracked as a workstream row in `outreach-log.md`. | ## Test plan - [ ] PR builds clean (docs-only, no code touched). - [ ] Markdown renders correctly on Forgejo. - [ ] PHY README index lists all four files. - [ ] No off-limits paths touched (ADR-017 boundaries respected). - [ ] No vendor figures or partner positions fabricated (skeleton's "no estimates without citation" rule). Closes #6.

navigator added 1 commit

2026-05-25 14:44:06 -03:00

docs(phy): add partnership scoping doc, commercial RFQ template, outreach log

build / scalafmt-check (pull_request) Successful in 4s

Details

build / sbt-compile (pull_request) Successful in 3s

Details

build / shell-lint (pull_request) Successful in 1m7s

Details

cffd924b74

Issue #6 asks to engage USP-LSI, UFRGS GME, IIT Madras with a formal
scoping document, issue RFQs to Innosilicon and VeriSilicon for SMIC N+2
SerDes, and track outreach status. The phy-options.md skeleton already
covers WHAT directions exist; the three new files cover WHAT to send and
WHERE to record what comes back.

- partnership-scoping.md: circulated to academic partners ahead of NDA;
  declares the FluidPopV1 PHY ask (Section 3 spec, channel context, IP
  framing under CHARRUA + AGPL with explicit student-publication
  protection, NDA process). PHY-3 track.
- rfq-commercial.md: vendor-facing RFQ template for the Pro tape-out.
  Mandates an export-control / FDPR chain-of-title attestation in
  Section 6; responses omitting it are not evaluated. PHY-2 track.
- outreach-log.md: append-only tracker. Carries the F-T4 tripwire so a
  silent decay into 'behavioral PHY forever' triggers an escalation.

No vendor figures, partner positions, or cost ranges are pre-populated:
phy-options.md mandates that those only appear after signed RFQ
responses or signed scoping memos. All concrete numbers in the new docs
are <FILL> placeholders or cross-references to PLAN.md / existing ADRs.

docs/phy/README.md indexed.

Closes #6.