|
.claude/agents
|
Pre-public scrub, the text pass (7 October 2026, 19:5x UK): no founder name, personal login, earlier business or personal address in any tracked text file, and a gate check that keeps it so
|
2026-10-07 18:39:50 +00:00 |
|
.forgejo/issue_template
|
Builder programme (8 October 2026): /build, /grants, the Devnet 3 faucet on build-1, docs/build as the source
|
2026-10-08 10:24:07 +00:00 |
|
.github/workflows
|
Merge branch 'ci-steward' into ci-steward-2
|
2026-10-07 17:02:55 +00:00 |
|
app
|
The wallet's History row: a recovery lock reads "finalised (recovery lock)", never plain final (review B F04, the founder's ruling)
|
2026-10-08 19:17:13 +00:00 |
|
brand
|
site: share cards and metas from one source (site/og), rendered on a build box
|
2026-10-08 14:51:03 +00:00 |
|
contracts
|
Bridge: the Install script (voter table and optional certificate onto an already deployed verifier; for a chain whose table is read at its first lock, igneum-devnet-4)
|
2026-10-08 16:57:34 +00:00 |
|
docs
|
Counter ASIC 3.0 status: the fleet block landed on INT-07 (FAIL), the hive canary FAIL on the lost-proof relay (the reset held), the reference hubs' state-root split after the same cut block, main's rulings and the relay-class diagnostic
|
2026-10-09 03:41:16 +00:00 |
|
igneum-census
|
Counter ASIC 3.0 item 8: the latency-shadow knob (LoadClass +sh<S>x<R>), its packs and the PC 2 playbook
|
2026-10-06 07:58:35 +00:00 |
|
igneum-pow
|
verdict-cache-fix: igneum-pow back to master's tree (the release-2.0.0 freeze pairing for box node builds had been staged by a checkout and rode into 99b83bbba; the spec read-back read it red)
|
2026-10-08 21:30:18 +00:00 |
|
infra
|
The harnesses' carried rows name the record's vote key hash as signer (the secrets check reads any 64-hex beside the word key, keyHash included)
|
2026-10-08 22:15:56 +00:00 |
|
packaging
|
Rule 33: the fresh-install canary record (tools/ci/canary/<sha>.json, one file per sha with an artefacts list) and its check; publish-manifest.sh and publish-public.sh refuse an entry whose sha has no PASS record for its own artefact; the canary cell under INT-07 (BLOCKED tonight); the merge replays modified batches too (the kills re-record reaches master's rows); the identity words out of the map
|
2026-10-08 20:46:09 +00:00 |
|
pool
|
Pool v0 rebased onto master and the 0.3.14 fork: the program class and era seed ride with every seeds and job line; the re-check test for class v3 and class v4
|
2026-10-06 18:49:13 +00:00 |
|
proto-cuda
|
Merge build/master 9cfaadbe7 into class-v6-kits (master's registry, harness map and gate-remote.sh taken; the kit's batch kit-class-v6-20261008-01 re-recorded on master's registry and the map page regenerated)
|
2026-10-08 20:43:21 +00:00 |
|
proto-metal
|
class v6 kit: the Metal worker runs generator 6 as it runs class v5 (packClassOf 6 = v6, the state-leaf rules on both classes, as packfile.h 5f21d1165); the kit's packfile-test names the checked-in class v5 pack as its known-good (the generator 6 all pack failed that check by construction in the third build)
|
2026-10-08 19:39:22 +00:00 |
|
proto-newpow
|
class v5: the pod bench's run script (proto-newpow/class-v5/run.sh: both packs, two passes, 20-s power windows)
|
2026-10-07 11:24:23 +00:00 |
|
proto-opencl
|
F10 rows, I05 epoch tag, I06 pack geometry rule across the three hosts
|
2026-10-08 19:53:24 +00:00 |
|
proto-vdf
|
proto-vdf: Wesolowski VDF between the certified checkpoint and the program seed
|
2026-10-03 16:39:01 +00:00 |
|
proving
|
Merge master 9f99c3f0a into v607-floor-memory under the master-landing lock
|
2026-10-08 22:20:07 +00:00 |
|
relay
|
Relay agent: the wait on a task is its own process with a cap, never -Wait (PC 2, 8 October 2026, 21:28 UK: a task that started Igneum Miner.exe held the agent for the app's whole life, because Start-Process -Wait waits for every descendant on the inherited console; the relay channel to PC 2 went silent for half an hour). Now WaitForExit(timeout_minutes, default 60) on the task's shell; a task past its cap is ended by its pid with a log line and exit 124, never by a name. Test known-failed first in relay/test/service.test.mjs
|
2026-10-08 21:01:54 +00:00 |
|
scene
|
Live proving feed: the page says when its shard states are stale, and a chain block with an empty plan reads "no shards in this block" (8 October 2026, main's order: the project lead wants to watch proving and shards in real time; a stale snapshot must read as stale). Reading of the day: /api/live's proven and paid states come from the Devnet 3 observer's own node on igneum-build-1 (igneum-observer-node-dn3, EVM 26850), not from hub-1; that node stopped crediting payouts at 23:57Z on 7 October (paidShards frozen at 7,304 while blocks carried 8,457 proof records by 03:00Z and hub-1 counted 11,861 by 08:56Z), and the page kept showing the paid total as fresh. site/lib/proving-health.mjs (tests known-failed first: "Cannot find module", then 10 green on build-2): stale when the observer's last status read is over 60 s old (status_at, new in the observer's live_state.proving), when the node's tip trails the newest block by over 300 DAA, or when blocks carried proof records in the last 10 minutes and no shard moved to verified or paid for 10 minutes (the blind-to-records class); a quiet chain is not stale for lack of credits. /api/live carries stale, stale_reason, status_age_s, tip_lag_daa, records_10m and last_change_at on proving (two more indexed readings; scene/feed-contract.json lists the keys; the recorded fixture carries them). /live: the Proven tile's line reads "proving feed stale: ..." in ember, else "... last credit N s ago"; the inspector's count adds "feed stale". Scene 2.0.7: a chain block whose plan is known (block.number set, carried as plan on the normalised block) and empty reads "no shards in this block"; loading and late stay for an unread plan (shard-words test, known-failed on 2.0.6). Gate: the health test joins the site unit-test line.
|
2026-10-08 09:12:56 +00:00 |
|
sim
|
The 2.0.3 reruns of rows 1b and 1c on the fixed node (finality-2.0.3-kind-and-conflict c8d22a85, 9 October 2026, 01:27 to 01:45 UK): the lock kind reads recovery on every node, two valid certificates at one index pause finality with reason conflict and no new lock above it; rows, files and the registry batch
|
2026-10-09 00:47:43 +00:00 |
|
site
|
Merge master 6d973e2a4 into ci-int07-kit2 under the master-landing lock
|
2026-10-09 01:39:12 +00:00 |
|
tools
|
Kit 2's rule-33 record with the fleet block (FAIL at sync under fix 2's walk bound) and INT-07 moved with it (FAIL; the mac block PASS, hive and windows pending); F0's rule-33 row
|
2026-10-09 03:18:30 +00:00 |
|
.gitignore
|
gitignore: infra/cross/out-workers-box/ (the workers tools/workers-remote.sh fetches from the box)
|
2026-10-06 19:11:39 +00:00 |
|
.vercelignore
|
Commit identity rule and a deploy ignore file
|
2026-10-03 17:33:46 +00:00 |
|
CLAUDE.md
|
Igneum: design docs, Metal lottery-hash prototype, CUDA test pack, finality simulation
|
2026-10-03 15:06:01 +00:00 |
|
rust-toolchain.toml
|
rust-toolchain.toml: one pin for every side (1.99.0, the two cross targets); the mismatch refusal reads it
|
2026-10-06 23:44:20 +00:00 |
