Phase 1: you submit an application

What happens here

Your application goes through the same processing as any other incoming case: seal, working copy, extract, prove, decide, notify. This page attaches the deployment's own token on the server; the raw endpoint POST /ingest stays closed with a 403 for direct callers.

Every applicant on this page is invented. The names, dates of birth, insurance numbers and addresses were constructed for this demonstration and belong to nobody.

Choose a fictional applicant

Sabine Musterfrau

Employment-status determination under par. 7a SGB IV

Frau Musterfrau has been working since January as a freelance IT consultant for one larger client and wants to know whether that counts as self-employment. She never names the procedure - her submission carries no channel hint.

Expected outcome: With no channel hint, the procedure is derived from the CONTENT (a client and an activity named together) and the case goes to the clearing unit, 340. Par. 7a demands an overall appraisal rather than a checklist, which is why tier 1 is not enabled for this procedure at all and the case lands with a human in full.
Beate Schliebermann chosen

Employment-status determination under par. 7a SGB IV, complete

Frau Schliebermann has been working since March as a freelance technical writer for a single client and applies for a determination of her employment status. She names the procedure, and every answer is in the form.

Expected outcome: Complete and cleanly routed: the case goes to the clearing unit, 340. Because par. 7a demands an overall appraisal rather than a checklist, tier 1 is not enabled for this procedure at all - a complete file buys no automatic decision here. No request for information and no flag are produced; the case lands with a human in full.
Bernd Beispielmann

Employment-status determination with no start date

Herr Beispielmann fills in the form but leaves open since when he has been working for his client. Everything else is there.

Expected outcome: Routable but incomplete: tier 2 at the clearing unit, 340. A request for information is prepared that asks for exactly the missing answer - in the procedure configuration's own wording, not in a generated sentence.
Theo Musterkind

Employment-status determination with a start date far ahead

Herr Musterkind fills the form in completely and within every rule - and enters a start of the activity far in the future, even though he is applying for a determination after taking the activity up. Every single answer is permissible.

Expected outcome: The calendar bounds in the procedure configuration are absolute and wide; they deliberately do not catch "possible, but unusual". That is exactly the shadow scorer's job: it flags the case and names its reason in plain words. Because the scorer runs in log_only mode the flag MOVES nothing - the page shows which tier an armed scorer would have set, and that the decision was reached without it.

What you can try

Go ahead and change things. Each of the changes below makes the system do something DIFFERENT, and something real - and the next step shows you exactly what.

Delete the insurance number: Empty the text box. The completeness check reports a gap, the case lands on tier 2, and a request for information is prepared carrying exactly the sentence the procedure configuration provides for it.
Make the date of birth implausible: Pick 1 January 1902 in the calendar. The insurance number carries the date of birth in positions 3 to 8 and no longer matches it: the cross-field check fires, without anything being unsealed.
Push the start of the activity far into the future: Pick 1 January 2035. The calendar bounds in the procedure configuration deliberately do not catch that - it is the shadow scorer's job, and it flags the case and names its reason in plain words.
Empty the client: On the applications that carry a channel hint this opens a gap and prepares a request for information asking for exactly that detail. With Frau Musterfrau, whose procedure is derived from the content, the derivation loses one of its two supports - the client and the activity are read together there.
Empty the given name: The surname goes through on its own. Both boxes write to the same place in the submission; the page joins them before anything is sealed, and an empty box is left out rather than sent as a space.

Edit the form and submit

What Beate Schliebermann submitted

Every field already filled in here is required: empty one and hit submit, and your browser marks it red and sends nothing. The exceptions are the three fields the suggestions above the form ask you to delete - insurance number, client and given name - because otherwise this page would recommend something it blocks itself. That check runs in the browser and without JavaScript; the system's own completeness check comes afterwards and separately from it.

Surname will be sealed: Name This answer is missing. The application will not be sent without it.

Given name

Date of birth will be sealed: Date of birth Date format YYYY-MM-DD if your browser offers no date picker. This answer is missing. The application will not be sent without it.

Insurance number will be sealed: Insurance number

Street will be sealed: Address This answer is missing. The application will not be sent without it.

Number This answer is missing. The application will not be sent without it.

Postcode This answer is missing. The application will not be sent without it.

Town This answer is missing. The application will not be sent without it.

Client will be sealed: Organisation / client

Kind of application The options come from the procedure configuration; picking one fills the field exactly as typing would. This answer is missing. The application will not be sent without it.

Who is applying The options come from the procedure configuration; picking one fills the field exactly as typing would. This answer is missing. The application will not be sent without it.

Description of the activity The options come from the procedure configuration; picking one fills the field exactly as typing would. This answer is missing. The application will not be sent without it.

Start of the activity Date format YYYY-MM-DD if your browser offers no date picker. This answer is missing. The application will not be sent without it.

Enclosures (PDF, simulated)

Choose what the applicant encloses. The documents are prepared and synthetic; their names are the ones the German pension insurance really asks for these papers under. A ticked document becomes a real attachment on the submission: it is sealed, gets a text layer and goes through the same processing as the form. The next step shows you the working copy of each document.

C0031 - description of the contractual relationship C0031-beschreibung-des-auftragsverhaeltnisses.pdf The annex without which, in form V0027's own words, no determination of employment status can be made.

Individual contract and project description (copy) einzelvertrag-und-projektbeschreibung.pdf V0027, item 16 asks for all individual contracts, project descriptions and task descriptions.

Copies of invoices rechnungen-in-kopie.pdf Asked for twice (V0027 item 3.2 and C0031 item 3.1): without them the employment status cannot be decided.

There is deliberately no way to upload a file of your own here. An upload control on a public demo would be an ingest path around the redaction boundary, and that boundary is what this whole system is about. The documents above belong to the fictional applicant you picked and to nobody.

Phase 1: you submit an application

What happens here

Choose a fictional applicant

Sabine Musterfrau

Beate Schliebermann chosen

Bernd Beispielmann

Theo Musterkind

What you can try

Edit the form and submit