ASK VINDEX3 · THE GRAPH IS THE AUTHORITY · READ-ONLY
ASK
Any answerable question about the public VINDEX3 universe — resolved against the knowledge graph, never guessed. Ask does not return chat: it returns typed VINDEX explanations — a definition, a component flow, a status report, the specification's own words — each rendered by HAUSE, each showing its interpretation, its path, and the Record line it answers to. When the graph does not establish something, Ask says exactly that.
ASK VINDEX3 — THE DOCUMENTATION IS A DATABASE TOO
If the model is a database, the documentation should feel like one.
A deterministic resolver over the VINDEX knowledge graph, snapshot 3.0-candidate (2026-08-30): question → five-word canonical form → entity and status resolution → typed explanation, rendered by HAUSE. The 48 canonical answers are a warm cache and a conformance suite, not the knowledge — behind them sit 63 graph entities, the Record's gates as status nodes, and the specification itself as a retrievable corpus. When no supported subgraph exists, Ask says so rather than guessing; the graph is the authority, and the synthesis tier can only ever narrate it. The contract, in one line: every answer names its source — a graph path, a spec passage, or a Record row — and when the current VINDEX3 graph does not establish an answer, Ask refuses.
Prefer to walk the structure yourself?