STAGE 1: Constrain the product
Concept: An assistant needs a clear task and a bounded knowledge source.
Task: Define supported questions, excluded decisions and a no-answer response.
Acceptance: Do not promise general factual reliability from a small demo.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 2: Design retrieval
Concept: Retrieval quality and answer quality are separate failure points.
Task: Split three sample documents into traceable passages and map questions to supporting evidence.
Acceptance: Every passage keeps a stable source identifier.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 3: Evaluate the answer
Concept: Fluent text can still be unsupported.
Task: Build ten test questions including missing evidence, conflicting information and an instruction embedded in a document.
Acceptance: Treat retrieved document instructions as untrusted content.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 4: Package the prototype
Concept: A useful demo explains limits and cost.
Task: Provide a local or mocked workflow, error handling and a cost-aware implementation note.
Acceptance: A paid API is optional; do not claim the mocked workflow executed a live model.

My assumptions:

My work / file link:

My checks and results:

What I changed:
