Research / architecture

Current research

CA-A1 — InfoScope boundary

Type: architecture Updated: 2026-10-05 Scale: cross-jurisdictional Path: ../architecture/INFOSCOPE-BOUNDARY.md

architectureinfoscopeai-boundary

InfoScope boundary

CA-A1 architecture record. Updated: 2026-10-05. Architecture boundary only — does not activate CA-AI1 or corpus ingestion.

Permitted role (advisory surfaces)

Future Cicada InfoScope may assist with:

Every one of these produces artefacts labelled as AI-derived, carrying provenance that records the model/process that produced them.

Prohibited role (hard boundary — structural, not policy)

InfoScope must not:

How the architecture enforces it

  1. ai_artefact flag — any record derived from AI/InfoScope output is structurally marked; it can never carry authority-class status.
  2. Advisory ≠ authoritative class — AI-derived material can attach only to non-authoritative fields (evidence discovery suggestions, research notes); object schemas for consequential states require an authority_ref, which an AI process can never hold.
  3. No write path to canonical records — ingestion flows produce proposals reviewed by humans; the canonical write is a human-attributed event.
  4. Distinguishability — published surfaces must render AI-derived material visibly distinct from canonical institutional records.
  5. Digest discipline — AI artefacts cited by canonical records are digest-pinned so later drift is detectable.

Boundary to corpus itself

This architecture record concerns runtime assistance. Use of this research corpus by InfoScope for retrieval is the CA-AI1 contract — separately gated, untouched here.