JiCoRedact. Approve. Document.

Glossary

JiCo's own vocabulary, explained in plain words - the panel and this website read from the same source.

From A to Z

Blocked (never read)

Projects JiCo never reads - not on a reference, not on an explicit request.

An area under this lock is not even read, let alone redacted (GR-2: what is never read does not have to be blacked out). In onboarding, in the Approval Cockpit, in jico status, in the audit and in messages to the AI model it is called the same everywhere: “blocked” (German: „gesperrt“).

Human in the loop

A human decides on every change before it reaches Jira - JiCo's ground rule GR-1.

The AI model proposes, JiCo holds, you approve or reject in the Approval Cockpit. Without that approval nothing is written, and it only holds for the state you saw (GR-5).

GR-1 — No write access without approval

Every changing and every unknown tool is held until a human decides.

Unknown counts as writing (fail-closed) - a new Jira tool that JiCo does not know yet never passes through unchecked.

GR-2 — Redaction happens before the AI model

Personal data is replaced before a single line reaches the AI model - never afterwards.

What has been in an AI model's context cannot be taken back. Filtering the AI model's output afterwards would therefore protect nothing any more.

GR-3 — The mapping stays minimal and expires

The placeholder ↔ plain text mapping is as small as possible and expires with the mapping deadline.

For Jira entities (user, assignee, reporter) only the stable Jira ID, no name; for everything else AES-256 encrypted and bound to the assignment. The AI model only ever sees the placeholder.

GR-4 — Nothing bypasses the JiCo core

Every path from the AI client to Jira runs through the redaction filter and the approval gate - a direct access makes both useless.

That is why JiCo warns about a second, unprotected Jira access in the same AI client (jico check), and why the one-line terminal command for an approval points at JiCo, never at Jira directly.

GR-5 — An approval only holds for its state

If a ticket has changed since the analysis, an approval that was given is no longer executed.

The message „changed since the analysis“ is exactly that: JiCo reads the state again immediately before execution and stops on any deviation - even in a field the action does not touch. The action moves to the follow-up list with a reason.

Placeholder

What the AI model sees instead of a real name or value, for example «Person 1».

It is resolved the moment an approval is executed - locally, never inside the AI model context. A placeholder an assignment does not know (invented instead of read) aborts the execution.

Redaction balance

How many values of which type were redacted in a ticket - never the values themselves.

It appears in the audit trail and in the ticket replica list (Settings › Data care) as a total with a tooltip per type, for example „3 redacted“ with the detail „person: 2, IBAN: 1“ on hover.

Mapping deadline (TTL)

How long the placeholder ↔ plain text mapping is kept - 96 hours by default.

It expires earlier as soon as the last open proposal of an assignment has been decided. After that a placeholder can no longer be resolved - the assignment has to be repeated.

Proposal

A prepared but not yet executed change - waiting for approval.

It carries the command in plain professional language, the effect, the checked state of the ticket and the equivalent Jira call as proof. Only after approval is it executed deterministically.

Outbound ledger

A record of what actually went to an AI model - hash, placeholders, final check.

Unlike the audit trail (proposal/decision/execution), the outbound ledger records what the AI model actually saw - the basis for „which personal data has the AI model seen?“.

Audit trail

A complete, append-only record of proposal, decision and execution.

It never contains plain-text personal data, only the redaction balance (count per type). Linked as a hash chain - a changed line stands out.

Ticket replica

A local, redacted and encrypted copy of tickets that were read - not a second plain-text store.

Limited by count, storage and deadline (Settings › Data care shows the fill level). Jira remains the source of truth; the replica speeds up repeated reading and the knowledge search.

Follow-up list

Prepared actions that could not be executed - with a reason, ready to repeat.

It fills up mainly through GR-5 stops (ticket changed since the analysis) and expired mapping deadlines. Formerly «Nachzieh-Liste».

Egress guard

Blocks network connections that do not belong to loopback or the configured services.

Violations are blocked and evidenced in the audit - protection against a dependency quietly sending data somewhere.

