Lesson objective

Place accountability for controlled technical data and company information with named people, and build a named-owner register that records what no tool, integrator or vendor can hold.

Plain-language explanation

Why this matters now

Earlier levels taught a person to stop before a controlled drawing reaches an AI tool. At company level the question changes: who in this company holds the authority to say what is controlled, and who answers when it goes wrong? If the honest answer is "whoever is uploading the file," the company has no export control function, whatever its training slides say.

Two federal regimes frame the question. Both run to the company and the people in it, not to a tool.

Law / rule (United States, federal; binds persons subject to the Export Administration Regulations): 15 CFR 734.13 defines export. Under 734.13(a)(1) it includes "An actual shipment or transmission out of the United States, including the sending or taking of an item out of the United States, in any manner." Under 734.13(a)(2) it includes "Releasing or otherwise transferring 'technology' or source code (but not object code) to a foreign person in the United States (a 'deemed export')." Under 734.13(b), "Any release in the United States of 'technology' or source code to a foreign person is a deemed export to the foreign person's most recent country of citizenship or permanent residency."

Three limits keep that definition honest:

  • The definition alone creates no licence requirement. Whether a licence is needed depends on the item's classification (its ECCN) and the destination on the Commerce Country Chart.
  • Object code is expressly outside the deemed-export definition. Do not generalise the rule to all software.
  • Who counts as a "foreign person" is defined elsewhere in the EAR, and this module does not set it out. The person holding export authority works from the regulation itself.

Law / rule (United States, federal; binds persons who manufacture, export or temporarily import defense articles or furnish defense services): 22 CFR 122.1(a) states that "Any person who engages in the United States in the business of manufacturing or exporting or temporarily importing defense articles, or furnishing defense services, is required to register with the Directorate of Defense Trade Controls." Registration is required of a manufacturer of defense articles even where it does not export. It is not an exporter-only duty.

The governance point is the one the profile of this programme calls the sharpest trap in manufacturing AI: export control follows the data, not the border. A file sent to a service, or a screen shared with a colleague, can raise an export question without anything leaving the building. Module 05 builds the screening control. This lesson places the authority.

A question to sit with

A process engineer wants to paste a customer's machining specification into an AI assistant to plan a fixture. Who in your company decides whether that specification is controlled technical data, and would the engineer know that person's name without asking around?

What goes wrong

Classification is left to the uploader. The person with the deadline decides whether a file is controlled. That person may be careful. They are not the person the company has authorised, and they are under time pressure.

Nobody holds export authority at all. In many small plants, export questions go to "the office" or to the customer. A customer's marking helps, but the company's own obligation is its own.

Registration is assumed to be an exporter's problem. A job shop that makes parts to a defense customer's drawings assumes that because it ships nothing abroad, the ITAR has nothing to say to it. Section 122.1(a) reaches manufacturing.

The exemptions are read loosely. Section 122.1(b) lists exemptions: officers and employees of the U.S. Government acting officially; persons whose pertinent business activity is confined to the production of unclassified technical data only; persons all of whose manufacturing and export activities are licensed under the Atomic Energy Act of 1954, as amended; and persons fabricating articles solely for experimental or scientific purposes, including research and development. A person exempt under the technical-data or experimental exemption may not receive an export licence or approval unless registered. None of these exemptions is a general small-shop exemption.

Company information has no owner. Process parameters, quoting models, customer pricing and employee records all leave through the same tools. No statute in this module names who owns that decision, so it falls to whoever is closest.

The practical answer

Name the export authority holder. This is a governance appointment. Record:

  1. Who holds authority to classify technical data and decide on releases, and who deputises.
  2. What that authority covers: classification requests, access to controlled folders, requests to use any outside service, including AI tools, and visitor and new-hire access to controlled areas.
  3. How questions reach that person: one route, known on every shift.
  4. What they record: every decision, with the file, the reasoning and the date.
  5. Whether the company must register under 22 CFR 122.1, decided by an officer with counsel and recorded, including which exemption is relied on, if any. Do not state or guess a fee; the Directorate sets fee tiers and changes them.

Keep company information in a separate row. Controlled technical data is governed by federal regulations. Company information such as process know-how, quoting logic, customer pricing and personnel files is governed by the company's own decisions and contracts, and by other laws Module 04 maps. Name an owner for it: usually the owner or an officer, with the quality manager for customer data and the office manager for personnel data.

Build the named-owner register. The register is the single page that answers "who is accountable here?" for every domain. The structure is an AI Coalition Network recommendation. Keep the four categories apart in the "authority" column: law; law arriving through a contract; voluntary standard; certification scheme.

Domain Authority and category Accountable person Deputy Cannot be held by
Worker safety General duty clause and OSHA standards (law) Named officer; EHS lead runs it Named, per shift Integrator, vendor, tool
Product release and conformity Quality system; customer contracts (contract) Person the quality system names Named AI drafting or inspection tool
Consumer product hazard reporting CPSA section 15(b) (law), consumer products only Named officer, with counsel Named Complaint summariser
Sealed engineering documents State engineering law (law, state by state) Licensed engineer where required Named Unlicensed person; tool
Controlled technical data EAR; ITAR where defense articles (law) Export authority holder Named Uploader; vendor setting
Defense contract requirements Clauses flowed down by the prime (law arriving through a contract) Named officer Named Prime; IT provider
Company information Company decision and contracts Owner or officer Named IT lead acting alone
The AI programme Company governance; voluntary frames such as NIST AI RMF 1.0 Programme owner Named Committee

