spec(PopRoCCRouter): promote PopRoCCRouter.SPEC.md to Draft #96

Merged

navigator merged 1 commit from spec/poproccrouter-draft into main 2026-05-26 02:44:03 -03:00

Conversation 2 Commits 1 Files changed 1 +40 -6

navigator commented 2026-05-26 02:41:29 -03:00

Owner

Copy link

Refs #48 (companion Chisel skeleton, area:rtl).
Refs #68 (Chisel package + PopRoCCRouter IO surface restore).
Refs #80 (spec-designer role onboarding).

This PR is opened by the autonomous spec-designer role; per infra/ops/agents/roles/spec-designer.sh the role is designer-driven and runs without a dedicated source issue, so no Closes # is attached. If the swarm policy requires a tracking issue per promotion, the follow-up tweak belongs in the role script, not in this SPEC change.

Summary

Promotes rtl/src/pop/specs/PopRoCCRouter.SPEC.md from Status: Stub to Status: Draft. No behaviour, no Chisel, no edits outside the single SPEC file. The IO contract is pinned to ADRs, PLAN.md sections, sibling Draft SPECs (MultiGemminiCluster, InterGemminiXbar, InterChipFabric), and to the rocket-chip RoCC ABI already mirrored in the existing elaborate-only skeleton at rtl/src/pop/PopRoCCRouter.scala. Widths and per-signal shapes that no source pins are recorded as _Open question:_ rather than invented.

Resolved TBDs

