Public documentation

IntelCit product documentation

Public product documentation about what IntelCit is designed to do and how to read current service results. Protected technical material is not included here.

Core concepts

The building blocks referenced across the product.

Platform

The shared product foundation used to organize services, user experiences, language, and review workflows.

Services

Offerings that accept a defined input and return a visible, reviewable output.

Capabilities

Reusable building blocks that services compose.

Evidence & provenance

A reviewable result should keep available source context, output details, and known boundaries together. Confidence and version appear only where supported.

Getting started

The shortest path from a question to a reviewable result.

  1. Pick the service that matches the signal you care about.
  2. Provide the input it expects, captured under reasonable conditions.
  3. Review the visible output against its source, then decide the follow-up. Where the workflow supports it, record the action chosen by the team.

Service input & output reference

Rendered from the same service registry used by the product to reduce content drift.

Evidence and provenance

How to interpret what a result is telling you.

  • Confidence is the model's own estimate for one output — not a validated accuracy figure.
  • Observations are labeled as observations; inferences and candidate events always require human review.
  • Available source, version, and limiting conditions should stay with the result; the fields available differ by service.

Public boundary

What this documentation intentionally does not include.

  • No API endpoints, infrastructure internals, credentials, or protected runbooks.
  • No accuracy percentages, ROI, certifications, or customer case studies.
  • No enforcement, fine, or citation behavior — vehicle-littering output stays a candidate event for human review.

Documentation status

  • This public release covers current product concepts, the five-service registry, and evidence language.
  • Public API and integration specifications are not yet published.
  • Protected internal runbooks, credentials, endpoints, and infrastructure details remain outside public documentation.

Want a walkthrough?

A guided demo can connect these concepts to the service most relevant to your team.