AI automation / Blockchain infrastructure / 2025–2026

DocPythia: Turning Validator Support Conversations into Documentation Updates

Lionscraft built DocPythia to find technical guidance buried in community conversations, identify gaps in existing documentation, and prepare updates that maintainers can review and submit through GitHub.

BuildAdvisory
135
candidate documentation gaps shown in the demo
MIT
licensed public repository
On this page

The story in brief

01 — Situation

NEAR's validator community was expanding, but answers to practical operating questions were spread across chat channels and existing documentation. Engineers could solve a problem in conversation without that answer ever reaching the official guides.

02 — Role

Lionscraft designed and developed DocPythia, an AI-assisted system that turns fragmented technical discussions into reviewable documentation improvements.

03 — Work

A working application that collects and analyses community discussions, compares findings with existing technical documentation, proposes changes and connects approved edits to GitHub pull requests.

04 — Outcome

The public source code and recorded product demonstration establish a functioning system, not just a proposed AI concept. The demonstration showed 135 candidate documentation gaps at that point in the analysis; this is a working-session figure, not a permanent measure of missing documentation.

Client
Meta Pool / NEAR ecosystem
Industry
AI automation · Blockchain infrastructure
Period
2025–2026
Project
DocPythia, developed for the NEAR validator ecosystem
Collaborator
Meta Pool
Technical stack
TypeScript, React, Express, PostgreSQL/pgvector, AI analysis, GitHub integration
Services
Build · Advisory

The challenge

Technical answers were being discovered repeatedly instead of documented once

Validators rely on accurate operating instructions for setup, client software, troubleshooting, upgrades and network participation. But the information that solves a real problem often appears first in a discussion between engineers.

NEAR community conversations on platforms such as Zulip and Telegram contained valuable technical detail. Maintaining documentation from those sources required someone to monitor conversations, identify answers worth keeping, compare them to published pages, draft revisions and obtain approval.

As the validator ecosystem expanded, that manual process became increasingly difficult to maintain consistently. The requirement was not another question-answering chatbot. It was an upstream workflow for finding new documentation content and moving it into the source repository under human review.

The story

01

Ingesting the knowledge already circulating

Lionscraft built DocPythia to collect discussions from community communication streams and process them into candidate technical issues, solutions and documentation topics.

The software organises relevant conversations, identifies recurring questions and uses AI analysis to compare the information against the existing documentation set.

Instead of producing a generic summary of each conversation, the system looks for material that could improve published guidance: missing steps, changed behaviour, newly discovered fixes and explanations that maintainers may want to preserve.

02

A working demonstration showed 135 possible gaps

In a recorded product demonstration, the Lionscraft-built interface showed how community discussion records could be grouped and analysed against the NEAR documentation.

At the time of that demonstration, the application displayed 135 candidate documentation gaps. The reviewer could inspect the underlying issue and proposed change rather than blindly accepting AI-generated text.

That is the important feature of the number: it reflects a working detection and review process. It does not mean 135 production documentation defects were independently verified or all subsequently fixed.

03

From AI proposal to an editable document

The application includes a reviewer interface for examining an issue, comparing the suggested update with the documentation and editing the proposed text. Maintainers can inspect a preview, modify the language or reject the suggestion.

The system was designed as a human-in-the-loop workflow because technical operating instructions carry real consequences. It supports maintainers rather than silently publishing changes on their behalf.

04

Connecting the workflow to GitHub

Lionscraft built the software components needed to turn reviewed documentation changes into the repository workflow used by engineers.

The public DocPythia codebase contains the application interface, processing pipeline, data handling, AI analysis and GitHub pull-request service.

The implementation uses React and TypeScript for the interface, Express/TypeScript backend services, Prisma/PostgreSQL with pgvector, configurable AI analysis and integration with GitHub. A maintainer can therefore move from identified information to a proposed documentation change without manually rebuilding the entire context in a separate editor.

The public repository is MIT licensed.

05

Delivery and handover

The project was developed in collaboration with Meta Pool for the NEAR ecosystem. The historical project records include a signed collaboration agreement, an architecture diagram, implementation material and technical handover instructions.

Lionscraft's founder reports that DocPythia was delivered to Meta Pool for ongoing NEAR documentation maintenance. The public source code and demonstration establish the developed product; a separately verified production-usage record and measured time savings have not yet been established.

What Lionscraft did

Results and impact

01

Working product: A demonstrated web application for collecting technical conversations, identifying candidate documentation gaps and preparing changes.

02

Observable output: 135 candidate gaps displayed during the recorded demonstration.

03

Human control: Reviewer editing, preview and approval before changes enter the documentation workflow.

04

Engineering artifacts: A public MIT-licensed repository containing the application and GitHub integration.

05

Project delivery: Architecture, implementation and handover materials prepared for Meta Pool.

No unsupported figure for hours saved, ongoing daily users or independently verified production changes is included.

Evidence and further reading

The public sources behind this story: announcements, partner reports and coverage. 5 sources.

Discuss a similar challenge

Valuable operational knowledge stuck in chat, tickets or scattered documents?

Lionscraft builds workflow automation that captures useful information from the systems teams already use, prepares actionable updates and keeps people responsible for final review and approval.

Discuss your workflow