• §Interface — RoCC request port (cmd): pinned to the local mirror of freechips.rocketchip.tile.RoCCCommand already declared in rtl/src/pop/PopRoCCRouter.scala and to ADR-006 Decision (Edu: 2 cores; Pro: 4) and ADR-006 Consequences (2-bit gemmini-id in funct7).
• §Interface — RoCC response port (resp): pinned to the local mirror of freechips.rocketchip.tile.RoCCResponse already declared in rtl/src/pop/PopRoCCRouter.scala (rd, data, xLen).
• §Interface — per-tile fan-out toward MultiGemminiCluster: tile count pinned to ADR-001 (4 Edu / 16 Pro); selection pinned to ADR-006 Consequences 2-bit gemmini-id; coherence boundary pinned to ADR-011 and cross-referenced to the consumer surface in rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Interface.
• §Behavior — funct7 decode and tile-id extraction: pinned to ADR-006 Consequences and to the inherited-Gemmini-RoCC policy in docs/spec/fluidpop-isa.md §3.
• §Behavior — dispatch to selected per-tile attach: pinned to rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Behavior ("Per-tile dispatch driven by PopRoCCRouter").
• §Behavior — ordering vs Rocket commit: pinned to the upstream RoCC ABI (xd / resp.valid handshake) already declared in the rocket-chip mirrors in rtl/src/pop/PopRoCCRouter.scala.
• §Behavior — quiescence behaviour: pinned to rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Behavior cluster-stop drain (forward-link to the cluster's open question on the CSR address / drain order).
• §Invariants — single response per request, no duplicate dispatch, no deadlock under per-tile back-pressure: lifted verbatim from the Stub and cross-referenced to the §Coverage targets bench.
• §Invariants — per-source response ordering preserved: mirrored from rtl/src/pop/specs/InterGemminiXbar.SPEC.md §Invariants.
• §Invariants — per-tile fan-out tracks active PopSoCConfig: pinned to ADR-001 (4 Edu / 16 Pro) and the PLAN.md §8.2 Config selection.
• §Invariants — intra-chip coherence preserved on per-tile attach: pinned to ADR-011 Decision and cross-referenced to rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Invariants.

Open questions explicitly retained

• §Interface — single shared cmd port across cores versus one per core: trade-off is per-core handshake clarity versus cluster-side fan-in area; not pinned by any ADR.
• §Interface — per-tile bundle shape (request / response port count, request-ID width, ordering of per-tile completion vs originating-core resp): mirrors the same Open in rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Interface; resolves jointly.
• §Interface — Pro variant 16-tile count vs ADR-006 2-bit funct7 field reconciliation: a follow-up ADR amending the gemmini-id encoding for Pro must close before the Pro variant elaborates without an invented funct7 encoding (mirrors the same Open in MultiGemminiCluster.SPEC.md §Behavior).
• §Interface — exception / error path cause encoding: explicitly forward-linked from docs/spec/fluidpop-isa.md §7 and §9; resolves with the trap-cause ADR called out there.
• §Behavior — in-flight table depth and per-tile request-ID width: pinned by neither ADR-006 nor any PLAN.md section; tracks the per-tile bundle-shape Open above.
• §Behavior — cross-source arbitration fairness on the per-tile attach (round-robin versus priority): trade-off is per-core fairness under contention versus simpler-arbiter area.
• §Behavior — quiescence signalling discipline (dedicated control bit versus per-tile attach drain): tracks the cluster-stop CSR Open in rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Behavior.

Scope

Only rtl/src/pop/specs/PopRoCCRouter.SPEC.md is touched (one file, +40/-6). No edits to PLAN.md, ADRs, Chisel sources, infra, or CI workflows, per ADR-017 off-limits paths for the spec-designer role.

Test plan

• CI fast lane (sbt compile + lint) green on the SPEC-only change.
• pr-reviewer confirms no fabricated widths / counts / opcodes / addresses (every commitment links back to ADR-001, ADR-006, ADR-011, PLAN.md §8.2 / §12.3, a Draft sibling SPEC, or the rocket-chip RoCC ABI already mirrored in rtl/src/pop/PopRoCCRouter.scala).
• pr-reviewer confirms all four original Stub TBDs are either resolved with a quoted source or recorded as _Open question:_ with a one-sentence trade-off.
• pr-reviewer confirms cross-references preserved: every ADR / PLAN.md section / sibling SPEC the Stub mentioned still appears in the Draft (ADRs preserved + ADR-001 / ADR-006 / ADR-011 added; PLAN.md §8.2 / §12.3 preserved).

Refs #48 (companion Chisel skeleton, area:rtl). Refs #68 (Chisel package + PopRoCCRouter IO surface restore). Refs #80 (spec-designer role onboarding). This PR is opened by the autonomous `spec-designer` role; per `infra/ops/agents/roles/spec-designer.sh` the role is designer-driven and runs without a dedicated source issue, so no `Closes #` is attached. If the swarm policy requires a tracking issue per promotion, the follow-up tweak belongs in the role script, not in this SPEC change. ## Summary Promotes `rtl/src/pop/specs/PopRoCCRouter.SPEC.md` from **Status: Stub** to **Status: Draft**. No behaviour, no Chisel, no edits outside the single SPEC file. The IO contract is pinned to ADRs, PLAN.md sections, sibling Draft SPECs (`MultiGemminiCluster`, `InterGemminiXbar`, `InterChipFabric`), and to the rocket-chip RoCC ABI already mirrored in the existing elaborate-only skeleton at `rtl/src/pop/PopRoCCRouter.scala`. Widths and per-signal shapes that no source pins are recorded as `_Open question:_` rather than invented. ## Resolved TBDs - **§Interface — RoCC request port (`cmd`)**: pinned to the local mirror of `freechips.rocketchip.tile.RoCCCommand` already declared in `rtl/src/pop/PopRoCCRouter.scala` and to ADR-006 Decision (Edu: 2 cores; Pro: 4) and ADR-006 Consequences (2-bit gemmini-id in `funct7`). - **§Interface — RoCC response port (`resp`)**: pinned to the local mirror of `freechips.rocketchip.tile.RoCCResponse` already declared in `rtl/src/pop/PopRoCCRouter.scala` (`rd`, `data`, `xLen`). - **§Interface — per-tile fan-out toward `MultiGemminiCluster`**: tile count pinned to ADR-001 (4 Edu / 16 Pro); selection pinned to ADR-006 Consequences 2-bit gemmini-id; coherence boundary pinned to ADR-011 and cross-referenced to the consumer surface in `rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Interface`. - **§Behavior — `funct7` decode and tile-id extraction**: pinned to ADR-006 Consequences and to the inherited-Gemmini-RoCC policy in `docs/spec/fluidpop-isa.md §3`. - **§Behavior — dispatch to selected per-tile attach**: pinned to `rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Behavior` ("Per-tile dispatch driven by `PopRoCCRouter`"). - **§Behavior — ordering vs Rocket commit**: pinned to the upstream RoCC ABI (`xd` / `resp.valid` handshake) already declared in the rocket-chip mirrors in `rtl/src/pop/PopRoCCRouter.scala`. - **§Behavior — quiescence behaviour**: pinned to `rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Behavior` cluster-stop drain (forward-link to the cluster's open question on the CSR address / drain order). - **§Invariants — single response per request, no duplicate dispatch, no deadlock under per-tile back-pressure**: lifted verbatim from the Stub and cross-referenced to the §Coverage targets bench. - **§Invariants — per-source response ordering preserved**: mirrored from `rtl/src/pop/specs/InterGemminiXbar.SPEC.md §Invariants`. - **§Invariants — per-tile fan-out tracks active `PopSoCConfig`**: pinned to ADR-001 (4 Edu / 16 Pro) and the PLAN.md §8.2 Config selection. - **§Invariants — intra-chip coherence preserved on per-tile attach**: pinned to ADR-011 Decision and cross-referenced to `rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Invariants`. ## Open questions explicitly retained - **§Interface — single shared `cmd` port across cores versus one per core**: trade-off is per-core handshake clarity versus cluster-side fan-in area; not pinned by any ADR. - **§Interface — per-tile bundle shape** (request / response port count, request-ID width, ordering of per-tile completion vs originating-core `resp`): mirrors the same Open in `rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Interface`; resolves jointly. - **§Interface — Pro variant 16-tile count vs ADR-006 2-bit `funct7` field reconciliation**: a follow-up ADR amending the gemmini-id encoding for Pro must close before the Pro variant elaborates without an invented `funct7` encoding (mirrors the same Open in `MultiGemminiCluster.SPEC.md §Behavior`). - **§Interface — exception / error path cause encoding**: explicitly forward-linked from `docs/spec/fluidpop-isa.md §7` and §9; resolves with the trap-cause ADR called out there. - **§Behavior — in-flight table depth and per-tile request-ID width**: pinned by neither ADR-006 nor any PLAN.md section; tracks the per-tile bundle-shape Open above. - **§Behavior — cross-source arbitration fairness on the per-tile attach** (round-robin versus priority): trade-off is per-core fairness under contention versus simpler-arbiter area. - **§Behavior — quiescence signalling discipline** (dedicated control bit versus per-tile attach drain): tracks the cluster-stop CSR Open in `rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Behavior`. ## Scope Only `rtl/src/pop/specs/PopRoCCRouter.SPEC.md` is touched (one file, +40/-6). No edits to PLAN.md, ADRs, Chisel sources, infra, or CI workflows, per ADR-017 off-limits paths for the spec-designer role. ## Test plan - [ ] CI fast lane (`sbt compile` + lint) green on the SPEC-only change. - [ ] `pr-reviewer` confirms no fabricated widths / counts / opcodes / addresses (every commitment links back to ADR-001, ADR-006, ADR-011, PLAN.md §8.2 / §12.3, a Draft sibling SPEC, or the rocket-chip RoCC ABI already mirrored in `rtl/src/pop/PopRoCCRouter.scala`). - [ ] `pr-reviewer` confirms all four original Stub `TBD`s are either resolved with a quoted source or recorded as `_Open question:_` with a one-sentence trade-off. - [ ] `pr-reviewer` confirms cross-references preserved: every ADR / PLAN.md section / sibling SPEC the Stub mentioned still appears in the Draft (ADRs preserved + ADR-001 / ADR-006 / ADR-011 added; PLAN.md §8.2 / §12.3 preserved).

navigator added 1 commit 2026-05-26 02:41:29 -03:00

spec(PopRoCCRouter): promote PopRoCCRouter.SPEC.md to Draft ... e6c08adebc

Refs #48 (companion Chisel skeleton, area:rtl).
Refs #68 (Chisel package + PopRoCCRouter IO surface restore).
Refs #80 (spec-designer role onboarding).

This change is opened by the autonomous spec-designer role; per
infra/ops/agents/roles/spec-designer.sh the role is designer-driven
and runs without a dedicated source issue, so no `Closes #` is
attached. If the swarm policy requires a tracking issue per
promotion, the follow-up tweak belongs in the role script, not in
this SPEC change.

Promotes rtl/src/pop/specs/PopRoCCRouter.SPEC.md from Status: Stub
to Status: Draft. No behaviour, no Chisel, no edits outside the
single SPEC file. The IO contract is pinned to ADRs, PLAN.md
sections, sibling Draft SPECs (MultiGemminiCluster, InterGemminiXbar,
InterChipFabric), and to the rocket-chip RoCC ABI mirrored in the
existing elaborate-only skeleton at rtl/src/pop/PopRoCCRouter.scala.
Widths and per-signal shapes that no source pins are recorded as
_Open question:_ rather than invented.

Resolved TBDs:

- §Interface — RoCC request port (`cmd`): pinned to the local mirror
  of `freechips.rocketchip.tile.RoCCCommand` already declared in
  rtl/src/pop/PopRoCCRouter.scala and to ADR-006 Decision (Edu: 2
  cores; Pro: 4) and Consequences (2-bit gemmini-id in funct7).
- §Interface — RoCC response port (`resp`): pinned to the local
  mirror of `freechips.rocketchip.tile.RoCCResponse` already
  declared in rtl/src/pop/PopRoCCRouter.scala (`rd`, `data`, xLen).
- §Interface — per-tile fan-out toward MultiGemminiCluster: tile
  count pinned to ADR-001 (4 Edu / 16 Pro); selection pinned to
  ADR-006 Consequences 2-bit gemmini-id; coherence boundary pinned
  to ADR-011 and cross-referenced to the consumer surface in
  rtl/src/pop/specs/MultiGemminiCluster.SPEC.md §Interface.
- §Behavior — funct7 decode and tile-id extraction: pinned to
  ADR-006 Consequences and to the inherited-Gemmini-RoCC policy
  in docs/spec/fluidpop-isa.md §3.
- §Behavior — dispatch to selected per-tile attach: pinned to
  MultiGemminiCluster Draft §Behavior ("Per-tile dispatch driven by
  PopRoCCRouter").
- §Behavior — ordering vs Rocket commit: pinned to the upstream
  RoCC ABI (`xd` / `resp.valid` handshake) already declared in the
  rocket-chip mirrors in rtl/src/pop/PopRoCCRouter.scala.
- §Behavior — quiescence behaviour: pinned to MultiGemminiCluster
  Draft §Behavior cluster-stop drain (forward-link to the cluster's
  open question on CSR address / drain order).
- §Invariants — single response per request, no duplicate dispatch,
  no deadlock under per-tile back-pressure: lifted verbatim from
  the Stub and cross-referenced to §Coverage targets bench.
- §Invariants — per-source response ordering preserved: mirrored
  from rtl/src/pop/specs/InterGemminiXbar.SPEC.md §Invariants.
- §Invariants — per-tile fan-out tracks active PopSoCConfig: pinned
  to ADR-001 (4 Edu / 16 Pro) and the PLAN.md §8.2 Config selection.
- §Invariants — intra-chip coherence preserved on per-tile attach:
  pinned to ADR-011 Decision and cross-referenced to the
  MultiGemminiCluster Draft §Invariants.

Open questions explicitly retained:

- §Interface — single shared `cmd` port across cores versus one per
  core.
- §Interface — per-tile bundle shape (request / response port count,
  request-ID width, ordering of per-tile completion vs originating-
  core `resp`); mirrors the same Open in the MultiGemminiCluster Draft.
- §Interface — Pro variant 16-tile count vs ADR-006 2-bit funct7
  field reconciliation (follow-up ADR amending the gemmini-id
  encoding).
- §Interface — exception / error path cause encoding; explicitly
  forward-linked from docs/spec/fluidpop-isa.md §7 and §9.
- §Behavior — in-flight table depth and per-tile request-ID width.
- §Behavior — cross-source arbitration fairness on the per-tile
  attach (round-robin versus priority).
- §Behavior — quiescence signalling discipline (dedicated control
  bit versus per-tile attach drain).

Scope: only rtl/src/pop/specs/PopRoCCRouter.SPEC.md is touched. No
edits to PLAN.md, ADRs, Chisel sources, infra, or CI workflows, per
ADR-017 off-limits paths for the spec-designer role.

navigator added the

ready-for-review

label 2026-05-26 02:41:33 -03:00

navigator commented 2026-05-26 02:43:17 -03:00

Author

Owner

Copy link

VERDICT: PASS

PR #96 promotes rtl/src/pop/specs/PopRoCCRouter.SPEC.md from Stub to Draft following the same disciplined pattern as PR #87, PR #91, PR #92, PR #93, PR #94, and PR #95. Mechanical guardrails pass: existing SPDX header preserved (diff starts at line 4), single file touched, no AI/Anthropic attribution, no off-limits paths, no Chisel module so rules 4–6 don't apply, autonomous spec-designer role explains missing Closes #. Rule 7 is meticulously handled — every concrete claim has a verbatim source quote. Cross-checking against approved PRs in this thread: ADR-006 Decision quote ("Edu: 2x Rocket RV64GC in-order with custom RoCC router to address any of 4 local Gemminis. Pro: 4x cores; option to swap to BOOM for OoO") extends PR #93's matching quote consistently; ADR-006 Consequences ("decodes a 2-bit gemmini-id field in funct7 of custom instruction") matches PR #93; ADR-001 Decision ("Adopt 4 Gemminis per SoC in the Edu configuration, parameterized to 16 in the Pro configuration") matches PR #92/#93; ADR-011 Decision ("Within a chip, 4 Gemminis share L2 coherently") matches all prior PRs; rocket-chip RoCC ABI mirrors (RoCCInstruction, RoCCCommand, RoCCResponse, PopRoCCRouterIO with inst/rs1/rs2/rd/data/xLen parameter defaulting to 64) faithfully match the local bundles materialised in PR #69; docs/spec/fluidpop-isa.md §3 inherited-Gemmini-ISA policy and §2 funct7-TBD policy match PR #77; cross-reference to InterGemminiXbar.SPEC.md §Invariants "Per-source ordering preserved" matches PR #92's invariant. The two facets fixed by the RoCC ABI (cmd, resp) are committed with widths sourced from the in-tree skeleton rather than invented; the two facets the SPEC names abstractly (per-tile fan-out, exception path) are appropriately split between concrete pins (tile count from ADR-001, gemmini-id from ADR-006, coherence boundary from ADR-011, cluster-side surface from MultiGemminiCluster Draft) and honest Open Questions (per-tile bundle shape — mirrored on MultiGemminiCluster's side; Pro 16-tile funct7 reconciliation — mirrored on MultiGemminiCluster's side; exception cause encoding — forward-linked to the docs/spec/fluidpop-isa.md §9 trap-cause ADR). The PR retroactively confirms the funct7-encoding-attribution-to-ADR-006 claim I had repeatedly flagged on PR #77: the SPEC now explicitly cites both ADR-006 Consequences and docs/spec/fluidpop-isa.md §2 for the gemmini-id-in-funct7 policy. Sibling Draft cites (MultiGemminiCluster, InterGemminiXbar, InterChipFabric) reference SPECs that are in fact Draft per PR #93, PR #92, and PR #91; the PR body's constraint check correctly distinguishes Draft-pin sources from Stub siblings used only in Open questions. Promotion history entry is appropriate.

Findings

None.

<!-- agent:review verdict=PASS ts=1779774197 --> **VERDICT:** PASS PR #96 promotes `rtl/src/pop/specs/PopRoCCRouter.SPEC.md` from Stub to Draft following the same disciplined pattern as PR #87, PR #91, PR #92, PR #93, PR #94, and PR #95. Mechanical guardrails pass: existing SPDX header preserved (diff starts at line 4), single file touched, no AI/Anthropic attribution, no off-limits paths, no Chisel module so rules 4–6 don't apply, autonomous `spec-designer` role explains missing `Closes #`. Rule 7 is meticulously handled — every concrete claim has a verbatim source quote. Cross-checking against approved PRs in this thread: ADR-006 Decision quote ("Edu: 2x Rocket RV64GC in-order with custom RoCC router to address any of 4 local Gemminis. Pro: 4x cores; option to swap to BOOM for OoO") extends PR #93's matching quote consistently; ADR-006 Consequences ("decodes a 2-bit gemmini-id field in funct7 of custom instruction") matches PR #93; ADR-001 Decision ("Adopt 4 Gemminis per SoC in the Edu configuration, parameterized to 16 in the Pro configuration") matches PR #92/#93; ADR-011 Decision ("Within a chip, 4 Gemminis share L2 coherently") matches all prior PRs; rocket-chip RoCC ABI mirrors (RoCCInstruction, RoCCCommand, RoCCResponse, PopRoCCRouterIO with `inst`/`rs1`/`rs2`/`rd`/`data`/`xLen` parameter defaulting to 64) faithfully match the local bundles materialised in PR #69; `docs/spec/fluidpop-isa.md` §3 inherited-Gemmini-ISA policy and §2 funct7-TBD policy match PR #77; cross-reference to `InterGemminiXbar.SPEC.md §Invariants` "Per-source ordering preserved" matches PR #92's invariant. The two facets fixed by the RoCC ABI (`cmd`, `resp`) are committed with widths sourced from the in-tree skeleton rather than invented; the two facets the SPEC names abstractly (per-tile fan-out, exception path) are appropriately split between concrete pins (tile count from ADR-001, gemmini-id from ADR-006, coherence boundary from ADR-011, cluster-side surface from MultiGemminiCluster Draft) and honest Open Questions (per-tile bundle shape — mirrored on MultiGemminiCluster's side; Pro 16-tile funct7 reconciliation — mirrored on MultiGemminiCluster's side; exception cause encoding — forward-linked to the `docs/spec/fluidpop-isa.md §9` trap-cause ADR). The PR retroactively confirms the funct7-encoding-attribution-to-ADR-006 claim I had repeatedly flagged on PR #77: the SPEC now explicitly cites both ADR-006 Consequences and `docs/spec/fluidpop-isa.md §2` for the gemmini-id-in-funct7 policy. Sibling Draft cites (MultiGemminiCluster, InterGemminiXbar, InterChipFabric) reference SPECs that are in fact Draft per PR #93, PR #92, and PR #91; the PR body's constraint check correctly distinguishes Draft-pin sources from Stub siblings used only in Open questions. Promotion history entry is appropriate. ## Findings _None._

navigator added the

review:pass

label 2026-05-26 02:43:17 -03:00

fluidpop-bot approved these changes 2026-05-26 02:44:02 -03:00

fluidpop-bot left a comment

Collaborator

Copy link

CI green (head e6c08adebc), auto-approving

CI green (head e6c08adebcfd3ff778626303b2b512afe9763b51), auto-approving

navigator merged commit c65fc42e8e into main 2026-05-26 02:44:03 -03:00

navigator referenced this pull request from a commit 2026-05-26 02:44:03 -03:00

spec(PopRoCCRouter): promote PopRoCCRouter.SPEC.md to Draft (#96)

navigator referenced this pull request 2026-05-26 02:59:54 -03:00

spec(PopSoCConfig): promote PopSoCConfig.SPEC.md to Draft #97

navigator referenced this pull request 2026-05-26 13:33:22 -03:00

rtl: PopRoCCRouter v1 — funct7 decode + dispatch + per-source ordering #104

navigator referenced this pull request 2026-05-26 13:43:29 -03:00

rtl: PopRoCCRouter v1 — funct7 decode + dispatch + per-source ordering #107

navigator referenced this pull request 2026-05-26 13:49:16 -03:00

rtl: PopRoCCRouter v1 — funct7 decode + dispatch + per-source ordering #107

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

Subscribe

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!96

No description provided.