You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
spec-kit became the default on-ramp for spec-driven development. Our draft spec boulder-evidence-format v0 adds what happens after the plan: HMAC-signed human-approval receipts bound to sha256 artifact digests, emitted before execution. Would a challenge-to-receipt adapter be valuable to spec-kit users, or noise?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
spec-kit became the default on-ramp for spec-driven development. Our draft spec boulder-evidence-format v0 adds what happens after the plan: HMAC-signed human-approval receipts bound to sha256 artifact digests, emitted before execution. Would a challenge-to-receipt adapter be valuable to spec-kit users, or noise?
Spec (2 pages): https://github.com/min9lin9/boulder/blob/main/spec/evidence-format/SPEC.md
Happy to adapt - one line on what would make this not worth adopting is genuinely welcome.
All reactions