Skip to content

odinfree/storm-ecdsa-harness / skills/proximity-prize-campaign

proximity-prize-campaign

Verified

Run a Proximity Prize (better.codes) proof lane. Read the live frontier and your campaign ledger, route the math to the exact-algebra, search and Lean skills, check dead routes, and gate every promotion on Lean and ArkLib. Includes digests of BitWonka's 31 public submission notes and of the Discussion #537 thread on the 116.13 upper-track wall.

references/campaign-gates.md

View on GitHub
# Proximity Prize campaign gates

## Route gate

- The proposal names its new mathematical ingredient and compares it with the dead-route ledger.
- Any use of class overlap checks the recorded Johnson-condition inequality before further work.
- The lane has one named owner, an authoritative worktree, a falsifier, and a stopping condition.

## Proof gate

- Every load-bearing claim is expressed in Lean with ArkLib under the repository's accepted imports.
- Exact-target build, placeholder scan, axiom audit, repository checker, and package checks pass.
- Computational evidence has a replay receipt and is not represented as accepted proof.

## Frontier gate

- The live benchmark ID and accepted source were reopened immediately before promotion.
- The candidate strictly exceeds the current target under the official evaluator.
- Rebase status and evaluator output are preserved with timestamps and source hashes.

## Credit and note gate

- Credit actual contributors according to evidence, distinguishing conception, implementation, validation, and operation.
- Read the live submission-note rules before setting the model field or contributor block; do not infer them from an older campaign.
- Do not disclose operational capacity, providers, costs, or response cadence in a public note.
- Treat submitted notes as immutable and review the complete final note before submission.

## Ownership gate

- Do not edit, build, submit, publish, or start processes in a lane transferred to another owner unless ownership is explicitly returned.
- A handoff records exact paths, hashes, verification results, replay commands, active processes, and unresolved blockers.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall