docs(repo): remove retired products, add readme and validator script

.coderabbit.yaml

@@ -0,0 +1,56 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+language: en-US
+reviews:
+  profile: assertive
+  auto_review:
+    enabled: true
+    drafts: true
+  path_filters:
+    - "!docs/BUNDLE_SPEC.md"
+    - "!docs/external-miner/proof-tbench.md"
+    - "!uv.lock"
+  path_instructions:
+    - path: "**"
+      instructions: |
+        Cortex review rules.
+        Cortex is a Python Bittensor research subnet. The owner-signed trust root lists
+        the live challenges: legacy bounty/proof 2,000/8,000 (algorithm 1), 3,000/7,000
+        (algorithm 2, version >=2) or 1..64 unique ids (algorithm 3, version >=3). The
+        sum is always 10,000. Proof is built in; every other challenge is a Docker
+        container per docs/CHALLENGES.md. Design, Prism and Relearn are retired and removed.
+
+        - Preserve frozen SCALE encodings, Merkle construction, aggregation and every
+          `base-*-v1` signature preimage. Cross-language vectors must remain green.
+          Algorithm 2 counts each valid Bounty report once, distributes proportionally,
+          scales its 30% share by min(total_valid/10, 1), and burns unused/quarantined
+          mass. The total includes only the signed expected participant population.
+          Algorithm 3 pays each challenge share * min(sum(leaves), 10^12) / 10^12 and
+          burns the rest; unpaid mass never moves to another challenge.
+          Never allow an algorithm 1 body under the new profile or activate before
+          the owner-signed epoch; historical seals and journals stay immutable.
+        - Preserve existing `BASE_*` names and deployed compatibility paths. New master
+          settings may add the matching `CORTEX_*` alias but conflicting values fail.
+        - Missing or unknown image digests, offers, baselines, topics, keys, feeds and
+          VM evidence fail closed. Never add a guessed digest or a simulation fallback.
+        - Refused Proof intake does not reserve a nonce, create a row or start paid work
+          unless the documented durable acceptance point has been reached.
+        - Proof environment values are checked before signatures, stored only in the
+          private vault, injected only into paid jobs and removed at terminal state.
+        - A measured result scores only after topic/job/image/artifact binding and
+          confirmed dedicated VM teardown. Experiment guests have no network.
+        - Recursive children share the parent's hard call, token, tool, depth and wall
+          budgets. External side effects require durable intent and idempotent recovery.
+        - Shared observations are untrusted and private until owner-signed approval.
+        - A trusted challenge container that is unregistered, failing or returns invalid
+          weights yields explicit `ChallengeInternal` leaves; never a stale or guessed
+          score. Containers never receive a leaf seed; only `challenge-supervisor`
+          mounts the Docker socket; the proxy never forwards `internal/` paths.
+        - Validators independently fetch historical chain state, recompute exact u16
+          weights and refuse the unsealed UID0 fallback. A sealed UID0 burn is valid.
+        - Production images are digest-pinned. Secrets are private files and must never
+          enter Git, image layers, request/status output, fixtures or logs.
+        - CI remains offline: no OpenRouter call, Lium rent, Firecracker boot or chain
+          submission. Fake-boundary tests cannot be described as live evidence.
+        - API changes update the matching `docs/external-miner/` guide.
+        - Do not edit the byte-pinned frozen specification (docs/BUNDLE_SPEC.md). Do not weaken
+          `scripts/check_repo.py` to accept protocol drift.

.github/PULL_REQUEST_TEMPLATE.md

@@ -17,10 +17,10 @@
 - [ ] No challenge content, credential, floating production image, or invented digest was added
 - [ ] Frozen protocol specifications and `BASE_*`/domain compatibility remain intact
 
-## Greptile
+## CodeRabbit
 
-- [ ] Greptile reviewed this PR and findings are resolved or answered
-- [ ] If the bot was silent, I commented `@greptileai review`
+- [ ] CodeRabbit reviewed this PR and findings are resolved or answered
+- [ ] If the bot was silent, I commented `@coderabbitai review`
 
 ## Risk
 

AGENTS.md

@@ -21,9 +21,8 @@ bounty/proof 2,000/8,000 profile; algorithm 2 is bounty/proof 3,000/7,000
 (document version >=2); algorithm 3 (document version >=3) admits any 1..64
 unique ids and pays each challenge `share * min(sum(leaves), 10^12) / 10^12`.
 Activation is an offline owner ceremony. Design, Prism and Relearn are retired
-products. Their frozen specifications and historical miner pointers remain for
-compatibility; no active code, service, trust-root row or leaf may register
-them.
+products and their documentation has been removed. No active code, service,
+trust-root row or leaf may register them.
 
 Start with [the architecture](docs/ARCHITECTURE.md),
 [Proof](docs/PROOF.md), [challenge containers](docs/CHALLENGES.md) and
@@ -51,8 +50,7 @@ The working branch is `main`. Production releases are annotated `v*.*.*` tags.
 
 - Preserve `BASE_*` names, deployed compatibility paths and every `base-*-v1`
   signature domain. `CORTEX_*` is an accepted master alias only.
-- Do not edit `docs/BUNDLE_SPEC.md`, `docs/DESIGN_CHALLENGE.md` or
-  `docs/PRISM.md`. Their exact SHA-256 values are checked by
+- Do not edit `docs/BUNDLE_SPEC.md`. Its exact SHA-256 value is checked by
   `scripts/check_repo.py`.
 - Production image references are digest-only. Never invent a digest; an empty
   or unknown pin remains fail-closed.
@@ -186,7 +184,7 @@ signed leaves, gateway seal, a `sealed: true` fetch and validator recomputation.
 Health endpoints alone do not verify a challenge. CI must not contact OpenRouter,
 rent provider compute, boot Firecracker or submit an on-chain transaction.
 
-Pull requests require a Greptile review. If silent, comment `@greptileai review`.
+Pull requests require a CodeRabbit review. If silent, comment `@coderabbitai review`.
 Commit subjects use `type(scope): lowercase summary`, at most 72 characters.
 
 ## Never commit

CONTRIBUTING.md

@@ -41,7 +41,7 @@ SQLite, signatures, RLM state, scoring, sealing, and validator verification.
 
 ## Pull requests
 
-Target `main`, fill in the pull request template, and request a Greptile review.
+Target `main`, fill in the pull request template, and request a CodeRabbit review.
 Use Conventional Commit subjects no longer than 72 characters:
 
 ```text