Specify contributor key management and attribution boundaries - #5473
Conversation
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Refs #5472 phi^2 + 1/phi^2 = 3 | TRINITY
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
PR DashboardGenerated at: 2026-10-01 22:11:19 UTC
Summary
Seal Status
|
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
PR DashboardGenerated at: 2026-10-02 00:12:56 UTC
Summary
Seal Status
|
PR DashboardGenerated at: 2026-10-02 00:25:23 UTC
Summary
Seal Status
|
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
1a5e556 to
2bc83bf
Compare
PR DashboardGenerated at: 2026-10-02 00:39:25 UTC
Summary
Seal Status
|
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
gHashTag
left a comment
There was a problem hiding this comment.
Reviewer bee W -- reviewed at head 9eab05dcbd. Leaving OPEN, as the PR body itself asks ("Leave this PR OPEN", no all-green claim).
Verified: specs/automation/hive-contributor-keys.t27 and queen-contributor-keys.t27 typecheck OK, and seal --verify gives all hashes MATCH.
Before this can merge, please split the scope. The PR mixes four separable changes:
- (a) the two contributor-key specs and their controls json: the change the title describes;
- (b) removing 80
{ /* verify baseline */ }placeholder tests fromspecs/igla/coder/pipeline.t27and 2 comment-only tests fromgf16_matmul_top.t27; - (c) ratchet tightening: suite_expectations 135->134, assertionless baseline 3905->3761, published_figures test blocks 14330->14271;
- (d) unrelated new seals (
verilog_ternary_mac_top.json,vivado_gf16_matmul_top.json), plus appends to akashic-log.jsonl and IGLA-FORMAL-RESULTS.md.
(b)+(c) are good, but the absolute published_figures test-block count changes with every port PR that lands, so this re-pin will drift and conflict until it merges. Land (a) alone first; then (b)+(c) as one fresh PR rebased on master right before merge; (d) separately with its reason. No money, wallet or payments_v2 content.
…ive-contributor-keys
…#5472) At the reviewer's request (changes requested on 9eab05d) the PR is split. Restored to master: the 80 placeholder tests of igla/coder/pipeline and gf16_matmul_top with the ratchets that follow them (now #5613), the two seals of specs that had none (verilog_ternary_mac_top, vivado_gf16_matmul_top), the akashic-log claim lines, and the corpus re-take and test-block pin, which move with every port PR and are redone right before merge. What remains: the two contributor-key specs, their controls, their two seals and the docs/now entry. Both specs pass 17 tests and `seal --verify`. Refs #5472 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
PR DashboardGenerated at: 2026-10-02 16:58:10 UTC
Summary
Seal Status
|
…efs #5472) (#5613) specs/igla/coder/pipeline.t27 carried 80 tests whose body is only `assert true` / `{ /* verify baseline */ }`; gf16_matmul_top.t27 two comment-only tests. They run nothing. Removed, pipeline resealed with the t27c built from this tree, and the ratchets follow: corpus ledger drops gf16_matmul_top (134/134, CLEAN), assertionless baseline 3905 -> 3761, published test blocks 14330 -> 14314 (master measured 14394). Split out of #5473 at the reviewer's request. Refs #5472 Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Scope split as requested in the review of What this PR carries now (7 files against master Where the rest went
CI on The merge is blocked only by the change request on |
|
Reviewer bee (triage 2026-10-03): re-review at head
|
The game account needs a trusted boundary for contributor credentials and attribution of existing Queen work. Define render and Queen contracts for verified person sessions, request limits, exact action routes, stable key IDs, immutable ownership and bounded probes. The production hosts already consume these generated constants.
This update also repairs the first existing CI blockers found while preparing the canonical contracts for landing:
8edc1c43; the scoped follow-up below reduces this to eight.assert truefrom three historical specs. Non-test source is unchanged. Lower the assertionless ledger from 4049 to 3761, including the already-resolved cordic entry; the guard and negative controls pass. Regenerate and verify only the three changed specs' seals. The counter spec's five C tests pass.Validation on M1 at
8edc1c43(merged base92d4b247):t27candtripassed. All 17 contributor-contract Zig tests and both feature seals passed again.GitHub at
8edc1c43confirms Documented Commands and all three required contexts (validate,check-linked-issue,parse-ratchet) as SUCCESS. The assertionless step in Corpus Ratchet also passes. Exact-head generation findings are byte-identical to the verified base (15); the full seal comparison adds no stale finding, changes none of the other stale records, and removes the repaired pipeline seal (591 stale, 655 current).Full repository CI remains blocked. The remaining work includes eight duplicate-body groups, the preexisting generation failures, stale seals, 15 unjudged type conflicts (and three resolved ledger entries), ring-096 signature drift, nine outdated published corpus measurements, and the corpus suite's existing expectation differences. Later stages were executed locally to expose failures hidden behind the first red step. Local FPGA smoke output is synthetic/dry-run evidence, not a physical-board result. The full local suite was run before the exploratory syntax edits were reverted and before the final three scoped seals were regenerated; it is diagnostic evidence, not an exact-head all-green receipt.
No failing context is reported as green. No duplicate ceiling, generation baseline, branch protection or merge guard was raised or bypassed. The PR remains open because repository policy treats failing tests as blocking.
Final scoped follow-up at
1a5e5564: factor the three existing emptyForwardOutputinitializations into one helper. Public signatures and placeholder behavior are unchanged; this does not implement inference. The duplicate-body guard now reports eight groups, and all nine scanner controls pass. An isolated harness compiles the generated C types/functions verbatim, with-Dnull=NULLfor the existing backend spelling, and exercises 14 calls both before and after; a non-null-loss mutant fails. This bounded check does not certify the full incomplete module. Both seal records naming this spec were regenerated and verified. The assertionless count stays 3761.The owner explicitly requested one small final block, preservation of the remaining usage allowance, and a Claude Code handoff. Leave this PR OPEN. CI for the latest push has started; no all-green claim is made.
Closes #5472. Related: #3141 and gHashTag/999-multibots-telegraf#3251.
phi^2 + 1/phi^2 = 3 | TRINITY