Masked

A particularly sensitive value (social security number, IBAN, credit card) was replaced by an identifier.

Unlike a pseudonymised personal name, a mask is not resolvable by default - only types explicitly configured as resolvable can be recovered with a password in the terminal.

Demo mode

A demonstration with invented data - no access to a real Jira, no ticket links.

For trying things out before setup. An installation started with --honigtopf cannot switch to real operation without being set up again.

Redacted · pseudonymised · masked

Three levels of making personal data unreadable for the AI model - redacted is the umbrella term.

Redacted means replaced before the AI model sees it (GR-2). Pseudonymised is a placeholder such as «Person 1» that can be resolved locally again. Masked is a particularly sensitive value (social security number, IBAN, credit card) that is not resolvable by default.

Redaction filter

The first stage of the JiCo core: replaces personal data with placeholders before the AI model sees it (R2).

It works in both directions: on the way to the AI model it redacts, and when an approval is executed it resolves the resolvable placeholders locally again (masked values stay masked). Formerly «Schleuse» (gate) for R2.

Approval gate

The second stage of the JiCo core: holds every changing and every unknown tool until a human decides (R3).

Before execution it reads the state of the ticket again and only executes if it is unchanged since the analysis (GR-5). Formerly «Schleuse» (gate) for R3.

JiCo core

The part of the program that redacts, holds, talks to Jira and Confluence and writes the audit.

On a single machine it runs in the same process as the Approval Cockpit; in a team it runs as a worker without a cockpit on a node. Formerly «gateway» - that word now stands for the team gateway.

Team gateway

A team's one address: accepts MCP and sign-in and forwards every session to one worker.

At session start it picks a worker that reaches all required sources and passes all requests of that session to exactly that worker. Jira, redaction and audit stay in the worker's JiCo core. Formerly «Verteiler» (distributor).

Team configuration

A team's record signed by the portal: members and roles, workers, team gateway, settings.

A worker fetches it with the hourly licence call. Formerly «Team-Stand» (team state).

Revision

The state of a ticket at a given point in time - the basis on which an approval holds (GR-5).

If the revision has changed since the analysis, nothing is executed. Formerly the «Stand» of a ticket.

Finding

An observation by the AI about a ticket, with an assessment - it appears in the approval bundle.

A human sees the assessment there before deciding. Formerly «Befund».

Approval bundle

The grouped findings, open questions and prepared actions of an assignment - one unit to decide on.

Not to be confused with the installer package (package build). Formerly «Freigabe-Mappe» (approval folder).

Approver

The human who approves or rejects a proposal in the Approval Cockpit.

Their decision is in the audit trail; afterwards the approval only holds for the revision they saw. Formerly «Entscheider».

Proof

A verifiable record that something was checked or decided.

For example the equivalent Jira call in a proposal, or the sign-in proof signed by the portal for remote access. Formerly «Beleg» (evidence).

Remote access

Reaching JiCo while away - through a tunnel, only when explicitly switched on.

Off by default. Formerly «Fernzugriff» and «Relais» (the relay host is now called tunnel address).

Version and variant

Version: a state of a release, licence or text. Variant: a form such as light/dark or Jira/Confluence.

Formerly both «Fassung» (version).

Build artifact

The compiled program that comes out of the package build.

Formerly «Kompilat» (compilate).

Licence issuer

The drkv tool that signs licences - the key stays offline.

Formerly «Lizenzstelle» (licence office).

Assignment

A repeatable run - scheduled or started by hand - across several projects or filters.

The findings of an assignment are grouped and condensed into an approval bundle with open questions, prepared actions and a follow-up list.

Glossary (project glossary)

Jira vocabulary for the AI model context - something different from this glossary page.

Settings › Glossary collects synonyms, boundaries and query terms from Jira metadata (issue types, statuses, fields) so that the AI model phrases things consistently. It contains no ticket content and goes to every AI model as context. This page here explains JiCo itself - for people, not for the AI model.