Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Promise Tracker - Implementation and Rollout Plan

Aperta
  • Qualcosa non va?
#475 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

@kelvinkipruto ci sta già lavorando.

Dal 11/8/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Promise Tracker Implementation and Rollout Plan
(Steps for dev implementation, integration, rollout and their current status)

Prompt Optimisation and Initial Accuracy Checks

  1. LLM Prompt Optimisation for Promise Extraction
    Status: Done
    Task: Tested and optimised different prompts for extracting promises from source documents using popular LLMs.
  2. PesaCheck Feedback Integration
    Status: In Progress
    Task: Collect and incorporate feedback from PesaCheck editors on the accuracy and clarity of extracted promises.
    Acceptance Criteria: Clear feedback received and used to adjust prompts where needed.

Data Preparation and API Development

  1. Upload Source Docs to Airtable
    Status: In Progress
    Task: Upload manifestos source documents or their links into Airtable with necessary metadata (e.g. Name, Country, Region, source type, date, language, etc).
    Acceptance Criteria: All required data sources are available in Airtable for API access and manual maintenance.
  2. Develop Airtable-to-LLM API for Extraction
    Status: In Progress
    Task: Build API that retrieves documents from Airtable, sends them to the LLM, and returns structured promise data (e.g. promise text, speaker, source, category, figures, dates etc).
    Output: Structured JSON payload per promise
    Deliverable: API documentation with request/response formats
    Acceptance Criteria: API returns accurate, structured data for at least 99% of test documents.

Partner CMS (Check) Integration

  1. Review Check CMS API
    Status: To Do
    Task: Review Check CMS API to confirm how to programmatically post text entries into the platform (https://meedan.com/check).
    Output: Summary of API endpoints required for promise posting.
    Acceptance Criteria: Developer confirms ability to push plain-text promise data to Check CMS via API.
  2. Integrate with Check CMS API
    Status: To Do
    Task: Develop connector that posts extracted promises to Check CMS, where they will appear as readable text entries.
    Deliverable: Connector/API integration code with deployment instructions
    Acceptance Criteria: Test promises successfully appear in Check CMS from the API
  3. Resolve Any Publishing Issues with Check CMS
    Status: To Do
    Task: Ensure Pesacheck verified extracted promises can be posted from Check CMS to the Promise tracker website
    Acceptance Criteria: No formatting or data loss during publishing

Website Recreation, Staging and Testing

  1. Recreate Promise Tracker Website on Payload CMS
    Status: To Do
    Acceptance Criteria: All current site components and pages are available on Payload and editable via Payload.
  2. Internal Testing, Review, Demo and Stakeholder Feedback
    Status: To Do
    Task: Demo on the test/dev/staging environment and collect feedback from the internal team and Sherpas.

Pre-Go-Live Feedback and Go-Live

  1. Final Feedback before Go-live
    Status: To Do
    Task: Resolve any outstanding bugs or usability issues flagged during the final stakeholder Feedback.
    Acceptance Criteria: Sign-off from stakeholders for public release
  2. Launch Promise Tracker MVP
    Status: To Do
    Task: Push live to production domain
    Acceptance Criteria: Website is live, integrated with Check CMS, with extracted promises fully accessible
Lingua principale
TypeScript
Stelle
1
Fork
1
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CodeForAfrica/PromiseTracker

Tutte le issue di CodeForAfrica/PromiseTracker

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.