Kikigaki Archiver

The description states that Kikigaki Archiver is:

• A mobile-first web app built with Next.js 16 and React 19.
• It uses GPT-5.6 via the OpenAI Responses API for both interview guidance and archive generation.
• It supports a structured oral-history interview process, asking one question at a time.
• After an interview, it produces:
  • An edited transcript preserving speaker phrasing;
  • An evidence-linked life timeline;
  • Three exhibition caption proposals;
  • A downloadable four-page A5 booklet PDF.
• The app includes optional voice input via the Web Speech API and uses React PDF for local PDF generation.
• It has a fictional reviewer path that works without an API key.

Inference: The product is described as a prototype or proof-of-concept, not a production-ready commercial offering. It is not evidenced to be used in real interviews or deployed beyond the hackathon submission.

The description states:

• The project was inspired by “portrait-exhibition practice” in rural Japan.
• It aims to help interviewers listen carefully and turn conversations into educational and exhibition material without flattening the speaker's voice.
• It positions itself as a tool for preserving local history through respectful, structured interviews.

Inference: The positioning is rooted in cultural preservation and ethical AI use. However, no evidence of market positioning or branding beyond the hackathon submission exists.

The description states:

• The product targets rural Japanese communities where oral history is important.
• It is intended for use by facilitators such as schools, libraries, museums, and local organizers.
• The fictional demo path allows review without API keys or personal data.

Inference: The target customer segment appears to be educational institutions, cultural organizations, and local heritage groups. No evidence of actual customers or user personas beyond the author’s self-description is provided.

The description states:

• There is no mention of pricing.
• It includes a fictional reviewer path that works without an API key.
• The live mode uses GPT-5.6 and requires an API key.
• Future plans include participant-controlled redaction, encrypted storage, deletion controls, and archival metadata export.

Inference: No business model or pricing structure is described. The product appears to be in early development with no commercialization strategy evident.

The description states:

• Built with Next.js 16, React 19, Vercel AI SDK, OpenAI Responses API (gpt-5.6).
• Uses Zod for schema validation.
• Implements Web Speech API for voice input and read-aloud.
• Generates PDFs using React PDF with embedded Japanese fonts.
• Includes automated tests and supports desktop/mobile environments.
• OpenAI Codex was used to scaffold the repository, draft prompts, implement UI/API routes, and verify behavior.

Inference: The technical stack is modern and well-suited for a web-based AI tool. However, no evidence of production deployment or scalability beyond the demo exists.

The description states:

• It was submitted to the OpenAI 2026 hackathon.
• A fictional demo exists that works without API keys.
• The submission includes a baseline commit (0890138) from July 18, 2026.
• Accomplishments include full workflow, GPT use in two stages, evidence-linked timelines, and printable booklets.

Inference: There is no evidence of traction, revenue, or user adoption. The project is described as a hackathon prototype with no indication of real-world usage or product-market fit.

The description does not mention any competitors or market context beyond its own self-positioning.

Inference: No competitive analysis or market positioning relative to other oral-history tools or AI interview platforms is provided. The project appears to be in a niche space with no known direct competitors mentioned.

• The product is described as a hackathon submission with no evidence of real-world use.
• No revenue, customers, or traction are reported.
• The fictional demo path does not reflect actual user behavior or data handling.
• There is no indication of how the tool would scale beyond a prototype.
• The inclusion of GPT-5.6 raises questions about API costs and dependency on external services without a clear monetization plan.

Inference: The project lacks commercial viability or evidence of traction, and its current form appears to be a proof-of-concept rather than a product ready for market.

1. What is the actual use case or problem you are solving beyond the fictional demo?
2. Have you conducted any interviews with real users or communities?
3. How do you plan to monetize this tool, and what is your go-to-market strategy?
4. Are there any plans for data privacy compliance (e.g., GDPR, CCPA)?
5. What are the technical challenges in scaling beyond a demo environment?
6. Do you have any partnerships with museums, schools, or cultural institutions?