{"id":51090309,"url":"https://github.com/tylerburleigh/lev-tracker","last_synced_at":"2026-06-24T01:03:35.634Z","repository":{"id":363110859,"uuid":"1254731112","full_name":"tylerburleigh/lev-tracker","owner":"tylerburleigh","description":"An agentic research project to collect, document, and track progress in longevity science","archived":false,"fork":false,"pushed_at":"2026-06-14T13:46:54.000Z","size":3717,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-06-14T15:25:39.753Z","etag":null,"topics":["agentic-research","ai","ai-agents","citizen-science","codex","geroscience","hallmarks-of-aging","longevity","longevity-escape-velocity","longevity-research","longevity-science","medicine","science-communication","science-research"],"latest_commit_sha":null,"homepage":"","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/tylerburleigh.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2026-05-30T23:56:36.000Z","updated_at":"2026-06-14T13:46:58.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/tylerburleigh/lev-tracker","commit_stats":null,"previous_names":["tylerburleigh/lev-tracker"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/tylerburleigh/lev-tracker","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tylerburleigh%2Flev-tracker","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tylerburleigh%2Flev-tracker/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tylerburleigh%2Flev-tracker/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tylerburleigh%2Flev-tracker/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/tylerburleigh","download_url":"https://codeload.github.com/tylerburleigh/lev-tracker/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tylerburleigh%2Flev-tracker/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":34712578,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-23T02:00:07.161Z","response_time":65,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["agentic-research","ai","ai-agents","citizen-science","codex","geroscience","hallmarks-of-aging","longevity","longevity-escape-velocity","longevity-research","longevity-science","medicine","science-communication","science-research"],"created_at":"2026-06-24T01:03:35.137Z","updated_at":"2026-06-24T01:03:35.616Z","avatar_url":"https://github.com/tylerburleigh.png","language":"JavaScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Hallmarks-Based Longevity Tracker Schema\n\nThis repository starts with a source-of-truth data schema for a longevity tracker built on the expanded Hallmarks of Aging framework.\n\nThe first pass is intentionally small:\n\n- `taxonomies/` holds canonical framework data.\n- `docs/` holds product and taxonomy rationale documents.\n- `research/` holds persistent planning state, backlog queues, and session journals for multi-pass research work.\n- `schemas/` defines JSON Schema contracts for core record types.\n- `examples/` shows how records should look in practice.\n- `data/` now holds the file-backed public records, review queue records, and staged promotion artifacts used by the prototype app.\n\n## Key Docs\n\n- [Project roadmap](docs/project-roadmap.md): active product, research, data, and docs task tracker.\n- [Product brief](docs/product-brief.md): product intent and domain model.\n- [Research ops state](docs/research-ops-state.md): default research work unit and queue rules.\n- [Coverage assessment](docs/coverage-assessment.md): internal rubric for source-landscape completeness and known evidence gaps.\n- [Admin review](docs/admin-review.md): candidate lifecycle, promotion readiness, and publication behavior.\n- [Evidence review](docs/evidence-review.md): review lanes, findings, and evidence-gate workflow.\n- [Publication checklist](docs/publication-checklist.md): pre-publish and post-publish checklist.\n- [Source ingestion rules](docs/source-ingestion-rules.md): PubMed, ClinicalTrials.gov, and manual source conventions.\n- [Intervention normalization](docs/intervention-normalization.md): rules for turning intervention IDs into public records.\n- [Data sustainability](docs/data-sustainability.md): rules and checks for keeping file-backed records maintainable as the tracker grows.\n- [Artifact retention](docs/artifact-retention.md): retention classes for canonical data, staged intermediates, generated state, reports, drafts, and compression candidates.\n\n## Design Principles\n\n- Hallmarks are the primary organizing axis.\n- Interventions, studies, findings, and milestones can map to one or more hallmarks.\n- Findings stay atomic and source-backed.\n- Milestones capture progress toward clinically meaningful aging interventions instead of raw activity.\n\n## Core Entities\n\n- `hallmarks taxonomy`: the canonical list of hallmark IDs and descriptions.\n- `track taxonomy`: the seeded list of stable track IDs grouped under hallmarks.\n- `source`: a bibliographic or registry record.\n- `track`: a stable research approach within a hallmark.\n- `intervention`: a therapy, modality, or program being tracked.\n- `study`: a trial, experiment, or observational study.\n- `finding`: one atomic observation or claim from a source or study.\n- `milestone`: a project-level progress checkpoint tied to one or more hallmarks.\n- `activity_item`: a contextual update such as trial, company, funding, or regulatory movement.\n- `outlook`: a curator judgment for the overall field, a hallmark, or a track.\n- `candidate_bundle`: a reviewable package of proposed changes from research ops.\n- `evidence_review`: a structured verification pass against a bundle revision and review lane.\n- `review_comment`: feedback exchanged during admin review.\n- `publication_event`: a record of what was published to the public site.\n- `coverage_status`: persistent internal state for what has baseline coverage and what mode comes next.\n- `coverage_assessment`: internal track-level assessment of source completeness, evidence categories, and known gaps.\n- `track_priority_queue`: the ordered internal queue that bootstrap, surveillance, and coverage repair consult when scope is vague.\n- `work_triage`: unified generated dispatcher for what the agent should work on next.\n- `research_session`: one bounded bootstrap, surveillance, or coverage-repair pass, including no-op and coverage-assessment-only outcomes.\n\n## Editorial Flow\n\n1. Research ops produce a `candidate_bundle`.\n2. Proposed record revisions are staged under `data/staged-records/\u003cbundle-id\u003e/`.\n3. Evidence reviewers add one or more `evidence_review` records for the current bundle revision.\n4. The admin review UI adds `review_comment` records, references evidence-review findings when needed, and updates bundle lifecycle status.\n5. Publishing promotes staged JSON into the public record paths under `data/` and writes a `publication_event` that records the approving evidence reviews.\n\n## Research Planning State\n\n- `ops/triage-state.v1.json` is the persistent answer to “what should the agent work on next?”\n- `research/state/coverage-status.v1.json` is the persistent answer to “what already has coverage?”\n- `research/backlog/track-priority.v1.json` is the persistent answer to “what should bootstrap, surveillance, or coverage repair do next?”\n- `research/sessions/*.json` records what each bounded research pass actually did, even when it produced no bundle.\n- `research/coverage-assessments/*.json` records how complete a track's source and evidence landscape appears, plus known gaps.\n- `npm run sync:research-planning` surfaces the latest coverage assessment verdict, gap counts, next action, and recommended next mode in `coverage-status.v1.json`.\n- `npm run sync:research-planning` also regenerates `ops/triage-state.v1.json`.\n- The default research work unit is one `track` per run.\n- Run `npm run sync:research-planning` after a research pass to regenerate state and queue files.\n\n## Validation Commands\n\n- `npm run validate:records`\n  Validates every JSON file under `data/`, `examples/`, `taxonomies/`, `research/`, and `ops/` against the repository JSON Schema contracts.\n- `npm run verify:data-sustainability`\n  Runs the full data sustainability verification chain without rewriting generated reports. Add `-- --write` to regenerate reports and `-- --include-build` to include the production build.\n- `npm run audit:data:sustainability`\n  Reports data footprint, staged-history pressure, candidate-bundle lifecycle shape, and staged files that are not linked from bundle metadata.\n- `npm run audit:artifacts`\n  Classifies file-backed artifacts by retention role and identifies prunable or compressible categories without deleting anything.\n- `npm run audit:staged-archive-readiness`\n  Compares terminal staged JSON with current live records to decide whether manifest-only archival would lose historical staged bodies.\n- `npm run manifest:staged-records`\n  Generates or checks the logical hash manifest for terminal staged records, including pruned live-backed staged paths.\n- `npm run archive:staged-records`\n  Generates or checks the archive pack containing changed terminal staged JSON bodies that cannot be represented by manifest-only archival.\n- `npm run verify:staged-archive`\n  Verifies every terminal staged record can be reconstructed from live records plus the archive pack before pruning staged JSON.\n- `npm run prune:staged-records -- --dry-run`\n  Reports terminal staged JSON prune state after archive verification. Use `--apply --confirm-prune-terminal-staged-records` only after reviewing the dry run.\n- `npm run audit:retained-staged-records`\n  Verifies every remaining physical terminal staged JSON file exactly matches a changed-body archive entry.\n\n## Research Commands\n\n- `npm run research:bundle -- status --bundle \u003cbundle-id\u003e`\n  Prints bundle validation, evidence-review gate, promotion readiness, and publication state.\n- `npm run research:bundle -- validate --bundle \u003cbundle-id\u003e`\n  Runs the same bundle checks and exits nonzero if the bundle is not publishable in its current state.\n- `npm run research:bundle -- approve --bundle \u003cbundle-id\u003e`\n  Moves a valid, review-ready bundle to `approved`.\n- `npm run research:bundle -- publish --bundle \u003cbundle-id\u003e`\n  Promotes staged records, writes a `publication_event`, and moves the bundle to `published`.\n- `npm run research:review-evidence -- status --bundle \u003cbundle-id\u003e`\n  Prints the current evidence-review state for a bundle revision, including missing lanes and blocking findings.\n- `npm run research:review-evidence -- scaffold --bundle \u003cbundle-id\u003e --lane \u003clane\u003e`\n  Creates a draft review JSON under `research/drafts/evidence-reviews/` with derived revision, round, and ID metadata.\n- `npm run research:review-evidence -- apply --file \u003cdraft-path\u003e`\n  Promotes a completed review into `data/evidence-reviews/`, updates `candidate_bundle.evidence_review_ids[]`, and supersedes older same-lane reviews for the same bundle revision.\n\n## Relationship Pattern\n\n1. A `source` documents one or more `studies`.\n2. A `track` groups related `interventions`, `studies`, and `findings`.\n3. A `study` evaluates one or more `interventions`.\n4. A `finding` points back to a `source`, and usually to a `study`.\n5. `Interventions`, `studies`, `findings`, and `milestones` all carry `hallmark_ids` and may also link to `track_ids`.\n6. `Outlooks` and `publication_events` sit above the evidence layer and expose editorial judgment and publishing history.\n\n## Next Steps\n\n- Use [docs/project-roadmap.md](docs/project-roadmap.md) as the current product and research roadmap.\n- Use [docs/triage-workflow.md](docs/triage-workflow.md) and `ops/triage-state.v1.json` when deciding what to work on next.\n- Keep `research/state/coverage-status.v1.json` and `research/backlog/track-priority.v1.json` as the generated source of truth for research coverage and next track selection.\n- Run `npm run validate:records`, `npm run typecheck`, and `npm run build` before treating roadmap implementation work as complete.\n- Run `npm run sync:research-planning` after research sessions, bundle changes, or publication events.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftylerburleigh%2Flev-tracker","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftylerburleigh%2Flev-tracker","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftylerburleigh%2Flev-tracker/lists"}