prove-it

原文涵盖的主题

• Prove it
• Establish the evidence
• Pull request checks and merge-queue state
• Shared status projections
• Verify effective entrypoint behavior
• Resolve retained payloads before checking fields
• Verify installed entrypoint behavior
• Split-binary startup failures

Support a claim with the authoritative object at the layer being claimed. Cached badges, summaries, undeployed branches and unchecked reports can differ from that object. When reviewing shared engines, verifiers or skills, test the three architectural invariants: neutral mechanisms with caller-owned policy, zero domain leakage including fixtures and denylists, and exact causal guards. Allowed, denied and unreadable-required-state cases must reach the actual decision, without identity guessing or fail-open defaults. Before claiming something is serving, deployed, merged, fixed or blocked, read its mutable status and name the object, version/revision and UTC read time; an immutable object already read can be reused at that exact version and scope. A cache reader can exit zero while an individual result says stale: true; check structured freshness, object identity/version and observation time rather than equating command success or a repository-level timestamp with current evidence. A stale observation cannot establish a current value or authorize a conditional write; any documented refresh or authoritative fallback stays within existing authority and the remaining read budget, withou

这里只展示节选，请以完整原文和当前要求为准。