Attention shows who gets seen; verified updates show which facts changed and which evidence boundaries still need confirmation.
Dates use UTC. The default view shows the newest event date; when an older event enters later, its recorded date appears separately.
How external evidence enters public history
A submission stays private until its source is checked, its public record is edited bilingually, and the patch is accepted.
See how evidence patches workChange type
DAILY VERIFICATION RECORD
BitShovel organized “the AI says it is done—how do I know it is deliverable?” into understanding, comparison, evidence, a verification card, and practice.
Why it matters
Products no longer stand as isolated profiles; they return to a reviewable problem and decision process.
Evidence boundary
This proves the page and checklist are public; it does not prove they have helped real users ship.
The work is split into content publication, hands-on product validation, and user impact; only publication is marked complete.
Why it matters
“Live” is no longer expanded into “the product works” or “growth happened,” so the next action can target the missing evidence.
Evidence boundary
BitShovel has not installed AgentLimb, completed a real-account task, or demonstrated user impact.
Follow public changes via RSS
Updates, problems, solutions, and practices share one subscribable timeline.
