Turn evidence into a Problem Case before designing the solution.
Analysis is the evidence-grounding step. It converts the project's source material into a structured description of the problems, affected users, situations, and evidence links that the Build can rely on later.
What Analysis is for
The goal is not to invent features. The goal is to understand the recurring problems well enough that a later Build can make decisions from a stable Problem Case.
- Separate distinct problems instead of collapsing everything into one vague pain point.
- Identify who experiences each problem and in what situation.
- Keep every problem traceable to known evidence IDs.
- Version the result so later Builds can point to the exact Problem Case they used.
Analysis through MCP
When you use Immensity through a connected coding agent, the host model performs the reasoning. Immensity supplies the evidence, instructions, schema, validation, and persistence.
start_analysis(project_id) → read every evidence page → host model produces structured Analysis save_problem_analysis(project_id, source_fingerprint, analysis) → get_problem_case(project_id)
1. Start with the current evidence
start_analysis returns evidence-grounded context, Analysis instructions, the exact output schema, paging metadata, and a sourceFingerprint.
If the response is paged, the host should retrieve all evidence pages before producing the final Analysis. Saving against an incomplete context undermines the grounding step.
2. Let the host model reason
The connected model uses the supplied instructions and schema to produce the structured Analysis. This reasoning happens in the host client, not in a second Immensity model call.
The output is expected to identify problem units with fields such as title, description, affected users, situation, evidence IDs, and relationships to other problems.
3. Save only against the same evidence state
save_problem_analysis validates the output schema and verifies that the evidence has not changed since start_analysis.
If the fingerprint is stale, Immensity rejects the save and the client should call start_analysis again. That prevents a newly saved Analysis from claiming to represent evidence it never actually saw.
4. Use the Problem Case as the next contract
A successful save creates a new Analysis version and makes it the current Problem Case for the project. The Build workflow should use that current version rather than reconstructing the problem from scratch.
Website vs. MCP
| Surface | Reasoning | Immensity owns |
|---|---|---|
| Immensity web app | Immensity's web Analysis workflow | Evidence, orchestration, validation, versioning, persistence |
| MCP client | The connected host model | Evidence, instructions, schema, validation, versioning, persistence |