{
  "markdown": "# capstone-498\n\nMSDS 498 capstone project, Summer 2026. Consumer Staples Earnings Intelligence Platform.\n\n> This repo is shared for portfolio/review purposes. It requires hosted infrastructure\n> (database, auth, deployed API) to actually run — it isn't a clone-and-run demo. See the\n> Screenshots section below for what the working app looks like.\n\n## Screenshots\n\nThis is a course capstone project. The app is not hosted anywhere public, so these\nfixture-backed screenshots (real Expo UI, committed demo data, not live market data)\nare the easiest way to see what it does.\n\n| Sector Pulse | Company Detail |\n|---|---|\n| ![Sector Pulse](docs/writeups/screenshots/mobile-demo/01-sector-pulse.png) | ![Company Detail](docs/writeups/screenshots/mobile-demo/02-company-detail.png) |\n\n| Earnings Analysis | Rankings |\n|---|---|\n| ![Earnings Analysis](docs/writeups/screenshots/mobile-demo/03-earnings-analysis.png) | ![Rankings](docs/writeups/screenshots/mobile-demo/04-rankings.png) |\n\nMore screenshots, including a UX-audit set and before/after homepage comparisons, are\nin [`docs/writeups/screenshots/`](docs/writeups/screenshots/) and\n[`screenshots/`](screenshots/).\n\n## Start here if you are new to app development\n\nThis repo is meant to become a deployed product, not just a collection of notebooks.\nIf your background is mostly notebooks and Python scripts, start with\n[`docs/developer-onboarding.md`](docs/developer-onboarding.md). It explains the repo\nmap, local setup, common app-development vocabulary, and the difference between\nrunning something on your laptop and deploying it so a phone or browser can reach it.\n\nThe shortest path to being productive:\n\n1. Read this README for the map.\n2. Read [`docs/developer-onboarding.md`](docs/developer-onboarding.md) for setup.\n3. Read [`docs/design/platform/product-requirements.md`](docs/design/platform/product-requirements.md) for what the team is building.\n4. Work in one area at a time: `apps/mobile`, `apps/api`, `apps/inference`,\n   `apps/data`, `apps/schema`, or `docs/writeups`.\n\n## Repo layout\n\n| Path | What lives there | First file to read |\n|------|------------------|--------------------|\n| `apps/inference/` | Inference and EDA workspace for traditional ML and AI workflows. Owner: Adwoa. | [`apps/inference/README.md`](apps/inference/README.md) |\n| `apps/mobile/` | Expo and React Native mobile/web frontend. Owner: Eli. | [`apps/mobile/README.md`](apps/mobile/README.md) |\n| `apps/api/` | App-facing TypeScript/Hono API, Better Auth, and SQL-backed data routes. Owner: Eli. | [`apps/api/README.md`](apps/api/README.md) |\n| `apps/data/` | Data pipeline and dashboard infrastructure. Owner: Jovana. | [`apps/data/README.md`](apps/data/README.md) |\n| `apps/schema/` | Shared SQLite/libSQL schema, local reset helper, and database smoke tests. | [`apps/schema/README.md`](apps/schema/README.md) |\n| `docs/writeups/` | Written deliverables: project goals, initial findings, final report, presentation. Owner: Ethan. | [`docs/writeups/`](docs/writeups/) |\n| `docs/` | Design docs, course materials, team notes. | [`docs/index.md`](docs/index.md) |\n\nSee [`docs/design/platform/product-requirements.md`](docs/design/platform/product-requirements.md) for the full PRD.\n\n## Local setup\n\nSetup commands are documented in the app-specific folders once that part of the\nproject has a confirmed workflow. Start with the README for the area you are working\nin:\n\n- [`apps/inference/README.md`](apps/inference/README.md)\n- [`apps/mobile/README.md`](apps/mobile/README.md)\n- [`apps/api/README.md`](apps/api/README.md)\n- [`apps/data/README.md`](apps/data/README.md)\n- [`apps/schema/README.md`](apps/schema/README.md)\n\nThe inherited scripts in `apps/data/` can download, transcribe, or write files when\nrun. Read [`apps/data/README.md`](apps/data/README.md) before running one.\n\n`apps/mobile/` and `apps/api/` form the user-facing application. Authentication\nalways uses the API; business data can use mobile fixtures or the live SQL-backed API.\nTheir READMEs document the two-terminal local workflow, environment variables,\nvalidation commands, and deployment boundaries.\n\n## Ops tooling\n\nThe daily team digest workflow is documented in\n[`docs/team/daily-team-digest.md`](docs/team/daily-team-digest.md). That document is\nthe source of truth for the Gmail OAuth environment variables used by\n`scripts/daily_team_digest.py`; do not copy sender, recipient, token, or client-secret\nvalues into this README.\n\n## Course deadlines\n\nSee [`docs/course/project-schedule-full.md`](docs/course/project-schedule-full.md).\n\n## Agent guidance\n\nAI coding assistants should read `AGENTS.md` (Codex + Cursor) or `CLAUDE.md` (Claude\nCode) at the repo root first, then the nearest scoped `AGENTS.md` for the directory\nthey are editing.\n\nBoth root files are generated from [`.ruler/AGENTS.md`](.ruler/AGENTS.md) — the\nsingle source of truth for agent instructions — via\n[Ruler](https://github.com/intellectronica/ruler). To update agent guidance, edit\n`.ruler/AGENTS.md` and regenerate:\n\n```sh\nnpx @intellectronica/ruler apply --no-mcp --no-gitignore\n```\n\nGenerated files (`AGENTS.md`, `CLAUDE.md`) are committed to git so that worktrees and\nfresh clones pick them up automatically without needing Ruler installed. MCP server\nconfigs live in agent-specific files (`.claude/settings.json`, `.codex/config.toml`,\n`.cursor/mcp.json`) and are managed manually.\n\nWhen adding or changing a runnable part of the project, maintain both the relevant\nREADME and `.ruler/AGENTS.md`: README files orient teammates, while agent files orient\ncoding harnesses that may be helping those teammates.\n",
  "bytes": 5611,
  "sha": "f4168ca1fa40160d4e04b4ffd3ed7681e8739b596903620af450b8d0b86b5243",
  "repo_slug": "aanyam22/capstone-market-prediction",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/okf_aanyam22_capstone_market_prediction_docs_b45bc075/readme"
}