chore: add eliza technical report/paper

[tomguluson92]

Add technical report to README @odilitime @shakkernerd @tcm390 @lalalune

Summary by CodeRabbit

• Documentation
  • Added a citation section to the README
  • Updated project links
  • Included academic reference for the project

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces a new citation section in the README.md file for the Eliza OS project. The changes include adding a BibTeX-formatted academic citation for a technical paper about Eliza, and modifying the existing links to improve documentation clarity. The update provides a formal reference for the project's academic background.

Changes

File	Change Summary
README.md	- Added new "Citation" section with BibTeX entry - Updated links to replace "Examples" with "Technical Report"

Possibly related PRs

• fix: update zero Gravity (0G) link #2441: Updates link in README.md, similar documentation improvement
• Update ElizaOS Documentation link #2495: Modifies URL in README.md for ElizaOS documentation

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 631cd6d and 895336b.

📒 Files selected for processing (1)

• README.md (2 hunks)

🧰 Additional context used

🪛 Markdownlint (0.37.0)

README.md

175-175: null
Images should have alternate text (alt text)

(MD045, no-alt-text)

🔇 Additional comments (1)

README.md (1)

9-9: Verify the arXiv paper link validity.

The arXiv link 2501.06781 appears to be from January 2025, which is in the future. Additionally, the ID format seems unusual for arXiv.

✅ Verification successful

The arXiv paper link is valid and correctly formatted

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify if the arXiv ID exists and follows the correct format
curl -s -o /dev/null -w "%{http_code}" "https://arxiv.org/abs/2501.06781"

Length of output: 77