Skip to content

docs(readme): add whitepaper pdf and shrink banner - #225

Merged
echobt merged 1 commit into
mainfrom
cursor/readme-whitepaper-banner-5b55
Sep 4, 2026
Merged

docs(readme): add whitepaper pdf and shrink banner#225
echobt merged 1 commit into
mainfrom
cursor/readme-whitepaper-banner-5b55

Conversation

@echobt

@echobt echobt commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Add the operator-published Cortex whitepaper at repo root and a README link under the badges. Resize the README banner so it no longer dominates the page.

  • Root whitepaper.pdf is the real PDF from https://165-227-91-243.sslip.io/cortex-whitepaper-bounty-and-proof.pdf (%PDF-1.5, 785105 bytes).
  • SHA-256: 1456e2b23a779425f9c2e875bc1469cb6e086c738953dec0f103a71967eb0334 (Mathis tip 1456e2b2…0334).
  • README: <a href="whitepaper.pdf">Whitepaper</a> under the badges (repo-root relative; GitHub blob/raw resolve it).
  • assets/banner.jpg shrunk from 1500×500 / 122KB to 720×240 / 38KB, with width="720" on the README <img>.

Does not touch ceremony secrets, proof InferenceOffer, or emission.

Greptile

Every PR is reviewed by Greptile before merge. Config: .greptile/.

  • Greptile has reviewed this PR; findings are fixed or answered
  • If the bot was silent, I commented @greptileai review

Test plan

  • file whitepaper.pdfPDF document, version 1.5
  • sha256sum whitepaper.pdf = 1456e2b23a779425f9c2e875bc1469cb6e086c738953dec0f103a71967eb0334
  • README contains <a href="whitepaper.pdf">Whitepaper</a>
  • Banner is 720×240 JPEG (~38KB vs prior 122KB)
  • cargo test --workspace — not run; docs/assets only
  • cargo fmt --all -- --check — not applicable
  • Clippy / deny / xtask gates — not applicable (no crate changes)

Risk

None for deploy, miner CVM measurement, signature domain, or emission. README + static assets only.

Naming

I did not rename BASE_* environment variables, deployed host paths
(/opt/base, /run/base, …), GHCR baseintelligence/base package names, or
base-*-v1 cryptographic domain tags, unless this PR’s purpose is a coordinated
cutover documented in docs/NAMING.md.

Open in Web Open in Cursor 

Add the operator-published Cortex whitepaper at repo root and a README
link under the badges. Resize the README banner so it no longer
dominates the page.

Co-authored-by: Mathis <echobt@users.noreply.github.com>
@echobt
echobt merged commit 8095bd8 into main Sep 4, 2026
4 checks passed
@greptile-apps

greptile-apps Bot commented Sep 4, 2026

Copy link
Copy Markdown

Greptile Summary

Summary

  • Adds the Cortex whitepaper and a README link to it.
  • Replaces the banner with a smaller 720×240 JPEG and displays it at its intrinsic 720-pixel width.
  • The README references resolve to valid repository assets.

Confidence Score: 5/5

Safe to merge.

The changed README link, PDF, and banner asset were checked against the parent and current revisions; the linked assets exist, have valid file signatures, and the documented banner width matches its intrinsic dimensions.

Files Needing Attention: None.

T-Rex T-Rex Logs

What T-Rex did

  • Validated the pre-run baseline state for README assets, confirming the parent revision lacked the new whitepaper link and explicit banner sizing.
  • Authored and ran the PR 225 assets validation script, capturing before and after logs that record the baseline and the updated results.
  • After running, the updated README asset references were validated: whitepaper.pdf is a 785105-byte PDF with valid signatures; assets/banner.jpg is a 38316-byte JPEG with 720×240 dimensions; and the README declares a 720px banner width, matching the asset.
  • The executable check was preserved, along with its before-and-after output.

View all artifacts

T-Rex Ran code and verified through T-Rex

Important Files Changed

Filename Overview
README.md Adds the whitepaper link and declares the banner at 720 pixels wide.
assets/banner.jpg Replaces the banner with a 720×240 JPEG.
whitepaper.pdf Adds the Cortex whitepaper PDF.

Reviews (1): Last reviewed commit: "docs(readme): add whitepaper pdf and shr..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants