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

docs(funding): expand board-fab-rfq.md to draft skeleton #62

Closed
navigator wants to merge 1 commit from auto/issue-57-20260525T192021Z_issue57 into main
pull from: auto/issue-57-20260525T192021Z_issue57
merge into: Fluid:main
Conversation 2 Commits 1 Files changed 2 +182 -4
navigator commented 2026-05-25 16:22:53 -03:00
Owner
Copy link

Summary

Expands docs/funding/board-fab-rfq.md from a single-paragraph stub into a Draft skeleton with the 10 EN sections required by PLAN.md Section 10 deliverable #10.

Each section has a TODO marker plus a 2-3 line intent description. All cost and lead-time placeholders trace back to PLAN.md (no fabricated numbers):

  • Section 11.2.B — US$ 30-50k per first-batch FluidPopV1 production board, excluding chips
  • Sections 15.4 / 15.5 — PCB fab and assembly suppliers (PCBWay primary; sanction-aware backups)
  • Section 15.11 — cooling integration (cold-plate CNC, G1/4" tubing)

The single-chip evaluation board (PLAN.md Section 11.2.A) is explicitly scoped out of this RFQ.

Promotes the board-fab-rfq.md row in docs/funding/README.md from Stub to Draft skeleton, matching the status taxonomy already in use for grant-proposal-pacid.md.

Closes #57

Acceptance criteria

  • docs/funding/board-fab-rfq.md exists with the EN sections from the issue
  • Each section has TODO marker + 2-3 line intent description
  • Status: Draft skeleton + Owner: TBD header
  • References PLAN.md Sections 11.2, 15.4, 15.5, 15.11
  • No fabricated prices — only ranges already in PLAN.md
  • docs/funding/README.md updated
## Summary Expands `docs/funding/board-fab-rfq.md` from a single-paragraph stub into a Draft skeleton with the 10 EN sections required by PLAN.md Section 10 deliverable #10. Each section has a `TODO` marker plus a 2-3 line intent description. All cost and lead-time placeholders trace back to PLAN.md (no fabricated numbers): - Section 11.2.B — US$ 30-50k per first-batch FluidPopV1 production board, excluding chips - Sections 15.4 / 15.5 — PCB fab and assembly suppliers (PCBWay primary; sanction-aware backups) - Section 15.11 — cooling integration (cold-plate CNC, G1/4" tubing) The single-chip evaluation board (PLAN.md Section 11.2.A) is explicitly scoped out of this RFQ. Promotes the board-fab-rfq.md row in `docs/funding/README.md` from Stub to Draft skeleton, matching the status taxonomy already in use for `grant-proposal-pacid.md`. Closes #57 ## Acceptance criteria - [x] `docs/funding/board-fab-rfq.md` exists with the EN sections from the issue - [x] Each section has `TODO` marker + 2-3 line intent description - [x] `Status: Draft skeleton` + `Owner: TBD` header - [x] References PLAN.md Sections 11.2, 15.4, 15.5, 15.11 - [x] No fabricated prices — only ranges already in PLAN.md - [x] `docs/funding/README.md` updated
docs(funding): expand board-fab-rfq.md to draft skeleton
All checks were successful
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 36s
Details
df9389cfe4 
Stub had only a single descriptive paragraph. PLAN.md Section 10
deliverable #10 needs the actual section skeleton in place so that
Phase 5 RFQ drafting can fill content into stable sections instead
of inventing the structure.

Adds the 10 EN sections required by the issue (executive summary,
board overview, stack-up, assembly, quantities, cooling interface,
quality, lead time, sanction-aware sourcing, contact/timeline),
each with a TODO marker and 2-3 line intent description.

All cost and lead-time placeholders trace back to PLAN.md
(Section 11.2.B for the US$ 30-50k first-batch range,
Sections 15.4/15.5 for fab/assembly suppliers, Section 15.11 for
cooling integration). No fabricated numbers.

Promotes board-fab-rfq.md status from Stub to Draft skeleton in
docs/funding/README.md.
navigator commented 2026-05-25 18:26:38 -03:00
Author
Owner
Copy link
No description provided.
<!-- agent:pinged ts=1779744397 -->
navigator commented 2026-05-25 19:48:51 -03:00
Author
Owner
Copy link

Closing as stale. Original branch was based off main from before #59/#60/#67 landed and the diff now collides with files those PRs added. Issue #57 can be re-queued; resolver will start from current main.

Closing as stale. Original branch was based off main from before #59/#60/#67 landed and the diff now collides with files those PRs added. Issue #57 can be re-queued; resolver will start from current main.
navigator closed this pull request 2026-05-25 19:48:59 -03:00
All checks were successful
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 36s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
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
1 participant
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!62
No description provided.