Skip to content

tri CLI wave 3: tri fleet — is the hardware this plan assumes actually attached? #2249

Description

@gHashTag

An audit found three present-tense capability claims in the project's notes (3-board inference cluster PROVEN, all three flash from software, on-chip training PROVEN) while ioreg showed no board on the bus at all. Each was true when measured; none was true that day. A measurement stays true because it happened — a capability quietly becomes false when the environment regresses. tri fleet scan turns the one-command check into a command, with --expect N for a non-zero exit when the fleet is short, and prints the sentence to send the owner instead of coding around an empty bus. Also carries wave 2 (pr-ready commit-walk baseline + tri now), which #2223 landed without.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions