trace

Note: This analysis is based entirely on the self-reported description provided by the authors. No external verification or historical data is available.

The description states that trace is a document editor with a focus on preserving the creative process of writing. It functions like a standard document editor but tracks changes through "milestones" — snapshots of document evolution, each containing metadata such as:

• Time elapsed between edits
• Word count at time of milestone
• Typing velocity (words per minute)
• Bulk paste detection (≥50 words)

Each milestone is created based on meaningful change thresholds (e.g., 12+ words changed). The system also includes an AI summarization engine that evaluates these milestones to assign a score indicating likelihood of human authorship. This score determines whether the document passes or fails a legitimacy check.

The tool supports:

• Creating and editing documents
• Joining assignments with access codes
• Tracking due dates
• Submitting assignments
• Viewing milestone summaries (including PDF receipts)
• Instructors reviewing submissions and full revision history

Claim: The product is described as a document editor that preserves writing process data to support authorship verification.

Evidence: Yes, from the project write-up.

The authors position trace not as an AI detection tool but as a way to "preserve the story behind the writing." Their core claim is:

• Traditional AI detectors fail because they judge only final drafts.
• Real writing involves revision, hesitation, and change — signals that disappear in final documents.
• trace preserves those signals to prove authorship.

They describe their solution as:

• A tool for students to demonstrate honest work
• An objective aid for educators to assess legitimacy

Claim: The product aims to shift focus from detecting AI use to preserving evidence of human effort.

Evidence: Yes, in the project write-up.

The primary users are:

• Students (who create and submit documents)
• Instructors (who review submissions and assign work)

The system is designed for educational environments where:

• Assignments are submitted digitally
• There's concern over AI-generated content
• Educators want objective proof of authorship

Claim: The tool targets students and teachers in academic settings.

Evidence: Yes, from the project write-up.

There is no mention of pricing, monetization strategy, or business model in the description. The authors describe trace as a hackathon submission with no indication of commercial intent or revenue streams.

Claim: No evidence of pricing or business model.

Evidence: Not evidenced.

The project was built using:

• Framework: Next.js
• Authentication: Clerk
• Database ORM: Drizzle + NeonDB (PostgreSQL)
• Frontend UI: ShadCN + TailwindCSS
• Document editor: BlockNoteJS (customized)
• AI integration: OpenAI API via Codex plugin, specifically using gpt-5.4-nano model

Key technical features include:

• Server-side components and actions for agentic workflows
• PDF export functionality
• Milestone creation logic based on change thresholds
• AI summarization system integrated via Codex

Claim: The tool uses modern web stack with AI integration.

Evidence: Yes, from the project write-up.

There is no evidence of:

• Revenue
• Customers or users
• Product adoption
• Market traction
• Prior versions or launches

The project was submitted to a hackathon and has no indication of having moved beyond prototype stage.

Claim: No evidence of traction or maturity.

Evidence: Not evidenced.

No mention is made of competitors, nor is there any indication that similar tools exist in the market. The authors frame their solution as novel in its approach to tracking writing process rather than detecting AI use.

Claim: No competitive landscape described.

Evidence: Not evidenced.

• Unproven AI accuracy: The description notes issues with the AI summarization system, including false positives when AI-generated content is pasted into the tool.
• Limited scope: The tool appears to be built for a specific hackathon use case and lacks evidence of broader applicability or scalability.
• No commercial viability: No indication of monetization, user base, or long-term strategy.
• Self-reported validation only: All claims are unverified by third parties.

Inference: The lack of real-world testing and validated performance raises concerns about the product’s readiness for deployment in educational environments.

1. What data was used to train or test the AI summarization system?
2. How does trace handle edge cases like collaborative writing or multi-user documents?
3. Has the tool been tested with actual students and teachers? If so, what were the results?
4. Are there plans to integrate with existing LMS platforms (e.g., Canvas, Schoology)?
5. What are the limitations of the current milestone detection logic?
6. How does trace ensure privacy and data security for student work?