Skip to content
Interface language: English
Imperium / Signal

Code, access and confidentiality: what should you receive after a project involving AI agents?

What should remain after a website or AI automation project: code, agreements, licences, accounts, documentation, deployment instructions and confirmation that access has ended.

Article language: English

Sheets tied with a dark ribbon and a seal lie on a stone surface beside a pen.
In this article

The project works, but the contractor holds the repository, a former collaborator remembers the hosting login, and the setup instructions amount to “it's simple”. That handover leaves the company with more hope than control. After work involving AI agents, check the code, accounts, documentation, origins of materials and what happens to the data. Then ask someone to run a specific version from a clean copy. A working screen is the beginning of the evidence, not the complete set of keys to the project.

Plan acceptance before the project starts. Include code, documentation and responsibility for the outcome in the order. In the agreement, specify exactly what you receive, when, in what form and which actions confirm the handover. A working website is an important part of acceptance, but the means of maintaining it remain to be checked.

What exactly should be handed over?

Prepare a list: source code, project files, content, images, configuration, documentation and a record of important decisions. For an automation, add workflow definitions, integrations and the monitoring method. Mark what was supplied by the client, contractor or an external provider.

Agree on the form of handover. The repository - the place where code and its change history are stored - should be accessible through the account agreed for the project, with appropriate roles and a way to make a copy. Design files need the formats specified in scope. Documentation should identify its current version and the application version it describes.

Check whether the list contains what is needed for future development. An image on the site may have a source file, several sizes and licence conditions. A copy of the output directory alone does not explain how to reproduce the whole process.

How do you establish rights to code and other materials?

The agreement should name how each component may be used and the rights required. Distinguish code created for the project from external libraries, fonts, photographs and other components. Their terms may require separate checks and attribution.

GitHub's documentation on repository licensing explains that a licence sets out what others may do with code. Publishing a repository does not settle every condition of use. At handover, request a list of significant components, their sources and licences.

If the project contains AI-generated material, record the tool used, the terms applicable to that product and the scope of checks performed on the result. Do not replace this with a general statement that “everything is yours”. Contract language and legal assessment should reflect the actual components and their intended use.

Who should control the domain, hosting and integrations?

The domain, hosting account, repository and external services should each have a named organisational owner. Establish which accounts belong to the company, who pays for each service and who can recover access. Record what happens if the person leading the project leaves.

Grant roles that match the work. Full administrator access should not be the only way to hand a project over. Check technical accounts, API keys and agent integrations too. An API is an interface through which programs perform actions in other services; its key may allow access without an ordinary login.

At the end, remove or restrict access needed only during delivery. Confirm the changes in the relevant systems. A list of people in one panel will not show every token, connection and account used in other tools.

What documentation does the next person working on the code need?

The documentation should enable someone to prepare an environment, build the project, run checks and deploy it. Give the required tools, commands and configuration variable names. Keep secrets in the agreed secure location; the description should explain their purpose without revealing their values.

A useful handover package includes:

  • Instructions for starting from a clean repository copy.
  • The project structure and its main connections.
  • External services and responsibility for their fees.
  • How to publish, roll back a version and make a backup.
  • Known limitations and items outside scope.
  • Evidence of checks performed and how to report an error. If an assistant prepared or ran tests, examine the command, assertions and reported result (in Polish) so “tests passed” corresponds to the behaviour actually checked.

Ask someone who did not prepare the instructions to follow them in the agreed environment. Record missing steps. The exercise shows whether knowledge was actually transferred or still depends on the author's presence.

How do you check confidentiality after agents have worked?

Review the tools and storage locations used. Material may appear in a repository, model conversations, logs, a task system and working directories. For each location establish the type of data, retention rules and how access can be limited or ended.

Confidentiality arrangements should also cover connected services and participating people. If material requires a particular processing method, record it before sending the first file. Confirm technically that a proposed solution can be used for the specific scope.

In the final report distinguish a declaration that data was deleted from actions confirmed in systems you can access. Record limits arising from provider terms or your access. A precise description is more useful than a promise covering places nobody checked.

What if a key or password is found in the code?

Removing the value from the current file does not resolve the whole situation. It may remain in repository history or copies. GitHub recommends first revoking or rotating an exposed secret. Further steps depend on the data and where it was exposed. See the official instructions for removing sensitive data from a repository.

