LFU Community

Note

This analysis is based entirely on self-reported information from the author. No independent verification, funding rounds, headcount, customers, or revenue data are available.

The description states that LFU Community is:

• A "bilingual, governed community-justice workspace"
• Designed to transform fragmented war-damage evidence into a transparent, human-authorized path toward justice
• An MVP demonstrating one complete workflow for the Dmytrivska Territorial Community in Bucha district

The product includes features such as:

• Preservation of sources, snapshots, assertions, versions, and provenance
• Distinguishing public facts from synthetic protected demonstration records
• AI analysis that proposes structured findings
• Human authorization required for every AI finding
• Task creation and audit receipts from decisions
• Calculation of dossier readiness without concealing missing or contradictory evidence
• Public projection using a positive allowlist

The description also notes that the application uses Next.js, React, TypeScript, Zod, Vitest, Playwright, and Vercel. The AI integration uses gpt-5.6-sol through a server-only OpenAI Responses API adapter.

Claim

The product is described as a "governed community-justice workspace" that preserves evidence and requires human authorization for AI findings.

Evidence Author's own write-up

The author positions LFU Community as:

• A tool for Ukrainian territorial communities affected by Russian aggression
• A solution to the challenge of proving what happened across changing records, incomplete evidence, different valuation periods, and conflicting official figures
• A system that preserves institutional memory with provenance, verification status, and decision-making authority

The claim evolution appears to be:

1. Initial problem: Communities need trustworthy institutional memory for legal action
2. Proposed solution: A governed workspace that combines AI analysis with human authorization
3. Core capability: Refusing to manufacture readiness when evidence is insufficient
4. Differentiation: Unlike conventional databases, it preserves why values changed and who authorized changes

Claim

The product aims to preserve institutional memory that tracks where every fact came from, what has been verified, what remains disputed, who made each decision, and whether the evidence is actually ready for legal action.

Evidence Author's own write-up

The description states:

• Primary users are Ukrainian territorial communities affected by Russian aggression
• Specifically mentioned: Dmytrivska Territorial Community in Bucha district
• The product is designed for "local authorities, civil-society institutions, counsel, and affected people"
• It supports "individual victims" through consultations and evidence support

The ICP appears to be:

• Ukrainian territorial communities
• Local authorities
• Civil-society institutions
• Legal counsel
• Affected individuals

Claim

The target customer is Ukrainian territorial communities affected by Russian aggression.

Evidence Author's own write-up

Not evidenced.

Finding

No information provided about business model, pricing, or monetization strategy.

The description states:

• Built with: chatgpt-5.6, codex, next.js, openai, playwright, react, typescript, vercel, vitest, zod
• Uses Codex as primary engineering environment
• Eight gated stages in development process
• AI boundary integrates gpt-5.6-sol through a server-only OpenAI Responses API adapter
• Strict structured output and valid evidence references required
• Supports citations, uncertainty, and abstention
• Enforces bounded timeouts and zero automatic retries
• Rejects malformed or injection-like output
• Cannot mutate governed memory, publish information, or make legal decisions
• Submitted demonstration is labeled VERIFIED_FIXTURE
• No API key stored in repository
• Demonstrates both deterministic fixture and live-AI paths that are visibly distinguished

Claim

The technical architecture includes strict separation between internal and public information, deterministic fixtures, and live-AI paths.

Evidence Author's own write-up

Not evidenced.

Finding

No evidence of traction, revenue, customers, or adoption beyond the hackathon submission.

Not evidenced.

Finding

No information provided about competitive landscape or existing solutions in this space.

• Single-person team: The project is built by one individual (LFUlab Tselovalnichenko)
• Hackathon demo only: The description indicates this is a hackathon submission with no evidence of further development or pilot use
• No commercial traction: No evidence of revenue, customers, or adoption beyond the demonstration
• Limited scope: The MVP only covers one community (Dmytrivska Territorial Community)
• Unverified claims: All information is self-reported and unverified
• AI integration constraints: The AI cannot make decisions or mutate memory, which may limit functionality

Inference The lack of evidence for traction, customers, or revenue suggests this project has not yet moved beyond the demonstration phase.

1. What is the current status of the project beyond the hackathon demo?
2. Have you piloted this with any actual Ukrainian territorial communities?
3. What are the plans for scaling beyond the MVP?
4. How will you ensure data privacy and security in a production environment?
5. What is your roadmap for moving from demonstration to commercial product?
6. How do you plan to handle legal liability issues around AI-assisted decision-making?
7. What are the technical challenges in moving from the current demo to a production system?

Inference These questions address the key gaps in evidence and the unverified claims made by the author.