Technical reference
Build against the whole system,
not a chat endpoint.
Architecture, interfaces, retrieval, evaluation, deployment, and operating guidance for teams integrating COGNI.BUILD into an existing product.
The guided path
Twenty-seven minutes, end to end.
Six interactive stops, in the order the questions actually come up. Nothing to install and nothing to read first — each one is a working model you can push on. If you only have time for one, take the second.
-
01
Where it sits in an app you already have
The seam between your application and the framework — what the host keeps, what the platform brings, and what is refused in each direction.
~4 min · interactive -
02
Who sees what
One question, two people, two correct answers. Then move the scope predicate out of the query and watch two specific failures appear — one of which reports nothing at all.
~5 min · interactive -
03
Nothing a passage can do
Untrusted content in model context is the design, not an oversight. Poison a document, run the turn, and watch where the attack stops — including the one that does not.
~4 min · interactive -
04
How you know a change made it better
What fifty labelled questions buy you: a retrieval suite that needs no model calls, the selection test almost nobody runs, and a gate that stops a regression shipping.
~5 min · interactive -
05
What it actually costs
An editable model, prices included. In the worked deployment, a quarter of the bill is suggestions nobody asked for — and that is the line most teams never look at.
~4 min · interactive -
06
What it would take for yours
Fourteen findings from a real conformance assessment, in dependency order, priced by what deferring each one costs later.
~5 min · interactive
Prefer to read rather than click? The compendium covers all of it in eight documents, and the source blueprint goes down to the file level.
Choose a path
Start with the question you need to answer.
Where does COGNI.BUILD sit in an existing application?
Walk through the host surface, control path, boundaries, and managed offering.
Open in-place guide ↗ PlanningWhat gaps should this product close first?
Prioritize the work required to reach a conformant, operable implementation.
Open conformance planner ↗ EvaluatingHow do we know a change is actually better?
Explore case sets, judges, gates, invalidation, and release eligibility.
Open evaluation lab ↗Architecture
The reference, at the depth you need.
Read the product as a layered system or inspect the source-shaped framework. Both describe the same boundaries and request path.
Evaluate & operate
Quality, cost, and boundaries are part of the design.
Build suites, define gates, and make changes earn release.
SecurityNothing a passage can doThe injection surface, and the one defence that holds structurally.
EconomicsWhat it actually costsModel conversation, ambient work, routing, and workload sensitivity.
DeploymentRun it where commitments requireCompare managed, hybrid, and self-hosted boundaries.
Technical reference