Nine products across seven categories, each with a live public experience, built before WAR existed — each one a reason we know what WAR has to absorb. Two of them taught a lesson we can name and point to in the architecture. The rest are products, and are labelled as products.
The same four fields every time, so the pattern becomes visible by repetition. Where the fourth field is missing, that is the honest state — not an omission.
A row here is a causal claim. Rows we cannot personally stand behind are cut, not softened.
| Venture | Domain | The limitation it exposed | The WAR component that answers it |
|---|---|---|---|
| KiranaMitra | Retail | Natural-language intent is ambiguous, and the ambiguity is culturally specific — udhaar khata is not accounts receivable, and translation flattens the difference. |
Intent Understanding Layer →
Genesis Vol. 2 §4–§11 · WAR-TRACE-001
|
| LetsClarifAI | Education | Understanding needs structured knowledge, not prose. |
The knowledge / graph layer →
Genesis Vol. 2
|
The portfolio does not demonstrate breadth. It explains why each part of WAR exists.
These two are outputs of the runtime, not precursors to it — which is why they close this page rather than appearing on the spine or in the Origin Map.
Intent → Build Along™ → blueprint → generated homepage → Artifact Center. Organisation-aware, persistent, downloadable. Runs on WAR in production today.
Structured objectives → provider routing → live web-grounded research → cited artifact. Runs on WAR in production today.
Intent → Build Along™ → Document Blueprint → Evidence → generated proposal → branded, print-ready artifact. Organisation-branded, evidence-grounded, print-ready. Runs on WAR in production today.
Intent → Build Along™ → deck blueprint → per-slide generation → structured deck → Deck Critique. Generated slide by slide against a real progress pipeline, then critiqued against its own brief. Runs on WAR in production today.
Intent → Build Along™ → Document Blueprint → your real history → branded, print-ready artifact. Written against the role actually being applied for, not a template with a name dropped into it. Runs on WAR in production today.
Intent → Build Along™ → Document Blueprint → employer and role context → branded, print-ready artifact. Addressed to that employer and that role. Runs on WAR in production today.
Attached sources → evidence extraction → Document Blueprint → cited summary. The first pack to require evidence before it will generate at all. Runs on WAR in production today.
Intent → Build Along™ → page blueprint → generated page → verification pass. Generated against a stated conversion goal, then checked against it. Runs on WAR in production today.
Attached requirement document → evidence extraction → Test Brief → structured test cases. Refuses to generate on zero evidence rather than inventing coverage. Runs on WAR in production today.
Intent → cost and competitor inputs → pricing blueprint → tier recommendations with the margin arithmetic shown. Strategy Studio's first pack, and the point at which all five Studios carry one. Runs on WAR in production today.
A submitted page → structured inspection → evidence-scored audit report. Scores what it can verify and states plainly what it could not. Runs on WAR in production today.
Intent → Build Along™ → Document Blueprint → recipient and occasion context → branded email artifact. Written to a stated recipient and occasion, not a generic template. Runs on WAR in production today.
Intent → Build Along™ → real inferred workflow → generated interactive board application. A downloadable, offline-capable application, not a document — the column structure itself is inferred from what you describe, not a fixed template. Runs on WAR in production today.
