StableSignal

Build log 0004

Gates before expansion.

A third reproducible and checkpointed Pulse record, a stronger StableScore calibration base, and a precise MigrationKit validation boundary—without turning private experiments into launch claims.

Status
Gates recorded
Network
Arc Testnet
Chain ID
5042002
Date

Objective

Advance the evidence pipeline while keeping each product's status legible. Pulse has a new public checkpointed record; StableScore and MigrationKit remain private experiments with explicit gates; AgentPay remains intentionally queued behind them.

Observation 0003 verified record

Fixed windowBlocks 56,319,551-56,319,570, selected once and re-read at the same head.
Activity197 transactions across 20 blocks; mean 9.85 per block.
Gas utilization8.8% from 52,931,190 / 600,000,000, rounded to one decimal place.
ReproductionThe fixed-head second capture was byte-identical, with SHA-256 e0035c...57714.
CheckpointPulseBeacon transaction 0x9d044e...ba6c5c confirmed with receipt status 1 at block 56,328,775.

The source bytes, research note, Pulse interface record, and checkpoint are public. The emitted digest and URI match the commit-pinned Observation 0003 source.

StableScore calibration

Evidence chain29 contiguous hashed windows through block 56,320,502, with zero gaps and 25 verified parent links.
Elapsed evidence3.978056 natural observation days; no historical backfill.
Reference coverageTwo labeled public Arc contract references are active, satisfying the reference-diversity gate.
Recent qualityThe latest 12 runs have complete token-log coverage.

Three of four maturity gates are satisfied. The remaining requirement is seven natural observation days. No score, formula, wallet profile, or production-readiness claim is public.

MigrationKit validation boundary

The private, local-first wizard completed an internal representative workflow check, its 14-test suite, demo generation, artifact hashing, and cross-link verification. A real operator still needs to run one sanitized workflow and confirm that the questions, outputs, and verifier are understandable without engineering assistance.

A possible MigrationReceiptRegistry has been documented as design-only. The current direction is a minimal, permissionless hash anchor that must never contain personally identifiable information, workflow names, URLs, scores, or private artifacts. No registry contract has been implemented or deployed, and an anchor would not prove approval, correctness, or migration completion.

Why AgentPay remains queued

AgentPay v0 begins only after StableScore reaches its seven-day evidence gate and MigrationKit passes a human operator-validation session. Keeping that dependency explicit prevents a new product surface from outrunning the evidence and operator feedback it depends on.

Related records

Independence notice: StableSignal is an independent project building on Arc testnet. We are not affiliated with, endorsed by, or sponsored by Circle or Arc.