Follow the evidence.
Select a layer to inspect its responsibility. Each layer passes a bounded record forward; it does not pass unrestricted access to the source.
Source admission
Ownership · Period · Data class
Source admission
Read-only connections and supported CSV imports bring in operational observations. Source ownership, period and data class establish what the records mean before evidence is assembled. The intake path owns validation; the model cannot choose new sources or widen their scope.
Evidence bundles
Aggregates · Coverage · Provenance
Evidence bundles
The bundle builder assembles aggregates, source coverage, data gaps and suppression metadata. The generated-Case path receives this bounded bundle rather than raw source rows.
Analysis & Cases
Finding · Context · Working record
Analysis & Cases
Analysis develops a reading from the permitted evidence. Cases link the finding to its source bundle and retain context, status and outcome records for later review.
Workflows & Voice
Approved scope · Authorized artifacts
Workflows & Voice
Workflows repeat reviews within approved scope. Voice makes the evidence and company context available through conversation, using records the viewer may read. Neither a question nor a model answer can grant access or authorize an external action.
Different records. Different responsibilities.
| Record | What it carries | Boundary |
|---|---|---|
| Source | Admitted observations and their original context. | Source permission and data classification. |
| Evidence bundle | Aggregates, coverage, gaps and provenance. | Privacy gates before model input. |
| Case | A finding, its evidence and the evolving working record. | Current Case visibility does not unlock raw sources. |
| Workflow contract | Approved objective, sources, capabilities and limits. | A published version is immutable; changes need a new draft. |
| Voice statement | Observed facts, interpretation, unknowns and artifact references. | The statement contract preserves audience and freshness boundaries. |
Every layer carries context.
Each owns a boundary.
A source record, an analytical reading and a person’s decision should remain distinguishable. That separation lets Ginsi preserve continuity while checking who may read the result and what the evidence can support.
How the boundaries hold together.
Related observations create questions.
The evidence graph connects related observations. Context memory carries governed company records into later analysis. These links help a reading consider what is already known; they do not establish causality or give every colleague the same view.
A generated answer cannot grant itself access.
Readers resolve the requested record through its owning service. Company membership, role, Case visibility and privacy state determine what may be released. Sensitive Case paths check again after privileged reads, because permission may change while work is in progress.
Carry useful context into the next review.
Cases retain findings, context and lifecycle outcomes. Later evidence can show whether a question persists, fades or recurs. Ginsi connects those reviews without treating a later change as proof that an earlier decision caused it.
