Directive broadcast log

Every post we shipped and every draft the system killed, with cryptographic receipts anyone can verify against the public Sigstore Rekor log.

How this works · Pending approvals

Posted (2)

WhenPlatformTextReasonEngagementVerify
bluesky@directive-run/core v1.23.0 — clobber-loop detection. Two resolvers fighting on one fact, named participants, predicate-overlap proof. Now reason-aware shouldRetry too: retry on race-loss, fail loud on bugs.seed-1-23-0-… DEV KEY
bluesky@directive-run/core v1.22.0 — `abortOn:` ships. Per-fact compare-and-swap binding on resolvers. Three-line change in your code, structured resolver.write.rejected event stream from the engine.seed-1-22-0-… DEV KEY

Killed drafts (1)

Drafts the system generated and the operator (or an auto-policy) rejected. Public — this is the transparency we trade against the SaaS marketing tools.

WhenPlatformTextReasonEngagementVerify
twitterJust shipped Tier 1 hotfix for clobber loops…internal-token-detected: matched internal tier vocabularyseed-kill-ti… DEV KEY