Maze

Build me a focused feedback boards, interviews and product research workflow for the personal core of Maze. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Resend. Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
- Paid product context: Run small unmoderated prototype tasks with consent and basic completion analytics. Build only this DIY scope: Run small unmoderated prototype tasks with consent, collect structured feedback with basic completion analytics, merge duplicates, connect evidence to themes, and publish a transparent research view.
- Create public and private feedback intake with consent text and optional contact details.
- Support posts, votes, comments, tags, statuses, owners, and duplicate merging.
- Add a research note type with evidence links, quotes, themes, and confidence. Publish a read-only roadmap or findings page using only explicitly public items.
- Use a local web page with input, progress, review, and export views. Required input or access: public HTTPS deployment; Resend API key. Keep credentials in .env.
- Recovery: If Resend API key is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: participant panel, prototype integrations, testing infrastructure, analytics, and recruitment; large participant panel. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Maze

## Project scope
Run small unmoderated prototype tasks with consent, collect structured feedback with basic completion analytics, merge duplicates, connect evidence to themes, and publish a transparent research view.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Maze, run small unmoderated prototype tasks with consent and basic completion analytics. The hard boundary is participant panel, prototype integrations, testing infrastructure, analytics, and recruitment, plus participant network, synthesis workflow, and collaboration.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- PostgreSQL
- public HTTPS deployment
- Resend API key
- optional video-call links

## Stack and architecture
- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Resend.
- Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
- Interface for this feedback boards, interviews and product research workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- If Resend API key is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Keep API keys and OAuth secrets in .env; redact them from logs, generated files, and error responses.
- State the practical limit: participant panel, prototype integrations, testing infrastructure, analytics, and recruitment.

## Agent implementation rules
- Project rule, data: Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
- Project rule, behavior: Create public and private feedback intake with consent text and optional contact details.
- Project rule, recovery: If Resend API key is unavailable, keep the source record and show a recoverable error instead of a fabricated result.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this feedback boards, interviews and product research operation with sample or user-owned data: Create public and private feedback intake with consent text and optional contact details.
- Show a concrete result or export: Provide email notifications, moderation, export, deletion, and an audit log.
- State the practical limit: participant panel, prototype integrations, testing infrastructure, analytics, and recruitment.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Resend. Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
2. Phase 2, implement: Create public and private feedback intake with consent text and optional contact details.
3. Phase 3, implement: Support posts, votes, comments, tags, statuses, owners, and duplicate merging.
4. Phase 4, review and output: Add a research note type with evidence links, quotes, themes, and confidence. Provide email notifications, moderation, export, deletion, and an audit log.
5. Phase 5, recovery and acceptance: If Resend API key is unavailable, keep the source record and show a recoverable error instead of a fabricated result. Verify this invariant with a saved fixture: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs. State the practical limit: participant panel, prototype integrations, testing infrastructure, analytics, and recruitment.

## Paid-product capabilities outside this build
- participant panel, prototype integrations, testing infrastructure, analytics, and recruitment
- large participant panel
- recording and transcription infrastructure
- advanced research repository
- enterprise governance

## Implementation prompt
Build me a focused feedback boards, interviews and product research workflow for the personal core of Maze. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Resend. Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
- Paid product context: Run small unmoderated prototype tasks with consent and basic completion analytics. Build only this DIY scope: Run small unmoderated prototype tasks with consent, collect structured feedback with basic completion analytics, merge duplicates, connect evidence to themes, and publish a transparent research view.
- Create public and private feedback intake with consent text and optional contact details.
- Support posts, votes, comments, tags, statuses, owners, and duplicate merging.
- Add a research note type with evidence links, quotes, themes, and confidence. Publish a read-only roadmap or findings page using only explicitly public items.
- Use a local web page with input, progress, review, and export views. Required input or access: public HTTPS deployment; Resend API key. Keep credentials in .env.
- Recovery: If Resend API key is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: participant panel, prototype integrations, testing infrastructure, analytics, and recruitment; large participant panel. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.