{
  "version": 1,
  "origin": "guided",
  "createdAt": "2026-10-21T00:00:00.000Z",
  "input": {
    "title": "Research library",
    "idea": "Our team needs a searchable library of research notes. People should be able to add sources, attach documents and find earlier work. An optional AI feature could suggest related notes with links back to the originals.",
    "audience": "An internal research team",
    "outcome": "A researcher finds earlier relevant work and can open its original source.",
    "requirements": "Create a note with a source link\nAttach a document to a note\nSearch titles and note content\nSuggest related notes with source links",
    "workflow": "Researcher adds a note and its source\nA colleague searches a topic\nThey inspect the result and open the original source",
    "platform": "internal",
    "capabilities": [
      "accounts",
      "uploads",
      "ai"
    ],
    "extras": [
      "hosting",
      "evaluation"
    ],
    "answers": {},
    "timeline": "",
    "budget": "",
    "hourlyRate": null,
    "weeklyCapacity": null,
    "exclusions": "Public publishing and automated external research"
  },
  "document": {
    "title": "Research library",
    "summary": "Our team needs a searchable library of research notes. People should be able to add sources, attach documents and find earlier work. An optional AI feature could suggest related notes with links back to the originals.",
    "audience": "An internal research team",
    "success": "A researcher finds earlier relevant work and can open its original source.",
    "exclusions": [
      "Public publishing and automated external research"
    ],
    "assumptions": [
      "This is a first-release planning draft; proposed requirements and tests need owner review.",
      "No implementation stack, external pricing or delivery commitment has been independently verified."
    ],
    "journeys": [
      {
        "actor": "An internal research team",
        "steps": [
          "Researcher adds a note and its source",
          "A colleague searches a topic",
          "They inspect the result and open the original source"
        ]
      }
    ],
    "requirements": [
      {
        "id": "R01",
        "title": "Create a note with a source link",
        "description": "Deliver this visitor-specified capability: Create a note with a source link",
        "priority": "must",
        "acceptance": [
          "Given a user permitted to perform this task, when they complete “Create a note with a source link”, then the intended result is visible and can be checked against an agreed worked example.",
          "When required information is missing or invalid, the system explains the problem and preserves any valid work already entered."
        ],
        "dependsOn": [],
        "reviewed": false,
        "effortHours": null
      },
      {
        "id": "R02",
        "title": "Attach a document to a note",
        "description": "Deliver this visitor-specified capability: Attach a document to a note",
        "priority": "must",
        "acceptance": [
          "Given a user permitted to perform this task, when they complete “Attach a document to a note”, then the intended result is visible and can be checked against an agreed worked example.",
          "When required information is missing or invalid, the system explains the problem and preserves any valid work already entered."
        ],
        "dependsOn": [],
        "reviewed": false,
        "effortHours": null
      },
      {
        "id": "R03",
        "title": "Search titles and note content",
        "description": "Deliver this visitor-specified capability: Search titles and note content",
        "priority": "must",
        "acceptance": [
          "Given a user permitted to perform this task, when they complete “Search titles and note content”, then the intended result is visible and can be checked against an agreed worked example.",
          "When required information is missing or invalid, the system explains the problem and preserves any valid work already entered."
        ],
        "dependsOn": [],
        "reviewed": false,
        "effortHours": null
      },
      {
        "id": "R04",
        "title": "Suggest related notes with source links",
        "description": "Deliver this visitor-specified capability: Suggest related notes with source links",
        "priority": "must",
        "acceptance": [
          "Given a user permitted to perform this task, when they complete “Suggest related notes with source links”, then the intended result is visible and can be checked against an agreed worked example.",
          "When required information is missing or invalid, the system explains the problem and preserves any valid work already entered."
        ],
        "dependsOn": [],
        "reviewed": false,
        "effortHours": null
      },
      {
        "id": "R05",
        "title": "Recover from an interrupted workflow",
        "description": "Define and implement safe failure handling for the primary workflow, including duplicate submission and connection loss.",
        "priority": "must",
        "acceptance": [
          "An interrupted operation reports its state and offers a recovery action.",
          "Repeating a completed action does not accidentally create a second completed operation."
        ],
        "dependsOn": [
          "R01"
        ],
        "reviewed": false,
        "effortHours": null
      },
      {
        "id": "R06",
        "title": "Support accessible use",
        "description": "Make the primary workflow operable by keyboard, label its controls and communicate errors in text.",
        "priority": "must",
        "acceptance": [
          "A user can complete the primary workflow with a keyboard and visible focus.",
          "Inputs have programmatic labels, and errors identify both the problem and the affected input."
        ],
        "dependsOn": [],
        "reviewed": false,
        "effortHours": null
      }
    ],
    "architecture": [
      {
        "area": "Interface",
        "proposal": "A responsive browser interface for the primary workflow and its recovery states.",
        "rationale": "A first-release proposal. Confirm supported devices, connectivity and accessibility needs before choosing an implementation."
      },
      {
        "area": "Application boundary",
        "proposal": "Server-side operations validate requests and enforce permissions before applying changes.",
        "rationale": "Business rules should remain consistent across interfaces and integrations."
      },
      {
        "area": "Data",
        "proposal": "A transactional data store for the core records, with explicit ownership, retention and backup decisions.",
        "rationale": "The final schema depends on the confirmed workflow. The entities below are starting proposals."
      },
      {
        "area": "AI boundary",
        "proposal": "A server-side model adapter with bounded usage, evaluation cases and explicit fallback behaviour.",
        "rationale": "AI output needs a defined review boundary. No specific provider, model or price is assumed."
      }
    ],
    "entities": [
      {
        "name": "WorkItem",
        "fields": [
          "id",
          "status",
          "createdAt",
          "updatedAt"
        ],
        "purpose": "Proposed representation of the core workflow record. Rename and expand it to match the confirmed domain."
      },
      {
        "name": "User",
        "fields": [
          "id",
          "role",
          "createdAt"
        ],
        "purpose": "Proposed identity and role reference; authentication and access rules still need review."
      },
      {
        "name": "Attachment",
        "fields": [
          "id",
          "workItemId",
          "storageReference",
          "mediaType",
          "createdAt"
        ],
        "purpose": "Proposed attachment metadata. Storage access and retention require explicit decisions."
      }
    ],
    "milestones": [
      {
        "title": "01 · Resolve the blocking decisions",
        "outcome": "The project owner confirms scope, data boundaries and failure behaviour. An engineer reviews the proposed requirements and tests.",
        "requirementIds": []
      },
      {
        "title": "02 · Deliver a complete vertical slice",
        "outcome": "Demonstrate the primary workflow in a test environment, including validation and recovery states.",
        "requirementIds": [
          "R01",
          "R05"
        ]
      },
      {
        "title": "03 · Complete the agreed release scope",
        "outcome": "Deliver the remaining first-release requirements and run their acceptance criteria.",
        "requirementIds": [
          "R02",
          "R03",
          "R04"
        ]
      },
      {
        "title": "04 · Verify and hand over",
        "outcome": "Review accessibility, permission boundaries and operational recovery. Record test evidence before release approval.",
        "requirementIds": [
          "R06"
        ]
      }
    ],
    "decisions": [
      {
        "id": "data",
        "question": "What data is stored, and how long should it be kept?",
        "reason": "Include personal or sensitive information, deletion rules and who controls access.",
        "answer": "",
        "blocking": true
      },
      {
        "id": "failure",
        "question": "What must happen when the main workflow fails?",
        "reason": "Consider lost connections, duplicate submissions and recovery without losing work.",
        "answer": "",
        "blocking": true
      },
      {
        "id": "accounts",
        "question": "Who can access or change what?",
        "reason": "Roles and permissions affect the data model, tests and every protected workflow.",
        "answer": "",
        "blocking": true
      },
      {
        "id": "uploads",
        "question": "What files are accepted, and who can retrieve or delete them?",
        "reason": "File types, size limits, retention and access controls determine storage behaviour.",
        "answer": "",
        "blocking": true
      },
      {
        "id": "ai",
        "question": "What may AI decide, and what requires human review?",
        "reason": "Grounding, evaluation, cost limits and failure behaviour are part of the product.",
        "answer": "",
        "blocking": true
      },
      {
        "id": "integrations",
        "question": "Which existing tools or systems must it connect to?",
        "reason": "Name required integrations and whether access is already available. “None” is a useful answer.",
        "answer": "",
        "blocking": false
      },
      {
        "id": "launch",
        "question": "Who signs off the first release, and how will they test it?",
        "reason": "A named owner and a realistic test setting make the handoff easier to execute.",
        "answer": "",
        "blocking": true
      }
    ],
    "complexity": {
      "level": "undetermined",
      "rationale": "Complexity needs engineering review of the proposed requirements, integrations and open decisions. Add effort estimates per requirement to calculate a planning total.",
      "costDrivers": [
        "Number of workflows and user roles",
        "User accounts",
        "File uploads",
        "AI features",
        "Data migration, testing and launch operations"
      ]
    }
  }
}