Transparency · Build in public
Progress, decisions, and lessons.
This log records progress and reversals. Entries describe internal development work on a pre-launch system; none of them announce a live network, product or token.
- Log 0004Validation
Validation must be able to fail loudly
Early internal runs accepted corrupted work too easily because divergence thresholds were tuned for agreement. We inverted the default: unresolved divergence is a challenge, not a rounding error. This makes throughput worse and the network more honest.
- Log 0003Architecture
Packet isolation is harder than packet size
Shrinking a work packet does not automatically isolate it. Several test jobs leaked context through input selection. Decomposition now has to justify the input boundary explicitly as part of the specification.
- Log 0002Provenance
Braid receipts changed shape twice
The first receipt format recorded outcomes but not method, which made after-the-fact auditing almost useless. Validation method and validator identity are now first-class strands rather than metadata.
- Log 0001Scope
Starting tokenless was a deliberate constraint
Adding an economic layer early would have hidden whether the validation model works at all. Scalar is being built with no token, no sale and no rewards until the network can survive adversarial testing without them.
Contribute
Bring your experience to the design
Feedback from distributed-systems builders, researchers, and validators helps us test the architecture.