Aeneia conceptual photography

Before acceptance, inspect history and configuration with suitable tools. Record the result and scope of the check. Do not put real secrets in the handover record, a presentation or an issue. Evidence should be assessable without creating another copy of the confidential value.

How do you accept one specific project version?

Tie the handover record to a code version identifier and publication date. Note where the source copy, documentation and materials list are kept. This makes it clear what the tests and comments refer to. Otherwise you may approve the site in a browser but receive instructions for an earlier state.

A working example: during acceptance, the form is corrected and a font is replaced. The contractor updates the version, identifies the change and repeats the test of that path. The person accepting checks the result at the correct address and confirms the corresponding code. They do not sign a general statement that all future versions will behave identically.

Add website acceptance scenarios and a project decision register to the record. The first describes behaviour; the second explains important choices. Keep known limitations too. An organised list of open matters distinguishes an agreed next stage from something discovered missing only after handover. For preparation, see the guide to preparing website acceptance scenarios (in Polish) and the guide to preparing a project decision register (in Polish).

How do you check startup from a clean copy?

The receiving person downloads the agreed version into a prepared environment and follows the instructions step by step. They use accounts and test data approved for the exercise. They record each step requiring clarification: a missing tool version, a setting name, an external service or an action previously performed only on the author's computer.

Check preparation of content and generated files. If the project creates metadata, images or a publication index during the build, instructions should cover that stage. A ready output directory is not enough to assess whether the next person can add an article and rebuild the site from source. Include such an exercise using working material.

For an existing site, add an address migration plan (in Polish). Code handover should preserve knowledge of the domain, redirects and important old links. Separately check whether a version can be rolled back in the agreed environment without disrupting the current site during the exercise.

How do you record the origin of images, fonts and other components?

Create an inventory with the name, source, version, licence or terms document and place of use. Mark who supplied the material and whether future work needs an account or paid access. Handover records should cover these dependencies before a change of provider becomes necessary.

For images, distinguish the source file, publication variants and provenance description. The brand photography plan (in Polish) helps preserve the image's purpose and cropping limits too. For fonts, record the scope of use stated in the documents you hold. Do not infer rights merely because a file is present in the repository.

We checked GitHub's licensing and exposed-secret documentation on 27 October 2026. Establishing rights for particular components requires their documents and an appropriate assessment of the agreement. This article describes how to prepare a handover; it does not replace legal analysis or guarantee the status of every AI-generated result.

How do you confirm access has ended without stopping the service?

First assign owners to accounts and check that the company can perform agreed activities without the contractor's access. Only then restrict temporary roles, connections and keys in the agreed order. Confirm the result in each relevant system. Changing a repository role does not replace a review of hosting and other services.

An AI data-flow register helps locate integrations and remaining copies of material. Compare it with the rules for responsible agent workflows (in Polish). For technical accounts, record the process they serve and who takes over responding to errors. This matters especially when automation continues to run after the project ends. For preparation, see the guide to preparing an AI data-flow register (in Polish).

Proof of completion should name the action, date and scope checked without exposing a password or token value. If some data cannot be inspected or removed independently, record the limitation and the provider confirmation available. The person signing acceptance needs to know what was done and what supports that conclusion.

Complement technical acceptance with a handover between teams (in Polish). Files, decision history and open limitations must reach the people taking over. Repository access lets them read code, but does not itself explain every reason for its present form.

How do you close a project without depending on one person?

Approve a record listing materials, accounts, permissions, tests and open matters. Name the people who confirmed handover and took over ongoing care. Agree what support remains after acceptance and how further work is requested.

Check whether the person taking over can actually use the materials. Dependence on a sole expert (in Polish) can persist despite a complete file list if ordinary tasks still require that person's memory and presence.

Include these points in the website brief (in Polish) and connect them to rules for AI agent work (in Polish). If company documentation needs organising too, read about knowledge architecture (in Polish). We discuss code and its acceptance through Aeneia Design; reviewing data flows and access relates to Aeneia Audit.

Aeneia Design: Prepare the website scope and the terms for handing it over for ongoing care. Discuss the materials and how the finished version will be confirmed within the agreed scope. Discuss the website scope and handover.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear