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 keeps its source context, output details, reviewer decision, and recorded action together.

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.

What stays protected

Public documentation explains the product while operational security stays private.

  • No API endpoints, infrastructure internals, credentials, or protected runbooks.
  • Product methods connect to public research and plain-language service guidance.
  • No enforcement, fine, or citation behavior — vehicle-littering output stays a candidate event for human review.

What you will find here

  • Product concepts, the five-service catalog, and the operating loop.
  • Inputs, outputs, evidence records, and human-review steps for every service.
  • Links to research foundations and guided next steps for municipal teams.

Want a walkthrough?

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