Skip to content

chore: civilian mesh positioning — drop drone wording (bpsk.t27) #1874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gHashTag merged 3 commits into from
Aug 21, 2026
Merged

chore: civilian mesh positioning — drop drone wording (bpsk.t27) #1874

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a727020
docs: civilian mesh wording in bpsk.t27 comment. Refs #1873
gHashTag Aug 7, 2026
f3fa3c6
docs: NOW.md entry for civilian mesh wording. Refs #1873
gHashTag Aug 7, 2026
9a5e1c3
Merge branch 'master' into chore/civilian-mesh-wording
gHashTag Aug 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/now/2026-08-21-civilian-mesh-wording.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# NOW -- chore: civilian mesh wording (2026-08-21)

## chore: civilian mesh positioning (Refs #1873)

- `specs/fpga/bpsk.t27` header comment: drop 'drone-mesh' -> 'mesh' (civilian 5.8 GHz mesh radio PHY). Comment-only, no spec logic change
- Refs #1873
- **Known cost, stated rather than hidden: this stales one seal.** `.trinity/seals/fpga_ZeroDSP_BPSK.json` records `spec_hash` `sha256:c03511ce...` which is exactly the hash of `specs/fpga/bpsk.t27` on master today -- the seal is VALID before this change and goes `[stale]` after it, taking `check_seal_coverage.py` from 131 stale to 132
- The seal was **not** repaired by editing `spec_hash` by hand. That field travels with four `gen_hash_{c,rust,verilog,zig}` values that certify what the compiler actually emitted; rewriting the spec hash alone would assert those four still describe the output without anything having re-run codegen to check. A comment-only edit very likely leaves the generated targets identical, but "very likely" is not what a seal records. Re-seal with `tri seal` on a machine with a built `t27c` to clear it
- Entry migrated from `docs/NOW.md` to `docs/now/` (the layout #2298 introduced); the original entry was dated 2026-08-07. The branch's own commit had deleted the heading `# NOW — feat: arbitrary-DEPTH trainer (>2 layers), proven bit-exact + synth (2026-08-07)` while keeping its body, orphaning it; `docs/NOW.md` is restored to master byte-for-byte, so that heading survives
2 changes: 1 addition & 1 deletion specs/fpga/bpsk.t27
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
// SPDX-License-Identifier: Apache-2.0
// t27/specs/fpga/bpsk.t27
// ZeroDSP BPSK modem core (TRI-NET 5.8 GHz drone-mesh radio PHY).
// ZeroDSP BPSK modem core (TRI-NET 5.8 GHz mesh radio PHY).
// Byte -> +/-1 BPSK serializer with a Barker-13 preamble, plus an integer
// Barker-13 correlator + threshold for frame synchronization. Port of the
// trios-mesh Rust modem's synthesizable core to the t27 spec-first language.
Expand Down
Loading