Developers, Works Councils and Employment: Telemetry, Rights and Intellectual Property

All courses / AI Developer / Module 4 / Chapter 22

Learning objectives

After the lesson the participant can:

• Explain which representation rights a coding assistant reaches and at which trigger points they arise
• Draft a field-by-field telemetry description with purpose, grain and retention
• Apply the four rules that name people for stewardship without scoring them
• Design the outline of an agreement on developer tooling that follows the mandate and the delegation profile

Key concepts

Trigger points

Five moments at which duties to inform or negotiate arise: a licence or pilot, a vendor update, a telemetry switch-on, a mandate change and an evaluative use. A pilot with real developers on real work is use, whatever the label.

Telemetry description

A short, mechanical file that lists each field the tool collects with why it is collected, its grain (event, person or team), its retention and who may read it. It is part of the consultation file sent before anything is switched on.

Naming for stewardship, not for scoring

A record names a person for a change, not for a rate. Reports to managers are by team with a minimum group size of 5, person-level data is read only for the purpose it was collected for, and prompts are not retained unless the agreement says so.

An agreement that follows the mandate

Coding tools change monthly, so an agreement written about a product version is soon out of date. One written about classes of work, the mandate and the delegation profile survives, with a review that has an evidence date and triggers.

The employer's right in the program

Under Directive 2009/24/EC, Article 2(3), where a computer program is created by an employee in the execution of duties, the employer exercises the economic rights unless the contract provides otherwise. The developer's skills and know-how are not the employer's property.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Teaching plan

Discussion

1. A coding assistant is normally not a high-risk AI system, yet the same telemetry turned into an appraisal tool would change its position. Where exactly is that line in your tooling?
2. The chapter says the evidence that agreements improve outcomes is thin, and argues for them from mechanism. Do you find the mechanism convincing, and why?
3. What should an obligation to use an assistant, or an adoption target for a team, be treated as in your organisation?

Written exercise

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

1. For the trigger vendor update, in which an IDE update switches on completion by default, when is information due according to the chapter's table?

   1. Within 90 days of the update reaching developers' machines, when the first telemetry is read
   2. At the next annual review of the works agreement
   3. Only if the update also changes the licence price
   4. Before the update enters the managed image, with the default off until a decision
   Show the answer

   D. Before the update enters the managed image, with the default off until a decision
   The platform team holds the sequence by configuration: information is due before the update is accepted into the managed image, and the default is set off until the decision is taken.

2. What does the Dutch Works Councils Act give the works council for facilities that observe attendance, conduct or performance?

   1. A right to be informed after the facility is in use
   2. A right of consent under Article 27(1)(k) and (l)
   3. A right to nominate the supplier of the facility
   4. A right to read person-level telemetry on request
   Show the answer

   B. A right of consent under Article 27(1)(k) and (l)
   The table gives consent of the works council under WOR Article 27(1)(k) and (l). At Hansa Mutual this made the remedy a matter of obtaining consent for something already in use.

3. Which statement matches the chapter's first rule on naming for stewardship?

   1. A record names a person for a change, not for a rate
   2. A record names a team only, never an individual reviewer
   3. A record names the tool and omits every human name
   4. A record names the developer with the lowest acceptance rate
   Show the answer

   A. A record names a person for a change, not for a rate
   Stewardship needs names: the review record says who read a pull request. But it names a person for a change and never for a rate, and reports upward are by team.