Every row needs a name. Where one person holds three rows, the register says so, and a second person reviews that person's own decisions.

Write down what cannot be delegated. Add a short list to the register, taken from the duties in this module:

  • the employer's safety duty, and any decision that a machine is safe to approach or restart;
  • a quality signature: conformance, disposition, corrective action, first article;
  • the manufacturer's decision whether to inform the Commission, where section 15(b) applies;
  • a decision that a release of technical data is permitted;
  • the decision whether the company must register under the ITAR;
  • the approval of an AI tool for use with controlled or confidential data.

A vendor, integrator or tool can support each one. None can hold it.

Tie the register to the voluntary frame, and keep it voluntary. Best practice (NIST AI RMF 1.0, voluntary): GOVERN applies to all stages, and after instituting GOVERN outcomes "most users of the AI RMF would start with the MAP function." A named-owner register is a practical GOVERN outcome. It is not something NIST requires; the framework is voluntary and being revised.

Remember this

  • Export includes a transmission out of the United States in any manner, and a release of technology or source code to a foreign person inside it; object code is outside the deemed-export definition.
  • The definition creates no licence requirement by itself; that depends on classification and destination, decided by the person holding export authority.
  • ITAR registration reaches manufacturers of defense articles even if they never export; the exemptions are narrow.
  • Company information needs its own named owner.
  • The named-owner register gives every domain a name, a deputy and a list of what no tool, integrator or vendor can hold.

Manufacturing example

Ostara Medical Devices is a fictional 90-person contract manufacturer. It machines housings for a medical customer and, since last year, brackets for a defense prime to the prime's drawings. A new process engineer, Farid Nasser, is asked to plan a fixture for the defense bracket and wants to paste the prime's specification into the AI assistant the engineering team uses for medical work. He asks his supervisor, who says "the office handles export stuff." The office manager says the prime would have told them if anything was controlled. Nobody can say whether Ostara must register under the ITAR, because nobody has asked. President Hannah Lisle calls a meeting. She names the operations director, Carmen Ruiz, as export authority holder, with the quality manager as deputy, and writes down what the authority covers: classifying technical data, deciding releases, approving any outside service for controlled files and approving access to the controlled folder. With counsel, Hannah reviews whether Ostara, as a manufacturer of parts to the prime's drawings, must register under 22 CFR 122.1, and records the outcome and the reasoning. Carmen reviews the specification and its markings, and until classification is settled, the file stays out of every AI tool and in the controlled folder. The named-owner register goes up in the engineering office with eight rows. Two rows, company information and the AI programme, sit with Hannah; she asks the controller to review her own decisions each quarter. Farid plans the fixture by hand that week. His request, Carmen's decision and the date go into the decision record.

Responsible-use warning

Do not let the person with the deadline decide whether a file is controlled technical data, and do not treat a vendor's enterprise setting or a customer's silence as the answer. Export control follows the data: a release to a foreign person inside the United States can be a deemed export. Name the person who holds export authority, route every question to that person, record every decision, and have an officer decide with counsel whether the company must register under the ITAR.

Human-review requirement

The export authority holder, named by the company with a deputy, owns every decision on classifying technical data, releasing it and approving any outside service, including AI tools, for controlled files, and records each decision with its reasoning. An officer, with counsel, owns the decision whether the company must register under 22 CFR 122.1. A named owner or officer owns company information. The programme owner checks that the named-owner register has a name and deputy in every row and that nobody reviews only their own decisions.

Practical exercise

Use a fictional plant that makes commercial parts and parts to a defense prime's drawings.

  1. List every route by which technical data leaves the engineering office today: email, shared drives, customer portals, AI tools, screen sharing and printouts.
  2. Write who decides today whether a file is controlled. If the answer is "the person sending it," say so.
  3. Draft the appointment of an export authority holder: who, which deputy, what the authority covers and how questions reach them on every shift.
  4. Write the questions an officer should put to counsel about registration under 22 CFR 122.1, including which exemption, if any, might apply.
  5. Name an owner for company information, and list the kinds of information that row covers.
  6. Build the named-owner register with the eight rows from the lesson. Fill the authority column using the four categories.
  7. Mark every row held by the same person, and name who reviews that person's own decisions.
  8. Write the list of decisions that cannot be delegated to a tool, an integrator or a vendor.
  9. Write the one line you would put on the engineering office wall so a new engineer knows whom to ask, and the date by which the register will next be reviewed.

Knowledge check

  1. What is a deemed export under 15 CFR 734.13?

    Answer guidance: Releasing or otherwise transferring technology or source code, but not object code, to a foreign person in the United States. It is treated as an export to that person's most recent country of citizenship or permanent residency.

  2. Does the export definition by itself mean a licence is required?

    Answer guidance: No. The definition creates no licence requirement by itself. Whether a licence is needed depends on the item's ECCN and the destination on the Commerce Country Chart, judged by the person holding export authority.

  3. Is ITAR registration only a duty for exporters?

    Answer guidance: No. Under 22 CFR 122.1(a), any person in the business of manufacturing, exporting or temporarily importing defense articles, or furnishing defense services, must register, so a manufacturer must register even if it never exports.

  4. What does the named-owner register record for each domain?

    Answer guidance: The authority that applies and its category, the accountable person, a deputy, and who cannot hold the duty, such as a tool, integrator or vendor. It also marks rows held by one person and names who reviews that person's decisions.

Sources and further reading