CivicDataForgeBuyer outcomes › Evidence bundles

Three evidence bundles. One proof discipline.

Each bundle begins with one real identifier, names the decision states before you run it, and keeps source failure separate from a negative result. Inspect the smallest useful answer first. Add a batch or monitor only after it fits.

Official source identityObservation timeExplicit scopeFingerprints or receiptsResponsible absenceFail-closed monitoring
United States · Production

U.S. Property Compliance Evidence Bundle

Check what a supported official permit, license, or violation source publishes for a property and preserve the decision trail.

Minimum inputOne property address and its supported city or jurisdiction.
Decision states
EVIDENCE_FOUNDREVIEW_REQUIREDNO_PUBLISHED_MATCHSCOPE_INCOMPLETESOURCE_UNAVAILABLE
Evidence packetDecision, scope completeness, observation time, source URL, jurisdiction, matched record, match method/confidence, and decision receipt hash.
MonitoringAccepted state advances only after a complete eligible source read. Capped, partial, or failed reads cannot become disappearance events.
BoundaryNO_PUBLISHED_MATCH is not an illegality finding and says nothing about another authority's records.
India · Production evidence + comparison

India Supplier Change Monitor

Anchor a supplier or counterparty to an exact CIN, preserve the official company-master snapshot, and identify changed published fields on a later bounded refresh.

Minimum inputOne exact CIN. For the next comparison, supply the previously accepted CIN fingerprint.
Change states
uncomparednewunchangedchangedsource_limited_or_unavailable
Evidence packetCIN, company name/status, entity key, source and fetch time, query hash, record fingerprint, change type, source reliability, run receipt, and optional exact-CIN GLEIF corroboration.
MonitoringOnly returned CINs are compared. A bounded query does not infer removed companies; warnings and source failures do not become changes.
BoundaryThis periodic company-master evidence is not real-time MCA status or a complete KYC, sanctions, ownership, or consented-document workflow.
China-facing · Integration route

China-facing Developer Integration Bundle

Give a Chinese-speaking application or AI agent an Actor, REST, or MCP path to current U.S. property and India company evidence without maintaining every source adapter.

Minimum inputTarget product or record type, jurisdiction, and one supported U.S. address or India CIN.
Routing states
ROUTE_READYNEEDS_SCOPEUNSUPPORTED_CHINA_NATIVE_SOURCE
Integration packetTarget product, input/output schema, execution interface, authentication, billing source, underlying source identity, evidence boundary, and receipt/fingerprint fields.
MonitoringThe selected U.S. or India product owns monitoring semantics. The language/integration layer creates no parallel baseline and cannot manufacture a negative result.
BoundaryThis is Chinese-language integration for existing products. Mainland-China official-source coverage is zero; no bulk China registry or resale rights are claimed.

The non-negotiable rule

Unknown is not negative. If a source is unavailable, a pull is incomplete, or the requested jurisdiction is unsupported, the bundle says so. It does not turn missing evidence into noncompliance, disappearance, or a failed company decision.

Machine-readable bundle manifest · Official source health · Cross-market reliability · Support
CivicDataForge provides research and compliance support, not a consumer report or issuing-authority decision. Do not use a result as the sole basis for a regulated eligibility, KYC, or adverse decision.