Phase 2: what happened to your application
Overview
Seven stages, in the order they ran. Every number and every sentence on this page comes from your case's journal or from a store the system keeps anyway. This page recomputes nothing: it cannot contradict what actually happened.
The working copy for this case is no longer held. This demo's scratch store keeps it for a short time and in memory only; everything else on this page comes from the journal and stays readable.
a) Arrival
Your application arrived and was given a case id; from here on every step can be read individually.
- Case
case-ar-0011-ohne-rentenbeginn- Channel
- Form (FIT-Connect)
- Received at
- 2026-08-18T17:07:53.564111+00:00
- Submitted as
- fictional applicant
- Journal events
- 10
b) Sealing
The machine never saw your name. What you entered was sealed at the boundary, before the working copy existed - and everything downstream computes on that copy alone.
- Values sealed
- 3
- Verification
- passed - a second, independent detector pass over the working copy found nothing
c) Extraction
Now the working copy is read - and every value found must be proven twice: the quote AND the character offsets, checked independently against the same text.
- Fields found
- geburtsdatum, versicherungsnummer, rentenart, auslandsbezug
- Discarded
- 1 - a DISCARDED proposal is a value whose span failed verification. It is not adopted, and it pushes the case towards tier 3.
| Field | Text part | Character range | Match mode |
|---|---|---|---|
| geburtsdatum | structured field | no text span | structured |
| versicherungsnummer | structured field | no text span | structured |
| rentenart | structured field | no text span | structured |
| auslandsbezug | structured field | no text span | structured |
d) Evidence
The proven values become the evidence: which procedure, what is missing, who is responsible. All of it is justified in readable form - and none of it is a decision yet.
- Procedure
- altersrente (derived from: hint; channel hint: altersrente)
- Completeness
- incomplete
- Clear-cut
- yes
What is missing, and what you will be asked
| Field | Status | Wording in the letter |
|---|---|---|
rentenbeginn |
missing | Bitte geben Sie an, ab wann Sie Ihre Rente beziehen moechten. |
Routing
Routed to: Referat_312_Renten. That is the decision plane's answer and the only one that actually put the case into a queue. The table below shows ALL the evidence, including the proposals that lost.
| Unit | Source | Rule | Confidence |
|---|---|---|---|
| Referat_312_Renten routed | rule | rule_altersrente_verfahren, rule_altersrente_hint | 1.000 |
e) Decision
The decision plane reads only what has been proven and evaluates a versioned table row by row. It decides nothing about you: it decides how closely a human has to look.
- Result
- Tier 2 - routable, incomplete
- Routed unit
- Referat_312_Renten
| Kind | Row | Reason |
|---|---|---|
| failed | tier1_clear_and_complete |
Zeile tier1_clear_and_complete (Tier 1) nicht erfuellt: completeness.verdict eq 'complete' (ist: 'incomplete'); extraction.discarded_count eq 0 (ist: 1) |
| qualified | tier2_routable_incomplete |
Zeile tier2_routable_incomplete (Tier 2) erfuellt: routing.rule_hit eq True (ist: True); routing.confidence ge 0.9 (ist: 1.0); completeness.verdict eq 'incomplete' (ist: 'incomplete') |
Anomaly check
- Score
- 0.109
- Flagged
- no
- Mode
- log_only
No feature reason was recorded.
f) Message
What you would have received after this submission. These messages are produced automatically from the journal and pass no human review - which is exactly why neither this page nor the inbox has any control with which somebody could trigger, edit or re-send one.
| Template | Subject | Delivered |
|---|---|---|
eingangsbestaetigung_v1 |
Eingangsbestaetigung zu Ihrem Anliegen | 2026-08-18T17:07:53.564111+00:00 |
zuordnung_v1 |
Zwischenstand zu Ihrem Anliegen | 2026-08-18T17:07:53.564111+00:00 |
Read it in the inbox: Inbox (read-only) / this case alone, as JSON.
g) Queue
Your case is now in the Referat 312 - Altersrenten queue, waiting for a human. In the next step, you are that human.
The queue is ordered by age, oldest case first. Your case is marked there so that you can find it - the marker is display only and does not change the order.
There you can confirm, re-route or escalate. Each of those actions appends a new journal event; none edits an old one. After that, the loop closes in the inbox for this case.